- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- target id change
StoreEver Tape Storage
1820594
Members
1545
Online
109626
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
Discussions
Forums
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
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
тАО11-02-2003 06:37 PM
тАО11-02-2003 06:37 PM
target id change
supportHi,
Let me begin to explain the SAN environment:
-VA7100 with 2 ctrl's connected to 2 separate SAN switch 8/EL (2 Fabrics)
-MSL5030 with 2 LTO1 drives and an internal NSR e1200 connected to only 1 of the 2 SAN switches.
- 2 PC servers with 2 QLOGIC 2400L HBA's installed per server, each HBA is connected to the 2 separated SAN switches
-Zonig is NOT configured
-OS = NT4.0 SP6A
-Backup Software = HP DP5.0
PROBLEM:
-when PC Server A reboot,PC server A's SCSI path have been change from "SCSI 3:0:1:2c" TO "scsi 3:0:3:2".
scsi port = 3
bus id =0
target id =1/3
LUN =2
In same time, reboot PC server B, B's SCSI path no change
Before reboot A ,Server A and B have run 30 days with no problem.
Can someone help me on this why server A's scsi PATH change?
what's mean of "target id"?
Let me begin to explain the SAN environment:
-VA7100 with 2 ctrl's connected to 2 separate SAN switch 8/EL (2 Fabrics)
-MSL5030 with 2 LTO1 drives and an internal NSR e1200 connected to only 1 of the 2 SAN switches.
- 2 PC servers with 2 QLOGIC 2400L HBA's installed per server, each HBA is connected to the 2 separated SAN switches
-Zonig is NOT configured
-OS = NT4.0 SP6A
-Backup Software = HP DP5.0
PROBLEM:
-when PC Server A reboot,PC server A's SCSI path have been change from "SCSI 3:0:1:2c" TO "scsi 3:0:3:2".
scsi port = 3
bus id =0
target id =1/3
LUN =2
In same time, reboot PC server B, B's SCSI path no change
Before reboot A ,Server A and B have run 30 days with no problem.
Can someone help me on this why server A's scsi PATH change?
what's mean of "target id"?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2003 12:12 AM
тАО11-03-2003 12:12 AM
Re: target id change
Could you please get 'supportshow' from both switches, zip them and attach to your next reply?
Eugeny
Eugeny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2003 01:38 AM
тАО11-03-2003 01:38 AM
Re: target id change
You need to set persistent bindings on the HBA cards. Depending on what card, OS etc, this is either configured through a GUI or a configuration file.
Haven't seen a target ID of 1/3 before. This is the target ID - any other devices configured below that level would be based on LUN (logical unit number) mappings. Go through fibre though, and it handles all the SCSI stuff for you (theoretically) and assigns this dynamically.
Haven't seen a target ID of 1/3 before. This is the target ID - any other devices configured below that level would be based on LUN (logical unit number) mappings. Go through fibre though, and it handles all the SCSI stuff for you (theoretically) and assigns this dynamically.
A sysadmin should never cross his fingers in the hope commands will work. Makes for a lot of mistakes while typing.
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
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP