Network Appliance Confidential Fibre Channel Supported Configurations Switching & Hosts

Network Appliance Confidential

Fibre Channel Supported ConfigurationsSwitching & Hosts

2Network Appliance & VIP Channel Program Confidential v1.7

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


Core-Edge

Design the Fabric for your requirements

Full mesh

Cascade

Mesh Configurations are appropriate when:Traffic patterns are evenly distributedOverall bandwidth consumption is lowThe maximum config is four to five switches

Cascade Configurations are appropriate when:Traffic patterns are localized onto individual switches

Core-Edge Configs are appropriate when:Fabric is likely to growA flexible system is required because of unknown or undefined requirementsReliability is required – this type of config has been well-tested and is used in most production environments

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


Fabric Scalability

Scale fabric size by replacing existing

core with a larger core

Scale # Core Switches

Scale # ISLs

Scale performance by adding ISLs or additional core switches

Scale fabric size by adding switches

Scale # ports

Examples of Fabric Scalability


1 2 3

Storage Storage

New New FirmwareFirmware Storage

Both Switches Both Switches have New have New FirmwareFirmware

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


Initiator/Target Relationship

SCSI over Fibre Channel

SCSI over TCP/IP(iSCSI)

TCP/IP

TCP/IP

HOST (Initiator) Controller (Target)

FC driver

FC driver

SCSI

WAFL

RAID

iGroup

SCSI driver

File System

Application

SCSI Adapters

Windows or UNIXFibre Channel HBAs

Data ONTAP

LUN

iSCSI HBAs or Ethernet NICs

Direct Attached Storage (DAS)

Fabric/Network

iSCSI driver

Fibre Channel or Serial ATA Attached

iSCSI driver


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


Fabric or Network Architectures

NetApp supports all industry-accepted fabric and network architectures.

Types of architectures are:– Single-Switch– Cascade – Mesh– Core-Edge – Director


Cascade

Maximum hop count supported is three


Mesh

Partial Mesh


Core-Edge


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


How many fabrics are show below?

FC_Switch4

FC_Switch8

FC_Switch2

FC_Switch5

FC_Switch3

FC_Switch6 FC_Switch7

FC_Switch1

FC_Switch10FC_Switch9


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.


SAN Made Easy – Auto Discovery

What do I want to be when I grow up?

y/n Do you want to talk loop?

G_Port I’m waiting for someone to talk to me…

yesno

Are you a switch or a fabric point-to-point device?

F_Portfabric pt-to-pt

E_Port

switch

y/n Is something plugged into the port?no

yes

U_Port

FL_Port


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.


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


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.


Additional switches are supported, see Switch Compatibility Matrixhttps://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/index.shtml

Brocade Silkworm 4100

Cisco 9020

Brocade Silkworm 200E

McDATA Intrepid 4400

McDATA 4700

Cisco MDS9140

Brocade Silkworm 4900

CiscoMDS 9506

CiscoMDS 9509

Cisco9216a / 9216i Brocade

Silkworm12000/24000

McDATAIntrepid

6064BrocadeSilkworm

48000

McDATAIntrepid

6140

CiscoMDS 9513

Fabric SwitchFabric SwitchTypically < 32 PortsTypically < 32 Ports

DirectorDirectorTypically => 32 portsTypically => 32 ports

DirectorDirectorTypically => 32 portsTypically => 32 ports

Switch Partnerships & Support

McDATAi10K

Qlogic SANbox 5600


FC SAN Host Support

Host ClusterOS Vendor

Multipath File SystemHBA

Native

HP PVLinks /VERITAS DMP

MC ServiceGuard /VERITAS VCS

Native

MSCSVERITAS VCS

Emulex /Qlogic

HACMP

QLogic QLogic

QLogic QLogic

QLogic QLogic

EmulexQLogic

VMware MSCSVirtualCenter (VMotion)

Volume Mgr

LVM

VERITAS VxVM

NSS

VMware

NTFS

VERITAS VxFS

JFS/2Raw

LVM /VERITAS VxVM

JFS/ HFSRaw

VERITAS VxFS

ext3 / ext2 /Reiser / GFS*

ext3ext2

Reiser

VMFS 2.xRaw

LVM Under Test

Oracle 9i, 10g, RAC

Novell Clusters

Always check the support matrix at https://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/index.shtml

SANpath /MPIO

VERITAS DMP /MPxIO*

VERITAS VCS /Native SUN Cluster*

Oracle 9i, 10g RAC /RH Cluster Suite*

* (via PVR)

MPIO NetApp DSM / VERITAS DSM for MPIO*

MMC /VERITAS

VxVM*Emulex /

Native 4Gb


Brocade Value Line Licensing


Cable Distance Chart


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 carefullyanalyzed. Doors and other moving components should be carefully analyzed to make sure that in allpositions they do not apply a shear force.

• Cable Strain: A good cable design will provide sufficient slack to prevent a significant strain. While this isoften sufficient, the weight of a group of cables hanging without support must be considered. This isespecially a concern if any device exhaust heats the cable. Another case frequently missed is the effect ofdoors, 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.


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.


Switch Commands


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


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


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


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


Switch Zoning


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


Domain 100Domain 200

VSANs and Domain IDs


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

Recall: Each VSAN acts as a completely independent fabric

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

Each switch will have a separate domain_ID for each active VSAN

– 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 126 Domain 153Domain 173





Domain 157Domain 170Domain 215


MDS9000-overview.ppt


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



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



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



10 Zoning Rules - Brocade1) If security is a priority, then a Hard Zone-based architecture

coupled with Hardware Enforcement is recommended2) 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.



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.


Zoning Example – Single Fabric

zone1

zone2

FAS270C

Host1

Host2 Host3

Host4

FC Fabric

What is needed on the hosts systems and on which systems is it needed in this configuration?


CFModes


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


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)


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


Partner cfmode

Host

Dual Controllers – F8xxC, FAS9xxC, FAS3020C, FAS3050C

Dual Card per FAS Device

TargetHBA’s

TargetHBA’s

If Filer X fails, then Filer Y takes over and the following occurs:No Port Take-Over, All Ports Active

Primary path should be thru the FAS Device that controls LUNSecondary path should be over other FAS Device thru cluster interconnect.

Controller 1

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.

Switch / Fabric 1 Switch / Fabric 2

Initiator HBA’s

Multipath software required or Zoning on

switch to allow supported paths for a

LUN

Supported on:

Solaris, Windows, HP-UX, AIX, Linux RHEL 3.0 and Novell

0c 0d 0a 0b

Controller 2

0c 0d 0a 0b


Available Paths - Partner Mode

Switch/Fabric 1 Switch/Fabric 2

Host

LUNs LUNs

Solid Blue are paths to the LUNs being served by Controller 1

Dashed Purple are paths to the LUNs being served by Controller 2

0c 0d 0c 0d0a 0b 0a 0bHA Configuration

Controller 1 Controller 2


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


Standby cfmode

Host


If Controller 1 fails, then Controller 2 takes over and the following occurs:

Port 0b on Controller 2 takes over for Port 0a in Controller 1Port 0d on Controller 1 takes over for Port 0c in Controller 2The ports that were standby take over the WWPN of the previous active ports on the failed FAS Device

Solid Lines indicate active connections

Dotted lines indicate standby connections.

Only supported on:

Solaris

Windows

Linux RHEL 3.0

Novell


Initiator HBA’s



LUN

Dual Controllers – F8xxC, FAS9xxC, FAS20X0, FAS30X0A, FAS60X0A

TargetHBA’s

TargetHBA’s

Controller 1

0c 0d 0a 0b

Controller 2

0c 0d 0a 0b


Available Paths- Standby Mode


Host

LUNs LUNs


Controller 1

Controller 2

Solid Blue are paths to the LUNs being served by Controller 1

Dashed Purple are paths to the LUNs being served by Controller 2



Controller 1

Controller 2

Path Access (Switch Failure) – Standby Mode


Host

LUNs LUNs

Solid and Blue are paths to the LUNs being served by Controller 1

Dashed and Purple are paths to the LUNs being served by Controller 2

Switch/Fabric 1 will experience a failure

MP layer works around the failure



Controller 1

Controller 2

Controller 2 Takes over all operations

Path Access (CFO event)- Standby Mode


Host

LUNs LUNs

Conntroller 1 will experience a failure





Controller 1

Controller 2

Filer Head 2 Takes over all operationsMP layer is not involved in switchover

Path Access (CFO event)- Standby Mode


Host

LUNs LUNs

Controller 1 will experience a failure

WWN1 WWN2 WWN3 WWN4 WWN5 WWN6 WWN7 WWN8




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


mixed cfmode

7a 7b

7a

7b

Host

9a

9b9a 9b

Clustered FAS – F8xxC or FAS9xxC


TargetHBA’s

Target HBA’s

FAS X FAS Y

Virtual Ports per Physical Port

Local

Standby

Partner


Initiator HBA’s

Target logs into fabric as loop 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

Solaris & Windows – Standby mode

HP-UX & AIX – Partner mode

Zoning is required on switches for this mode



LUN

Supported on:

Solaris, Windows, HP-UX, AIX, Linux RHEL 3.0 and Novell


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


Host 1Host 1

Host 1Host 2

FAS 1 *FAS270

FAS 1 / FAS 2FAS270C FAS 1 / FAS 2

FAS270C

Direct AttachedFAS270 – Secondary Storage

Multipath software required

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

Two Hosts, single attach, dual controller head (no failover)

Two Host Cluster, single attach, dual controller head (no controller failover)


Host 2

FC Fabric 1

Host 1

…

Host N

FAS 1

FAS270

Switched Fabric – Single Switch - Single Head

FAS270 – Secondary StorageMultipath software

required for all dual attached

hosts


Host 2

FC Fabric 1

Host 1

…

Host N

FAS 1 / FAS 2 FAS270C

Switched Fabric – Single Switch - Dual HeadFAS270C – Primary or Secondary Storage

Multipath software required or fabric zoning is required to avoid multiple paths

Multipath software required for all dual attached hostsMultipath software

required or fabric zoning is required to avoid multiple paths


Host 2

FAS 1 / FAS 2 FAS270C

FC Fabric 2

Host 1

…

Host N

FC Fabric 1

Host 3

Dual Switched Fabric - Dual HeadFAS270C – Primary or Secondary Storage

Storage Array failover is not available with single

attached hosts

Multipath software required for all dual attached hosts


Host 1 Host 1 2 Host Cluster

FAS 1 F8XX/FAS9XXNearStore RXXX



2 Host Cluster


Direct Attached – Single Head - FAS 8xx/FAS9XX/Rxxx - Primary Storage



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


7a 7b 7a 7b


9a 9b 9a 9b

2 - Dual Cards per FAS Device

CF Mode Supported :

Partner

Standby

Mixed

FAS 1 FAS 2

TargetHBA’s

Target HBA’s

Initiator HBA’s

F8XXC/FAS9XXC

Host 2Host 1

…

Host NHost 3Multipath software required or Zoning on


LUN depending on cfmode

Dual Switched Fabric – Dual HeadF8XXC/FAS9XXC - Primary Storage

Cluster Interconnect


4a/b 7a/b4a/b

7a/b5a/b

9a/b 5a/b 9a/b

4 - Dual Port Cards per FAS Device

CF Mode Supported :

Partner

Standby

Mixed

FAS 1 FAS 2

TargetHBA’s

Target HBA’s

Initiator HBA’s


Host 2Host 1

…

Host NHost 3

F8XXC/FAS9XXC

Dual Switched Fabric – Dual HeadF8XXC/FAS9XXC - Primary Storage




LUN depending on cfmode


Host 1

Host N (max 4)


…Host 1 Host 3


Host 2

Host 1 Host 2

FAS 1 F8XX/FAS9XX NearStore RXXX

Direct Attached – Single Head – F8XX/FAS9XX/Rxxx – Secondary Storage

Multipath software

required both systems



Host 2

FAS 1F8XX/FAS9XXNearStore RXXX

FC Fabric 1

Host 1

…

Host N

1 to 4 connections

Switched Fabric – Single SwitchFAS800/900/RXXX – Secondary Storage

Multipath software required or Zoning on switch to allow only one path to a LUN

Multipath software required or Zoning on switch to allow only one path to a

LUN


4a/b 9a/b… TargetHBA’s

CF Mode Supported :

Partner

Standby

Mixed


7a 7b

Switch / Fabric

Single Port Card or Dual Port Card using

only 1 Port per FASD

CF Mode Supported :

Partner

Standby

Mixed

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

FAS 1 FAS 2

TargetHBA

Target HBA

Initiator HBA’s

F8XXC/FAS9XXC

Switched Fabric – Single Switch – F8XXC/FAS9XXC – Secondary Storage

Host 2Host 1

…

Host N

Multipath software required or Zoning on switch to allow only one path to a LUN


LUN




4a/b

Switch / Fabric

9a/b… 4a/b … 9a/b

Multiple Dual Port Cards per FAS – Max 4

CF Mode Supported :

Partner

Standby

Mixed

Important:

HBAs internal to the FAS have to be in the same slot on both FAS systems

FAS 1 FAS 2

TargetHBA’s Target

HBA’s

Initiator HBA’s

Host 2Host 1

…

Host N


or Zoning on switch to allow

only one path to a LUN


LUN


F8XXC/FAS9XXC

Switched Fabric – Single SwitchF8XXC/FAS9XXC – Secondary Storage



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 but pvlinks will only utilize 8

16 16

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


Configuration Limits

Parameter Storage Solutions *

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


Supported Configurations

NetApp has detailed compatibility matrices available on the NetApp On the Web (NOW) site with up-to-date 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/


Target HBA Comparisons

X1028A (

QLA 2342)2Gb/s

X1033 (

QLA 2352)2Gb/s

X1088A (

QLA 2462)4Gb/s

Onboard Memory 256KB 4MB 4MB

Maximum Commands, Queue Depth(per card, not port)

512 2048 2048

Maximum Port Logins, Maximum Initiators

256 2048 2048


Host Configuration Info

LUN Queue Depth – controls the maximum number of outstanding I/O’s

Authentication between FC Targets and Initiators – DH-CHAP


Host OS Support


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_config/fcp_support.shtml#solaris9


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-to-

date information.

https://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/iscsi_support_matrix.shtml


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


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/docs/san/fcp_iscsi_config/fcp_support.shtml


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


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/


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


Storage System Commands

Refer to the Commands: Manual Page Reference for more information at:

– 6.5(http://now.netapp.com/NOW/knowledge/docs/ontap/rel656/pdfs/ontap/cmdref.pdf)

– 7.0(http://now.netapp.com/NOW/knowledge/docs/ontap/rel704/pdfs/ontap/cmdref1.pdf)

– 7.1(http://now.netapp.com/NOW/knowledge/docs/ontap/rel7101/pdfs/ontap/cmdref1.pdf)

– 7.2(http://now.netapp.com/NOW/knowledge/docs/ontap/rel72rc/pdfs/ontap/cmdref1.pdf)


Host Utilities


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


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


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


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


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


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


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


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.


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.


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


Creating a LUN with SnapDrive

Create a LUN using the LUN Wizard

Right-click


LUN Management with SnapDrive

Notification settings– You can use the existing autosupport settings on

the storage controller or use another SMTP server


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


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


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


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


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.


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 HP-UX’s Logical Volume Manager, refer toe the FCP HP-UX Attach Kit Installation and Setup Guide.– https://now.netapp.com/NOW/knowledge/docs/hba/

fcp_hp-ux/relhp-ux11/pdfs/setup.pdf


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


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/


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/


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/


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/


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/


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


SAN Boot LUNs

Fibre ChannelSwitch

NetApp Storage System with FCP

Four Split-Clone Boot LUNs

Boot LUNs

Master Boot LUN


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


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


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


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


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


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


Questions / Answers


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


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


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


View Path to LUN

fas270a> lun show -m

LUN path Mapped to LUN ID Protocol

-----------------------------------------------------------------------

/vol/vol2/esx2 ESX2 0 iSCSI

/vol/vol2/esxtest.lun ESX 0 iSCSIfas270a>

Documents

Network Appliance Confidential Fibre Channel Supported Configurations Switching & Hosts