Oracle Fabric Interconnect F1-15
 
Oracle Fabric Interconnect F1-4
 

PLA-Support>Sun Systems>SAND>Network>SN-SND: Oracle Virtual Networking
 

In this Document

Purpose

Details

Applies to:

Purpose

 Seeing recurring LUN Resets in NetApp Array logs, LUN snapshots are also failing, along with problems writing to LUNs.

Details

 In NetApp Storage Array logs see LUN reset messages along with these types of messages:

Thu May 5 22:00:00 EDT [bctnetapp2: kern.uptime.filer:info]: 10:00pm up 54 days, 15:27 0 NFS ops, 1049008 CIFS ops, 661 HTTP ops, 10609747740 FCP ops, 0 iSCSI ops
Thu May 5 22:17:46 EDT [bctnetapp2: ems.engine.inputSuppress:error]: Event 'scsitarget.partnerPath.misconfigured' suppressed 179 times since Mon May 2 19:33:50 EDT 2011.
Thu May 5 22:17:46 EDT [bctnetapp2: scsitarget.partnerPath.misconfigured:error]: FCP Partner Path Misconfigured - Host I/O access through a non-primary and non-optimal path was detected

NetApp LUN Snapshots may able also be failing.

Here are some NetApp logs snippets that show ALUA mismatched setups:

The following initiator groups have ALUA setting mismatch
igroup local partner

EXAMPLE:

ESX28 no yes
ESX27 no yes
viaRPC.21:00:00:1b:32:02:9a:ee.FLLFS01 no yes
viaRPC.21:01:00:1b:32:22:9a:ee.FLLFS01 no yes
viaRPC.21:00:00:1b:32:02:9a:ee.FLLFS04 no yes
viaRPC.21:01:00:1b:32:22:9a:ee.FLLFS04 no yes
esx06.fll.emb_smvidg_fcp no yes
ESX18 no yes
ESX22 no yes
ESX23 no yes
EAH-AMD-DMZ-CLUSTER no yes
viaRPC.21:00:00:1b:32:0f:13:89.FLLCCDEV01 yes no




With NetApp DSM 3.4 ALUA is required.
 
Here is NetApp information on  ALUA: http://www.yellow-bricks.com/2009/09/29/whats-that-alua-exactly/.

------- From the Netapp doc ----

https://now.netapp.com/NOW/knowledge/docs/mpio/win/reldsm34/html/software/install/frameset.html

Enabling ALUA for FC paths

ALUA is required for Fibre Channel paths starting with DSM 3.4.
Enable ALUA on the igroups for any LUNs with FC paths.

About this task

All igroups mapped to a LUN must have the same ALUA setting. Because ALUA is not currently supported for iSCSI, mixed FC and iSCSI paths to the same LUN are not currently supported.

Step

1. Enter the following command on the storage controller to enable ALUA on each igroup with FC paths mapped to LUNs used by the host:   

igroup set igroup_name alua yes

The host does not detect the ALUA setting until it is rebooted.

After you finish

Remove any iSCSI paths to LUNs that also use FC paths.
Parent topic: Installing the DSM

Another entry example from Netapp log, please note that Linux shows ALUA yes but the following hosts do not :

MESORACLEDB (FCP):
OS Type: linux
Host Multipathing Software: Required
Member: 50:01:39:70:00:31:21:2f (logged in on: vtic, 0b, 0d)
Member: 50:01:39:70:00:31:21:2e (logged in on: vtic, 0a, 0c)
Member: 50:01:39:70:00:32:91:32 (logged in on: 0b, 0d, vtic)
Member: 50:01:39:70:00:32:91:31 (logged in on: 0c, vtic, 0a)
ALUA: Yes
OS Type: windows
Host Multipathing Software: Required
Member: 50:01:39:70:00:32:91:2c (logged in on: 0b, 0d, vtic)
Member: 50:01:39:70:00:32:91:2b (logged in on: 0c, vtic, 0a)
Member: 50:01:39:70:00:31:21:29 (logged in on: vtic, 0b, 0d)
Member: 50:01:39:70:00:31:21:28 (logged in on: vtic, 0a, 0c)
MLBSAP02 (FCP):
OS Type: windows
Host Multipathing Software: Required
Member: 50:01:39:70:00:31:21:2b (logged in on: vtic, 0b, 0d)
Member: 50:01:39:70:00:31:21:2a (logged in on: vtic, 0a, 0c)
Member: 50:01:39:70:00:32:91:2e (logged in on: 0b, 0d, vtic)
Member: 50:01:39:70:00:32:91:2d (logged in on: 0c, vtic, 0a)
MLBSAP04 (FCP):
OS Type: windows
Host Multipathing Software: Required
Member: 50:01:39:70:00:31:21:33 (logged in on: vtic, 0b, 0d)
Member: 50:01:39:70:00:31:21:32 (logged in on: vtic, 0a, 0c)
Member: 50:01:39:70:00:32:91:36 (logged in on: 0b, 0d, vtic)
Member: 50:01:39:70:00:32:91:35 (logged in on: 0c, vtic, 0a)

This solution has no attachment