- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: Connecting to 3583 LTO with A6795A card
StoreEver Tape Storage
1752261
Members
4924
Online
108785
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
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
10-26-2003 06:27 PM
10-26-2003 06:27 PM
Re: Connecting to 3583 LTO with A6795A card
Actually, the solution was in the fact that both of the IBM 3583 SAN Data Gateway fibre channel ports (FC1 and FC2) defaults to HostType 2 (aix) and aix uses soft addressing. This means that HP-UX servers cannot connect to these ports and so the ports cannot be shared by hp-ux and aix servers. We had to dedicate one port to aix and the other to hp-ux access.We will leave FC1 to aix and soft addressing, and reconfigure FC2 to HostType hpux and set FC2 to use hard addressing by doing a "setFcHardId 2,100" on the SAN data gateway, ie setting the FCHardID to anything else than 0 or 255. The rest of the setup follows the ATDD install guide.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-29-2003 05:53 AM
10-29-2003 05:53 AM
Solution
Ah, you're original post just indicated that the device files were missing. HP-UX does require the corresponding SNC FC port to have the HostType set to HP-UX which pretty much precludes sharing that port with any other OS. Using the Autosense/NT HostType on the other port will allow you to use it for others (e.g. we share AIX, SunOS and Windows). Soft vs. hard addressing method is specific to the SAN environment / configuration rather than the OS though.
As previously mentioned, please note that insf will not create the device files any tape devices managed by atdd â the atdd_mksf script has to be run (atdd_mksf | sh) to make the corresponding nodes. The default atdd installation runs this automatically and it will have to be run manually if the configuration changes.
As previously mentioned, please note that insf will not create the device files any tape devices managed by atdd â the atdd_mksf script has to be run (atdd_mksf | sh) to make the corresponding nodes. The default atdd installation runs this automatically and it will have to be run manually if the configuration changes.
- « Previous
-
- 1
- 2
- Next »
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP