Download 01_FC_and_Host_Supported_Configurations_v1

Fibre Channel Supported
Configurations
Switching & Hosts
Network Appliance Confidential
Supported Fibre Channel Configurations
Fibre Channel Switched Fabrics
– Cascade
– Mesh
– Core / Edge
FC Limits
Direct Attached
– FAS200
– FAS3000
– FAS6000
Fabric Attached
– FAS200
– FAS3000
– FAS6000
Zoning – Brocade Example
Network Appliance & VIP Channel Program Confidential
v1.7
2
Design the Fabric for your requirements
Cascade
Cascade Configurations are appropriate
when:
Traffic patterns are localized onto
individual switches
Consider the Fabric Port Count :
The total number of FC ports in the
Fabric, this would include ALL ports on
ALL switches for A fabric, remember that
you have dual fabrics, larger numbers
should mean moving from cascade /
mesh to core-edge
Full
mesh
Mesh Configurations are appropriate
when:
Traffic patterns are evenly distributed
Overall bandwidth consumption is low
The maximum config is four to five
switches
Core-Edge
Core-Edge Configs are appropriate when:
Fabric is likely to grow
A flexible system is required because of
unknown or undefined requirements
Reliability is required – this type of config
has been well-tested and is used in most
production environments
Network Appliance & VIP Channel Program Confidential
v1.7
3
Fabric Scalability
Examples of Fabric Scalability
Scale performance by adding ISLs
or additional core switches
Scale # ISLs
Scale fabric size by
replacing existing
core with a larger core
Scale # Core Switches
Scale fabric size by
adding switches
Network Appliance & VIP Channel Program Confidential
Scale # ports
v1.7
4
Design the Fabric for your requirements
Serviceability using a Dual Fabric Design
 Firmware upgrade can be done without I/O interruption if the
following Rolling Upgrade is applied
– Dual path is required from server and storage
 Add new switches or upgrade current switches easily
1
Storage
2
New
Firmware
Network Appliance & VIP Channel Program Confidential
3
Both Switches
have New
Firmware
Storage
v1.7
Storage
5
Initiator/Target Relationship
HOST (Initiator)
Fabric/Network
Controller (Target)
Fibre Channel HBAs
Windows or UNIX
FC
driver
Application
SCSI over
Fibre Channel
FC
driver
iGroup
File
System
SCSI
driver
iSCSI
driver
iSCSI
driver
TCP/
IP
SCSI over TCP/IP
(iSCSI)
TCP/
IP
WAFL
RAID
Data ONTAP
Fibre Channel or
Serial ATA Attached
iSCSI HBAs or Ethernet NICs
SCSI Adapters
SCSI
LUN
Direct Attached Storage (DAS)
Network Appliance & VIP Channel Program Confidential
v1.7
6
WWNN and WWPN Examples
HBA WWNN (World Wide Node Name)
20:00:00:2b:34:26:a6:54
HBA WWPN (World Wide Port Name)
21:00:00:2b:34:26:a6:54
22:00:00:2b:34:26:a6:54
Network Appliance & VIP Channel Program Confidential
v1.7
7
Fabric or Network Architectures
NetApp supports all industry-accepted fabric
and network architectures.
Types of architectures are:
–
–
–
–
–
Single-Switch
Cascade
Mesh
Core-Edge
Director
Network Appliance & VIP Channel Program Confidential
v1.7
8
Cascade
Maximum hop count supported is three
Network Appliance & VIP Channel Program Confidential
v1.7
9
Mesh
Partial Mesh
Network Appliance & VIP Channel Program Confidential
v1.7
10
Core-Edge
Network Appliance & VIP Channel Program Confidential
v1.7
11
Fabric Choices – What are they?
FC Switch
FC Switch
FC Switch
FC Switch
FC Switch
FC Switch
FC Switch
FC Switch
FC Switch
FC Switch
FC Switch
FC Switch
FC Switch
FC Switch
FC Switch
FC Switch
Network Appliance & VIP Channel Program Confidential
v1.7
12
How many fabrics are show below?
FC_Switch1
FC_Switch2
FC_Switch9
FC_Switch5
FC_Switch6
Network Appliance & VIP Channel Program Confidential
FC_Switch3
FC_Switch4
FC_Switch10
FC_Switch7
v1.7
FC_Switch8
13
Switch Ports
E_Port - An expansion port connecting two switches to
make a fabric.
F_Port - A fabric port to which an N_Port attaches.
FL_Port - A fabric loop port to which a loop attaches; needs
FL card LED turned on. It is the gateway to the fabric for
NL_Ports on a loop.
G_Port - A generic port that supports either E_Port or F_Port
functionality.
L_Port - Node Loop port; a port supporting the Arbitrated
Loop protocol.
N_Port - A fibre channel port in a fabric or point-to-point
connection.
Network Appliance & VIP Channel Program Confidential
v1.7
14
SAN Made Easy – Auto Discovery
U_Port
What do I want to be when
I grow up?
Is something plugged into the port?
y/n
no
yes
FL_Port
y/n
yes
Do you want to talk loop?
no
G_Port
F_Port
fabric
pt-to-pt
I’m waiting for someone to talk to me…
Are you a switch or a fabric point-to-point
device?
switch
E_Port
Network Appliance & VIP Channel Program Confidential
v1.7
15
FC Definitions
 ISL: Inter-Switch Link or a Switch-to-Switch Link; ISLs connect between two switch nodes to form
E_ports.
 Locality: The degree that I/O is confined to a particular switch or segment of a fabric. If two
devices that need to communicate with each other are located on the same switch or segment,
then these two devices are said to have high locality. If these same devices are located on different
switches or segments of a fabric and these two devices need to communicate with each other,
then these devices are said to have low locality.
 Redundancy: When devices have two or more fabrics and multiple paths for a source to reach its
destination the fabric is considered to have redundancy. This is critical so that when an initiator
primary path fails, the secondary initiator path will be available so that initiator hosts can still
communicate with their targets, at reduced performance.
 Resiliency: The ability of a fabric to adapt to or tolerate a failure of a component. A fabric is said
to have resiliency when it can tolerate 1 or more device failures from any component within the
fabric, whether it is a switch, ISL, or HBA failure.
 RSCN: Registered State Change Notification is the fabric mechanism that allows notifications to be
sent to nodes if a change occurs within the fabric, ie. device going offline or online on a fabric port.
 SCR: State Change Registrations are used by devices to register to receive RSCNs.
Network Appliance & VIP Channel Program Confidential
v1.7
16
FC Definitions
 ISL Oversubscription Ratio: Inter-switch Link Oversubscription Ratio is the ratio of
device, or data input ports that might drive I/O between switches to the number of
ISLs over which the traffic could cross.
 ISL Oversubscription = Number of Host Nodes: Number of ISLs, or IO=Nhn:Ni.
 Fan-in ratio: The ratio of storage ports to a single host port
 Fan-out ratio: The ratio of host ports to a single storage port
 Buffer-to-buffer credits: The number of buffer-to-buffer credits determines the
number of Fibre Channel frames that a switch can transmit on a link at one time
before requiring an acknowledgement back from the receiver. Performance
degradation may occur if there aren’t enough credits available to sustain
communication between switches. As the distance between switches increases,
additional buffer-to-buffer credits are required to maintain maximum performance.
Credits are allocated from a common pool of memory on the switch ASIC.
Formula to approximate # of Credits required over long distance:
• Buffer Credits = ((Distance in KM) * (Data Rate) * 1000) / 2112
• Data Rate = 1.0625 Mbaud for 1 Gbit/sec Fibre Channel
• Data Rate = 2.1250 Mbaud for 2 Gbit/sec Fibre Channel
• Data Rate = 4.2500 Mbaud for 4 Gbit/sec Fibre Channel
Network Appliance & VIP Channel Program Confidential
v1.7
17
Best Practice – ISL Oversubscription
 A 7:1 ISL oversubscription ratio is aligned with an industry average of
6:1 fan-out. The trend in the storage industry is that the hosts to storage
ratios are increasing, as is the performance of storage devices. A 7:1 ISL
oversubscription ratio should be targeted in SAN designs, with the ISL
oversubscription ratio being adjusted higher or lower to meet particular
performance requirements. While this ISL oversubscription ratio is
conservative, it is felt that the cost of not having enough performance
and having to reshuffle devices and ISLs is much greater than the cost
of having a few extra spare ports that can be used to connect SAN
devices at a later point in time.
 Rule of thumb: The higher the ISL oversubscription ratio, the lower the
performance and conversely, the lower the ISL oversubscription ratio, the
higher the expected I/O performance. An ISL oversubscription ratio of 3:1
results in high performance and fewer available ports while an ISL
oversubscription ratio of 15:1 results in lower potential performance and
additional available ports reserved for devices. With the advent of 4Gbps
ISLs, higher oversubscription ratios can exist while maintaining more than
adequate bandwidth (since bandwidth is doubled per ISL) and higher device
port counts for 2Gbps devices.
Network Appliance & VIP Channel Program Confidential
v1.7
18
Switch Partnerships &
Support
McDATA
i10K
Additional switches are supported, see Switch Compatibility Matrix
https://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/index.shtml
Director
Typically => 32 ports
McDATA
Intrepid
6140
Fabric Switch
Typically < 32 Ports
Brocade Silkworm 4900
McDATA 4700
Cisco
9216a / 9216i
Cisco 9020
Cisco
MDS 9509
McDATA
Intrepid
6064
Qlogic SANbox
5600
Cisco
MDS 9513
Cisco
MDS 9506
Brocade
Silkworm
48000
Brocade
Silkworm
12000/24000
Cisco MDS9140
McDATA Intrepid 4400
Brocade Silkworm 4100
Brocade Silkworm 200E
Network Appliance & VIP Channel Program Confidential
v1.7
19
FC SAN Host Support
OS
Vendor
HBA
Multipath
Emulex / MPIO NetApp DSM /
MSCS
VERITAS
DSM
for
MPIO*
Qlogic
VERITAS VCS
Emulex /
Native 4Gb
Native
Native
Volume Mgr File System
Host Cluster
MMC /
VERITAS VxVM*
VERITAS VCS /
VERITAS DMP /
VERITAS
Native SUN Cluster*
MPxIO*
VxVM
NTFS
VERITAS
VxFS
JFS/ HFS
HP PVLinks / MC ServiceGuard /
LVM /
Raw
VERITAS DMP
VERITAS VCS VERITAS VxVM
VERITAS VxFS
SANpath /
MPIO
HACMP
LVM
Oracle 9i, 10g RAC /
LVM Under Test
RH Cluster Suite*
QLogic
QLogic
QLogic
QLogic
Oracle 9i, 10g, RAC
QLogic
QLogic
Novell Clusters
Emulex
QLogic
VMware
MSCS
VirtualCenter (VMotion)
JFS/2
Raw
ext3 / ext2 /
Reiser /
GFS*
ext3
ext2
Reiser
NSS
VMware
VMFS 2.x
Raw
* (via PVR)
Always check the support matrix at https://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/index.shtml
Network Appliance & VIP Channel Program Confidential
v1.7
20
Brocade Value Line Licensing
Network Appliance & VIP Channel Program Confidential
v1.7
21
Cable Distance Chart
Network Appliance & VIP Channel Program Confidential
v1.7
22
Cable Management
When designing a cable management strategy the following cable limitations must be
considered:
• Bend radius: Do not violate the minimum bend radius anywhere in the entire path of the cable.
• Shear Force: Any object that has the potential of applying a contact shear force to a cable must be carefully
analyzed. Doors and other moving components should be carefully analyzed to make sure that in all
positions they do not apply a shear force.
• Cable Strain: A good cable design will provide sufficient slack to prevent a significant strain. While this is
often sufficient, the weight of a group of cables hanging without support must be considered. This is
especially a concern if any device exhaust heats the cable. Another case frequently missed is the effect of
doors, sliding patch panels, and moving components.
Violating these rules can result in internal faults in the cable. In some cases this can cause a complete failure of
a cable. Often, faults result in intermittent problems that require a specific cable orientation. This type of fault
can be difficult to isolate and the best resolution for this is preventive maintenance. Use the following guidelines
when planning a cable layout.
Adhere to manufacture recommended bend radius limitation. As a general rule a bend should not have a radius
of less that four inches but each manufacture can provide more precise guidelines for their cable. A common
mistake is to route cables over a 90 degree angle. When loose this does not cause a problem, but if the cables
are pulled taught then a 90 degree bend can occur. Over time this can destroy a cable even if there is only
limited strain.
Network Appliance & VIP Channel Program Confidential
v1.7
23
Cable Best Practices
• Label each end of the cable with a removable label that identifies the source and
destination. Be very careful if zip ties are used. If pulled too tight, severe pressure may
be applied to the cable.
• Bundle cables together in groups of four whenever possible. A bundle is easier to manage.
Bundle the cables with wraps, wire ties, or Velcro every 18 to 24 inches. This can vastly
improve the ability to isolate a bad cable and remove it with minimal impact.
• In a high-density environment, try using a combination of thinner patch cables, patch panels,
and bundled cables. This can be effective in a static environment. Do not design a dynamic
high-density system.
• Use the correct length cable – Minimum FC cable length is 2 meters
• Try to separate ISL cables and device cables.
• Use horizontal guides to route cables to the edge of a rack. Use vertical guides to route
cables to the correct height.
• Do not mix 50 micron and 62.5-micron cables.
• Keep patch panels clean and all ports capped.
• Keep all cables bagged and capped when not in use.
Network Appliance & VIP Channel Program Confidential
v1.7
24
Switch Commands
Network Appliance Confidential
FC switch tools – provided by switch manufacturer
(Brocade)
– switchshow
• Displays status of the FC switch and all its ports
• Show FC nodes currently logged into the switch (depends on FC zones, if
any)
– cfgshow
• Show zones currently available on the FC switch
• Shows information about the current FC configuration and which zone(s)
are enabled
–
–
–
–
–
supportshow: Displays switch information for debugging purposes
ssshow: Displays information about the name server
nsshow: Verifies that clients are logged into the name server
fabricshow: Displays fabric membership information
configure
• Changes switch configuration settings.
• Switch need to be offline to run this command
Network Appliance & VIP Channel Program Confidential
v1.7
26
FC switch tools – provided by manufacturer
(Brocade) (cont.)
– alicreate, zonecreate: Create aliases and zones
– cfgcreate, cfgsave, cfgenable: Manage zone configs
– version: Displays firmware version information
– portshow, portcfgshow, porterrshow,
portLogDumpPort
• Manage ports
– diagshow: Displays switch diagnostics
– webUI: Web GUI available by browsing to the switch ip
adress
– brocade_info (Host based tool provided by Netapp)
• Collects information about configuration of FC switch
Network Appliance & VIP Channel Program Confidential
v1.7
27
FC switch tools – provided by
switch manufacturer (Cisco)
– show tech-support
• Displays system configuration information for Cisco Technical Support
– show fcdomain
• Displays global FC domain information
– show fcdomain domain-list
• Displays list of WWNNs of switches owning each domain ID
– show zoneset <VSAN>
• Displays information for a specific VSAN
– show version
• Displays hardware, software, and web interface version
– Cisco Fabric Manager
• Provides complete suite of GUI tools to manage and monitor the switch
– cisco_info (Host based tool provided by Netapp)
• Collects information about configuration of FC switch
Network Appliance & VIP Channel Program Confidential
v1.7
28
FC switch tools – provided by switch
manufacturer (McData)
– show system: Displays system attributes
– show switch: Displays switch attributes
– show fabric topology/principal: Displays
topology
– show port info: Displays port information
– show zoning: Displays fabric zoning information
– Enterprise Fabric Connectivity Manager
(EFCM)
• Provides complete suite of GUI tools to manage and monitor the
switch
– mcdata_info (Host based tool provided by Netapp)
• Collects information about configuration of FC switch
Network Appliance & VIP Channel Program Confidential
v1.7
29
Switch Zoning
Network Appliance Confidential
Domain on Brocade & Cisco Switches
Make sure that the Domain ID is set to a different
value on all switches in a fabric
Example : if there are two fabrics in solution then the
Domain ID on each switch in Fabric A should be set
to an increasing odd number and for Fabric B set
each Domain ID to an increasing even number
– Fabric A – 11, 13, 15, 17, etc.
– Fabric B – 10, 12, 14, 16, etc.
Note: if HP-UX is involved then skip 8, this ID was used for Loop
Configs
Cisco – Each VSAN should have a unique Domain ID
so each MDS switch will have multiple Domain ID’s
Name Server – service in fabric that provides
directory services and info about ALL devices in the
fabric
Network Appliance & VIP Channel Program Confidential
v1.7
31
VSANs and Domain IDs
Recall: Each VSAN acts as a completely
independent fabric

Domain 105
Domain 223
Domain 126
Domain 153
Domain 173
Each VSAN has its own principle switch
and domain_ID allocation policy (static or
dynamic)
–

Principle switches for different VSANs don’t
have to reside on same physical switch
Domain 110
Domain 153
Domain 112
Domain 171
Domain 156
Domain 102
Domain 113
Domain 180
Each switch will have a separate
domain_ID for each active VSAN
–
–

Domain 100
Domain 200
These domain_IDs can overlap between VSANs
All ports are originally in VSAN1
Each VSAN can have a separate FC_ID
allocation policy (static or dynamic)
Domain 104
Domain 204
MDS9000-overview.ppt
Domain 157
Domain 170
Domain 215
Domain 201
Domain 162
Each switch that has end ports in a particular
VSAN will have a domain_ID assigned that that
particular VSAN. Core switches that trunk these
VSANs will also have assigned domain_IDs in
these VSANs
Network Appliance & VIP Channel Program Confidential
v1.7
32
Define and Implement Zoning
How do I manage Zoning?
 Manage zone physically or Logically
 Three components to the zone information
– One or more devices are placed in a zone
– One or more zones are placed in a configuration
– One and only one config is made the effective
 Soft Zoning: Name Server assisted
– Name Server restricts visibility
– Always available when zoning enabled
– No reduction in performance
 Hard Zoning: Hardware Enforced
– Available when certain rule checking criteria are met through hardware
logic checking.
– Provides additional security in addition to Soft zoning
– Prevents illegal access from “bad” citizens.
– No reduction in performance with hard-Port level zoning.
– Available using port or WWN with Brocade 2 Gbit/sec
Network Appliance & VIP Channel Program Confidential
v1.7
33
Define and Implement Zoning
Zoning Setup Guidelines
 Create a detailed diagram of the fabric, showing all the switches with
their ISLs
 Create a “blowup” diagram of each switch in the fabric to account for
devices
 Account for private loop devices if they exist
 There are special considerations for mixed 1 Gbit/sec and 2Gbit/sec
based fabrics
 For security reasons, consider disabling a port if the zoned fabric is
going to contain unused ports, with nothing connected to them
 Configure one zone at a time and then test it
– Do not create all the zones at once; it will be troublesome to debug
– After the first zone is setup in the fabric, plug in devices and then test the
connections to confirm that everything is functioning properly
– This process may seem a little tedious, but it will save time and money
trying to debug this after creating all the zones and then plugging in the
devices
Network Appliance & VIP Channel Program Confidential
v1.7
34
Define and Implement Zoning
Implementing Zoning
 Naming convention
– There typically of three types of devices, server HBA, the storage port, and
the tape port.
– These will have an alias.
• SRV – for servers
• STO – for Storage
• TPE – for Tape
• For example,
SRV_MAILPROD_SLT5 – a server, hostname “mailprod”, in PCI slot 5
– Keep names as small as possible to conserve space in zone database
– Minimize duplication in alias definitions where possible
– Keep zoning database as clean and accurate as possible
 Fabric Name
– Fabric name is the name that the fabric is generally known by.
– PROD configuration is to easily identify the configuration that can be
implemented and provide the most generic services.
– BACKUP_XX, TEST_XX may be used
Network Appliance & VIP Channel Program Confidential
v1.7
35
Define and Implement Zoning
10 Zoning Rules - Brocade
1) If security is a priority, then a Hard Zone-based architecture
coupled with Hardware Enforcement is recommended
2) Using aliases, though optional, should force some structure
when defining your zones.
3) Add Secure Fabric OS® into the Zone Architecture if extra
security is required.
4) If a SilkWorm 12000 is part of the fabric, then use it to administer
zoning within the Fabric
5) If QuickLoop is required for legacy devices and the switch is
running Brocade Fabric OS v4.x:
– QuickLoop / QuickLoop zones cannot run on switches
running Brocade Fabric OS v4.x.
– QuickLoop Fabric Assist - Brocade Fabric OS v4.x cannot
have a Fabric Assist host directly connected to it.
Network Appliance & VIP Channel Program Confidential
v1.7
36
Define and Implement Zoning
10 Zoning Rules - Brocade
6) Before implementing a zone run the Zone Analyzer and
isolate any possible problems.
7) Before enabling or changing a fabric configuration, verify
that no one is issuing I/O in the zone that will change.
8) Changes to zoning should be done during preventative
maintenance to minimize any potential disruption.
9) After changing or enabling a zone configuration, confirm
that nodes and storage are able to see and access one
another.
10) LUN Masking should be used in conjunction with fabric
zoning for maximum effectiveness.
Network Appliance & VIP Channel Program Confidential
v1.7
37
Zoning Example – Single Fabric
Host2
Host3
Host1
Host4
zone
1
FC Fabric
zone
2
What is needed on the hosts
systems and on which systems is
it needed in this configuration?
FAS270C
Network Appliance & VIP Channel Program Confidential
v1.7
38
CFModes
Network Appliance Confidential
Cluster Failover Mode - CFMode
These define how FCP deals with Filer Cluster
Failover
There are currently five (5):
–
–
–
–
–
Dual Fabric cfmode – FAS270C Only
Partner cfmode
Standby cfmode
Mixed cfmode
Single System Image (SSI) – Covered in Software
presentation on Data ONTAP 7.1 features
View cfmode with:
– fcp show cfmode
Network Appliance & VIP Channel Program Confidential
v1.7
40
Dual Fabric cfmode
Only available on the FAS270C
LUN’s served by the FAS Device are always
accessible from the fibre channel port on either
FASD head in the cluster.
For best performance access of LUN’s should
be made thru the head controlling LUN
Advantages
– Support for all operating systems
– Requires fewer number of switch ports
Disadvantages
– Not supported by all switches because loop mode is
required (McData Enterprise Class Switches)
Network Appliance & VIP Channel Program Confidential
v1.7
41
Partner cfmode
 Default cfmode starting with Data ONTAP 6.5.x
 Available on F8XX, FAS9xx, FAS3020 and FAS3050
solutions
 LUN’s serviced from fibre channel port “A” on FAS
Device serving LUN and thru cluster interconnect to
port “B” on partner FASD
 Advantages
– Support for all operating systems
– Supports all switches
– Easy to manage
 Disadvantages
– Requires more switch ports/wiring since both the A and B
target fibre channel ports need to be connected
Network Appliance & VIP Channel Program Confidential
v1.7
42
Partner cfmode
If Filer X fails, then Filer Y takes over and the following occurs:
No Port Take-Over, All Ports Active
Multipath software
required or Zoning on
switch to allow
supported paths for a
LUN
Host
Primary path should be thru the FAS Device that controls LUN
Secondary path should be over other FAS Device thru cluster
interconnect.
Dual Card per FAS Device
Initiator
HBA’s
Switch / Fabric 1
Switch / Fabric 2
All paths are active.
Solid Lines indicate active
connection used for primary access
Dotted lines indicate active
connections for LUN’s accessed
over cluster interconnect used as
secondary access.
Target
HBA’s
Target
HBA’s
0c
0d
0a
0b
0c
0d
0a
0b
Supported on:
Solaris, Windows, HP-UX, AIX, Linux
RHEL 3.0 and Novell
Controller 2
Controller 1
Dual Controllers – F8xxC, FAS9xxC, FAS3020C, FAS3050C
Network Appliance & VIP Channel Program Confidential
v1.7
43
Available Paths
- Partner Mode
Host
Switch/Fabric 1
Switch/Fabric 2
Solid Blue are paths to
the LUNs being served
by Controller 1
0c
0d
0a
0b
0c
0d
0a
Dashed Purple are
paths to the LUNs
being served by
Controller 2
0b
HA
Configuration
Controller 2
Controller 1
LUNs
Network Appliance & VIP Channel Program Confidential
LUNs
v1.7
44
Standby cfmode
 Available on F8xxC and FAS9xxC series FAS Device
 LUN’s serviced by port “A” on FASD are made
available on port “B” of the partner on failover
 Advantages
– Supports all switches
– Allows multiple active port with the NetApp ASL 2.0 for Veritas
 Disadvantages
– Supports only Sun and Windows environments
– Requires more switch ports/wiring since both the A
and B target fibre channel ports need to be connected
– Require a minimum of two FC target cards per filer
Network Appliance & VIP Channel Program Confidential
v1.7
45
Standby cfmode
If Controller 1 fails, then Controller 2 takes over and the following
occurs:
Multipath software
required or Zoning on
switch to allow
supported paths for a
LUN
Host
Port 0b on Controller 2 takes over for Port 0a in Controller 1
Port 0d on Controller 1 takes over for Port 0c in Controller 2
The ports that were standby take over the WWPN of the previous
active ports on the failed FAS Device
Initiator
HBA’s
Switch / Fabric 1
Switch / Fabric 2
Dual Card per FAS Device
Solid Lines indicate active connections
Dotted lines indicate standby
connections.
Target
HBA’s
Only supported on:
Target
HBA’s
0c
0d
0a
0b
0c
0d
0a
0b
Solaris
Windows
Linux RHEL 3.0
Novell
Controller 2
Controller 1
Dual Controllers – F8xxC, FAS9xxC, FAS20X0, FAS30X0A, FAS60X0A
Network Appliance & VIP Channel Program Confidential
v1.7
46
Available Paths
- Standby Mode
Host
Switch/Fabric 1
Switch/Fabric 2
Solid Blue are paths to
the LUNs being served
by Controller 1
0c
0d
0a
0b
0c
0d
0a
Dashed Purple are
paths to the LUNs
being served by
Controller 2
0b
HA
Configuration
Controller
1
Controller 2
LUNs
Network Appliance & VIP Channel Program Confidential
LUNs
v1.7
47
Path Access (Switch Failure)
– Standby Mode
Host
Switch/Fabric 1 will
experience a failure
MP layer works
around the failure
Switch/Fabric 1
Switch/Fabric 2
Solid and Blue are
paths to the LUNs
being served by
Controller 1
0c
0d
0a
0b
0c
0d
0a
0b
Dashed and Purple
are paths to the LUNs
being served by
Controller 2
HA
Configuration
Controller
1
Controller 2
LUNs
Network Appliance & VIP Channel Program Confidential
LUNs
v1.7
48
Path Access (CFO event)
- Standby Mode
Host
Conntroller 1 will
experience a failure
Controller 2 Takes
over all operations
Switch/Fabric 1
Switch/Fabric 2
Solid and Blue are
paths to the LUNs
being served by
Controller 1
0c
0d
0a
0b
0c
0d
0a
0b
Dashed and Purple
are paths to the LUNs
being served by
Controller 2
HA
Configuration
Controller
1
Controller 2
LUNs
Network Appliance & VIP Channel Program Confidential
LUNs
v1.7
49
Path Access (CFO event)
- Standby Mode
Host
Controller 1 will
experience a failure
Switch/Fabric 1
WWN1
0c
Switch/Fabric 2
WWN2 WWN3 WWN4 WWN5
0d
0a
0b
0c
WWN6 WWN7 WWN8
0d
0a
Controller
1
Controller 2
Network Appliance & VIP Channel Program Confidential
Solid and Blue are
paths to the LUNs
being served by
Controller 1
0b
HA
Configuration
LUNs
Filer Head 2 Takes
over all operations
MP layer is not
involved in switchover
Dashed and Purple
are paths to the LUNs
being served by
Controller 2
LUNs
v1.7
50
Mixed cfmode
Available on F8xxC and FAS9xxC series FAS
Device
Equivalent to standby mode for Solaris &
Windows and partner mode for AIX & HP-UX
Virtual Ports are used on the physical A & B
fibre channel ports
Advantages
– Support for all operating systems
– Requires fewer number of ports
Disadvantages
– Not supported by all switches because loop mode is
required
Network Appliance & VIP Channel Program Confidential
v1.7
51
mixed cfmode
Multipath software
required or Zoning on
switch to allow
supported paths for a
LUN
Target logs into fabric as loop device
Host
Virtual Ports per Physical Port
Local
Standby
Initiator
HBA’s
Partner
Switch / Fabric 1
Switch / Fabric 2
Dual Card per FAS Device
This mode allows the use of both Standby and
Partner modes at the same time each having
access over the appropriate Virtual Port
Same rules apply for the Virtual Ports for each
mode
9a
7a
7b
7b
Solaris & Windows – Standby mode
HP-UX & AIX – Partner mode
9a
Target
HBA’s
9b
7a
9b Target
HBA’s
Zoning is required on switches for this mode
Supported on:
FAS X
Clustered FAS – F8xxC or FAS9xxC
FAS Y
Solaris, Windows, HP-UX, AIX, Linux
RHEL 3.0 and Novell
Network Appliance & VIP Channel Program Confidential
v1.7
52
Cfmode Recommendations
 Dual Fabric Mode
– All FAS270C environments until Data ONTAP 7.1
 Partner Mode – RECOMMENDED FOR F8XX or FAS9XX
or FAS3020 or FAS3050 Series Devices with Data
ONTAP 7.0 or less
 Single System Image – RECOMMENDED for FAS270C,
FAS9XX, FAS3020, FAS3050 solutions with Data
ONTAP 7.1 or greater
 Single System Image – REQUIRED for FAS2020,
FAS2050, FAS3040, FAS3070, FAS6030, FAS6070
solutions
 World Wide Port Name (WWPN) Binding
– WWPN binding is recommended with all cfmodes
– WWNN binding is NOT supported
Network Appliance & VIP Channel Program Confidential
v1.7
53
Direct Attached
FAS270 – Secondary Storage
Host 1
FAS 1 *
FAS270
Host 1
Multipath
software
required
Host 1
FAS 1 / FAS 2
FAS270C




Entry-level unified storage
2Gb Fibre Channel host connectivity
Fully expandable to SAN config
Windows, Linux, Solaris, HP-UX, and AIX
dual-attach multi-pathing support
 Concurrent NAS and FC DAS data access
Network Appliance & VIP Channel Program Confidential
Two Hosts, single attach, dual
controller head (no failover)
Host 2
FAS 1 / FAS 2
FAS270C
Two Host Cluster, single attach, dual
controller head (no controller failover)
v1.7
54
Switched Fabric – Single Switch - Single Head
FAS270 – Secondary Storage
Multipath software
required for all
dual attached
hosts
Host 1
Host 2
Host N
…
FC Fabric 1
FAS 1
FAS270
Network Appliance & VIP Channel Program Confidential
v1.7
55
Switched Fabric – Single Switch - Dual Head
FAS270C – Primary or Secondary Storage
Multipath software
required or fabric
zoning is required
to avoid multiple
paths
Host 1
Host 2
Multipath software
required for all dual
attached hosts
Host N
…
Multipath software
required or fabric
zoning is required to
avoid multiple paths
FC Fabric 1
FAS 1 / FAS 2
FAS270C
Network Appliance & VIP Channel Program Confidential
v1.7
56
Dual Switched Fabric - Dual Head
FAS270C – Primary or Secondary Storage
Multipath software
required for all dual
attached hosts
Host 1
Host 2
Host 3
Host N
…
FC
Fabric 1
FC
Fabric 2
Storage Array failover is
not available with single
attached hosts
FAS 1 / FAS 2
FAS270C
Network Appliance & VIP Channel Program Confidential
v1.7
57
Direct Attached – Single Head - FAS
8xx/FAS9XX/Rxxx - Primary Storage
Host 1
2 Host Cluster
Host 1
Multipath
software
required
2 Host Cluster
FAS 1
F8XX/FAS9XX
NearStore
RXXX
FAS 1
F8XX/FAS9XX
NearStore
RXXX
Multipath
software
required




Mid-level unified storage
2Gb Fibre Channel host connectivity
Fully expandable to SAN config
Windows, Linux, Solaris, HP-UX, and AIX
dual-attach multi-path support
 Concurrent NAS and FC DAS data access
Network Appliance & VIP Channel Program Confidential
FAS 1
F8XX/FAS9XX
NearStore
RXXX
FAS 1
F8XX/FAS9XX
NearStore
RXXX
v1.7
58
Dual Switched Fabric – Dual Head
F8XXC/FAS9XXC - Primary Storage
Multipath software
required or Zoning on
switch to allow
supported paths for a
LUN depending on
cfmode
Host 2
Host 1
Host N
Host 3
…
Initiator
HBA’s
Switch / Fabric 1
Switch / Fabric 2
2 - Dual Cards per FAS Device
CF Mode Supported :
Partner
Standby
Mixed
Cluster Interconnect
Target
HBA’s
7a
7b
9a
9b
7a
FAS 1
7b
9a
9b
Target
HBA’s
FAS 2
F8XXC/FAS9XXC
Network Appliance & VIP Channel Program Confidential
v1.7
59
Dual Switched Fabric – Dual Head
F8XXC/FAS9XXC - Primary Storage
Multipath software
required or Zoning on
switch to allow
supported paths for a
LUN depending on
cfmode
Host 1
Host 2
Host N
Host 3
…
Initiator
HBA’s
Switch / Fabric 1
Switch / Fabric 2
4 - Dual Port Cards per FAS Device
CF Mode Supported :
Partner
Standby
Mixed
5a/b
4a/b
7a/b
7a/b
9a/b
4a/b
5a/b
9a/b
Target
HBA’s
Target
HBA’s
Cluster Interconnect
FAS 1
Network Appliance & VIP Channel Program Confidential
F8XXC/FAS9XXC
v1.7
FAS 2
60
Direct Attached – Single Head –
F8XX/FAS9XX/Rxxx – Secondary Storage
Host 1
Host 2
Host N (max 4)
FAS 1
F8XX/FAS9XX
NearStore RXXX
Host 1
Multipath
software
required
Host 3
FAS 1
F8XX/FAS9XX
NearStore RXXX
Network Appliance & VIP Channel Program Confidential
Host 1
Multipath
software
required both
systems
Host 2
FAS 1
F8XX/FAS9XX
NearStore RXXX
v1.7
61
Switched Fabric – Single Switch
FAS800/900/RXXX – Secondary Storage
Multipath software
required or Zoning
on switch to allow
only one path to a
LUN
Host 1
Host 2
Multipath
software
required
Host N
…
Multipath software
required or Zoning on
switch to allow only
one path to a LUN
FC Fabric 1
1 to 4 connections
4a/b
…
9a/b
Target
HBA’s
CF Mode Supported :
Partner
Standby
Mixed
FAS 1
F8XX/FAS9XX
NearStore RXXX
Network Appliance & VIP Channel Program Confidential
v1.7
62
Switched Fabric – Single Switch –
F8XXC/FAS9XXC – Secondary Storage
Host 1
Host 2
Single Port Card or Dual Port Card using
Multipath
software
required
…
only 1 Port per FASD
CF Mode Supported :
Partner
Standby
Mixed
Host N
Multipath software
required or Zoning
on switch to allow
only one path to a
LUN
Initiator
HBA’s
Multipath software
required or Zoning on
switch to allow only
one path to a LUN
Switch / Fabric
Important:
LUNs can only be served by FAS 1, FAS 2
is inactive until failure of FAS 1.
Connections have to be from port A on
FAS 1 and port B on FAS 2, the HBA
internal to the FAS has to be in the same
slot on both FAS systems
Target
HBA
7a
7b
Target
HBA
Cluster Interconnect
FAS 1
Network Appliance & VIP Channel Program Confidential
F8XXC/FAS9XXC
v1.7
FAS 2
63
Switched Fabric – Single Switch
F8XXC/FAS9XXC – Secondary Storage
Multipath software
required or Zoning
on switch to allow
only one path to a
LUN
Host 1
Host 2
Host N
…
Initiator
HBA’s
Multiple Dual Port Cards per FAS – Max 4
CF Mode Supported :
Multipath
software
required
Switch / Fabric
Partner
Multipath
software required
or Zoning on
switch to allow
only one path to a
LUN
Standby
Mixed
Important:
HBAs internal to the FAS have to be in the
same slot on both FAS systems
Cluster Interconnect
Target
HBA’s
4a/b
…
9a/b
4a/b
FAS 1
…
9a/b
Target
HBA’s
FAS 2
F8XXC/FAS9XXC
Network Appliance & VIP Channel Program Confidential
v1.7
64
Configuration Limits
Parameter
Operating System
Windows
Linux
HP-UX
Solaris
AIX
Target Controller
Ports per System
16
16
16
16
16
LUN’s per System
512
128
512
512
128
Paths per LUN
4
4
8 more possible 16
16
but pvlinks will
only utilize 8
Max LUN Size
2 TB
2 TB
2 TB
1023 GB
1 TB
FCP & iSCSI Configuration Guide:
https://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/QuickRef/fc_iscsi_config_guide.pdf
Network Appliance & VIP Channel Program Confidential
v1.7
65
Configuration Limits
Storage Solutions *
Parameter
FAS270
FAS920
FAS940
FAS960
FAS980
FAS3020
FAS3050
FAS6030
FAS6070
LUNS-Per-Solution
1024
2048
2048
2048
2048
1024
1024
2048
2048
LUN’s Per Volume
1024
2048
2048
2048
2048
1024
1024
2048
2048
Maximum Port Fan-in
16
64
64
64
64
64
64
64
64
Maximum Dual
Controller Fan-in
16
256
256
256
256
256
256
256
256
Igroups per Solution
256
256
256
256
256
256
256
256
256
Number of Initiators
per igroup
256
256
256
256
256
256
256
256
256
Numbers of LUN
mappings per system
4096
4096
8192
8192
8192
4096
4096
8192
8192
Maximum length of
lun path name
255
255
255
255
255
255
255
255
255
Maximum LUN Size
6 TB
4 TB
6 TB
12 TB
12 TB
12 TB
12 TB
12 TB
12 TB
Maximum FC Ports
per Dual Controllers
2
16
16
16
16
8
8
16
16
* All Active – Active Solutions
FCP & iSCSI Configuration Guide: https://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/QuickRef/fc_iscsi_config_guide.pdf
Network Appliance & VIP Channel Program Confidential
v1.7
66
Supported Configurations
NetApp has detailed compatibility matrices available
on the NetApp On the Web (NOW) site with up-todate information on supported
–
–
–
–
–
Operating Systems (OS)
FC switches
HBAs
NetApp Storage Systems
Data ONTAP versions
For supported NetApp storage systems, Data
ONTAP™, switch and/or host combinations, refer to
https://now.netapp.com/NOW/knowledge/docs/san/
fcp_iscsi_config/
Network Appliance & VIP Channel Program Confidential
v1.7
67
Target HBA Comparisons
Onboard Memory
X1028A (
X1033 (
X1088A (
QLA 2342)
2Gb/s
QLA 2352)
2Gb/s
QLA 2462)
4Gb/s
256KB
4MB
4MB
512
2048
2048
256
2048
2048
Maximum
Commands,
Queue Depth
(per card, not port)
Maximum Port
Logins, Maximum
Initiators
Network Appliance & VIP Channel Program Confidential
v1.7
68
Host Configuration Info
LUN Queue Depth – controls the maximum
number of outstanding I/O’s
Authentication between FC Targets and
Initiators – DH-CHAP
Network Appliance & VIP Channel Program Confidential
v1.7
69
Host OS Support
Network Appliance Confidential
SUN™ FCP Host Operating Systems
 Solaris™
– Solaris 8 – Qualified with the following:
• Maintenance Update 7
• Patch cluster dated 10/01/04
– Solaris 9 – Qualified with the following:
• Most recent Solaris patch cluster at http://sunsolve.sun.com/
• For Sun native, see the Sun native section on the FCP/iSCSI
Configuration Matrix for more details.
• See the VERITAS Installation Guide for required OS patches
– Solaris 10 – Qualified with the following:
• Maintenance Update 1
• Hardware Update 2 for 32- and 64-bit
 Note: See the NOW™ site for the most up-to-date information.
https://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_conf
ig/fcp_support.shtml#solaris9
Network Appliance & VIP Channel Program Confidential
v1.7
71
SUN iSCSI Host Operating Systems
Solaris
– Solaris - Software Initiator
• (Solaris 10 Update 1)
– QLogic HBA QLA4010 - Hardware Initiator
• (Solaris 8, 9, 10 Update 1)
Note: See the NOW™ site for the most up-todate information.
https://now.netapp.com/NOW/knowledge/docs/san/
fcp_iscsi_config/iscsi_support_matrix.shtml
Network Appliance & VIP Channel Program Confidential
v1.7
72
Solaris Third-Party Software
Functions such as multipathing and host clustering
require supporting software
–
–
–
–
–
–
VERITAS® Dynamic Multipathing (DMP)
VERITAS Volume Manager (VxVM)
VERITAS Storage Foundation Cluster File System (SFCFS)
VERITAS Storage Foundation for ORACLE RAC (SFOR)
VERITAS Cluster Services (VCS)
VERITAS File System (VxFS)
Note: See the NOW™ site to determine which
version and patches are required
https://now.netapp.com/NOW/knowledge/docs/san/
fcp_iscsi_config/fcp_support.shtml#solaris9
Network Appliance & VIP Channel Program Confidential
v1.7
73
Host Fibre Channel Initiator HBAs (UNIX)
Solaris Attach Kit 3.0 supports Emulex
LP11000, LP11002, LP10000, LP10000DC,
LP9002L, LP9002DC, LP9002C, LP9002S.
For more information on supported HBAs,
refer to the FC SAN Support Matrix.
https://now.netapp.com/NOW/knowledge/doc
s/san/fcp_iscsi_config/fcp_support.shtml
Network Appliance & VIP Channel Program Confidential
v1.7
74
Supported Windows® Hosts
Intel® based
– Windows 2000 Server or Advanced Server with Service Pack 3
or 4
– Windows Server 2003
• Standard Edition (32-bit, x86; 64-bit, x64)
• Enterprise Edition (32-bit, x86; 64-bit, x64)
• Standard or Enterprise Edition SP1 (32-bit, x86; 64-bit, x64)
• R2 (32-bit, x86; 64-bit, x64)
Service Pack requirements vary depending on the
supported function. See the NOW site for more
information at:
https://now.netapp.com/NOW/knowledge/docs/san/
fcp_iscsi_config/fcp_support.shtml#win2000
Network Appliance & VIP Channel Program Confidential
v1.7
75
Supplemental NetApp Software for
Windows
NetApp host-side software
– SnapDrive™ 3.2 R1/4.0/4.1/4.2 for Windows®
• Microsoft® Cluster Services (MSCS) support
– Multipath Input/Output (MPIO) support
– SnapDrive for Windows is required for use with:
• SnapManager® for Exchange
• SnapManager for SQL
Note: See the NOW™ site for current
information and supported configurations at:
https://now.netapp.com/NOW/knowledge/
docs/olio/guides/snapmanager_snapdrive_
compatibility/
Network Appliance & VIP Channel Program Confidential
v1.7
76
Host FC Initiator HBAs (Windows)
Windows Attach Kit 3.0 supports
– Emulex (LP11000, LP11002, LPe11000, LPe11002,
LP10000, LP10000DC, LP9002L, LP9002DC, LP9802)
– QLogic (QLA2460, QLA2462, QLE2460, QLE2462).
– IBM Bladecenter (HS20, HS40, LS20)
For more information, refer to the NOW™ site
at:
https://now.netapp.com/NOW/knowledge/docs/san/
fcp_iscsi_config/fcp_support.shtml#win2003
Network Appliance & VIP Channel Program Confidential
v1.7
77
Storage System Commands
Refer to the Commands: Manual Page
Reference for more information at:
– 6.5(http://now.netapp.com/NOW/knowledge/docs/on
tap/rel656/pdfs/ontap/cmdref.pdf)
– 7.0(http://now.netapp.com/NOW/knowledge/docs/on
tap/rel704/pdfs/ontap/cmdref1.pdf)
– 7.1(http://now.netapp.com/NOW/knowledge/docs/on
tap/rel7101/pdfs/ontap/cmdref1.pdf)
– 7.2(http://now.netapp.com/NOW/knowledge/docs/on
tap/rel72rc/pdfs/ontap/cmdref1.pdf)
Network Appliance & VIP Channel Program Confidential
v1.7
78
Host Utilities
Network Appliance Confidential
Host Utilities
Items that may be included in Host Utilities
include (exact tools and utilities vary by the
host):
– Configuration Tools (UNIX) /Installation Tools
(Windows) - that allow you to configure the HBA,
system files, persistent bindings/checks OS
patches, registry settings
– Diagnostic scripts
– Sanlun
– Documentation (Release Notes, Install Guides,
Quick Reference Guides)
Need to run set_tunables.exe on Windows to
set registry variables
Network Appliance & VIP Channel Program Confidential
v1.7
80
Why to Use Host Utilities
Diagnostic Scripts – Used by Support to diagnose
problems
Documentation – Contains crucial setup information,
known problems
UNIX – sanlun utility - Allows you to manage LUNs
and the host HBA
AIX® – ODM (Object Data Manager) definition –
identifies and sets parameters for NetApp devices
Windows® – set tuneables script – updates registry
and WMI (Windows Management Instrumentation)
values
Network Appliance & VIP Channel Program Confidential
v1.7
81
FC SAN host based tools – provided by
FC Host Utilities Kits
– sanlun
• utility program used to obtain information about LUNs on
host
– filer_info
• collects information about FC configuration of the storage
system
– solaris_info, aix_info, hpux_info,
linux_info, windows_info
• collects information about configuration of host OS
– brocade_info, cisco_info, mcdata_info
• collects information about configuration of FC switch
Network Appliance & VIP Channel Program Confidential
v1.7
82
SnapDrive for UNIX
Create and restore consistent Snapshot™ copies of
one or more volume groups on a storage system.
– snapdrive snap create -vg vg1 -snapname snap1
Rename, restore, or delete a Snapshot™ copy.
– To rename a Snapshot
• snapdrive snap rename -snapname
toaster:/vol/vol1:snap1 bkup40105
– To restore a Snapshot
• snapdrive snap restore -dg vg1 -snapname
toaster:/vol/vol1:bkup40105
– To delete a Snapshot
• snapdrive snap delete
toaster:/vol/vol1:bkup40105
Network Appliance & VIP Channel Program Confidential
v1.7
83
SnapDrive for UNIX
Display information about Snapshot™ copies
created by SnapDrive™.
– snapdrive snap show –snapname
toaster:/vol/vol1:snap1
Display information about which Data ONTAP
LUNs are used for a specific host volume
group, host volume, or file system.
– snapdrive storage show -vg vg1
Network Appliance & VIP Channel Program Confidential
v1.7
84
SnapDrive for UNIX
Connect and Disconnect objects captured by
a Snapshot copy.
– To connect a Snapshot to a different location
• snapdrive snap connect –fs
/db2/datafiles2 /db2_bkup40105
-snapname toaster:/vol/vol1:bkup40105
– To disconnect a Snapshot from a location on a host
• snapdrive snap disconnect -fs
/db2_bkup40105
Create storage on a storage system.
– snapdrive storage create -vg vg1 -lun
toaster:/vol/vol1/lunA lunB lunC -lunsize
100m -fs /db1/datafiles1
Network Appliance & VIP Channel Program Confidential
v1.7
85
SnapDrive for UNIX
Resize or delete storage.
– To resize storage
• snapdrive storage resize -vg vg1 -addlun
–growby 155m
– To delete storage
• snapdrive storage delete -fs /db1/datafiles1
Connect storage to and disconnect storage from the
host.
– To disconnect storage from the host
• snapdrive storage disconnect -lun
toaster:/vol/vol1/lunD
– To connect storage to the host
• snapdrive storage connect –lun
toaster:/vol/vol1/lunD
Network Appliance & VIP Channel Program Confidential
v1.7
86
SnapDrive for Windows
Integrated with Windows® Volume Manager, allowing
storage systems to serve as storage devices for
application data.
Manages LUNs and allows Windows® to interact
with them as if they were directly attached.
Additional features include the following:
– Enables online storage configuration, LUN expansion, and
streamlined management.
– Integrates Snapshot technology to create point-in-time
images of data stored on LUNs.
Aids SnapMirror™ in facilitating disaster recovery.
SnapDrive™ 4.1 and later support both x64 and x86
architectures.
Network Appliance & VIP Channel Program Confidential
v1.7
87
SnapDrive for Windows Multipathing
SnapDrive for Windows multipathing
integrates the NetApp version of the
Microsoft MPIO device-specific module
(ntapdsm.sys) with Microsoft software
drivers (mpio.sys, mpdev.sys, and
mspspfltr.sys).
The NetApp DSM for Windows is managed
through the SnapDrive plug-in under the
MMC or the sdcli.exe command-line utility.
Network Appliance & VIP Channel Program Confidential
v1.7
88
SnapDrive 4.1 for Windows
SnapDrive™ 4.1 and later support both x64 and x86
architectures.
SnapDrive™ 4.2 enables you to monitor fractional
space reservation thresholds when you are using
Data ONTAP 7.1 or later.
If you are using Data ONTAP 7.1 or later,
SnapDrive™ uses the LUN clone and split feature of
Data ONTAP when restoring a LUN.
For more information on SnapDrive™ 4.1, refer to
the SnapDrive™ 4.1 for Windows® Installation and
Administration Guide at:
– http://now.netapp.com/NOW/knowledge/docs/snapdrive/
relsnap41/pdfs/admin.pdf
Network Appliance & VIP Channel Program Confidential
v1.7
89
Creating a LUN with SnapDrive
Create a LUN using the LUN Wizard
Right-click
Network Appliance & VIP Channel Program Confidential
v1.7
90
LUN Management with SnapDrive
Notification settings
– You can use the existing autosupport settings on
the storage controller or use another SMTP server
Network Appliance & VIP Channel Program Confidential
v1.7
91
SnapDrive for Windows Dependent
Products
SnapManager for Exchange® - rapid online
backup and near instantaneous restoration of
Exchange® 2003 & 2007 databases.
– Data management
– Data archival
– Data replication for disaster recovery.
SnapManager for SQL® - SnapManager
provides rapid online backup and near
instantaneous restoration of SQL Server 2000
and 2005 databases.
– Data management
– Data archival for long term or remote storage of
backups
Network Appliance & VIP Channel Program Confidential
v1.7
92
SnapDrive for UNIX Dependent Products
SnapManager for Oracle®
– Uses Snapshots to create a backup of data on a
NetApp storage system
– Restores and recovers a full database or a portion
of the database
– Tracks details and produce reports
– Verifies the validity of the backup
– Clones a backup of a database
Network Appliance & VIP Channel Program Confidential
v1.7
93
Topic Questions
If there are two 200GB LUNs in a volume
(400GB total), and the fractional reserve
option is set to 50 percent, then Data ONTAP
guarantees that the volume has _________
available for overwrites to those LUNs.
– 400GB total * 50% = 200 GB
What command can you use to monitor space
reservations?
– df –r
Network Appliance & VIP Channel Program Confidential
v1.7
95
Access LUNs on AIX® (FCP-type igroup)
Configure with native AIX LVM (Logical Volume
Manager):
–
–
–
–
–
Getting the host to discover the LUNs (cfgmgr)
Verify the LUNs (sanlun lun show)
Creating a volume group (smit vg)
Access storage on a volume group
Create a file system (smit fs)
For more information on discovering LUNs with
native AIX LVM, refer to the FCP IBM® AIX® Attach
Kit Installation and Setup Guide on the NOW site.
– https://now.netapp.com/NOW/knowledge/docs/hba/fcp_aix/
relaix12/pdfs/install.pdf
Network Appliance & VIP Channel Program Confidential
v1.7
96
Access LUNs on HP-UX® (FCP-type
igroup)
Discover the new LUNs on HP-UX (2
methods):
– Preferred Process
• Perform ioscan to discover LUNs.
• Create device entries on HP-UX (ioinit –i).
• Check to see which disk devices map to which
HBA devices (tdlist or fcdlist).
• Display information about device nodes
(sanlun lun show –p all).
• Use Logical Volume Manager (LVM) or VERITAS
Volume Manager (VxVM) to manage the LUNs.
Network Appliance & VIP Channel Program Confidential
v1.7
97
Access LUNs on HP-UX® (FCP-type
igroup) (Continued)
Discover the new LUNs on HP-UX (2 methods):
– Alternative Process
• Reboot the host
• Check to see which disk devices map to which HBA
devices (tdlist or fcdlist).
• Display information about device nodes
(sanlun lun show –p all).
• Use Logical Volume Manager (LVM) or VERITAS Volume
Manager (VxVM) to manage the LUNs.
For more information on managing LUNs with HPUX’s Logical Volume Manager, refer toe the FCP HPUX Attach Kit Installation and Setup Guide.
– https://now.netapp.com/NOW/knowledge/docs/hba/
fcp_hp-ux/relhp-ux11/pdfs/setup.pdf
Network Appliance & VIP Channel Program Confidential
v1.7
98
Access LUNs on Linux® (FCP-type igroup)
To configure the LUNs on Linux, you must do the
following:
– Configure the host to find the LUNs (Reboot or modprobe).
– Verify that the new LUNs are visible (sanlun lun show
filer_name:path_name).
– Enable the host to discover new LUNs (modprobe)
– Label the new LUNs as Linux disks.
• File system – fdisk /dev/sd[char]
• Raw access - raw
For more information on configuring Linux LUNs,
refer to the Installion and Setup Guide for Fibre
Channel Protocol on Linux.
– https://now.netapp.com/NOW/knowledge/docs/hba/fcp_linux/
fcp_linux10/pdfs/install.pdf
Network Appliance & VIP Channel Program Confidential
v1.7
99
Access LUNs on Solaris (iSCSI-type
igroup)
Perform the following steps to access LUNs with
iSCSI-type igroups on Solaris:
– Configure an iSCSI target for static or dynamic discovery
• iSNS (dynamic): iscsiadm add iSNS-server IPaddress:port
• Static: iscsiadm add static-config eui_number, IPaddress
– Enable an iSCSI target delivery method
• iSNS: iscsiadm modify discovery –isns enable
• Static: iscsiadm modify discovery –static enable
– Discover LUNs – devfsadm –i iscsi
– View LUNs - /opt/NTAP/SANToolkit/bin/sanlun lun
show all
– Create file systems – format
– Make iSCSI devices available on reboot – Add an entry to the
/etc/vfstab file.
 For more information an accessing Solaris LUNs with an
igroup type of iSCSI, refer to the iSCSI Initiator Support
Kits for Solaris at:
https://now.netapp.com/NOW/download/software/
kit_iscsi/Solaris/
Network Appliance & VIP Channel Program Confidential
v1.7
10
0
Access LUNs on Windows (iSCSI-type
igroup)
Perform the following steps to access LUNs
with iSCSI-type igroups on Windows:
– Rescan host’s disks – Disk Management
– Initialize and partition the disk – Disk Management
– Configure dependent services to start after iscsi (if
necessary)
For more information an accessing Windows
LUNs with an igroup type of iSCSI, refer to
the iSCSI Initiator Support Kits for Windows
at: https://now.netapp.com/NOW/download/
software/kit_iscsi/Windows/
Network Appliance & VIP Channel Program Confidential
v1.7
10
1
Access LUNs on AIX (iSCSI-type igroup)
Perform the following steps to access LUNs
with iSCSI-type igroups on AIX:
– Configure /etc/iscsi/targets file
– Discover LUNs using cfgmgr –l iscsi0
– View LUN information using sanlun lun show
all
– View disk properties using lsattr –El hdiskx
For more information an accessing AIX LUNs
with an igroup type of iSCSI, refer to the
iSCSI Initiator Support Kits for AIX at:
https://now.netapp.com/NOW/download/
software/kit_iscsi/AIX/
Network Appliance & VIP Channel Program Confidential
v1.7
10
2
Access LUNs on HP-UX (iSCSI-type
igroup)
Perform the following steps to access LUNs with
iSCSI-type igroups on HP-UX:
– Configure the host for iSCSI
• Assign the host an iSCSI node name
• Set CHAP authentication and passwords (if necessary)
• Add the storage systems IP address as a discovery target
– Discover the LUNs – ioscan –H 255
– Create iSCSI device entries – insf –H 255
For more information an accessing HP-UX LUNs with
an igroup type of iSCSI, refer to the iSCSI Initiator
Support Kits for HP-UX at:
https://now.netapp.com/NOW/download/software/
kit_iscsi/HP-UX/
Network Appliance & VIP Channel Program Confidential
v1.7
10
3
Access LUNs on Linux (iSCSI-type igroup)
Linux has several Support Kits, depending on
your version of Linux (Red Hat, SuSE)
Perform the following steps to access LUNs
with iSCSI-type igroups on Linux (Red Hat):
– Start the iSCSI service on the host
– Access LUNs either with dm-multipath (RHEL
Update 3) or without dm-multipath
For more information an accessing Linux
LUNs with an igroup type of iSCSI, refer to
the iSCSI Initiator Support Kits for Linux at:
https://now.netapp.com/NOW/download/
software/kit_iscsi/Linux/
Network Appliance & VIP Channel Program Confidential
v1.7
10
4
Host Booting from SAN or IP SAN
Host booting uses a LUN as a boot device
Configuration varies by operating system, but
requires the following:
–
–
–
–
Creating a boot LUN (with the appropriate OS)
Copying of boot data
Defining boot paths
Rebooting the System
Network Appliance & VIP Channel Program Confidential
v1.7
10
5
SAN Boot LUNs
Master
Boot LUN
Fibre Channel
Switch
Boot
LUNs
NetApp Storage System
with FCP
Four Split-Clone Boot LUNs
Network Appliance & VIP Channel Program Confidential
v1.7
10
6
SAN Boot Tasks – Windows FCP
Configure PC BIOS boot order
Enable Boot BIOS on the HBA
Obtain the WWPN of the host initiator HBA
Cable the storage system so that only one path
exists from the HBA to the boot LUN
Create the LUN that will be used as a Boot LUN
Configure the BootBIOS to use the Boot LUN
Copy the Emulex or Qlogic SAN boot driver from the
web to a floppy disk
Install Windows (2000, 2003) OS on the Boot LUN
Install the FCP Windows Attach Kit software drivers
Network Appliance & VIP Channel Program Confidential
v1.7
10
7
SAN Boot Tasks – Solaris™ FCP
Configure Host and Storage System with
supported firmware
Install Host operating system on a local disk
Download and install OpenBoot firmware on
the HBA
Create the Boot LUN
Copy bootblks and boot data
Modify OpenBoot
Reboot the system
Network Appliance & VIP Channel Program Confidential
v1.7
10
8
SAN Boot Tasks – FCP HP-UX
Assumptions for HP-UX SAN Boot Tasks are:
– PA-RISC Server
– Host booting from an existing internal OS disk
– Boot LUN managed with the HP-UX Logical Volume
Manager
– FCP-UX Attach Kit 1.1 or later installed on the host
Create the Boot LUN
Configure the HP-UX operating system on the
Boot LUN
Set the host’s boot environment
Network Appliance & VIP Channel Program Confidential
v1.7
10
9
SAN Boot Tasks – FCP AIX
Assumptions for AIX SAN Boot Tasks are:
– The host is booting from an existing internal OS
disk
– The FCP IBM AIX Attach Kit 1.2 or later is installed
Complete the following steps to use the LUN
as a boot device on AIX:
– Configure NetApp igroup and SAN Boot LUN
– Install the OS on the Boot LUN
Network Appliance & VIP Channel Program Confidential
v1.7
11
0
Host Boot from IP SAN (QLogic)
Assumptions for host boot from IP SAN are:
–
–
–
–
–
Supported Configuration
HBA Manager Interface Installed
Device driver diskette available
Primary hard drive disabled
HBA has IP address, available on the network
Network Appliance & VIP Channel Program Confidential
v1.7
11
1
Host Boot from IP SAN (QLogic)
(Continued)
To boot from IPSAN using QLogic:
–
–
–
–
Update HBA with current firmware and BootBIOS
Obtain initiator and target iSCSI node names
Create the Boot LUN and map it to an igroup
Configure the BootBIOS utility to use the LUN as a
boot device
– Configure the boot order
– Install the OS on the LUN
– Alter HBA, SnapDrive, and initiator settings to
support SAN Boot
Network Appliance & VIP Channel Program Confidential
v1.7
11
2
Questions / Answers
Network Appliance Confidential
Storage system based tools –
provided by Data Ontap
– fcp config
• Shows information about FC target ports configuration
• Provides functionality to configure the FC target adapters
– Example: enabling/disabling an FC adapter
– Example: setting the mediatype to loop, auto, ptp
– Example: setting the speed to auto,1,2,4
– fcp show adapter
• Shows information about FC target ports configuration
– fcp show/set cfmode
• Shows cfmode being used on the storage system
• Changes cfmode being used on the storage system
– fcp show initiator
• Shows host initiators currently connected to the storage system
– fcp show nodename
• Shows FC nodename currently assigned to the storage system
– options
• Shows global configuration settings on the storage system
Network Appliance & VIP Channel Program Confidential
v1.7
11
4
FC SAN host based tools – provided by
FC Host Utilities Kits
– sanlun
• utility program used to obtain information about LUNs on
host
– filer_info
• collects information about FC configuration of the storage
system
– solaris_info, aix_info, hpux_info,
linux_info, windows_info
• collects information about configuration of host OS
– brocade_info, cisco_info, mcdata_info
• collects information about configuration of FC switch
Network Appliance & VIP Channel Program Confidential
v1.7
11
5
SnapDrive™ host based tools – provided by
SnapDrive for Unix (SDU) or SnapDrive for
Windows (SDW) products
– snapdrive version
• SDU option used to obtain version of SDU on host
– snapdrive config
• SDU option used to obtain information about SDU configuration
on host
– snapdrive storage
• SDU option used to obtain information about LUNs managed by
SDU on host
– SnapDrive Data Collection Utility
• SDW option used to obtain information about FC environment on
Windows host and SDW configuration
Network Appliance & VIP Channel Program Confidential
v1.7
11
6
View Path to LUN
fas270a> lun show -m
LUN path
Mapped to
LUN ID Protocol
----------------------------------------------------------------------/vol/vol2/esx2
/vol/vol2/esxtest.lun
fas270a>
ESX2
ESX
Network Appliance & VIP Channel Program Confidential
0
iSCSI
0
iSCSI
v1.7
11
7