Mod 1

This module focuses on qualifying the existing SAN configuration and documenting
everything contained in the environment.
Copyright 2012 EMC Corporation. All rights reserved
Module 1: Documentation
This is an overview of the tasks that are involved in setting up a host to communicate with
storage in a Storage Area Network (SAN). The next modules focus on various aspects of this
roadmap. These tasks are Host configuration - OS modifications, Volume Management,
Filesystems, and Multipathing, SAN Configuration - Fabric and HBA configuration and Storage
Array configuration.
This lesson covers tools to qualify and analyze the current SAN configuration.
Qualification of the environment is an important step to setting up a trouble free SAN

environment. Every component of the SAN is manufactured and maintained by a different
vendor, and it is important that the vendors guidelines be adhered to when attaching that
component to another vendor component.
EMC open systems support matrix is a commonly used document that lists all the supported
versions of components that can be plugged into an EMC supported SAN. If a version is not
listed as supported, it may have to be qualified as a one-off.
When reviewing the host OS you must validate that the correct patch level and OS code is
installed. Each OS has a set of commands or GUI windows to view the current configuration.
Tools like EMC Grab utilities are useful for gathering this data and verifying before the
implementation begins.
Be aware of unsupported patches, applications, and drivers. Verify the interoperability of the
host with all appropriate EMC Support Matrix information. Using tools like EMC Reports and
SAN Advisor can be helpful in larger environments since these tools visually flag misconfigurations.
Most installations, regardless of the types of HBAs theyre using (Fibre Channel, iSCSI, CNA)
require two HBAs per host to make use of multipathing and failover.
Whenever possible, HBAs should be installed to make use of hardware redundancy on the
host. For example, if a host has multiple I/O boards, each HBA should be installed on a
different I/O board. This is so that a failing I/O board allows the host to access storage using
the other path. Of course, this assumes the proper multipathing software is installed on the
host.
Most hardware and OS probes detect the presence of new cards when the host is booted up
for the first time with the HBAs installed. For example, Emulex HBAs display the hardware
model and firmware revision of each HBA during system boot.
Common AIX commands for gathering data:
lsattr El sys0 a modelname Hardware make and model

oslevel - OS version, release, maintenance level
lsdev -Cc adapter | grep fcs - look for installed HBAs
lscfg -vl fcs# - Gather information on each HBA
Common HP-UX commands for gathering data:
uname -a
swlist -l bundle - OS version and release
swlist | grep -i bundle - Patches in the OS.
ls /dev | egrep "fcd|td" - Look for HBA instance in host, fcd, td are the two types of
HBAs.
fcmsutil /dev/td# vpd - Gather vital product data for HBA (part number, model).
fcmsutil /dev/td0 - Gather HBA info such as WWN.
swlist | grep <HBA Model> - Check driver version for HBA, driver model is gathered
two steps above.
swlist -l product | egrep -i "vrts|lvm" - Check the type of lvm installed and version
etc.
Common Solaris commands for gathering data:
uname -a
patchadd -p | egrep "119130|120222" - This are patches required for leadville driver,
this is explained in host config module.
fcinfo hba-port - All the information on all the HBAs installed

pkginfo SUNWiscsiu SUNWiscsir - Check packages for iSCSI, this is explained in host
config module.
10
Common LINUX commands for gathering data:
uname -a
lspci | grep "Fibre Channel" - Verify HBA is installed
lvm version
11
Most data in Windows hosts can be gathered from within Server Manager. To open it, rightclick My Computer > Manage. The Server Summary is listed with Computer Information,
Security Information, Roles Summary and Features Summary. On the right side notice you
can access Device Manager, Configure Services, Users, Firewall etc. and Manage your
Storage. Another good source of information is System properties, within the Control Panel.
Alternatively you can use common Windows tools for gathering data such as:
winver - Command for Windows version

Device Manager - SCSI RAID controller to check HBA
Control Panel - Verify iSCSI initiator is installed in Control Panel
12
Use VMware infrastructure, log into the hosts and do the following:
From Summary, check number of VMs, make, model, processor, memory, etc.
From Configuration, check the licenses.
Verify HBAs are installed from Storage Adapters in Configuration, get their WWN.
Verify iSCSI software initiator is installed.
From the CLI, log in and check proc/scsi directory to see what HBA brand is installed. In our
example notice we have lpfc which tells us we have an Emulex HBA. We can also see
qla4010, the qlaxxx represents QLogic. In this case the 4010 is an iSCSI HBA installed in the
system.
Every SCSI device is assigned a number, when we list the files in lpfc directory we see the two
HBAs are numbered 3 and 4. When the file is opened, the model, speed, serial number,
firmware level and WWNs are displayed. The file also contains link status, if the link is up it
provides information on what its connected to.
13
Qualify and verify the micron level of all cables within the solutions. In some scenarios and
environments, corners may have been cut in order to save cost. 50 to 62 micron cables may
not be compatible in your environment and may require re-wiring. Test all cabling to avoid
frustration during implementation time.
Many customers use patch panels to manage their long-run cabling. Verify that the panel is
labeled correctly and the connections are operating properly. Be aware of the dB loss that
can occur by using multiple patch panels, degrading the signal and causing potential
problems for negotiation or data exchange.
14
The physical installation and the initial configuration of the array and switches are performed
by different groups. These details are not covered in this course.
15
It is important to have consistent system configuration settings since inconsistent parameters

amongst switches in the same fabric can cause fabric segmentation. Each switch in a multiswitch fabric is identified by a unique Domain ID, in the range 1 through 239. Domain IDs are
used in 24-bit Fibre Channel addresses to identify source and destination ports in a fabric.
When adding a new switch, assign it a Preferred Domain ID that is not in use. When the
switch comes online, it requests that it be assigned this ID. If the ID is already in use, the
principal switch assigns an unused one.
To change a Domain ID, a switch must be taken off line. Some HBAs can manage a Domain ID
change without requiring device driver administration changes. In some operating
environments, however (for example HP-UX and AIX), drivers may require device driver-level
administrative changes when the Domain ID is changed.
If two operational fabrics join, they determine if any Domain ID conflicts exist between the
fabrics. If a conflict exists, the interswitch link (ISL) E_Ports segment themselves from each
other, preventing the fabrics from joining. To avoid this problem, assign a unique Preferred
Domain ID to each switch in a data center. If there are plans to go data center to data center,
apply this uniqueness across both data centers. This facilitates future fabric mergers, and is
particularly important if zoning is implemented through port number (and by default Domain
ID) rather than WWN.
Poor documentation or miscommunications on switch configuration can add time and result
in unplanned outages during the implementation.
16
When preparing to implement a SAN, a list of all hardware and software components must
be generated. These components may require licenses that the customer must secure.
Features such as FCIP, Routing Services, Extension, application or feature sets often are
licensed for installation and use. Many components offer limited time try and buy licenses.
These license keys allow the installation and function of the product however they expire
after a relatively short time resulting in customer call-backs to the implementation team.
Always confirm the applications and features to be used and determine if licensing is
required. Develop and deliver a list to the customer of any outstanding licenses needed and
explain the ramifications of not securing a full and legal license prior to the implementation.
17
Standard telnet connections allow you to run various reports to help with data and
performance analysis. The captured data files (txt format) may be uploaded to SWAT which
will perform an analysis and deliver a report to you in HTML and XML formats.
Common commands useful in data collection include:
B-Series
switchshow
ipaddrshow
Firmwareshow
MDS Series
Show version
Show running-config
Show ip interface
Show hardware
18
A network link is said to be congested if contention for it causes queues to build up and
packets start getting dropped. The TCP protocol detects these dropped packets and starts
retransmitting them , but using aggressive retransmissions to compensate for packet loss
tends to keep systems in a state of network congestion even after the initial load has been
reduced to a level which would not normally have induced network congestion. In this
situation, demand for link bandwidth (and eventually queue space), outstrips what is
available.
When congestion occurs, all the flows that detect it must reduce their transmission rate. If
they do not do so, the network remains in an unstable state with queues continuing to build
up.
Proper data collection and assessment reduces connectivity issues during the
implementation.
19
Security attacks against SANs are similar to security attacks against IP networks. Breaches of
security can include breaches of authorization, authentication, data confidentiality, and/or
data integrity. When implementing a SAN the team may discover products, configurations or
policies that are in place to secure the environment but that affect the implementation of
the SAN. This disruption may be an inability to access a resource due to card key access,
security access, or policies around access times and procedures to secure that access. The
result is additional time must be added to the implementation that was not defined during
the planning stage.
Applications such as RSA Key Manager, or security protocols such as CHAP or IPSec may
already be in place. Authentication is a key resource for security minded customers and they
may have already begun to secure their network environment against unauthorized attacks.
Without knowledge of these tools, the designer or Project Manager has to modify the
implementation teams schedule to accommodate access grants or escorted access to the
resources.
These are just a few of the issues that could arise if security systems have been put in place
before implementation.
20
This lesson covered tools to qualify and analyze the current SAN configuration.
21
This lesson covers the tools used to validate a SAN and the use of different Procedure
Generators.
22
There are many tools to gather data and develop a baseline for performance. EMC maintains
tools to help in the data gathering phase at https://elabadvisor.emc.com.
Connectrix Manager - Identifies over-utilized ports. Performance Manager license is
required.
Data Center Network Manager with Server license - Long term historical Fibre Channel
performance monitoring and reporting Centralizes MDS Management. The license is offered
in the form of a temporary license for a grace period of 120 days by enabling this feature on
the switch.
23
CAP 2 is an analysis and report generation tool which utilizes SP Collects as a primary source
of data. Reports are generated from data contained in SP Collects and stored in an XML file.
The XML reports can be opened in either CAP or in most modern web browsers. The use of
XML also allows further cross compatibility with other software that may be able to use the
data, for example another spreadsheet application capable of reading XML.
24
Some useful native tools for unix and linux hosts are iostat and sar.
The iostat utility iteratively reports terminal, disk, and tape I/O activity, as well as CPU
utilization. The first line of output is for all time since boot; each subsequent line is for the
prior interval only.
vmstat reports information about processes, memory, paging, block IO, traps, and cpu
activity.
The sar command writes to standard output the contents of selected cumulative activity
counters in the operating system.
Windows 2008 and above have Windows Performance Monitor. You can use Performance
Monitor to examine how programs you run affect your computer's performance, both in real
time and by collecting log data for later analysis.
Windows Performance Monitor uses performance counters, event trace data, and
configuration information, which can be combined into Data Collector Sets.
25
EMC E-Lab Advisor website can be found at: https://elabadvisor.emc.com

This website allows you to download EMCGrab and EMCReports for host data collection and
CAP2 for CLARiiON data collection. Under the Analysis tools it provides HEAT and VMHEAT, to
examine the host collections performed by the programs mentioned before. It also allows a
switch analysis tool SWAT and WWN Decoder/Encoder utility. This website is for internal
employees only but customers can ask for EMCGrab and EMCReports and run it in their
hosts.
26
EMC provides a switch analysis tool which analyzes data collected on M-Model, B-Series and
MDS-Series switches.
For B-Series switches telnet to your switch and run the command supportsave. This
command will upload the information through FTP or SCP to your specified location.
For MDS-Series switches telnet to your switch and run the command show tech-support
details, make sure to copy the output to a specified location.
After the switch information is gathered, go to E-Lab Advisor and upload your supportsave
or show tech-support details file.
27
EMC has several Procedure generators to create documents with step by step procedures to
install, configure, and maintain EMC systems. These are useful and often required for
implementation teams. Additionally these tools can be used to verify installed systems and
provide checklists of points in the system to collect data.
Here we see the Connectrix Procedure Generator. The Connectrix Procedure Generator helps
guides users through Brocade and Cisco FRU Replacements, and Upgrading Firmware.
Senior EMC management mandates use of Procedure Generators for all activities. In
addition, most procedures are only available from the Procedure Generator.
28
E-Lab Interoperability Navigator allows you to input your desired configuration and outputs
the problems and recommendations according to EMC Support and Interoperability
Matrices. You can review the individual components with this tool by selecting the
component family on the left of the application and drilling down to the specific object.
As you select the components, they are added to the right side in the same way as a
shopping cart works on many internet sites. When you select Get Results, the database
engine searches the entire support matrix and places documents and portions of documents
with relative information on the right side of the screen.
You can download these documents in PDF format to review.
29
This lesson covered the tools used for validating SAN components and how to use Procedure
Generators.
30
This lesson covers validation documents such as Configuration Guide and Test and
Acceptance Plan. It also covers configuration for switch, host, and storage arrays.
31
For the most up-to-date information, always consult the EMC Support Matrix (ESM),
available through E-Lab Interoperability Navigator (ELN), at: http://elabnavigator.EMC.com,
under the PDFs and Guides tab.
Also refer to the EMC Networked Storage Topology Guide, available Powerlink, which
provides a top-down view of networked storage and assists the network designer in
designing a suitable networked storage infrastructure. The EMC Networked Storage Topology
Guide provides best practices for Storage Networking Technologies that are created through
E-Lab interoperability and integration testing and authored by E-Lab engineers and product
content experts.
Documentation and release notes can be found on http://Powerlink.EMC.com. From the

toolbar, select Support > Technical Documentation and Advisories, then choose the
appropriate Hardware/Platforms, Software, or Host Connectivity/HBAs documentation links.
32
Creating and maintaining a core set of documents that may be customized for individual
setups allows central control over the legal and financial aspects of service offerings. These
documents are based on financial rules and requirements and are able to be justified based
on time, billable rates, and other factors.
Project Plan A list of tasks, milestones and timelines.
Level of Effort Estimator Determine effort by task and labor required to perform an
engagement.
Configuration Guide A complete representation of the customer environment design. This
document is completed during/after service and a signed copy left with the customer.
Statement of Work (SOW) Details the specific tasks to be performed for the project.
Test and Acceptance Plan A set of tests to confirm the implementation was performed
properly.
EMC Assessment for SANs Final Report The final report is the final deliverable for an
assessment engagement
33
Project Plans are designed to be used by the internal Project Managers as a foundation to
build a customized Project Plan for an engagement. The Project Plan is used to manage EMC
projects including tracking tasks, timelines, milestones, and completion status. Once
completed, it may also serve as a communication vehicle with the customer.
Benefits:
Standardized format to correspond to the Work Breakdown Structure (WBS) steps

Can be printed as a customer deliverable
Corresponds to the WBS steps
Serves as a foundation
Provides content to build customized Project Plan for your engagement
34
The level of effort estimator includes two tabs:

Start Here Effort Estimator This tab has many questions about quantities for your
implementation, they are divided into:
Basic Tips
Level of Effort Estimates List of roles, project members, man-hours for roles.
Additional Cost Considerations Add additional work, hours and price.
Scope Variables To increase or decrease time of engagement.
Other Engagement / Environment Factors Can add new hours/percentages.
WBS (Work Breakdown Structure). The WBS is generated based on the input in the effort
estimator.
35
The Configuration Guide is intended to be used as a customer deliverable used to record

target system design parameters and the actual configuration parameters made during the
engagement.
It includes sign-off blocks for customer approval of proposed system design configuration.
Used to capture specific details for the engagement

Content can be used to input into other Configuration Guides
Excel-based Tool
Includes Custom Toolbar buttons for

Automatically adding/updating the customer name and/or date throughout the
workbook, including footers.
Inserting a portrait, landscape tab, or text box.
Updating the TOC for a quick list of all tabs.
This is an External Document that can be given to the customer for signoff.
Configuration Design/Plan Agreement (initial sign-off)
Configuration Design/Plan Documentation Approval (final sign-off)
Target Audience: SAs, ISs, Partners, Customers
36
The Storage Layout page in the Configuration Guide is a listing of all the settings and
parameters of the storage array. This can be used during the design phase to instruct the
implementation team on how to specifically configure the array to meet the planned design.
There are separate pages for CLARiiON and Symmetrix.
37
Another example from the Configuration Guide, the Switch Information page is a full listing
of switch parameters and configuration. It may be used to document the existing devices or
to indicate the new switch configuration. It is essential that you document the entire SAN for
the implementation team.
38
A Statement of Work contains a detailed description of the specific services or tasks required
to perform to meet the terms in a service contract. The Statement of Work should include all
aspects of job requirements, performance and assessment. A Full SOW has eight main
sections and depending on the variant, they are included or excluded.
Sections of the SOW
The parties to the contract (EMC and Customer) are identified in the Introduction and all
discussion in the document is now clearly defined as between those parties.
The Background section allows the user to identify and technical background for why this
engagement is taking place and what objectives it will cover. These objectives are often
linked directly to milestones in the payment section. Objectives are optional and this section
is removed if no none are specified.
Project Documents lists the deliverable documents to the customer. Engagement objects
such as Project Plans and CCA tickets are never listed as they are internal documents not
intended for a customer. Often the customer sees the Project Plan but EMC does not make
this a required document which would affect payment. This section is removed if no Project
Documents are specified.
Project Staffing is a list of generic duties performed by that personnel. This section is
removed if no positions are specified.
Fees and Payment lists how EMC will be paid. There are several methods of payment open to
the user, some are required by a specific engagement type or service.
39
The Test and Acceptance Plan is used to record EMC-defined testing criteria to ensure the
service was performed successfully. It includes sign-off blocks for customer approval of the
proposed testing criteria, and post-test implementation acceptance.
Document Content:
Product Demonstration Agreement

Sign-off agreeing that the documented tests adequately test the implementation.
EMC-Developed Tests
One or more tables containing tests developed by EMC that are specific to the
implementation.
Each test is clearly delineated within the table.
Customer-Developed Tests
Field Input, if necessary
Omitted for fixed-price services
Product Demonstration Approval

Final sign-off once the engagement is complete.
This is an External Document given to the customer for signoff
Intended Audience: SAs, ISs, Partners, Customers
40
The final report is the final deliverable for an assessment engagement. The Final Report
includes an assessment of the following components:
Current SAN infrastructure and software components.
Performance Data collected on a per port basis.
Predictive bandwidth analysis based on customer needs looking forward 6 months, 1 year.
Fan-in Fan-out ratios.
EMC E-Lab and best practice. Current infrastructure component and application revision
levels installed.
Current business continuance staff resources.

Existing or planned business continuance policies, procedures or requirements, and service
level agreements.
This Final Report is organized into the following main sections:
Introduction
Executive Summary
Assessment Overview
Assessment Findings and Observations
Assessment Recommendations
Implementation Plans and Next Steps
41
This lesson covered documents such as the Configuration Guide, Test and Acceptance plan
and different configuration for switch host and storage arrays.
42
The purpose of this lab is to qualify all SAN-related components.
43
This module covered how to qualify the existing SAN configuration and documenting
everything contained in the environment.
44

Mod 1

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Mod 1

Hochgeladen von

Copyright:

Verfügbare Formate

This module focuses on qualifying the existing SAN configuration and documenting

everything contained in the environment.

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Qualification of the environment is an important step to setting up a trouble free SAN

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Common AIX commands for gathering data:

lsattr El sys0 a modelname Hardware make and model

Copyright 2012 EMC Corporation. All rights reserved

Common HP-UX commands for gathering data:

Copyright 2012 EMC Corporation. All rights reserved

Common Solaris commands for gathering data:

fcinfo hba-port - All the information on all the HBAs installed

Copyright 2012 EMC Corporation. All rights reserved

Common LINUX commands for gathering data:

Copyright 2012 EMC Corporation. All rights reserved

winver - Command for Windows version

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

It is important to have consistent system configuration settings since inconsistent parameters

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

EMC E-Lab Advisor website can be found at: https://elabadvisor.emc.com

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Documentation and release notes can be found on http://Powerlink.EMC.com. From the

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Standardized format to correspond to the Work Breakdown Structure (WBS) steps

Copyright 2012 EMC Corporation. All rights reserved

The level of effort estimator includes two tabs:

Copyright 2012 EMC Corporation. All rights reserved

The Configuration Guide is intended to be used as a customer deliverable used to record

Used to capture specific details for the engagement

Includes Custom Toolbar buttons for

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved

Product Demonstration Agreement

Product Demonstration Approval

Copyright 2012 EMC Corporation. All rights reserved

Current business continuance staff resources.

Copyright 2012 EMC Corporation. All rights reserved

Copyright 2012 EMC Corporation. All rights reserved