Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Tape\s+Drive\s+SN\s+issue\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Tape\s+Drive\s+SN\s+issue\s*$/: 22 ]

Total 22 documents matching your query.

1. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: "Huebner,Andy,FORT WORTH,IT" <Andy.Huebner AT ALCONLABS DOT COM>; Date: Fri, 1 May 2009 10:13:13 -0500; No, tape and disk reside on different fabrics. There are 7 tape HBAs, 3 of which go to physical tape, two of those have drives with this problem. Andy Huebner I am not aware of this problem. Are you; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-05/msg00002.html (11,733 bytes)
2. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: Shawn Drew <shawn.drew AT AMERICAS.BNPPARIBAS DOT COM>; Date: Fri, 1 May 2009 11:33:15 -0400; We had this problem as well. Our dedicated HBAs would just randomly log out of the Clariion. Presumably when a SAN Discovery "probe" went out. We couldn't get it to log back in without a reboot. A re; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-05/msg00004.html (13,069 bytes)
3. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: Jo Lay <jolay AT US.IBM DOT COM>; Date: Fri, 1 May 2009 09:15:31 -0700; We will appreciate if someone can work with IBM support to report this problem. SAN Discovery is a very important TSM function and it is widely used by our customer. Regards, Jo Lay Tivoli Storage Pr; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-05/msg00005.html (15,027 bytes)
4. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: "Huebner,Andy,FORT WORTH,IT" <Andy.Huebner AT ALCONLABS DOT COM>; Date: Thu, 30 Apr 2009 09:39:50 -0500; Update: We turned on TapeAlertMSG - no new messages We have changed the GBics on the switches - No change We had IBM do a health check on the drives - Last abnormal error was months earlier on one dr; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-04/msg00380.html (16,442 bytes)
5. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: Dwight Cook <cookde AT COX DOT NET>; Date: Thu, 30 Apr 2009 09:53:49 -0500; You are aware that under AIX if any WWN in the path of a drive changes, then that constitutes an entirely new device as seen by AIX. If you replaced GBics, it possibly could have caused the tape driv; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-04/msg00381.html (17,744 bytes)
6. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: "Huebner,Andy,FORT WORTH,IT" <Andy.Huebner AT ALCONLABS DOT COM>; Date: Thu, 30 Apr 2009 10:21:48 -0500; The drives were verified in AIX after GBic change. Since there was not a port change there was no effect on AIX. The library is aware of all of the drives. I think I mentioned earlier that the AS/400; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-04/msg00383.html (19,139 bytes)
7. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: Jo Lay <jolay AT US.IBM DOT COM>; Date: Thu, 30 Apr 2009 08:39:14 -0700; Andy, Do you have TSM SAN Discovery turned on? If you do, you can perform "q SAN" and look for the drive serial number in the output of "q san". If you have ran cfgmgr after you changed GBIC, TSM SAN; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-04/msg00384.html (21,244 bytes)
8. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: "Huebner,Andy,FORT WORTH,IT" <Andy.Huebner AT ALCONLABS DOT COM>; Date: Thu, 30 Apr 2009 10:49:54 -0500; We had to turn off SAN discovery due to other issues. Andy Huebner Andy, Do you have TSM SAN Discovery turned on? If you do, you can perform "q SAN" and look for the drive serial number in the output; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-04/msg00385.html (22,162 bytes)
9. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: Jo Lay <jolay AT US.IBM DOT COM>; Date: Thu, 30 Apr 2009 09:06:53 -0700; Ok, you might want to resolve the SAN Discovery issue on your machine. This will save you time in the long run. BTW, what is the issue for SAN discovery? Regards, Jo Lay Tivoli Storage Products, IBM; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-04/msg00387.html (23,019 bytes)
10. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: Richard Rhodes <rrhodes AT FIRSTENERGYCORP DOT COM>; Date: Thu, 30 Apr 2009 12:40:58 -0400; Here are some things to do . . . Check that the tape drive is logged into the switch port, and you see the wwn on the switch port. Check the tape drive that it sees the san - usually a light indicati; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-04/msg00390.html (18,637 bytes)
11. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: Alex Paschal <apaschal AT MSIINET DOT COM>; Date: Thu, 30 Apr 2009 11:57:31 -0500; Hi, Andy. Going back to simple, in addition to deleting the paths, did you also delete and redefine your drives? I'm just double-checking because I don't see it explicitly mentioned in the thread and; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-04/msg00392.html (20,693 bytes)
12. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: "Ochs, Duane" <Duane.Ochs AT QG DOT COM>; Date: Thu, 30 Apr 2009 12:01:48 -0500; You can issue a show library command from a TSM prompt. For detailed info that is not always represented in TSM. I've used this to see if tapes are stuck in older DLT drives. But it shows WWN and ser; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-04/msg00393.html (21,252 bytes)
13. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: Dwight Cook <cookde AT COX DOT NET>; Date: Thu, 30 Apr 2009 12:30:32 -0500; OH, are only 3590's having problems??? We did a switch upgrade and the short story is that the switches we migrated to would not function with 3590's / 3590's would not function with the switch... I; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-04/msg00394.html (22,069 bytes)
14. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: "Huebner,Andy,FORT WORTH,IT" <Andy.Huebner AT ALCONLABS DOT COM>; Date: Thu, 30 Apr 2009 13:04:50 -0500; With SAN discovery on our Clariion disks become inaccessible at a random time. Since we turned on SAN discovery to fix the tape drive thing and it did not, we turned it back off. Andy Huebner Ok, you; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-04/msg00398.html (24,067 bytes)
15. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: "Huebner,Andy,FORT WORTH,IT" <Andy.Huebner AT ALCONLABS DOT COM>; Date: Thu, 30 Apr 2009 13:09:27 -0500; IBM had me delete and recreate the drives in TSM. When we recreated the paths TSM was unable to contact the drive. AIX did not report an error. Since I am down to trying things that won't work I rese; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-04/msg00399.html (22,042 bytes)
16. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: Jo Lay <jolay AT US.IBM DOT COM>; Date: Thu, 30 Apr 2009 11:29:23 -0700; I am not aware of this problem. Are you putting disk and tape under the same HBA? Regards, Jo Lay Tivoli Storage Products, IBM Software Group jolay AT us.ibm DOT com; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-04/msg00401.html (11,897 bytes)
17. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: "Clark, Robert A" <Robert.Clark AT PROVIDENCE DOT ORG>; Date: Thu, 30 Apr 2009 11:40:53 -0700; If you use tapeutil to do an inquiry on a tape drive, the serial number should be recognizable in the output. You can compare this with the results from a "lscfg -vl rmt1" or "lsattr -El rmt1". I've; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-04/msg00402.html (19,275 bytes)
18. [ADSM-L] Tape Drive SN issue (score: 1): Author: "Huebner,Andy,FORT WORTH,IT" <Andy.Huebner AT ALCONLABS DOT COM>; Date: Mon, 30 Mar 2009 10:50:14 -0500; We have a three drives that generate these messages and we are unable to use the drives because the path will not stay on-line. We have not been able to find a solution to this problem. 03/30/2009 04; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-03/msg00456.html (13,276 bytes)
19. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: Kelly Lipp <lipp AT STORSERVER DOT COM>; Date: Mon, 30 Mar 2009 09:52:33 -0600; I assume these message occur when you try to define the path? Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com We have a three drive; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-03/msg00457.html (13,759 bytes)
20. Re: [ADSM-L] Tape Drive SN issue (score: 1): Author: Thomas Denier <Thomas.Denier AT JEFFERSONHOSPITAL DOT ORG>; Date: Mon, 30 Mar 2009 12:08:55 -0400; --Andy Huebner wrote: -- We have a 3494 attached to a mainframe Linux system. We sometimes get similar messages after a reboot. Our system is configured in such a way that the relationship between ph; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-03/msg00458.html (12,918 bytes)

Current List: 1 - 20
Page: [1] [2]