PMR 04710, 379, 000

--------------------------------------------------------------------------------
Category: PMR
Status: CL1L1
Create date: 2006-08-29
Last modified: 2006-08-30
Rating: not yet rated
Harmful: No
--------------------------------------------------------------------------------
IBM Confidential
RETAIN view | Organized view
PMR 04710, 379, 000
--------------------------------------------------------------------------------
use TSM driver and TSM device name for HP tape drives
SRID: USR3S7DC3JG Stat: CL1L1 PMR: 04710,379,000 Entitle: CCMS

Rqst: SOFTWARE SubRqst: SOFTWARE DEFECT SUPPORT
Queu: ADSM33 Ctr: 19L S2 P2 __ Con: Stephen Turmo Turmo ________
Comp: 5698ISMSV __ Rel: 52W ConPh: __________________ SC: 75
RtID: ___________ 000 Lvl: 1 GenPh: 612-204-6403 ______ Cat: WEB
PID#: 5698ISX VRM: 520 NxtQ: TSM __ NxtCtr: 19L PA: _____
Cust: 3015155 Federal Reserve Bank of CPU: ___ ______ CUS SP: Y
Cmts: use TSM driver and TSM device name for HP tape drives Ar: 05
_______________________________________________________________
Ent: __:__/__ _____ Dly: __ : __ / __ APAR: ______ BU: O06/08/29 12:07
Dsp: __:__/__ _____ T/D: ECT: ________ Ter: A06/08/30 12:29
Req: __:__/__ _____ ESN: ____________ Sysdown: Surv: _ FUP/MM/DD
Own: BARKER, GEORGE H. ____ OwnID: O500852 SWBO/Cty: S _____
Res: BARKER, GEORGE H. ____ ResID: R500852
EMail: Stephen.Turmo@mpls.frb.org
Service Options: __ __ __ __ __ __ __ CritSit: _____________

KW1: ETR ______________ KW2: ________ KW3: ______________
+BARKER, GEORGE H. -FORMAT 1529-L19L/-------P2S2-06/08/30-11:28--FA
IBM Rep Name: George B
(Problem Owner)
Regarding: use TSM driver and TSM device name for HP tape drives
(Problem Description, to be read to the customer)
If there is a marketing opportunity, you can submit the lead at website:
http://rtsweb1.raleigh.ibm.com/ServiceOffering/
Questions to ask Client: We want you to be VERY SATISFIED with
the support which we have provided...
-Have I answered your questions to your satisfaction? y (Y/N)
-Is there anything else I can do for you on this problem? n (Y/N)
-Do you have any other issues with the product or our service
that I can help you with or can get someone to help you with? n (Y/N)
-May I close this call? Offer follow-up if appropriate. y (Y/N)
- THANK YOU FOR USING IBM!! y (Y/N)
+TY2K 010 -5698ISMSV -L19L/TSM -P2S2-06/08/29-10:07--CE
*** T1S2R3V4 Userid: 3015155
*** Electronic creation by customer via ESR Tool
*** Please contact customer by email.
*** Email Address: Stephen.Turmo@mpls.frb.org
*** Alt. Email Address:
*** Pager Number:
.
Problem Details
.
Product or Service: IBM Tivoli Storage Manager Extended Edition
Component ID: 5698ISMSV
.
Short description
ESR: Attempting to install TSM 5.3.3 on an HP Server with a MSL4048
Tape Library. When 'Unknown Medium Changer' is driver for library, HP
Tape Tools work, but TSM does not, when IBM Device Driver loaded, it
cannot communicate properly with the library or drives.
.
Severity explanation
.
Recent changes to the system
New system.
.
Corrective actions already taken
Tried different TSM version.
.
Values in input variables when problem occurred
.
Operating System: Windows
.
Other relevant information
Windows 2003 SP1, HP Proliant server. MSL 4048 tape library with 3 LTO-
2 drives.
.
+BARKER, GEORGE H. -5698ISMSV -L19L/TSM -P2S2-06/08/29-11:27--CT
+BARKER, GEORGE H. -5698ISMSV -L19L/-------P2S2-06/08/29-11:34--AL
+BARKER, GEORGE H. -5698ISMSV -L19L/-------P2S2-06/08/29-11:34--AT
Environment.:
Server..: Win2003, TSM 5.3.3.0
Client..:
Library.: HP MSL 4048
Customer Rep: Stephen Turmo
Problem.....: Installing TSM device driver
Action Taken: Customer's problem statement:
Attempting to install TSM 5.3.3 on an HP Server(HW -OS is win2003) with
a MSL4048
----------------------------------------------------------------------
Sent email to customer:
Hi Stephen.
The HP MSL 4048 library is supported with TSM 5.3.3. See the following
instructions from the TSM Administrator's Guide for installing the TSM
device driver.
Controlling Devices on Windows Server 2003
On the Windows Server 2003 system, devices are automatically controlled
by the default Windows device driver, even if you install the IBM Tivoli
Storage Manager driver (TSMSCSI). If you are running IBM Tivoli Storage
Manager on Windows Server 2003, you must manually update the controlling
driver for each device that you want controlled by the TSMSCSI device
driver.
Perform the following procedures from the Device Manager Console:
1. Right click on the device and select Properties. Select the driver
tab and Driver File Details. This will allow you to see the driver that
is currently controlling your device.
2. You will need to configure the device to be used by tsmscsi.sys by
right clicking on the device and selecting Update Driver or by selecting
Action and then Update Driver. The Hardware Update Wizard will appear.
3. Select Install from a list or specific location (Advanced).
4. Click Next.
5. Select Don?t search. I will choose the driver to install.
6. Click Next.
7. Select the IBM Tivoli Storage Manager device driver to control the
device.
8. Click Next.
9. From the Hardware Installation panel, click Continue Anyway.
10. Click Finish.
11. Verify that the device has been configured correctly for tsmscsi:
a. Right click on the device and select Properties.
b. Select the driver tab and driver details.
Action Plan.: Follow-up no later than 2006/
Test Case...:
+BARKER, GEORGE H. -FORMAT 1586-L19L/-------P2S2-06/08/29-11:34--FI
The following information is required to perform entitlement:
Operating System: Windows Ver: 2003 Rel:
Product Name: TSM Server Ver: 5 Rel: 3
Product Component ID: 5698ISMSV
If Product is bundled, with which product?: TSM
Machine: Serial#:
Does customer require offshift support? Y N x N/A
When complete, send call to Queue: close Location:
Following fields for Z/OS VM, or VSE ONLY: Entitle for Voice Q and A
(TSR will entitle as SL/PA, OR Registration Discrepancy)
Entitle for Electronic Q and A
(TSR will entitle as SL/PA, OR if XCL flag, PMR w/NOT be CCMS entitled)
Entitle for EOS Product
(TSR will entitle against extended support contract, OR Reg Discrepancy)
+BARKER, GEORGE H. -5698ISMSV -L12G/RENT -P2S2-06/08/29-11:34-SCG
+BARKER, GEORGE H. -5698ISMSV -L12G/RENT -P2S2-06/08/29-11:34-SAT
+BARKER, GEORGE H. -5698ISMSV -L19L/TSM -P2S2-06/08/29-11:34--CR
+BARKER, GEORGE H. -5698ISMSV -L19L/ADSM33-P2S2-06/08/29-11:34--AT
S5> SERVICE GIVEN= 99 SG/99/
+SERVER, CCMS -5698ISMSV -L12M/-------P2S2-06/08/29-11:35--AL
+MALONE, ESSIE -5698ISMSV -L19L/-------P2S2-06/08/29-11:35--AL
+MALONE, ESSIE -5698ISMSV -L19L/-------P2S2-06/08/29-11:36--AT
*** Format Insert 1021 Data for RENT ***
RETAIN Category Field(PS/AIX only):PAX - Passport Advantage 24x7
Entitlement Request: Customer entitled to voice supt
If not entitled: N/A
DPL Checked N/A
Additional Comments:
em0829rnt
****** End of SMC REQUEST COMPLETION FORM Format Insert ******
-EMEA FTP SERVER BDCROB-5698ISMSV -L181/-------P2S2-06/08/29-13:48--AT
ECuRep Mail Gateway - mail from support (barkerg@us.ibm.com)
/ecurep/pmr/0/4/04710,379,000/mail20060829-214722_George_Barker
+BARKER, GEORGE H. -5698ISMSV -L19L/ADSM33-P2S2-06/08/29-14:04--CR
Customer Contact:
Action Taken: Received email from customer:
George,
The steps below had already been done and the Library is using the
tsmscsi driver. Do I also have the tsmscsi driver for each tape drive.
Here is the Device Manager output:
<screen print sent to emea>
As you can see, the library has a Device Name, but the tape drives are
not reporting the Device Name as I would expect. I have added the
library and drives to the TSM server, but they keep coming up with
GENERICTAPE and I would like to see them as LTO.
<screen print sent tot emea>
When I try to check in tapes from the mail slot, I get a library I/O
error, but I can move tapes from the mail slot into internal slots using
the front panel.
We currently daisy-chain all three drives, but will be ordering another
dual channel scsi card so each drive will be on it's own channel so that
may help.
Stephen
-----------------------------------------------------------------------
Relied to customer:
Hi Stephen,
The library and drives should all be using the TSM device driver. If TSM
driver is being used by the library and drives are all the PATHS online?
Send me the following output from TSM server cmdline:
1. Q LIBR
2. Q PATH F=D
3. Q DRIVE F=D
4. Activity log showing the CHECKIN command and all messages for the
next 5 minutes. Use command:
Q ACT BEGINTIME=<hh:mm> ENDTIME=<hh:mm>
Action Plan: Follow-up no later than 2006/08/31
Customer Contact: Stephen
George,
I'll see if I can send you the output tomorrow, running out of time
today. BTW, I cannot get the tape drives to accept the IBM driver.
Windows 2003 constantly redetects them and loads it's own HP LTO driver
and cannot find the IBM driver. Is there an IBM driver for HP LTO
drives that I should be using?
Stephen
-------------------------------------------------------------------
Replied to customer:
Hi Stephen,
Make sure that the Windows RSM (Removable Storage) service is not
running. If RSM is running it will keep loading the Windows drivers.
The TSM device driver should be used with the HP MSL 4048.
George,
The Windows Removable Storage service is disable and not started. I
checked another TSM server with HP LTO drives and they are using the
tsmscsi.sys driver file. I did not set them up so I am confused on how
they managed to do this.
Here is the output from the commands:
Stephen
-----------------------------------------------------------------------
Hi Stephen,
The drive paths were configured with the Windows device names instead of
the TSM device names. The device names needed are the ones that show up
in the console under 'TSM Name'.
First delete the existing drive path definitions:
DEL PATH I1RMGT01_SERVER1 DRIVE1 SRCT=SERVER DESTT=DR LIBR=LIBRARY
Then define the drive paths with the correct TSM driver device names:
DEF PATH I1RMGT01_SERVER1 DRIVE1 SRCT=SERV DESTT=DR LIBR=LIBRARY
DEVI=mt4.0.0.3 AUTODETECT=YES
George,
Thanks! I had that configured in a script before and just changed it
to the Windows device names instead of the TSM device names. On the
other servers with HP LTO drives, the Windows device names have the
format mtn.n.n.n. On this new server they show up as \\.\Tapen. I
think that is because it's using the hplto.sys driver vs. the
tsmscsi.sys driver. I deleted path and drives and recreated them and
they still show generictape.
Stephen
+BARKER, GEORGE H. -5698ISMSV -L19L/ADSM33-P2S2-06/08/30-11:29--CC
George,
I finally was able to get the drives to use the tsmscsi.sys driver! I
was a bit confused because of the name given by the driver, but they are
now all using it. The Windows name now starts with mtn.n.n.n in the
TSM device and I ran a check-in tape and it worked! I think you can now
close this PMR and thank you very much for all your help!
Stephen
Action Plan: Close
Customer Information
Customer Number: 3015155 Customer Name: Federal Reserve Bank of
Contact: Stephen Turmo Turmo
Email Address: Stephen.Turmo@mpls.frb.org
Phone 1: 612-204-6403 Phone 2:
Country: 000 - null
Call Status Information
Severity: 2 Priority: 2
Status: CL1L1
Category: WEB
Caller Type: CUS
Created Date: O06/08/29 12:07
Last Altered Date: A06/08/30 12:29
Product Information
Product: 5698ISMSV
Release: 52W
APAR:
CPU Type:
CPU Serial:
Call Routing Information
Queue: ADSM33 Next Queue: TSM
Center: 19L Next Center: 19L
External Systems PMR Number:
Call Information
Comments: use TSM driver and TSM device name for HP tape drives
Has ScratchPad: Y
Keyword 1: ETR
Keyword 2:
Keyword 3:
Owner: BARKER, GEORGE H.
Resolver: BARKER, GEORGE H.
Critical Situation Description:
Type: Software
PMR Text
+TY2K 010 -5698ISMSV -L19L/TSM -P2S2-06/08/29-10:07--CE
*** T1S2R3V4 Userid: 3015155
*** Electronic creation by customer via ESR Tool
*** Please contact customer by email.
*** Email Address: Stephen.Turmo@mpls.frb.org
*** Alt. Email Address:
*** Pager Number:
.
Problem Details
.
Product or Service: IBM Tivoli Storage Manager Extended Edition
Component ID: 5698ISMSV
.
Short description
ESR: Attempting to install TSM 5.3.3 on an HP Server with a MSL4048
.
Severity explanation
.
Recent changes to the system
New system.
.
Corrective actions already taken
Tried different TSM version.
.
Values in input variables when problem occurred
.
Operating System: Windows
.
Other relevant information
Windows 2003 SP1, HP Proliant server. MSL 4048 tape library with 3 LTO-
2 drives.
.
+BARKER, GEORGE H. -5698ISMSV -L19L/TSM -P2S2-06/08/29-11:27--CT
+BARKER, GEORGE H. -5698ISMSV -L19L/-------P2S2-06/08/29-11:34--AT
Environment.:
Server..: Win2003, TSM 5.3.3.0
Client..:
Library.: HP MSL 4048
Customer Rep: Stephen Turmo
Problem.....: Installing TSM device driver
Action Taken: Customer's problem statement:
Attempting to install TSM 5.3.3 on an HP Server(HW -OS is win2003) with
a MSL4048
----------------------------------------------------------------------
Sent email to customer:
Hi Stephen.
The HP MSL 4048 library is supported with TSM 5.3.3. See the following
instructions from the TSM Administrator's Guide for installing the TSM
device driver.
Controlling Devices on Windows Server 2003
On the Windows Server 2003 system, devices are automatically controlled
by the default Windows device driver, even if you install the IBM Tivoli
Storage Manager driver (TSMSCSI). If you are running IBM Tivoli Storage
Manager on Windows Server 2003, you must manually update the controlling
driver for each device that you want controlled by the TSMSCSI device
driver.
Perform the following procedures from the Device Manager Console:
1. Right click on the device and select Properties. Select the driver
tab and Driver File Details. This will allow you to see the driver that
is currently controlling your device.
2. You will need to configure the device to be used by tsmscsi.sys by
right clicking on the device and selecting Update Driver or by selecting
Action and then Update Driver. The Hardware Update Wizard will appear.
3. Select Install from a list or specific location (Advanced).
4. Click Next.
5. Select Don?t search. I will choose the driver to install.
6. Click Next.
7. Select the IBM Tivoli Storage Manager device driver to control the
device.
8. Click Next.
9. From the Hardware Installation panel, click Continue Anyway.
10. Click Finish.
11. Verify that the device has been configured correctly for tsmscsi:
a. Right click on the device and select Properties.
b. Select the driver tab and driver details.
Action Plan.: Follow-up no later than 2006/
Test Case...:
+BARKER, GEORGE H. -FORMAT 1586-L19L/-------P2S2-06/08/29-11:34--FI
The following information is required to perform entitlement:
Operating System: Windows Ver: 2003 Rel:
Product Name: TSM Server Ver: 5 Rel: 3
Product Component ID: 5698ISMSV
If Product is bundled, with which product?: TSM
Machine: Serial#:
Does customer require offshift support? Y N x N/A
When complete, send call to Queue: close Location:
Following fields for Z/OS VM, or VSE ONLY: Entitle for Voice Q and A
(TSR will entitle as SL/PA, OR Registration Discrepancy)
Entitle for Electronic Q and A
(TSR will entitle as SL/PA, OR if XCL flag, PMR w/NOT be CCMS entitled)
Entitle for EOS Product
(TSR will entitle against extended support contract, OR Reg Discrepancy)
+BARKER, GEORGE H. -5698ISMSV -L12G/RENT -P2S2-06/08/29-11:34-SCG
+BARKER, GEORGE H. -5698ISMSV -L12G/RENT -P2S2-06/08/29-11:34-SAT
+BARKER, GEORGE H. -5698ISMSV -L19L/TSM -P2S2-06/08/29-11:34--CR
+BARKER, GEORGE H. -5698ISMSV -L19L/ADSM33-P2S2-06/08/29-11:34--AT
+SERVER, CCMS -5698ISMSV -L12M/-------P2S2-06/08/29-11:35--AL
+MALONE, ESSIE -5698ISMSV -L19L/-------P2S2-06/08/29-11:35--AL
+MALONE, ESSIE -5698ISMSV -L19L/-------P2S2-06/08/29-11:36--AT
*** Format Insert 1021 Data for RENT ***
RETAIN Category Field(PS/AIX only):PAX - Passport Advantage 24x7
Entitlement Request: Customer entitled to voice supt
If not entitled: N/A
DPL Checked N/A
Additional Comments:
em0829rnt
****** End of SMC REQUEST COMPLETION FORM Format Insert ******
Customer Contact:
George,
The steps below had already been done and the Library is using the
tsmscsi driver. Do I also have the tsmscsi driver for each tape drive.
Here is the Device Manager output:
As you can see, the library has a Device Name, but the tape drives are
not reporting the Device Name as I would expect. I have added the
library and drives to the TSM server, but they keep coming up with
GENERICTAPE and I would like to see them as LTO.
When I try to check in tapes from the mail slot, I get a library I/O
error, but I can move tapes from the mail slot into internal slots using
the front panel.
We currently daisy-chain all three drives, but will be ordering another
dual channel scsi card so each drive will be on it's own channel so that
may help.
Stephen
-----------------------------------------------------------------------
Relied to customer:
Hi Stephen,
The library and drives should all be using the TSM device driver. If TSM
driver is being used by the library and drives are all the PATHS online?
Send me the following output from TSM server cmdline:
1. Q LIBR
2. Q PATH F=D
3. Q DRIVE F=D
4. Activity log showing the CHECKIN command and all messages for the
next 5 minutes. Use command:
Q ACT BEGINTIME= ENDTIME=
George,
I'll see if I can send you the output tomorrow, running out of time
today. BTW, I cannot get the tape drives to accept the IBM driver.
Windows 2003 constantly redetects them and loads it's own HP LTO driver
and cannot find the IBM driver. Is there an IBM driver for HP LTO
drives that I should be using?
Stephen
-------------------------------------------------------------------
Hi Stephen,
Make sure that the Windows RSM (Removable Storage) service is not
running. If RSM is running it will keep loading the Windows drivers.
The TSM device driver should be used with the HP MSL 4048.
George,
The Windows Removable Storage service is disable and not started. I
checked another TSM server with HP LTO drives and they are using the
tsmscsi.sys driver file. I did not set them up so I am confused on how
they managed to do this.
Here is the output from the commands:
Stephen
-----------------------------------------------------------------------
Hi Stephen,
The drive paths were configured with the Windows device names instead of
the TSM device names. The device names needed are the ones that show up
in the console under 'TSM Name'.
First delete the existing drive path definitions:
Then define the drive paths with the correct TSM driver device names:
George,
Thanks! I had that configured in a script before and just changed it
to the Windows device names instead of the TSM device names. On the
other servers with HP LTO drives, the Windows device names have the
format mtn.n.n.n. On this new server they show up as \\.\Tapen. I
think that is because it's using the hplto.sys driver vs. the
tsmscsi.sys driver. I deleted path and drives and recreated them and
they still show generictape.
Stephen
+BARKER, GEORGE H. -5698ISMSV -L19L/ADSM33-P2S2-06/08/30-11:29--CC
George,
I finally was able to get the drives to use the tsmscsi.sys driver! I
was a bit confused because of the name given by the driver, but they are
now all using it. The Windows name now starts with mtn.n.n.n in the
TSM device and I ran a check-in tape and it worked! I think you can now
close this PMR and thank you very much for all your help!
Stephen
Action Plan: Close
--------------------------------------------------------------------------------
End of PMR 04710, 379, 000

PMR 04710, 379, 000

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PMR 04710, 379, 000

Uploaded by

Copyright:

Available Formats

--------------------------------------------------------------------------------

SRID: USR3S7DC3JG Stat: CL1L1 PMR: 04710,379,000 Entitle: CCMS

Service Options: CritSit: ___________

End of PMR 04710, 379, 000

You might also like