M02 FCConnectivity

SAN Administration
on Data ONTAP 7.3

FC Connectivity
2008 NetApp. All rights reserved.
Objectives
At the end of this module, you should be able to:
Describe single path implementation with Fibre
Channel (FC) connectivity
Describe how to configure FC ports on
Windows, Solaris, and NetApp systems
Describe commands/utilities to identify the
worldwide node name (WWNN) and worldwide
port name (WWPN) on Windows, Solaris, and
NetApp systems
Use commands/utilities to examine FC switch
activity
2
Single Path FC Connectivity
3
FCP
NetApp
FAS
FC Connectivity
Data ONTAP
Windows
Solaris
Type of Topologies:
1. Direct-attached
2. Single Fabric
2008 NetApp. All rights reserved. 4
Direct-Attached Topology
Solaris
Storage System 1
Windows
Fibre Channel
Problems with Direct-Attached
Fibre Channel
1. Does not scale
2. No fault tolerance
X
Windows no
longer has
connectivity
with Storage
System 1
Solaris
Storage System 1
Windows
Single-Fabric Topology
Solaris Windows
0 1 2 3 4 5 6 7
Fibre Channel
4 5 6 7
Storage System 1
0
Topology Summary
Single fabric implementation:
Is simple
Doesnt provide redundancy for losing a switch
or cable
NOTE: In Module 8, we will discuss a multipath
FC implementation that overcomes the
limitations of a single fabric design

7
Compatible Systems
FC Switches
Brocade
Cisco
Target operating system (OS):
Data ONTAP
Initiator OS:
Solaris
Windows
AIX
HP-UX

QLogic

VMware
Linux
Novell Netware
OpenVMS
8
NOTE: This course will focus on Brocade, Solaris,
Windows, and Data ONTAP 7.3

NOTE: Always verify
your configuration
with the
Interoperability Matrix
on the
NOW site
FC Switch Issues
An FC switch is optional but is often present
For an initiator to discover a target, it must be visible
through the switch
FC switches can be zoned
a zone is an access list for a group of FC ports that
are allowed to communicate with each other within a
fabric
a single port might be in more than one zone
9
FC Switch Zoning
Two methods of FC switch zoning:
Port Zoning
Ports are grouped into a zone
Moving a cable from one port to another doesnt
necessarily require zone updating
WWPN Zoning
WWPNs are associated with a particular port, which
are then grouped into a zone
Moving a cable from one port to another requires
zone updating
Within this class, we will not zone our FC switch
10
Data ONTAP as an FC Target
Data ONTAP 6.3 and later has support for FC
Data ONTAP features:
Built-in FC functionality
Simple LUN creation and management
To properly configure Data ONTAP for FC
connectivity:
1. Confirm FC HBA
2. Configure Fibre Channel Protocol (FCP)
3. Configure the FC Target HBA(s)
4. Identify the worldwide node name (WWNN)
5. Identify the worldwide port name (WWPN)
11
FC Connectivity
Data ONTAP
Windows
Solaris
HBA Confirmation
Confirm the current HBAs:

To identify the type of the built-in HBAs :
12
system> fcadmin config

Local
Adapter Type State Status
---------------------------------------------------
0a initiator CONFIGURED online
0b initiator CONFIGURED online
0c target CONFIGURED online
0d target CONFIGURED online
system> sysconfig
NOTE: Add-on cards are configured at manufacturing to be either
an initiator or target and cannot be changed in the field
HBA Confirmation (Cont.)
To change an onboard interface from an
initiator to a target:

To change an onboard interface from a target
to an initiator:
13
system> fcadmin config -d 0b
system> fcadmin config -t target 0b
system> reboot

Down the
interface
Reconfigure
the interface
as a target A reboot is
required
system> fcadmin config -d 0b
system> fcadmin config -t initiator 0b
system> reboot

Configuring FCP Services in Data ONTAP
1. Verify Fibre Channel Protocol (FCP) service
is running
fcp status
2. Verify FCP is licensed (license the FCP
services if needed)
license
license add XXXXXX
3. Start the FCP service
fcp start

14
Configuring FC HBA in Data ONTAP
1. List the installed HBAs
fcp show adapters
2. Take an HBA offline
fcp config adapter down
3. Set HBA options if necessary
For example:
fcp config adapter speed
[auto|1|2|4]
4. Bring an HBA online
fcp config adapter up
15
Identify WWNN in Data ONTAP
WWNN uniquely identifies the storage system
The default WWNN is generated by a serial
number in its NVRAM and stored on disk
Normally doesnt need to be changed

To identify the WWNN:
system> fcp nodename
Fibre Channel nodename: 50:0a:09:80:86:f7:c7:86
(500a098086f7c786)
16
Identify WWPN in Data ONTAP
WWPN uniquely identifies an FC HBA port
WWPNs are determined by:
WWNN
Controller failover mode (cfmode) discussed
later in Module 8
Internal port index
To verify the default WWPN:
system> fcp portname show
Portname Adapter
-------- -------
50:0a:09:81:86:f7:c7:86 0c
50:0a:09:82:86:f7:c7:86 0d

17
Windows as an FC Initiator
NetApp has supported Windows as an FC
initiator OS since Windows 2000 Server
Windows Server 2008 has many advantages
over previous versions
New tools
Storage Explorer
Storage Manager for
SANs
Multipath I/O (MPIO)
Built-in FC drivers
Windows must be properly configured for FC
connectivity
18
FC Connectivity
Data ONTAP
Windows
Solaris
Windows Server 2003/2008 Configuration
1. Verify host operating system releases, required patches, and
NetApp FC Host Utility Kit with Interoperability Matrix
Use System Properties dialog to verify release
Interoperability Matrix can be found on the NOW site
2. Install compatible host bus adapters (HBAs)
3. Install / Configure required HBA drivers and utilities
4. Verify an HBA
Emulex: Use HBAnyware
QLogic: Use SANsurfer
All HBA Types: Device Manager Dialog
5. Install compatible NetApp FC Host Utility Kit for Windows
Provides Perl scripts to diagnose and troubleshoot Windows
Example: windows_info provides diagnostic information
19
Windows/Emulex Implementation
After installation, to configure a
Windows/Emulex implementation:
Verify the HBA is enabled
Identify the WWNN on the host
Identify the WWPN on the host
Verify connectivity between the initiator and
target

20
NOTE: in this example, we
with be configuring an Emulex HBA. In
Module 8, we will configure a
QLogic HBA
Windows/Emulex Implementation (Cont.)
Verify that Windows Server 2003 has identified the
HBA(s)
21
Within Device Manager
Select SCSI and RAID
controllers
(NOTE: in Windows 2008,
this is called
Storage controllers)
Enabled Emulex HBA
Double-click to investigate
Disabled QLogic HBA
Identify the driver associated with the HBA(s)

22
Other HBAs will be at
a different location
For more
information
Verify the HBA(s) is connected on Windows Server 2008

23
Locate the correct server
In this example,
2 Emulex HBAs
are installed
Identify the local WWPN(s) on Windows Server 2008

24
Select one of the HBA
The WWPN
The WWNN
Verify the HBA(s), WWNN(s) and WWPN(s) are
connected on Windows Server 2003/2008

25
Select HBA
WWPN
WWNN
Discovery
Windows
Storage System
Fibre Channel
Fibre Channel
Initiator
Target
Discovery is
automatic
Data ONTAP Discovery of Initiators
Verify connectivity from the storage system
system> fcp show initiators
Initiators connected on adapter 0c:
Portname Group
-------- -----
10:00:00:00:c9:2d:9f:76

27
Windows
WWPN
NOTE: For convenience, we can alias
the Windows WWPN
WWPN Aliases
In large Fibre installations, it can be difficult to
identify WWPNs because of their cryptic 64-bit
name
Example: 50:0a:09:81:97:99:28:01
For convenience, WWPN may now be named
or aliased within Data ONTAP
Both target and initiator ports may be aliased
fcp wwpn-alias Command
To alias a WWPN:
Use fcp wwpn-alias set [-f] alias wwpn
Example:
system> fcp wwpn-alias set mySolarisPort1
10:00:00:00:c9:48:ce:9f
To remove an alias:
Use fcp wwpn-alias remove {-a alias|-w wwpn}
Example:
system> fcp wwpn-alias remove -a melvar1 melvar0
(removes the aliases)
system> fcp wwpn-alias remove -w 10:00:00:00:c9:48:ce:9f
(removes all aliases for a particular WWPN)
To show aliases:
Use fcp wwpn-alias show [-a <alias> | -w <wwpn>]
Alias Rules
A storage system can have up to 1024 aliases
An alias can have the following characters:
A-Z, a-z, 0-9, '_','-','.','{','}' and no spaces
Many aliases maybe associated with a single
WWPN, but each alias will be assigned to only
one WWPN
Use fcp wwpn-alias help
<subcommand> for more information on the
subcommand
WWPN Aliases Example

system> fcp wwpn-alias set win0 10:00:00:00:c9:2d:9f:76
system> fcp wwpn-alias show
WWPN Alias
---- -----
10:00:00:00:c9:2d:9f:76 win0

Portname Group
-------- -----
10:00:00:00:c9:2d:9f:76
WWPN Alias(es): win0

Windows Discovery of Targets
Verify connectivity from Windows Server 2008
32
Select the
Brocade fabric
Storage systems
WWPNs show up
Windows Discovery of Targets
Verify connectivity from Windows Server 2003/2008

33
Expand the
local adapter
Storage systems
1 and 2 are visible
Binding
Binding or mapping in FC SAN is the process
of associating an OS device name to a targets
worldwide port name
Persistent binding in FC SAN is the process of
ensuring that the same binding occurs even
after a host OS reboot
NOTE: Binding is done automatically in most
modern OS; therefore, it does not need to be
manually configured
34
Window/Emulex Binding
35
Select
Current
Bindings
Current
SCSI IDs
Do not use
persistent
binding
SCSI ID =
Bus Number, Target Id
From Device Properties...
Solaris as an FC Initiator
NetApp has supported Solaris as an FC
initiator OS since Solaris 8
Solaris 10 has many advantages over previous
versions:
SAN Foundation Suite (SFS)
A.K.A. Leadville
Provides built-in drivers and utilities for FC SAN
Better scalability
Solaris must be properly configured for FC
connectivity
36
FC Connectivity
Data ONTAP
Windows
Solaris
Solaris 10 Configuration
1. Verify host operating system releases, required patches, and
NetApp FCP Solaris Host Utility Kit with Interoperability Matrix
Use /etc/release to verify Solaris version
Interoperability Matrix can be found on the NOW site
2. Install compatible host bus adapters (HBAs)
3. Install / Configure required HBA drivers and utilities if needed
(not required with SFS)
4. Verify an HBA
All HBA Types: prtdiag, prtconf, luxadm, cfgadm
Emulex: Use /usr/sbin/lpfc/lputil or HBAnyware
QLogic: Use /usr/bin/scli or SANsurfer
5. Install compatible FCP Solaris Host Utility Kit for Native OS
Provides Perl scripts to configure and tune Solaris
Example: sanlun application to manage LUNs from Solaris
37
Solaris/Emulex Implementation
After installation, to configure a Solaris/Emulex
implementation:
Identify the correct HBA driver
Verify that Solaris has correctly identified the
HBA and loaded the driver
Identify the WWPN on the host
Verify connectivity between the initiator and
target

38
NOTE: in this example, we
with be configuring an Emulex HBA. In
Module 8, we will configure a
QLogic HBA
Solaris/Emulex Implementation (Cont.)
Solaris has two categories of Emulex HBA
drivers:
SFS drivers provided by Sun
LightPulse Fibre Channel (LPFC) drivers
provided by Emulex
To simplify our setup, this course will focus on
SFS
39
Verify that Solaris has identified the HBA(s)
# prtdiag | grep LP
pci 33 +tem-board/PCI3 fibre-channel-
pci10df,f900 LP9002L

Identify the driver associated with the HBA(s)
#cat /etc/driver_aliases | grep pci10df,f900
emlxs "pci10df,f900"

40
Emulex HBA
The emlxs driver is associated
with the Emulex HBA
emlxs is the SFS driver
32-bit driver: /kernel/drv/emlxs
64-bit driver: /kernel/drv/sparcv9/emlxs
Configuration file: /kernel/drv/emlxs.conf
To verify the driver when loaded:
# modinfo | grep emlxs
87 7ba44000 245e28 130 1 emlxs (SunFC emlxs
FCA v20060920-2.11l)
To load the 64-bit driver (if needed):
# modload /kernel/drv/sparcv9/emlxs

41
Verify the HBA is connected to the fabric
# luxadm -e port
/devices/pci@1f,0/pci@5/fibre-channel@0/fp@0,0:devctl CONNECTED

Identify the local WWPN
# fcinfo hba-port
HBA Port WWN: 10000000c92da063
OS Device Name: /dev/cfg/c1
Manufacturer: Emulex
Model: LP9002L
Firmware Version: 3.93a0
FCode/BIOS Version: none
Type: N-port
State: online
Supported Speeds: 1Gb 2Gb
Current Speed: 2Gb
Node WWN: 20000000c92d9f8a

42
Emulex HBA is connected to the fabric
WWPN for the
Emulex HBA
OS attachment point
Solaris WWNN
SCSI driver configuration files used for Fibre
Channel devices
x86/x64 file: /kernel/drv/sd.conf
SPARC file: /kernel/drv/ssd.conf
Within the FCP Host Utility Kit, NetApp provides
a script to update the appropriate conf
basic_config [ssd_set|-sd_set]
Resulting output for ssd.conf:

43
# cat /kernel/drv/ssd.conf
...
ssd-config-list="NETAPP LUN", "netapp-ssd-config";
netapp-ssd config=1,0x9007,64,300,30,0,0,0,0,0,0,0,0,
0,30,0,0,8,0,0;

Solaris Discovery of Targets
Verify connectivity from Solaris

44
# cfgadm -al
Ap_Id Type Receptacle Occupant Condition
...
c1 fc-fabric connected unconfigured unknown
c1::10000000c92d9f76 unknown connected unconfigured unknown
c1::10000000c96b7710 unknown connected unconfigured unknown
c1::10000000c92da0c4 unknown connected unconfigured unknown
c1::500a098186f7c786 unknown connected unconfigured unknown
c1::500a098196f7c786 unknown connected unconfigured unknown
...
In your exercise environment, both
storage systems WWPNs should
be visible to Solaris
OS attachment point
Discovery
Solaris
Storage System
Fibre Channel
Fibre Channel
Initiator
Target
Discovery is
automatic
Data ONTAP Discovery of Initiators
Verify connectivity from the storage system
Portname Group
-------- -----
10:00:00:00:c9:2d:a0:63
10:00:00:00:c9:2d:9f:76

46
Solaris WWPN
NOTE: For convenience, we can alias
the Solaris WWPN
Solaris 10 Binding
In Solaris 10 with SFS, binding is no longer
needed:
SFS allows the operating system to see the FC
devices directly (also known as direct mapping)
Longer device names eliminate need for binding
SFS: /dev/rdsk/c1t00000011C6E60ARCd0
Solaris 9: /dev/rdsk/c1t0d0
To verify visible devices:
47
# luxadm probe
No Network Array enclosures found in /dev/es

Found Fibre Channel device(s):
Node WWN:500a098086f7c786 Device Type:Disk device
Logical Path:/dev/rdsk/c4t60A980004334622D4B34486B42357435d0s2
Direct mapping -
no need for
persistent binding
Summary
A single path FC architecture is simple to use
but does not provide the redundancy of a
multiple path
FC initiators and targets automatically discover
each other on a properly configured fabric
Binding is the process of associating an OS
device name to a worldwide port name
48
FC Connectivity
Data ONTAP
Windows
Solaris
Exercise
Estimated Time: 60 minutes
49 2008 NetApp. All rights reserved.
Module Review
What is the best location to identify a
supported implementation?
Interoperability Matrix
A storage system can only be configured to
communicate with either Windows initiator or
Solaris initiator but not both. True or false?
False
To easily remember a WWPN, a WWPN may
be assigned a(n) ___________.
alias

51

M02 FCConnectivity

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

M02 FCConnectivity

Uploaded by

Copyright:

Available Formats

SAN Administration

on Data ONTAP 7.3

You might also like