FC Connectivity

Interoperability Matrix:
http//now.netapp.com/NOW/products/interoperability

Steps to Implement SAN

1> Discovery of a Target by an initiator
2> Bind an initiator to a target (persist the binding between reboot)
3> Create an igroup on the storage system if necessary
4> Create a LUN on the storage system
5> Map a LUN to an igroup on storage system
6> Find the virtual disk (lun) on the host
7> Prepare the disk for the host OS if necessary
********************************************************************************
**********************************************
To properly configure Data ONTAP for FC connectivity:
1> Confirm FC HBA
system> sysconfig
To identify the type of the built-in HBAs
system> fcadmin config
To change an onboard interface from an initiator to a target
system> fcadmin config -d 0b /* down the interface */
system> fcadmin config -t target 0b /* Reconfigure the interface
as a target */
system> reboot /* A reboot is requ
ired */
To change onboard interfce froom a target to an initiator
system> fcadmin config -d 0b /* down the interface*/
system> fcadmin config -i initiator 0b /* Reconfigure the interface as
an initiator */
system> reboot /* A reboot is require
d */
2> Configure the fibre Channel Protocol (FCP) in Data ONTAP
> Verify the Fibre Channel Protocal (FCP) services is running
system> fcp status
> Verify FCP is licensed (licensed the FCP service if needed)
system> license
system> license add xxxxxx
> Start the FCP service
system> fcp start
3> Configure the FC target HBA(s) in Data ONTAP
system> fcp show adapter
/* list the installed HBA */
system> fcp config adapter down /*T
ake an HBA offlines */
system> fcp config adapter speed [auto|1|2|4] /* Set HB
A options if necessary */
system> fcp config adapter up
/* Bring an HBA online */
4> Identify the WWNN in Data ONTAP
system > fcp nodename
5> Identify the WWPN
system> fcp portname show
********************************************************************************
********************************************************
Verify the connectivity from the storage system
system> fcp show initiator
system> fcp wwpn-alias set mySolarisPort 10:00:00:00:c9:48:ca:9f /* to
Alais a WWPN */
system> fcp wwpn-alias remove -a melvar1 melvar0
/* removethe aliases */
system> fcp wwpn-alias remove -w 10:00:00:00:c9:48:ca:9f /*
remove all aliases for a WWN */
system> fcp wwpn-alias show [-a <alias> -w <wwpn>
/* Disaply all aliases */
********************************************************************************
*******************************************************
Windows Discovery of targets --- Using Storage Explorer (2008)
---- HBAanyway (Emulex) (2003)
Windoes/Emulex Binding ---- HBAanyway (Emulex) (2003)
Solaris/Emulex Implementation using SFS driver
32-bit driver: /kernel/drv/emlxs
64-bit driver: /kernel/drvsparcv9/emlxs
Configuration file: /kernel/drv/emlxs.conf
#prtdiag | grep LP /*
Verify that Solaris has identified the HBA */
#cat /etc/driver_alias | grep pci10df,f900 /* Identify th
e drive associated with the HBA(s)
#mdload /kernel/drv/sparcv9/emlxs /* To load the
64-bits drivers
#mdinfo | grep emxls /* to
verify the driver when loaded */
#luxadm -e port /*
verify the HBA is cponnected to the fabric */
#fcinfo hba-port /*
Identiify the local WWPN */
Within the FCP HOST Unitility Kits, NetApp provides a script to update the
appropriate conf
basic_config [-ssd_set | -sd_set]
x86/x64 file: /kernel/drv/sd.conf
SPARC file: /kernel/drv/ssd.conf
#cat /kernel/drv/ssd.conf
/* Resulting output for ssd.conf */
# cfgadm -al
 /* Verify the connective from Solaris */
system> fcp show initiators
/* Verify connectivity from the storage sysem */
# luadm probe
/* in Solaris 10, no bind ing is need /