- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: FC60 and Binding Disks.
Disk Enclosures
1748124
Members
3250
Online
108758
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
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
тАО07-05-2001 06:40 AM
тАО07-05-2001 06:40 AM
FC60 and Binding Disks.
I have installed 3 new disks to create a new LUN (FC60-SC10), I have 2 disk array controllers, does it matter what controller I select to bind these LUN's????
In SAM...
a) Select Disks & File Systems
b) Disk Devices
c) Select Controller
i) Actions
ii) Disk Array Maintenance
iii) Bind LUN
In SAM...
a) Select Disks & File Systems
b) Disk Devices
c) Select Controller
i) Actions
ii) Disk Array Maintenance
iii) Bind LUN
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2001 06:44 AM
тАО07-05-2001 06:44 AM
Re: FC60 and Binding Disks.
This has bothered me a bit too. This array is not like the FC30 where you will get a penalty by accessing through the non owning controller. I have noticed no significant performance decrease doing it. What is more important is to access some luns through the A controller and some through the B, but not all through A etc.. configuring the alternate links and getting a bottleneck on failure is only temporary. In either case I'd recommend just to be on the safe side to access through the controller that you bind it with.
Later,
Bill
Later,
Bill
It works for me (tm)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2001 07:58 AM
тАО07-05-2001 07:58 AM
Re: FC60 and Binding Disks.
This is what I found.
To ensure optimum performance, LUN ownership should be balanced between controllers.
This ensures that one controller is not overloaded with I/O requests, while the other is idle.
In the mean time, please notice this in line below.
The primary I/O path established using LVM defines the owning controller for the LUN.
This may override the controller ownership defined when the LUN was bound.
So, My answer for your question is that it doesn't matter what controller you select to bind LUN.
Because you can change controller ownership on an existing LUN with LVM without impacting operation.
Because if controller A was identified as the owning controller when the LUN was bound, and
LVM subsequently established the primary path to the LUN through controller B, controller B becomes the owning controller.
Hope this helps,
In-Su,
To ensure optimum performance, LUN ownership should be balanced between controllers.
This ensures that one controller is not overloaded with I/O requests, while the other is idle.
In the mean time, please notice this in line below.
The primary I/O path established using LVM defines the owning controller for the LUN.
This may override the controller ownership defined when the LUN was bound.
So, My answer for your question is that it doesn't matter what controller you select to bind LUN.
Because you can change controller ownership on an existing LUN with LVM without impacting operation.
Because if controller A was identified as the owning controller when the LUN was bound, and
LVM subsequently established the primary path to the LUN through controller B, controller B becomes the owning controller.
Hope this helps,
In-Su,
Never say "no" first.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2001 04:59 AM
тАО07-09-2001 04:59 AM
Re: FC60 and Binding Disks.
The solution I have found was doing the work from the command line instead of SAM. I also noticed a patch various patch releases for SAM and LVM that have not been applied.
amcfg -L A:4 -d 1:2,3:2,5:2 -r 5 000800A0B807A858
amcfg -L A:4 -d 1:2,3:2,5:2 -r 5 000800A0B807A858
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