Re: Problems after 4.1 Upgrade and Resolutions
I posted a message last week, but it was under a different email address. The new microcode has been loaded and we have seen no errors since (we were seeing at least 2-3 errors a day prior to the fix). It is an engineering fix, microcode level E306. It was loaded last Thursday. At 12:27 PM 2/5/01 -0500, Kathleen M Hallahan wrote: Are the drives themselves showing errors? That's one of the weird things we've got...our CE has checked the drive logs and there are absolutely no errors to be found. I'm going to give our CE printed copies of all these emails so that he can pass this along to Tuscon, unless anyone has any objections. Diana, did you ever get that microcode? If you did, have you had the opportunity to see if it fixes the problem? Thanks all! Kathleen |+--- || "Short, Anne"| || anne.short@L| || MCO.COM | || | || 02/05/2001 | || 09:53 AM | || Please | || respond to | || "ADSM: Dist | || Stor Manager"| || | |+--- | | | | To: [EMAIL PROTECTED] | | cc: (bcc: Kathleen M Hallahan/ISS/HQ/FHLMC) | | Subject: Re: Problems after 4.1 Upgrade and Resolutions | | We also get many ANR8302 errors. We are W2K server with TSM 4.1.2 server (before 4.1.2, we were 4.1.0). Since this is a new server and never had anything other than 4.1.x on it, and we have many other problems with the tape drives, such as tapes getting stuck, we attributed these errors to bad drives. Though the drives have been replaced twice now and we are still getting these same errors. Maybe it's not the drives after all. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: Braich, Raminder [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 9:31 AM To: [EMAIL PROTECTED] Subject: Re: Problems after 4.1 Upgrade and Resolutions I am aslo getting ANR8301E ANR8302E op=write errors. This started happening after we upgraded to TSM 4.1. We are on WIN 2000 environment. Raminder -Original Message- From: Kathleen M Hallahan [SMTP:[EMAIL PROTECTED]] Sent: Friday, February 02, 2001 6:55 PM To: [EMAIL PROTECTED] Subject: Re: Problems after 4.1 Upgrade and Resolutions I haven't heard back yet as to whether the code is available, or even if our problem is definitely the same problem. Our CE mentioned her PMR number in our PMR, and he and I have both spoken to someone in Tuscon, so hopefully I'll have more data on that soon. What error codes are you getting, and what is your environment? Have you taken it up with IBM yet? I'd love to know if there really are others seeing the same problems besides just a couple of us. Kathleen "Braich, Raminder" [EMAIL PROTECTED] on 02/02/2001 11:17:04 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Kathleen M Hallahan/ISS/HQ/FHLMC) Subject Re: Problems after 4.1 Upgrade and Resolutions : Kathleen, I read your post on ADSM forum regarding the tape IO errors Diana Noble was having. I am also having the same errors. You mentioned they were working on some microcode and should be released soon. Did they ever release it, if so from where can I download it. Raminder
Re: Problems after 4.1 Upgrade and Resolutions
I am aslo getting ANR8301E ANR8302E op=write errors. This started happening after we upgraded to TSM 4.1. We are on WIN 2000 environment. Raminder -Original Message- From: Kathleen M Hallahan [SMTP:[EMAIL PROTECTED]] Sent: Friday, February 02, 2001 6:55 PM To: [EMAIL PROTECTED] Subject: Re: Problems after 4.1 Upgrade and Resolutions I haven't heard back yet as to whether the code is available, or even if our problem is definitely the same problem. Our CE mentioned her PMR number in our PMR, and he and I have both spoken to someone in Tuscon, so hopefully I'll have more data on that soon. What error codes are you getting, and what is your environment? Have you taken it up with IBM yet? I'd love to know if there really are others seeing the same problems besides just a couple of us. Kathleen "Braich, Raminder" [EMAIL PROTECTED] on 02/02/2001 11:17:04 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Kathleen M Hallahan/ISS/HQ/FHLMC) Subject Re: Problems after 4.1 Upgrade and Resolutions : Kathleen, I read your post on ADSM forum regarding the tape IO errors Diana Noble was having. I am also having the same errors. You mentioned they were working on some microcode and should be released soon. Did they ever release it, if so from where can I download it. Raminder
Re: Problems after 4.1 Upgrade and Resolutions
We also get many ANR8302 errors. We are W2K server with TSM 4.1.2 server (before 4.1.2, we were 4.1.0). Since this is a new server and never had anything other than 4.1.x on it, and we have many other problems with the tape drives, such as tapes getting stuck, we attributed these errors to bad drives. Though the drives have been replaced twice now and we are still getting these same errors. Maybe it's not the drives after all. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: Braich, Raminder [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 9:31 AM To: [EMAIL PROTECTED] Subject: Re: Problems after 4.1 Upgrade and Resolutions I am aslo getting ANR8301E ANR8302E op=write errors. This started happening after we upgraded to TSM 4.1. We are on WIN 2000 environment. Raminder -Original Message- From: Kathleen M Hallahan [SMTP:[EMAIL PROTECTED]] Sent: Friday, February 02, 2001 6:55 PM To: [EMAIL PROTECTED] Subject: Re: Problems after 4.1 Upgrade and Resolutions I haven't heard back yet as to whether the code is available, or even if our problem is definitely the same problem. Our CE mentioned her PMR number in our PMR, and he and I have both spoken to someone in Tuscon, so hopefully I'll have more data on that soon. What error codes are you getting, and what is your environment? Have you taken it up with IBM yet? I'd love to know if there really are others seeing the same problems besides just a couple of us. Kathleen "Braich, Raminder" [EMAIL PROTECTED] on 02/02/2001 11:17:04 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Kathleen M Hallahan/ISS/HQ/FHLMC) Subject Re: Problems after 4.1 Upgrade and Resolutions : Kathleen, I read your post on ADSM forum regarding the tape IO errors Diana Noble was having. I am also having the same errors. You mentioned they were working on some microcode and should be released soon. Did they ever release it, if so from where can I download it. Raminder
Re: Problems after 4.1 Upgrade and Resolutions
In our case the errors show up in activity log. The drive logs do not show any errors. I don't have any objection of you passing the emails to Tucson. Raminder Braich SAP/Oracle DBA The Davey Tree Expert Company Kent OH 44240 330-673-9515 Ext 270 -Original Message- From: Kathleen M Hallahan [SMTP:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 12:27 PM To: [EMAIL PROTECTED] Subject: Re: Problems after 4.1 Upgrade and Resolutions Are the drives themselves showing errors? That's one of the weird things we've got...our CE has checked the drive logs and there are absolutely no errors to be found. I'm going to give our CE printed copies of all these emails so that he can pass this along to Tuscon, unless anyone has any objections. Diana, did you ever get that microcode? If you did, have you had the opportunity to see if it fixes the problem? Thanks all! Kathleen |+--- || "Short, Anne"| || anne.short@L| || MCO.COM | || | || 02/05/2001 | || 09:53 AM | || Please | || respond to | || "ADSM: Dist | || Stor Manager"| || | |+--- - ---| | | | To: [EMAIL PROTECTED] | | cc: (bcc: Kathleen M Hallahan/ISS/HQ/FHLMC) | | Subject: Re: Problems after 4.1 Upgrade and Resolutions | - ---| We also get many ANR8302 errors. We are W2K server with TSM 4.1.2 server (before 4.1.2, we were 4.1.0). Since this is a new server and never had anything other than 4.1.x on it, and we have many other problems with the tape drives, such as tapes getting stuck, we attributed these errors to bad drives. Though the drives have been replaced twice now and we are still getting these same errors. Maybe it's not the drives after all. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: Braich, Raminder [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 9:31 AM To: [EMAIL PROTECTED] Subject: Re: Problems after 4.1 Upgrade and Resolutions I am aslo getting ANR8301E ANR8302E op=write errors. This started happening after we upgraded to TSM 4.1. We are on WIN 2000 environment. Raminder -Original Message- From: Kathleen M Hallahan [SMTP:[EMAIL PROTECTED]] Sent: Friday, February 02, 2001 6:55 PM To: [EMAIL PROTECTED] Subject: Re: Problems after 4.1 Upgrade and Resolutions I haven't heard back yet as to whether the code is available, or even if our problem is definitely the same problem. Our CE mentioned her PMR number in our PMR, and he and I have both spoken to someone in Tuscon, so hopefully I'll have more data on that soon. What error codes are you getting, and what is your environment? Have you taken it up with IBM yet? I'd love to know if there really are others seeing the same problems besides just a couple of us. Kathleen "Braich, Raminder" [EMAIL PROTECTED] on 02/02/2001 11:17:04 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Kathleen M Hallahan/ISS/HQ/FHLMC) Subject Re: Problems after 4.1 Upgrade and Resolutions : Kathleen, I read your post on ADSM forum regarding the tape IO errors Diana Noble was having. I am also having the same errors. You mentioned they were working on some microcode and should be released soon. Did they ever release it, if so from where can I download it. Raminder
Re: Problems after 4.1 Upgrade and Resolutions
Ditto on all counts. (Actually, I'm not sure I even have drive logs on the unit we use (EXB-440). And it's remote, so I can't easily check that out.) Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: Braich, Raminder [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 1:24 PM To: [EMAIL PROTECTED] Subject: Re: Problems after 4.1 Upgrade and Resolutions In our case the errors show up in activity log. The drive logs do not show any errors. I don't have any objection of you passing the emails to Tucson. Raminder Braich SAP/Oracle DBA The Davey Tree Expert Company Kent OH 44240 330-673-9515 Ext 270 -Original Message- From: Kathleen M Hallahan [SMTP:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 12:27 PM To: [EMAIL PROTECTED] Subject: Re: Problems after 4.1 Upgrade and Resolutions Are the drives themselves showing errors? That's one of the weird things we've got...our CE has checked the drive logs and there are absolutely no errors to be found. I'm going to give our CE printed copies of all these emails so that he can pass this along to Tuscon, unless anyone has any objections. Diana, did you ever get that microcode? If you did, have you had the opportunity to see if it fixes the problem? Thanks all! Kathleen |+--- || "Short, Anne"| || anne.short@L| || MCO.COM | || | || 02/05/2001 | || 09:53 AM | || Please | || respond to | || "ADSM: Dist | || Stor Manager"| || | |+--- - ---| | | | To: [EMAIL PROTECTED] | | cc: (bcc: Kathleen M Hallahan/ISS/HQ/FHLMC) | | Subject: Re: Problems after 4.1 Upgrade and Resolutions | - ---| We also get many ANR8302 errors. We are W2K server with TSM 4.1.2 server (before 4.1.2, we were 4.1.0). Since this is a new server and never had anything other than 4.1.x on it, and we have many other problems with the tape drives, such as tapes getting stuck, we attributed these errors to bad drives. Though the drives have been replaced twice now and we are still getting these same errors. Maybe it's not the drives after all. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: Braich, Raminder [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 9:31 AM To: [EMAIL PROTECTED] Subject: Re: Problems after 4.1 Upgrade and Resolutions I am aslo getting ANR8301E ANR8302E op=write errors. This started happening after we upgraded to TSM 4.1. We are on WIN 2000 environment. Raminder -Original Message- From: Kathleen M Hallahan [SMTP:[EMAIL PROTECTED]] Sent: Friday, February 02, 2001 6:55 PM To: [EMAIL PROTECTED] Subject: Re: Problems after 4.1 Upgrade and Resolutions I haven't heard back yet as to whether the code is available, or even if our problem is definitely the same problem. Our CE mentioned her PMR number in our PMR, and he and I have both spoken to someone in Tuscon, so hopefully I'll have more data on that soon. What error codes are you getting, and what is your environment? Have you taken it up with IBM yet? I'd love to know if there really are others seeing the same problems besides just a couple of us. Kathleen "Braich, Raminder" [EMAIL PROTECTED] on 02/02/2001 11:17:04 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Kathleen M Hallahan/ISS/HQ/FHLMC) Subject Re: Problems after 4.1 Upgrade and Resolutions : Kathleen, I read your post on ADSM forum regarding the tape IO errors Diana Noble was having. I am also having the same errors. You mentioned they were working on some microcode and should be released soon. Did they ever release it, if so from where can I download it. Raminder
Re: Problems after 4.1 Upgrade and Resolutions
Kathleen, I read your post on ADSM forum regarding the tape IO errors Diana Noble was having. I am also having the same errors. You mentioned they were working on some microcode and should be released soon. Did they ever release it, if so from where can I download it. Raminder
Re: Problems after 4.1 Upgrade and Resolutions
I haven't heard back yet as to whether the code is available, or even if our problem is definitely the same problem. Our CE mentioned her PMR number in our PMR, and he and I have both spoken to someone in Tuscon, so hopefully I'll have more data on that soon. What error codes are you getting, and what is your environment? Have you taken it up with IBM yet? I'd love to know if there really are others seeing the same problems besides just a couple of us. Kathleen "Braich, Raminder" [EMAIL PROTECTED] on 02/02/2001 11:17:04 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Kathleen M Hallahan/ISS/HQ/FHLMC) Subject Re: Problems after 4.1 Upgrade and Resolutions : Kathleen, I read your post on ADSM forum regarding the tape IO errors Diana Noble was having. I am also having the same errors. You mentioned they were working on some microcode and should be released soon. Did they ever release it, if so from where can I download it. Raminder
Problems after 4.1 Upgrade and Resolutions
I had posted some questions last month regarding problems we encountered after our upgrade to TSM 4.1 and thought I would pass along what we found. We are using AIX 4.3, 3590E's and a 3494. When issuing the dsmadmc command we received "ANS1033E An invalid TCP/IP host name was specified". Resolution was to edit /usr/tivoli/tsm/client/ba/bin/dsm.sys and add a line for TCPServeraddress which stated the tsm server name in full. This was apparently not necessary under 3.1. We could not label K tapes. We had problems with this under 3.1, but it turned out IBM needed to flick a switch on the drives. We upgraded the same day. We would receive "ANR8750E Volume is incompatible with specified device type". IBM had defined the volume range for the K tapes as "K extended" and should have been defined as just "K". We also started receiving IO errors on our 3590 tape drives. This still persists today, but a microcode fix for the problem is in test at IBM and is suppose to be released by the end of the month (Hopefully!). The error we are receiving is "ANR8302E I/O error on drive RMT1 (/dev/rmt1) (OP=WRITE, CC=0, KEY=0B, ASC=44, ASCQ=00".
Re: Problems after 4.1 Upgrade and Resolutions
Thanks Diana, Will be making the jump from 3.1 to 4.1 very soon, so any other Hints or Tips would be most valuable!!
Re: Problems after 4.1 Upgrade and Resolutions
Diane, What level of microcode are you currently running on your 3590 tape drives. We are running 3590E1A tape drives with a microcode level of D22E. We have been on this level of code for quite some time with no errors. Our 3590's are also house within a 3494. -Original Message- From: Diana Noble [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 30, 2001 8:15 AM To: [EMAIL PROTECTED] Subject: Problems after 4.1 Upgrade and Resolutions I had posted some questions last month regarding problems we encountered after our upgrade to TSM 4.1 and thought I would pass along what we found. We are using AIX 4.3, 3590E's and a 3494. When issuing the dsmadmc command we received "ANS1033E An invalid TCP/IP host name was specified". Resolution was to edit /usr/tivoli/tsm/client/ba/bin/dsm.sys and add a line for TCPServeraddress which stated the tsm server name in full. This was apparently not necessary under 3.1. We could not label K tapes. We had problems with this under 3.1, but it turned out IBM needed to flick a switch on the drives. We upgraded the same day. We would receive "ANR8750E Volume is incompatible with specified device type". IBM had defined the volume range for the K tapes as "K extended" and should have been defined as just "K". We also started receiving IO errors on our 3590 tape drives. This still persists today, but a microcode fix for the problem is in test at IBM and is suppose to be released by the end of the month (Hopefully!). The error we are receiving is "ANR8302E I/O error on drive RMT1 (/dev/rmt1) (OP=WRITE, CC=0, KEY=0B, ASC=44, ASCQ=00".
Re: Problems after 4.1 Upgrade and Resolutions
Are you running with K cartridges as well? We've been seeing these errors also, but only on the K cartridges. Kathleen "Michael, Monte" [EMAIL PROTECTED] on 01/30/2001 09:43:28 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Kathleen M Hallahan/ISS/HQ/FHLMC) Subject Re: Problems after 4.1 Upgrade and Resolutions : Diane, What level of microcode are you currently running on your 3590 tape drives. We are running 3590E1A tape drives with a microcode level of D22E. We have been on this level of code for quite some time with no errors. Our 3590's are also house within a 3494. -Original Message- From: Diana Noble [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 30, 2001 8:15 AM To: [EMAIL PROTECTED] Subject: Problems after 4.1 Upgrade and Resolutions I had posted some questions last month regarding problems we encountered after our upgrade to TSM 4.1 and thought I would pass along what we found. We are using AIX 4.3, 3590E's and a 3494. When issuing the dsmadmc command we received "ANS1033E An invalid TCP/IP host name was specified". Resolution was to edit /usr/tivoli/tsm/client/ba/bin/dsm.sys and add a line for TCPServeraddress which stated the tsm server name in full. This was apparently not necessary under 3.1. We could not label K tapes. We had problems with this under 3.1, but it turned out IBM needed to flick a switch on the drives. We upgraded the same day. We would receive "ANR8750E Volume is incompatible with specified device type". IBM had defined the volume range for the K tapes as "K extended" and should have been defined as just "K". We also started receiving IO errors on our 3590 tape drives. This still persists today, but a microcode fix for the problem is in test at IBM and is suppose to be released by the end of the month (Hopefully!). The error we are receiving is "ANR8302E I/O error on drive RMT1 (/dev/rmt1) (OP=WRITE, CC=0, KEY=0B, ASC=44, ASCQ=00".
Re: Problems after 4.1 Upgrade and Resolutions
We are running D25D. This level of microcode ran fine prior to going to TSM 4.1. We had never had an IO error before then. Now we receive the errors on both our tape drives. At 08:43 AM 1/30/01 -0600, you wrote: Diane, What level of microcode are you currently running on your 3590 tape drives. We are running 3590E1A tape drives with a microcode level of D22E. We have been on this level of code for quite some time with no errors. Our 3590's are also house within a 3494. -Original Message- From: Diana Noble [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 30, 2001 8:15 AM To: [EMAIL PROTECTED] Subject: Problems after 4.1 Upgrade and Resolutions I had posted some questions last month regarding problems we encountered after our upgrade to TSM 4.1 and thought I would pass along what we found. We are using AIX 4.3, 3590E's and a 3494. When issuing the dsmadmc command we received "ANS1033E An invalid TCP/IP host name was specified". Resolution was to edit /usr/tivoli/tsm/client/ba/bin/dsm.sys and add a line for TCPServeraddress which stated the tsm server name in full. This was apparently not necessary under 3.1. We could not label K tapes. We had problems with this under 3.1, but it turned out IBM needed to flick a switch on the drives. We upgraded the same day. We would receive "ANR8750E Volume is incompatible with specified device type". IBM had defined the volume range for the K tapes as "K extended" and should have been defined as just "K". We also started receiving IO errors on our 3590 tape drives. This still persists today, but a microcode fix for the problem is in test at IBM and is suppose to be released by the end of the month (Hopefully!). The error we are receiving is "ANR8302E I/O error on drive RMT1 (/dev/rmt1) (OP=WRITE, CC=0, KEY=0B, ASC=44, ASCQ=00".
Antwort: Re: Problems after 4.1 Upgrade and Resolutions
Are you using 4.1.0 or 4.1.2? Von: Diana Noble [EMAIL PROTECTED] Am: 30.01.2001 16:22 GMT Bitte antworten an "ADSM: Dist Stor Manager" [EMAIL PROTECTED] An: [EMAIL PROTECTED] Kopie: (Blindkopie: Matthew Muldoon/MAINSTOR/Niedernberg/mus/DE) Thema:Re: Problems after 4.1 Upgrade and Resolutions We are running D25D. This level of microcode ran fine prior to going to TSM 4.1. We had never had an IO error before then. Now we receive the errors on both our tape drives. At 08:43 AM 1/30/01 -0600, you wrote: Diane, What level of microcode are you currently running on your 3590 tape drives. We are running 3590E1A tape drives with a microcode level of D22E. We have been on this level of code for quite some time with no errors. Our 3590's are also house within a 3494. -Original Message- From: Diana Noble [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 30, 2001 8:15 AM To: [EMAIL PROTECTED] Subject: Problems after 4.1 Upgrade and Resolutions I had posted some questions last month regarding problems we encountered after our upgrade to TSM 4.1 and thought I would pass along what we found. We are using AIX 4.3, 3590E's and a 3494. When issuing the dsmadmc command we received "ANS1033E An invalid TCP/IP host name was specified". Resolution was to edit /usr/tivoli/tsm/client/ba/bin/dsm.sys and add a line for TCPServeraddress which stated the tsm server name in full. This was apparently not necessary under 3.1. We could not label K tapes. We had problems with this under 3.1, but it turned out IBM needed to flick a switch on the drives. We upgraded the same day. We would receive "ANR8750E Volume is incompatible with specified device type". IBM had defined the volume range for the K tapes as "K extended" and should have been defined as just "K". We also started receiving IO errors on our 3590 tape drives. This still persists today, but a microcode fix for the problem is in test at IBM and is suppose to be released by the end of the month (Hopefully!). The error we are receiving is "ANR8302E I/O error on drive RMT1 (/dev/rmt1) (OP=WRITE, CC=0, KEY=0B, ASC=44, ASCQ=00".
Re: Antwort: Re: Problems after 4.1 Upgrade and Resolutions
We are running 4.1.2. At 05:41 PM 1/30/01 +0100, you wrote: Are you using 4.1.0 or 4.1.2? Von: Diana Noble [EMAIL PROTECTED] Am: 30.01.2001 16:22 GMT Bitte antworten an "ADSM: Dist Stor Manager" [EMAIL PROTECTED] An: [EMAIL PROTECTED] Kopie: (Blindkopie: Matthew Muldoon/MAINSTOR/Niedernberg/mus/DE) Thema:Re: Problems after 4.1 Upgrade and Resolutions We are running D25D. This level of microcode ran fine prior to going to TSM 4.1. We had never had an IO error before then. Now we receive the errors on both our tape drives. At 08:43 AM 1/30/01 -0600, you wrote: Diane, What level of microcode are you currently running on your 3590 tape drives. We are running 3590E1A tape drives with a microcode level of D22E. We have been on this level of code for quite some time with no errors. Our 3590's are also house within a 3494. -Original Message- From: Diana Noble [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 30, 2001 8:15 AM To: [EMAIL PROTECTED] Subject: Problems after 4.1 Upgrade and Resolutions I had posted some questions last month regarding problems we encountered after our upgrade to TSM 4.1 and thought I would pass along what we found. We are using AIX 4.3, 3590E's and a 3494. When issuing the dsmadmc command we received "ANS1033E An invalid TCP/IP host name was specified". Resolution was to edit /usr/tivoli/tsm/client/ba/bin/dsm.sys and add a line for TCPServeraddress which stated the tsm server name in full. This was apparently not necessary under 3.1. We could not label K tapes. We had problems with this under 3.1, but it turned out IBM needed to flick a switch on the drives. We upgraded the same day. We would receive "ANR8750E Volume is incompatible with specified device type". IBM had defined the volume range for the K tapes as "K extended" and should have been defined as just "K". We also started receiving IO errors on our 3590 tape drives. This still persists today, but a microcode fix for the problem is in test at IBM and is suppose to be released by the end of the month (Hopefully!). The error we are receiving is "ANR8302E I/O error on drive RMT1 (/dev/rmt1) (OP=WRITE, CC=0, KEY=0B, ASC=44, ASCQ=00".
Antwort: Re: Antwort: Re: Problems after 4.1 Upgrade and Resolutions
With the latest Atape driver 5.4.4.0 ? Von: Diana Noble [EMAIL PROTECTED] Am: 30.01.2001 16:46 GMT Bitte antworten an "ADSM: Dist Stor Manager" [EMAIL PROTECTED] An: [EMAIL PROTECTED] Kopie: (Blindkopie: Matthew Muldoon/MAINSTOR/Niedernberg/mus/DE) Thema:Re: Antwort: Re: Problems after 4.1 Upgrade and Resolutions We are running 4.1.2. At 05:41 PM 1/30/01 +0100, you wrote: Are you using 4.1.0 or 4.1.2? Von: Diana Noble [EMAIL PROTECTED] Am: 30.01.2001 16:22 GMT Bitte antworten an "ADSM: Dist Stor Manager" [EMAIL PROTECTED] An: [EMAIL PROTECTED] Kopie: (Blindkopie: Matthew Muldoon/MAINSTOR/Niedernberg/mus/DE) Thema: Re: Problems after 4.1 Upgrade and Resolutions We are running D25D. This level of microcode ran fine prior to going to TSM 4.1. We had never had an IO error before then. Now we receive the errors on both our tape drives. At 08:43 AM 1/30/01 -0600, you wrote: Diane, What level of microcode are you currently running on your 3590 tape drives. We are running 3590E1A tape drives with a microcode level of D22E. We have been on this level of code for quite some time with no errors. Our 3590's are also house within a 3494. -Original Message- From: Diana Noble [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 30, 2001 8:15 AM To: [EMAIL PROTECTED] Subject: Problems after 4.1 Upgrade and Resolutions I had posted some questions last month regarding problems we encountered after our upgrade to TSM 4.1 and thought I would pass along what we found. We are using AIX 4.3, 3590E's and a 3494. When issuing the dsmadmc command we received "ANS1033E An invalid TCP/IP host name was specified". Resolution was to edit /usr/tivoli/tsm/client/ba/bin/dsm.sys and add a line for TCPServeraddress which stated the tsm server name in full. This was apparently not necessary under 3.1. We could not label K tapes. We had problems with this under 3.1, but it turned out IBM needed to flick a switch on the drives. We upgraded the same day. We would receive "ANR8750E Volume is incompatible with specified device type". IBM had defined the volume range for the K tapes as "K extended" and should have been defined as just "K". We also started receiving IO errors on our 3590 tape drives. This still persists today, but a microcode fix for the problem is in test at IBM and is suppose to be released by the end of the month (Hopefully!). The error we are receiving is "ANR8302E I/O error on drive RMT1 (/dev/rmt1) (OP=WRITE, CC=0, KEY=0B, ASC=44, ASCQ=00".
Re: Problems after 4.1 Upgrade and Resolutions
Kathleen - We are running J's and K's and the IO errors occur on both types of tapes. At 11:10 AM 1/30/01 -0500, you wrote: Are you running with K cartridges as well? We've been seeing these errors also, but only on the K cartridges. Kathleen "Michael, Monte" [EMAIL PROTECTED] on 01/30/2001 09:43:28 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Kathleen M Hallahan/ISS/HQ/FHLMC) Subject Re: Problems after 4.1 Upgrade and Resolutions : Diane, What level of microcode are you currently running on your 3590 tape drives. We are running 3590E1A tape drives with a microcode level of D22E. We have been on this level of code for quite some time with no errors. Our 3590's are also house within a 3494. -Original Message- From: Diana Noble [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 30, 2001 8:15 AM To: [EMAIL PROTECTED] Subject: Problems after 4.1 Upgrade and Resolutions I had posted some questions last month regarding problems we encountered after our upgrade to TSM 4.1 and thought I would pass along what we found. We are using AIX 4.3, 3590E's and a 3494. When issuing the dsmadmc command we received "ANS1033E An invalid TCP/IP host name was specified". Resolution was to edit /usr/tivoli/tsm/client/ba/bin/dsm.sys and add a line for TCPServeraddress which stated the tsm server name in full. This was apparently not necessary under 3.1. We could not label K tapes. We had problems with this under 3.1, but it turned out IBM needed to flick a switch on the drives. We upgraded the same day. We would receive "ANR8750E Volume is incompatible with specified device type". IBM had defined the volume range for the K tapes as "K extended" and should have been defined as just "K". We also started receiving IO errors on our 3590 tape drives. This still persists today, but a microcode fix for the problem is in test at IBM and is suppose to be released by the end of the month (Hopefully!). The error we are receiving is "ANR8302E I/O error on drive RMT1 (/dev/rmt1) (OP=WRITE, CC=0, KEY=0B, ASC=44, ASCQ=00".
Re: Antwort: Re: Antwort: Re: Problems after 4.1 Upgrade and Resolutions
Yes, our Atape driver is at 5.4.4.0. We initially went from 5.0.2.0 to 5.4.2.0 and saw the problem there also. At 05:51 PM 1/30/01 +0100, you wrote: With the latest Atape driver 5.4.4.0 ? Von: Diana Noble [EMAIL PROTECTED] Am: 30.01.2001 16:46 GMT Bitte antworten an "ADSM: Dist Stor Manager" [EMAIL PROTECTED] An: [EMAIL PROTECTED] Kopie: (Blindkopie: Matthew Muldoon/MAINSTOR/Niedernberg/mus/DE) Thema:Re: Antwort: Re: Problems after 4.1 Upgrade and Resolutions We are running 4.1.2. At 05:41 PM 1/30/01 +0100, you wrote: Are you using 4.1.0 or 4.1.2? Von: Diana Noble [EMAIL PROTECTED] Am: 30.01.2001 16:22 GMT Bitte antworten an "ADSM: Dist Stor Manager" [EMAIL PROTECTED] An: [EMAIL PROTECTED] Kopie: (Blindkopie: Matthew Muldoon/MAINSTOR/Niedernberg/mus/DE) Thema: Re: Problems after 4.1 Upgrade and Resolutions We are running D25D. This level of microcode ran fine prior to going to TSM 4.1. We had never had an IO error before then. Now we receive the errors on both our tape drives. At 08:43 AM 1/30/01 -0600, you wrote: Diane, What level of microcode are you currently running on your 3590 tape drives. We are running 3590E1A tape drives with a microcode level of D22E. We have been on this level of code for quite some time with no errors. Our 3590's are also house within a 3494. -Original Message- From: Diana Noble [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 30, 2001 8:15 AM To: [EMAIL PROTECTED] Subject: Problems after 4.1 Upgrade and Resolutions I had posted some questions last month regarding problems we encountered after our upgrade to TSM 4.1 and thought I would pass along what we found. We are using AIX 4.3, 3590E's and a 3494. When issuing the dsmadmc command we received "ANS1033E An invalid TCP/IP host name was specified". Resolution was to edit /usr/tivoli/tsm/client/ba/bin/dsm.sys and add a line for TCPServeraddress which stated the tsm server name in full. This was apparently not necessary under 3.1. We could not label K tapes. We had problems with this under 3.1, but it turned out IBM needed to flick a switch on the drives. We upgraded the same day. We would receive "ANR8750E Volume is incompatible with specified device type". IBM had defined the volume range for the K tapes as "K extended" and should have been defined as just "K". We also started receiving IO errors on our 3590 tape drives. This still persists today, but a microcode fix for the problem is in test at IBM and is suppose to be released by the end of the month (Hopefully!). The error we are receiving is "ANR8302E I/O error on drive RMT1 (/dev/rmt1) (OP=WRITE, CC=0, KEY=0B, ASC=44, ASCQ=00".
Re: Problems after 4.1 Upgrade and Resolutions
Our CE has been working with Hardware support on this issue. The Hardware PMR is 34925 Branch 422. As of yesterday, the record still stated the fix would be released by the end of the month per our CE. At 11:54 AM 1/30/01 -0500, you wrote: Diana, Who are you working with on the I/O problems? Is there a contact in Tuscon (or wherever) that you could give me? We've got an open PMR on this issue right now and I'd like to be able to pass that info on to our CE so he can touch base with them. And the end of the month is tomorrow...I sure hope they can have this ready soon! This is causing us a lot of headaches! Good luck, Kathleen Diana Noble [EMAIL PROTECTED] on 01/30/2001 11:22:46 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Kathleen M Hallahan/ISS/HQ/FHLMC) Subject Re: Problems after 4.1 Upgrade and Resolutions : We are running D25D. This level of microcode ran fine prior to going to TSM 4.1. We had never had an IO error before then. Now we receive the errors on both our tape drives. At 08:43 AM 1/30/01 -0600, you wrote: Diane, What level of microcode are you currently running on your 3590 tape drives. We are running 3590E1A tape drives with a microcode level of D22E. We have been on this level of code for quite some time with no errors. Our 3590's are also house within a 3494. -Original Message- From: Diana Noble [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 30, 2001 8:15 AM To: [EMAIL PROTECTED] Subject: Problems after 4.1 Upgrade and Resolutions I had posted some questions last month regarding problems we encountered after our upgrade to TSM 4.1 and thought I would pass along what we found. We are using AIX 4.3, 3590E's and a 3494. When issuing the dsmadmc command we received "ANS1033E An invalid TCP/IP host name was specified". Resolution was to edit /usr/tivoli/tsm/client/ba/bin/dsm.sys and add a line for TCPServeraddress which stated the tsm server name in full. This was apparently not necessary under 3.1. We could not label K tapes. We had problems with this under 3.1, but it turned out IBM needed to flick a switch on the drives. We upgraded the same day. We would receive "ANR8750E Volume is incompatible with specified device type". IBM had defined the volume range for the K tapes as "K extended" and should have been defined as just "K". We also started receiving IO errors on our 3590 tape drives. This still persists today, but a microcode fix for the problem is in test at IBM and is suppose to be released by the end of the month (Hopefully!). The error we are receiving is "ANR8302E I/O error on drive RMT1 (/dev/rmt1) (OP=WRITE, CC=0, KEY=0B, ASC=44, ASCQ=00".
Re: Problems after 4.1 Upgrade and Resolutions
Thanks for the info! Diana Noble [EMAIL PROTECTED] on 01/30/2001 12:16:03 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Kathleen M Hallahan/ISS/HQ/FHLMC) Subject Re: Problems after 4.1 Upgrade and Resolutions : Our CE has been working with Hardware support on this issue. The Hardware PMR is 34925 Branch 422. As of yesterday, the record still stated the fix would be released by the end of the month per our CE. At 11:54 AM 1/30/01 -0500, you wrote: Diana, Who are you working with on the I/O problems? Is there a contact in Tuscon (or wherever) that you could give me? We've got an open PMR on this issue right now and I'd like to be able to pass that info on to our CE so he can touch base with them. And the end of the month is tomorrow...I sure hope they can have this ready soon! This is causing us a lot of headaches! Good luck, Kathleen Diana Noble [EMAIL PROTECTED] on 01/30/2001 11:22:46 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Kathleen M Hallahan/ISS/HQ/FHLMC) Subject Re: Problems after 4.1 Upgrade and Resolutions : We are running D25D. This level of microcode ran fine prior to going to TSM 4.1. We had never had an IO error before then. Now we receive the errors on both our tape drives. At 08:43 AM 1/30/01 -0600, you wrote: Diane, What level of microcode are you currently running on your 3590 tape drives. We are running 3590E1A tape drives with a microcode level of D22E. We have been on this level of code for quite some time with no errors. Our 3590's are also house within a 3494. -Original Message- From: Diana Noble [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 30, 2001 8:15 AM To: [EMAIL PROTECTED] Subject: Problems after 4.1 Upgrade and Resolutions I had posted some questions last month regarding problems we encountered after our upgrade to TSM 4.1 and thought I would pass along what we found. We are using AIX 4.3, 3590E's and a 3494. When issuing the dsmadmc command we received "ANS1033E An invalid TCP/IP host name was specified". Resolution was to edit /usr/tivoli/tsm/client/ba/bin/dsm.sys and add a line for TCPServeraddress which stated the tsm server name in full. This was apparently not necessary under 3.1. We could not label K tapes. We had problems with this under 3.1, but it turned out IBM needed to flick a switch on the drives. We upgraded the same day. We would receive "ANR8750E Volume is incompatible with specified device type". IBM had defined the volume range for the K tapes as "K extended" and should have been defined as just "K". We also started receiving IO errors on our 3590 tape drives. This still persists today, but a microcode fix for the problem is in test at IBM and is suppose to be released by the end of the month (Hopefully!). The error we are receiving is "ANR8302E I/O error on drive RMT1 (/dev/rmt1) (OP=WRITE, CC=0, KEY=0B, ASC=44, ASCQ=00".
