#FCP Trident Error

1 messages · Page 1 of 1 (latest)

lost lantern
#

Hi,

we have a Trident config where we get the following error message in OpenShift:
AttachVolume.Attach failed for volume "pvc-264f3132-22ab-4082-961d-1bcebe1b018f" : rpc error: code = Unknown desc = error publishing ontap-san driver: no matching WWPN found for node 20:00:d0:39:ea:d1:23:51

This WWPN is the target name of the SVM.

The SVM has 4 FCP ports configured and the zoning works without errors.

The Lun and the Igroup are created with trident.
However, the Igroup has no initiators and will not be mapped to the Lun.

Used Trident Backend Konfig:

apiVersion: trident.netapp.io/v1
kind: TridentBackendConfig
metadata:
name: tbc-san
namespace: trident
spec:
version: 1
backendName: fcp-backend
storageDriverName: ontap-san
managementLIF: X.X.X.X
svm: vsXXX
credentials:
name: XXXX
sanType: fcp
defaults:
encryption: ""

Does anyone have an idea what the reason for this error is:
error publishing ontap-san driver: no matching WWPN found for node 20:00:d0:39:ea:d1:23:51

next flame
#

is the initiator logged in into ONTAP? fcp initiator show

#

the error means Trident can't find the node's WWPNs to put in the igroup

#

are you sure the Linux kernel driver for your FC HBA is loaded correctly?