- Install Fibre Channel HBAs in all systems
- Install EMC CLARiiON LP8000 port driver ( For Emulex) on all system
- Connect each host to both switches ( Broace/Cisco/McData)
- Connect SP1-A and SP2-A to the first switch
- Connect SP1-B and SP2-B to the second switch
- Note:- You can use cross SP connection for HA and connect SPA1 and SPB1 to first switch and SPB2 and SPA2 to the second switch.
- Install Operating System on windows/solaris/linux/Vmware hosts
- Connect all hosts to the Ethernet LAN
- Install EMC CLARiiON Agent Configurator/Navisphere Agent on all hosts
- Install EMC CLARiiON ATF software on all hosts if you are not using EMC powerpath fail-over software otherwise install supported version EMC Powerpath on all hosts.
- Install the Navisphere Manager on one of the NT hosts
- Configure Storage Groups using the Navisphere Manager
- Assign Storage groups to hosts as dedicated storage/Cluster/Shared Storage
- Install cluster software on host.
- Test the cluster for node failover
- Create Raid Group with protection as application required(raid5,raid1/0 etc)
- Bind LUN according to application device layout requirement.
- Add LUN to storage Group.
- Zone SP port and Host HBA on both switch
- Register Host on CLARiiON using Navisphere Manager.
- Add all hosts to storage group.
- Scan the devices on host.
- Label and Format the device on host.
Tier "0" is not new in storage market but for implementation purposes it has been difficult to accommodate because it requires best performance and lowest latency. Enterprise Flash disks (Solid State Disks) capable to meet this requirement. It is possible to get more performance for company most critical applications. The performance can be gained through using Flash drives supported in VMAX and DMX-4 systems. Read More →
RAID Virtual Architecture (RVA) - Enginuity 5874 introduces a new RAID implementation infrastructure. This enhancement increases configuration options in SRDF environments by reducing the number of mirror positions for RAID 1 and RAID 5 devices. This enhancement also provides additional configuration options, for example, allowing LUN migrations in a Concurrent or Cascaded SRDF environment. Large Volume Support Enginuity 5874 increases the maximum volume size to approximately 240 GB for open systems environments and 223 GB for mainframe environments.
512 Hyper Volumes per Physical Drive: - Enginuity 5874 supports up to 512 hyper volumes on a single drive, twice as much as Enginuity 5773. Customers can improve flexibility and capacity utilization by configuring more granular volumes that more closely meet their space requirements and leave less space unused. Autoprovisioning Groups Autoprovisioning Groups reduce the complexity of Symmetrix device masking by allowing the creation of groups of host initiators, front-end ports and storage volumes. This provides the ability to mask storage to multiple paths instead of one path at a time, reducing the time required and potential for error for consolidated and virtualized server environments. Concurrent Provisioning and Scripts Concurrent configuration changes provide the ability to run scripts concurrently instead of serially, improving system management efficiency. Uses for concurrent configuration changes include parallel device mapping, unmapping, metavolume form and dissolve from different hosts.
Dynamic Provisioning Enhancements: - Dynamic configuration changes allow the dynamic setting of the BCV and dynamic SRDF device attributes and decrease the impact to hosts I/O during the corresponding configuration manager operations.
New Management Integration: - With Enginuity 5874, the Symmetrix Management Console (SMC) and SMI-S provider are available on the Symmetrix system's Service Processor. This frees host resources and simplifies Symmetrix system management; by attaching the Service Processor to a customer network, the customer can open SMC and manage the Symmetrix system from anywhere in their enterprise.
Enhanced Virtual LUN :- With Enginuity 5874, Virtual LUN technology provides the ability to nondisruptively change the physical location on disk, and/or the protection type of Symmetrix logical volumes and allows the migration of open systems, Mainframe and System i volumes to unallocated storage or to existing volumes. Organizations can respond more easily to changing business requirements when using tiered storage in the array.
Enhanced Virtual Provisioning:- Draining With Enginuity 5874, Virtual Provisioning support for draining of data devices allows the nondisruptive removal of one or more data devices from a thin device pool, without losing the data that belongs to the thin devices. This feature allows for improved capacity utilization.Enhanced Virtual Provisioning: Support for all RAID Types with Enginuity 5874, Virtual Provisioning no longer restricts RAID 5 data devices. Virtual Provisioning now supports all data device RAID types.
Veritas Disk Group Configuration Guidelines:-
1) Use multiple Disk Groups—preferably a minimum of four; place the DATA, REDO, TEMP, UNDO, and FRA archive logs in different (separate) Veritas Disk Groups
2) Optimally, use RAID 1 for tier 1 storage
3) Configure Disk Groups so that each contains LUNs of the same size and performance characteristics
Distribute Veritas Disk Group members over as many spindles as is practical for the site’s configuration and operational needs
Data Striping and Load Balancing:-
1) Veritas software level striping: layout=stripe ncols=10 stripeunit=128k
2) Storage-level striping further parallelizes the individual I/O requests within storage
3) Using the storage RAID protection, the amount of I/O traffic (host to storage) is reduced
4) EMC PowerPath should be used for load balancing and path failover
5) Use of metavolumes is optional
a) There is an upper limit on the number of LUNs that a host can address—typically ranging from 256 to 1,024 per HBA.b) When these limits are reached, metavolumes are a convenient way to access more Symmetrix hypervolume.
Volume Configuration with Veritas (Hypervolumes):
1) Created 5 Veritas Disk Groups
2) Five Disk Groups are used because this number provides better granularity for performance planning
3) The use of five Disk Groups also provides increased flexibility when planning for the utilization of EMC replication technology within the context of an enterprise-scale workload
4) Having five Disk Groups permits the placement of data onto different storage tiers if desired
Average Disk Utilization for Raid 1 should be below 150 IOPS per disk and should not go above 200 IOPS per disk as per below configuration.
-- 80 physical disks (40 mirrored pairs)
-- 240 devices visible to Veritas-- Average user count ~ 16,000