- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- EVA 4400: one or two disk groups?
HPE EVA Storage
1752277
Members
4777
Online
108786
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
тАО05-20-2009 03:48 AM
тАО05-20-2009 03:48 AM
Re: EVA 4400: one or two disk groups?
Zoning is not so much used for 'security' - it is for isolation of ports, for example to prevent server FC adapters from talking to each other or receiving unnecessary update information (RSCNs) from the Fibre Channel switches.
Separate fabrics are used to create different failure domains. It will also reduce the number of 'redundant' paths - I beleive it is not really necessary to have 8 paths to an EVA 4400 virtual disk. All these paths will need to be managed by the operating system and in the case of a failure, the OS might waste some time trying many failed paths.
Zones are managed from one switch only and (of course) can span interswitch links [ISLs] - do NOT include those switch ports in the zones.
Yes, it is some work during initial setup, but it allows fine-grained control of access. For example, you can temporarily remove one server from the EVA by changing the zoning -- without making physical changes like unplugging ports.
Use member alias names and be wise when chosing zone/alias names and you even have kind-of 'online documentation'. Since you are using Brocade switches, learn about the "nsaliasshow" command and how it includes member names in the output (I'll put the example in the attachment).
Separate fabrics are used to create different failure domains. It will also reduce the number of 'redundant' paths - I beleive it is not really necessary to have 8 paths to an EVA 4400 virtual disk. All these paths will need to be managed by the operating system and in the case of a failure, the OS might waste some time trying many failed paths.
Zones are managed from one switch only and (of course) can span interswitch links [ISLs] - do NOT include those switch ports in the zones.
Yes, it is some work during initial setup, but it allows fine-grained control of access. For example, you can temporarily remove one server from the EVA by changing the zoning -- without making physical changes like unplugging ports.
Use member alias names and be wise when chosing zone/alias names and you even have kind-of 'online documentation'. Since you are using Brocade switches, learn about the "nsaliasshow" command and how it includes member names in the output (I'll put the example in the attachment).
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-25-2009 05:31 AM
тАО05-25-2009 05:31 AM
Re: EVA 4400: one or two disk groups?
Thank you, Uwe Zessin.
I have some questions.
As i said, i have 24 disks (146 GB). One disk group.
I create four vdisks (200GB, 400GB, 800GB and 900 GB).
1. Every disk is managed by Controller 1. Can i assign Controller 1 for 200 GB and 400 GB and Controller 2 for 800 GB and 900 GB for balancing? How?
2. I see "Alarm level exceeded" for disk group. "Total 2877 GB" and Alarjavascript:postAnswerSubmit('submit');m Level is 90%. There are 98 GB free space for Vraid5. Security level is Single. What does it mean? Necessary two disks (Single level) are already allocated? Or i need to leave 300 GB free space manually?
I have some questions.
As i said, i have 24 disks (146 GB). One disk group.
I create four vdisks (200GB, 400GB, 800GB and 900 GB).
1. Every disk is managed by Controller 1. Can i assign Controller 1 for 200 GB and 400 GB and Controller 2 for 800 GB and 900 GB for balancing? How?
2. I see "Alarm level exceeded" for disk group. "Total 2877 GB" and Alarjavascript:postAnswerSubmit('submit');m Level is 90%. There are 98 GB free space for Vraid5. Security level is Single. What does it mean? Necessary two disks (Single level) are already allocated? Or i need to leave 300 GB free space manually?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-25-2009 05:39 AM
тАО05-25-2009 05:39 AM
Re: EVA 4400: one or two disk groups?
You can set the preferred controller for each vdisk.
- Controller A Failover Only
- Controller B Failover Only
or set "No preference" and let the multipath software device. The EVA4400 is Active/Active, so both controllers and all 4 paths can be used to access a vdisk.
In the disk group you have two lines:
Disk failure protection = Single reserves the space equivalent to 2 x (biggest disk on the disk group). That space cannot be used to create vdisks and is not taken into account in the disk group total space.
Alarm level: This sets a line on the remaining space, if you fill the disk group above that line, the EVA logs an event and shows a warning on the disk group.
- Controller A Failover Only
- Controller B Failover Only
or set "No preference" and let the multipath software device. The EVA4400 is Active/Active, so both controllers and all 4 paths can be used to access a vdisk.
In the disk group you have two lines:
Disk failure protection = Single reserves the space equivalent to 2 x (biggest disk on the disk group). That space cannot be used to create vdisks and is not taken into account in the disk group total space.
Alarm level: This sets a line on the remaining space, if you fill the disk group above that line, the EVA logs an event and shows a warning on the disk group.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-25-2009 06:10 AM
тАО05-25-2009 06:10 AM
Re: EVA 4400: one or two disk groups?
I set "Controller A Failover Only" and "Controller B Failover Only", but in "Presentation" of every Vdisk is "Managing Controller: Controller 1".
If there are no free space and i get alarm - will i have problems?
If there are no free space and i get alarm - will i have problems?
- « 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