- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Business Copy XP
Disk Enclosures
1752866
Members
3673
Online
108791
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
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
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
тАО12-15-2003 10:02 PM
тАО12-15-2003 10:02 PM
I reach limit in horcm.conf due to each BC LUN is identified by x and y where x,y are target and lun from device file cztxdy from BC luns
LUN 7F is czt15d7 and LUN 80 is c(z')t0d0
how can i diferrentiate LUN 80 from LUN 00 in horcm template (card instance is not specified here!)?
Thanks in advance
LUN 7F is czt15d7 and LUN 80 is c(z')t0d0
how can i diferrentiate LUN 80 from LUN 00 in horcm template (card instance is not specified here!)?
Thanks in advance
Teach is the best way to learn
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-16-2003 04:55 PM
тАО12-16-2003 04:55 PM
Solution
Hello
In case of Business copy XP or Continuous Access XP always use the following command to determine the correct TID and LU#.
# raidscan -p port -fx
Sample output of above command is given below
Port TID LU#CU LDEV
CL1-H / da/ 7, 2, 3.1(6).............S-VOL SSUS ASYNC 6, ----- d4
CL1-H / da/ 7, 2, 4.1(16)............S-VOL SSUS ASYNC 16, ----- d5
This requires Raid Manager instance.
Regards.
Sanjay
In case of Business copy XP or Continuous Access XP always use the following command to determine the correct TID and LU#.
# raidscan -p port -fx
Sample output of above command is given below
Port TID LU#CU LDEV
CL1-H / da/ 7, 2, 3.1(6).............S-VOL SSUS ASYNC 6, ----- d4
CL1-H / da/ 7, 2, 4.1(16)............S-VOL SSUS ASYNC 16, ----- d5
This requires Raid Manager instance.
Regards.
Sanjay
A rigid mind is very sure, but often wrong. A flexible mind is generally unsure, but often right.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-16-2003 05:01 PM
тАО12-16-2003 05:01 PM
Re: Business Copy XP
To add further to my reply:
1st line: TID = 2, LU#=3
2nd line: TID = 2, LU#=4
Thanks
1st line: TID = 2, LU#=3
2nd line: TID = 2, LU#=4
Thanks
A rigid mind is very sure, but often wrong. A flexible mind is generally unsure, but often right.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2003 02:10 PM
тАО12-22-2003 02:10 PM
Re: Business Copy XP
Just continue the sequence using Target '16'.
Regards, Maurice.
ESC Team
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