- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: Does anyone else still use L&TT for their MSLs...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2009 07:57 AM
тАО02-09-2009 07:57 AM
Does anyone else still use L&TT for their MSLs?
I've got a 2 node VMS cluster (v8.3 - Alpha ES47's). They're in two separate locations 6 miles apart. Correspondingly, I have 2 MSL 5026SLs (one in each location), but I get 2 different responses when I use L&TT (v4.2) for the same command. Needless to say, it gives more differences as you continue further on in the menu.
Would anyone have an idea as to what I might have set up differently to generate such a type of thing?
I've asked HP Support in the past, but they seem to only have folks that do Windows these days ("they're basically the same" - yeh, but they're *not* the same - they're on 2 different O/S' with 2 different interfaces)
Thoughts welcome,
Rich
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2009 08:00 AM
тАО02-09-2009 08:00 AM
Re: Does anyone else still use L&TT for their MSLs?
CACHE1::DISK$INFSYS:[RJHEARN]_>
CACHE1::DISK$INFSYS:[RJHEARN]_>show time
9-FEB-2009 10:35:43
CACHE1::DISK$INFSYS:[RJHEARN]_>
CACHE1::DISK$INFSYS:[RJHEARN]_>define usr sys$sysdevice:[vms$common.opt.ltt.misc.usr]
CACHE1::DISK$INFSYS:[RJHEARN]_>set def sys$sysdevice:[vms$common.opt.ltt]
CACHE1::DISK$INFSYS:[RJHEARN]_>run hp_ltt.exe
skipping Welcome screens...
Scan Mode Selection >
------------------------------------------------------------------------------
A scan mode allows user to select either Hardware scan or Saved/Manual scan.
1 [X] Hardware Scan
2 [ ] Saved/Manual Scan
Enter Command>continue <----
------------------
Main >
------------------------------------------------------------------------------
Type the corresponding number to select a device, or enter a blank command for
a command list
Libraries/Autoloaders:
1 COMPAQ MSL5000 Series (Address: 1.0.0[1-$2$GGA0])
Processors/Enclosures:
Drives:
2 COMPAQ SuperDLT1 (Address: 1.0.0[1-$2$MGA0])
3 COMPAQ SuperDLT1 (Address: 1.1.0[1-$2$MGA1])
4 COMPAQ SuperDLT1 (Address: 1.2.0[1-$2$MGA2])
5 COMPAQ SuperDLT1 (Address: 1.3.0[1-$2$MGA3])
Other Devices:
6 COMPAQ HSV110 (C)COMPAQ (Address: 1.0.0[1-$1$DGA64])
7 COMPAQ BF036863B9 (Address: 3.0.0[3-$1$DKA0])
8 COMPAQ BF03685A35 (Address: 4.0.0[4-$1$DKB0])
Enter Command>exit
------------------
CACHE1::DISK$INFSYS:[RJHEARN]_>
CACHE2::DISK$INFSYS:[RJHEARN]_>
CACHE2::DISK$INFSYS:[RJHEARN]_>show time
9-FEB-2009 10:35:51
CACHE2::DISK$INFSYS:[RJHEARN]_>
CACHE2::DISK$INFSYS:[RJHEARN]_>define usr sys$sysdevice:[vms$common.opt.ltt.misc.usr]
CACHE2::DISK$INFSYS:[RJHEARN]_>set def sys$sysdevice:[vms$common.opt.ltt]
CACHE2::DISK$INFSYS:[RJHEARN]_> run hp_ltt.exe
Skipping Welcome Screens...
Scan Mode Selection >
------------------------------------------------------------------------------
A scan mode allows user to select either Hardware scan or Saved/Manual scan.
1 [X] Hardware Scan
2 [ ] Saved/Manual Scan
Enter Command>continue
Main >
------------------------------------------------------------------------------
Type the corresponding number to select a device, or enter a blank command for
a command list
Libraries/Autoloaders:
1 COMPAQ MSL5000 Series (Address: 1.0.0[1-$2$GGA0])
2 COMPAQ MSL5000 Series (Address: 1.1.0[1-$2$GGA1])
3 Drive 1:COMPAQ SuperDLT1 (Address: 1.2.0[1-$2$MGA2])
4 Drive 2:COMPAQ SuperDLT1 (Address: 1.3.0[1-$2$MGA3])
Processors/Enclosures:
Drives:
5 COMPAQ SuperDLT1 (Address: 1.0.0[1-$2$MGA0])
6 COMPAQ SuperDLT1 (Address: 1.1.0[1-$2$MGA1])
Other Devices:
7 COMPAQ HSV110 (C)COMPAQ (Address: 1.0.0[1-$1$DGA64])
8 COMPAQ BF03688284 (Address: 3.0.0[3-$2$DKA0])
9 COMPAQ BF03685A35 (Address: 4.0.0[4-$2$DKB0])
Enter Command>exit
--------------
CACHE2::DISK$INFSYS:[RJHEARN]_>
_
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2009 10:42 AM
тАО02-09-2009 10:42 AM
Re: Does anyone else still use L&TT for their MSLs?
- different mapping on the NSR
(I guess the libraries have an internal E1200 board)
and/or
- differences in SYS$COMMON:[SYSEXE]SYS$DEVICES.DAT
-- you have 2 system disks and/or
-- a file in SYS$SPECIFIC:[SYSEXE]
This different order of devices can be a result of the SAN topology (on which switch/port a storage device or a server is connected).
A tape drive should not come up in the 'Libraries/Autoloaders:' section, but I would first verify / cleanup SYS$DEVICES.DAT and do a cluster reboot to clean up stale data (yes, I understand that ruins your uptime ;-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2009 11:03 AM
тАО02-09-2009 11:03 AM
Re: Does anyone else still use L&TT for their MSLs?
Thank you for your response. A place to start is what I was looking for. I'll be taking a look at my fabric and the NSRs'(I have 2). If necessary, I'll get HP Network Support to help me (I hope); we've got a contract, so it's (theoretically) possible :^)
Your response specifing that the drives *shouldn't* show up in the Library section let's me know which one is set up correctly. I wasn't sure before.
Thanks for your thoughts,
Rich
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2009 07:52 PM
тАО02-09-2009 07:52 PM
Re: Does anyone else still use L&TT for their MSLs?
Based on the screenshots, I don't think there is a problem with the NSR mapping (if both the nodes are able to see the libraries properly in show device output). Till LTT v 4.4), we had a problem in LTT wherein it couldn't map the drives of a FC connected library properly.
The issue has been fixed from LTT v 4.5 onwards. Installing LTT v 4.7 should resolve the anomaly.
Regards,
Satya
LTT Team