HPE GreenLake Administration
- Community Home
- >
- Storage
- >
- Legacy
- >
- Automated Backup
- >
- dlt4000s on d class server
Automated Backup
1826614
Members
2736
Online
109695
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
08-06-2002 03:09 AM
08-06-2002 03:09 AM
dlt4000s on d class server
we have a D350 server and have been trying to install a dlt4000s to it. The dlt4000s is an external box made by TTI and distributed by HP with 7980S emulation.
When connected to the se-scsi port on the back of the D class the unit does'nt see it upon searching. We have tried changing id's and switches on the back to no avail. even when connected on its own so their are no conflicts it is still not seen. The same drive can be attached and seen without any problems on k class servers, C class workstations and even a pc. I know the external port is good as it sees other devices attached to it ok.
Does anyone have one of these drives attached succesfully to a D class server or know if it will work.
thanks
When connected to the se-scsi port on the back of the D class the unit does'nt see it upon searching. We have tried changing id's and switches on the back to no avail. even when connected on its own so their are no conflicts it is still not seen. The same drive can be attached and seen without any problems on k class servers, C class workstations and even a pc. I know the external port is good as it sees other devices attached to it ok.
Does anyone have one of these drives attached succesfully to a D class server or know if it will work.
thanks
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-06-2002 11:07 PM
08-06-2002 11:07 PM
Re: dlt4000s on d class server
Dear Andrew,
The DLT4000 should be 'seen' by the D350. The SCSI port is narrow single-ended. I always use the mapper program before booting the system into HP-UX. At the ISL> prompt you enter ODE and then at the ODE> prompt enter mapper. (Later releases are called mapper2). Typing run will identify all the peripherals.
The TTI electronics cause the model string to be reported as an HP7980S. The tape2 driver should handle this. There is a setting somewhere on the DLT4000S where it can revert to standard Quantum ID.
I can only suggest checking the SCSI cable and terminator, which you appear to have done.
Rothery
The DLT4000 should be 'seen' by the D350. The SCSI port is narrow single-ended. I always use the mapper program before booting the system into HP-UX. At the ISL> prompt you enter ODE and then at the ODE> prompt enter mapper. (Later releases are called mapper2). Typing run will identify all the peripherals.
The TTI electronics cause the model string to be reported as an HP7980S. The tape2 driver should handle this. There is a setting somewhere on the DLT4000S where it can revert to standard Quantum ID.
I can only suggest checking the SCSI cable and terminator, which you appear to have done.
Rothery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2002 03:39 AM
08-07-2002 03:39 AM
Re: dlt4000s on d class server
thanks, i have now got it to work, only at id 0 though and it is still not seen at BCH level.
hp-ux will now see it and work ok aslong as its set to this id.
hp-ux will now see it and work ok aslong as its set to this id.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP