Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Library\s+manager\/library\s+conundrum\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Library\s+manager\/library\s+conundrum\s*$/: 19 ]

Total 19 documents matching your query.

1. [ADSM-L] Library manager/library conundrum (score: 1): Author: Mark Stapleton <Mark.Stapleton AT CDW DOT COM>; Date: Thu, 2 Oct 2008 10:47:28 -0500; We're setting up a TS3310 tape library for two TSM servers to share through a library manager/library client arrangement. We got successful server-to-server comm, and the library client calls for tap; /lists/html/ADSM-L/2008-10/msg00026.html (10,980 bytes)
2. Re: [ADSM-L] Library manager/library conundrum (score: 1): Author: Remco Post <r.post AT PLCS DOT NL>; Date: Thu, 2 Oct 2008 18:17:39 +0200; We're setting up a TS3310 tape library for two TSM servers to share through a library manager/library client arrangement. hi Mark, do you have the paths for the library client configured correctly o; /lists/html/ADSM-L/2008-10/msg00027.html (11,785 bytes)
3. Re: [ADSM-L] Library manager/library conundrum (score: 1): Author: Paul Zarnowski <psz1 AT CORNELL DOT EDU>; Date: Thu, 2 Oct 2008 12:19:57 -0400; Double check your element numbers and paths to the drives. Make sure you have a path defined for each drive to each library-client server. We got successful server-to-server comm, and the library cli; /lists/html/ADSM-L/2008-10/msg00028.html (12,622 bytes)
4. Re: [ADSM-L] Library manager/library conundrum (score: 1): Author: Mark Stapleton <Mark.Stapleton AT CDW DOT COM>; Date: Thu, 2 Oct 2008 11:27:13 -0500; As I said, the client's request for a tape mount is honored by the manager, and it appears that the client gets an acknowledgement that the tape is mounted, because it tries to talk to the tape volum; /lists/html/ADSM-L/2008-10/msg00029.html (10,872 bytes)
5. Re: [ADSM-L] Library manager/library conundrum (score: 1): Author: Paul Zarnowski <psz1 AT CORNELL DOT EDU>; Date: Thu, 2 Oct 2008 12:32:53 -0400; I'm guessing this is because the library put the tape in the wrong drive, or a different drive than the client-server is looking at. Check your element addresses in Q DRIVE and the device names in yo; /lists/html/ADSM-L/2008-10/msg00030.html (11,332 bytes)
6. Re: [ADSM-L] Library manager/library conundrum (score: 1): Author: Mark Stapleton <Mark.Stapleton AT CDW DOT COM>; Date: Thu, 2 Oct 2008 11:33:06 -0500; you There are no drive definitions for the "remote" library in the library client, and therefore no element numbers or paths to check. There is a path in the library manager that connects each of the; /lists/html/ADSM-L/2008-10/msg00031.html (12,002 bytes)
7. Re: [ADSM-L] Library manager/library conundrum (score: 1): Author: Remco Post <r.post AT PLCS DOT NL>; Date: Thu, 2 Oct 2008 18:33:54 +0200; From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of Remco Post do you have the paths for the library client configured correctly on the library manager? Are the paths up?; /lists/html/ADSM-L/2008-10/msg00032.html (12,297 bytes)
8. Re: [ADSM-L] Library manager/library conundrum (score: 1): Author: "Abbott, Joseph" <JABBOTT AT PARTNERS DOT ORG>; Date: Thu, 2 Oct 2008 12:38:15 -0400; I think that's your problem right there. The element and path have to match on all of your systems. The element/serial number and paths have to be the same for drive1 on all three systems. JoeA Josep; /lists/html/ADSM-L/2008-10/msg00033.html (12,692 bytes)
9. Re: [ADSM-L] Library manager/library conundrum (score: 1): Author: "Abbott, Joseph" <JABBOTT AT PARTNERS DOT ORG>; Date: Thu, 2 Oct 2008 12:40:32 -0400; Correct and there shouldn't be any paths on the client systems. Only the library manager needs the paths. You need to setup paths from the library manager to itself and then to the other library clie; /lists/html/ADSM-L/2008-10/msg00034.html (13,653 bytes)
10. Re: [ADSM-L] Library manager/library conundrum (score: 1): Author: "Bos, Karel" <Karel.Bos AT ATOSORIGIN DOT COM>; Date: Thu, 2 Oct 2008 18:42:06 +0200; Mark, Checking drive things on windows with: - ITSM device manager (serial number/ \\.\tapeX mapping - communication with the drive via lbtest/mttest.exe utils (part of tsm install) - and anything el; /lists/html/ADSM-L/2008-10/msg00035.html (12,591 bytes)
11. Re: [ADSM-L] Library manager/library conundrum (score: 1): Author: Paul Zarnowski <psz1 AT CORNELL DOT EDU>; Date: Thu, 2 Oct 2008 13:06:07 -0400; Mark, You're correct that there is only an element number in one place. However, there should be paths defined (on the library manager server) as follows: one path to the library for the library mana; /lists/html/ADSM-L/2008-10/msg00036.html (13,695 bytes)
12. Re: [ADSM-L] Library manager/library conundrum (score: 1): Author: Remco Post <remco AT PIPSWORLD DOT NL>; Date: Thu, 2 Oct 2008 19:04:08 +0200; From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of Paul Zarnowski Double check your element numbers and paths to the drives. Make sure you have a path defined for each d; /lists/html/ADSM-L/2008-10/msg00037.html (13,807 bytes)
13. Re: [ADSM-L] Library manager/library conundrum (score: 1): Author: Fred Johanson <Fred AT UCHICAGO DOT EDU>; Date: Thu, 2 Oct 2008 12:22:06 -0500; If you're SAN connected, Q SAN on the client supplies the device name for each path. Fred Johanson TSM Administrator University of Chicago 773-702-8464 This may be a clue, the drive is accessed direc; /lists/html/ADSM-L/2008-10/msg00038.html (13,711 bytes)
14. Re: [ADSM-L] Library manager/library conundrum (score: 1): Author: Mark Stapleton <Mark.Stapleton AT CDW DOT COM>; Date: Thu, 2 Oct 2008 13:59:13 -0500; Here's the deal... The physical device tape0, as seen by the library manager, has the devicename mt1.0.0.3. The same tape drive on the client, however, sees the tape drive as devicename mt3.0.0.5. (W; /lists/html/ADSM-L/2008-10/msg00039.html (15,689 bytes)
15. Re: [ADSM-L] Library manager/library conundrum (score: 1): Author: "Abbott, Joseph" <JABBOTT AT PARTNERS DOT ORG>; Date: Thu, 2 Oct 2008 15:14:55 -0400; You hit it right on the head. The library manager has to be the higher of the software code levels. JoeA Joseph A Abbott MCSE/MCSD Partners Healthcare Systems Development Team Tivoli Storage Manager; /lists/html/ADSM-L/2008-10/msg00040.html (16,839 bytes)
16. Re: [ADSM-L] Library manager/library conundrum (score: 1): Author: Remco Post <r.post AT PLCS DOT NL>; Date: Thu, 2 Oct 2008 21:12:51 +0200; Here's the deal... The physical device tape0, as seen by the library manager, has the devicename mt1.0.0.3. The same tape drive on the client, however, sees the tape drive as devicename mt3.0.0.5. (; /lists/html/ADSM-L/2008-10/msg00041.html (17,109 bytes)
17. Re: [ADSM-L] Library manager/library conundrum (score: 1): Author: Remco Post <remco AT PIPSWORLD DOT NL>; Date: Thu, 2 Oct 2008 21:20:54 +0200; You hit it right on the head. The library manager has to be the higher of the software code levels. this sounds interesting. Could you provide a reference? It's not an obvious comment in the admin g; /lists/html/ADSM-L/2008-10/msg00042.html (18,230 bytes)
18. Re: [ADSM-L] Library manager/library conundrum (score: 1): Author: Remco Post <remco AT PIPSWORLD DOT NL>; Date: Thu, 2 Oct 2008 21:26:57 +0200; One other thing comes to mind, have you updated the library to shared=yes on the libmgr? I'd think yes from what you told us, but just to be sure. Here's the deal... The physical device tape0, as see; /lists/html/ADSM-L/2008-10/msg00043.html (17,485 bytes)
19. Re: [ADSM-L] Library manager/library conundrum (score: 1): Author: Paul Zarnowski <psz1 AT CORNELL DOT EDU>; Date: Fri, 3 Oct 2008 11:31:12 -0400; At this point, I think it would be useful to see the following output, just to make sure we're all seeing the same thing.. from your library manager server: Q DRIVE F=D Q PATH F=D Q LIBRARY F=D On yo; /lists/html/ADSM-L/2008-10/msg00053.html (18,025 bytes)

Current List: 1 - 19
Page: [1]