[QUESTION]: CSM with Unity Storage

[dancohen21]

How can the Team help you today?

Details: ?

Supporting a client with Unity XT.
They want to leverage FC connectivity.
The existing host registrations on the Unity XT system have both iSCSI and FC initiators.
Is this the intended configuration?

Is it possible for these Unity XT host registrations to only have FC initiators and not to include the iSCSI initiators?

What might cause this to occur and how can we prevent it when we redeploy the CSM instance?

Thanks, Dan

[karthikk92]

• FC Configuration: If the storage and cluster are configured with FC, the FC initiators will be logged in. If not, they won’t be added in host entry and FC initiators are typically present by default as they are configured at the hardware level.
• iSCSI Utilities: If the user wants only FC and the iSCSI utilities should not be added(software iscsi), then do not install software iscsi utils, so that iSCSI won’t be added in host registration.
  @dancohen21

let me know any confusion on this further.

[dancohen21]

@karthikk92 makes sense. For a K8s deployment such as with using OpenShift, iSCSI utils are included in the worker nodes by default. Do I need to ensure that iscsid is disabled or is there another test the code is doing to check for the iscsi utils on the worker node. The more specific the better so I can assist this client. Thanks!

[karthikk92]

@dancohen21
If you don't want the initiators to be present, uninstall the iSCSI utils package if possible. Otherwise, as per default configuration, initiators will be present but it will be inactive.

[dancohen21]

@karthikk92
We got a little creative, removing the iSCSI Utils seemed challenging with openshift and coreos.
So, we disabled the iscsi service and we added a machineconfig to blank out the iscsi inititorname file.

Redeploying the CSM instance after applying this machineconfig, the iSCSI initiator records were not made on the Unity.

apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfig
metadata:
labels:
machineconfiguration.openshift.io/role: worker
name: 99-worker-delete-iqn
spec:
config:
ignition:
version: 3.2.0
systemd:
units:
- contents: |
[Unit]
Description=Custom CoreOS remove iscsi iqn

       [Service]
       Type=oneshot
       ExecStart=/usr/bin/cp /dev/null /etc/iscsi/initiatorname.iscsi
       RemainAfterExit=yes

       [Install]
       WantedBy=multi-user.target
     enabled: true
     name: custom-coreos-remove-iscsi-iqn.service

[karthikk92]

That's Great . So @dancohen21 are we good with this ticket and close on this ?