Doc update on simultaneous iSCSI and FC Protocol Support (#1441)

* Updated the the fc and iscsi dependency notes * Updated the the fc and iscsi dependency notes * Updated the the fc and iscsi dependency notes * Updated FC initiator to FC WWNs * Updated the notes --------- Co-authored-by: Surya Gupta <[email protected]>
dell · Feb 5, 2025 · c3ceefc · c3ceefc
1 parent fe796fe
commit c3ceefc
Show file tree

Hide file tree

Showing 8 changed files with 20 additions and 0 deletions.
diff --git a/content/docs/csidriver/troubleshooting/unity.md b/content/docs/csidriver/troubleshooting/unity.md
@@ -16,3 +16,4 @@ description: Troubleshooting Unity XT Driver
 | When a node goes down, the block volumes attached to the node cannot be attached to another node | 1. Force delete the pod running on the node that went down <br /> 2. Delete the VolumeAttachment to the node that went down. <br /> Now the volume can be attached to the new node. |
 | Standby controller pod is in crashloopbackoff state | Scale down the replica count of the controller pod's deployment to 1 using ```kubectl scale deployment <deployment_name> --replicas=1 -n <driver_namespace>``` |
 | fsGroupPolicy may not work as expected without root privileges for NFS only [https://github.com/kubernetes/examples/issues/260](https://github.com/kubernetes/examples/issues/260) | To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter |
+| When both iSCSI IQNs and FC WWNs are present, host registrations on Unity systems will include all initiators. If only FC WWNs are present, a warning message will appear: **‘iSCSI Initiators’ cannot be retrieved.**| Ensure only desired initiators are configured on the worker nodes to limit the initiators included in the host registrations |
diff --git a/content/docs/deployment/helm/drivers/installation/unity.md b/content/docs/deployment/helm/drivers/installation/unity.md
@@ -51,6 +51,10 @@ If you use the iSCSI protocol, set up the iSCSI initiators as follows:
 - Enable and start the _iscsid_ service on each Kubernetes worker node. This service is responsible for managing the iSCSI initiator. You can enable the service by running the following command on all worker nodes: `systemctl enable --now iscsid`
 - Ensure that the unique initiator name is set in _/etc/iscsi/initiatorname.iscsi_.
 
+**Note**: The Dell CSI driver supports both iSCSI and FC protocols simultaneously.If both iSCSI IQNs and 
+FC WWNs are present, then the Host registrations on the Unity system will include all initiators. 
+    To limit the initiators, ensure only the desired initiators are configured on the worker nodes.
+
 For more information about configuring iSCSI, see [Dell Host Connectivity guide](https://www.delltechnologies.com/asset/en-us/products/storage/technical-support/docu5128.pdf).
 
 ### Linux multipathing requirements

diff --git a/content/v1/csidriver/troubleshooting/unity.md b/content/v1/csidriver/troubleshooting/unity.md
@@ -16,3 +16,4 @@ description: Troubleshooting Unity XT Driver
 | When a node goes down, the block volumes attached to the node cannot be attached to another node | 1. Force delete the pod running on the node that went down <br /> 2. Delete the VolumeAttachment to the node that went down. <br /> Now the volume can be attached to the new node. |
 | Standby controller pod is in crashloopbackoff state | Scale down the replica count of the controller pod's deployment to 1 using ```kubectl scale deployment <deployment_name> --replicas=1 -n <driver_namespace>``` |
 | fsGroupPolicy may not work as expected without root privileges for NFS only [https://github.com/kubernetes/examples/issues/260](https://github.com/kubernetes/examples/issues/260) | To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter |
+| When both iSCSI IQNs and FC WWNs are present, host registrations on Unity systems will include all initiators. If only FC WWNs are present, a warning message will appear: **‘iSCSI Initiators’ cannot be retrieved.**| Ensure only desired initiators are configured on the worker nodes to limit the initiators included in the host registrations |
diff --git a/content/v1/deployment/helm/drivers/installation/unity.md b/content/v1/deployment/helm/drivers/installation/unity.md
@@ -53,6 +53,10 @@ If you use the iSCSI protocol, set up the iSCSI initiators as follows:
 
 For more information about configuring iSCSI, see [Dell Host Connectivity guide](https://www.delltechnologies.com/asset/en-us/products/storage/technical-support/docu5128.pdf).
 
+**Note**: The Dell CSI driver supports both iSCSI and FC protocols simultaneously.If both iSCSI IQNs and 
+FC WWNs are present, then the Host registrations on the Unity system will include all initiators. 
+    To limit the initiators, ensure only the desired initiators are configured on the worker nodes.
+
 ### Linux multipathing requirements
 
 Dell Unity XT supports Linux multipathing. Configure Linux multipathing before installing the CSI Driver for Dell

diff --git a/content/v2/csidriver/troubleshooting/unity.md b/content/v2/csidriver/troubleshooting/unity.md
@@ -16,3 +16,4 @@ description: Troubleshooting Unity XT Driver
 | When a node goes down, the block volumes attached to the node cannot be attached to another node | 1. Force delete the pod running on the node that went down <br /> 2. Delete the VolumeAttachment to the node that went down. <br /> Now the volume can be attached to the new node. |
 | Standby controller pod is in crashloopbackoff state | Scale down the replica count of the controller pod's deployment to 1 using ```kubectl scale deployment <deployment_name> --replicas=1 -n <driver_namespace>``` |
 | fsGroupPolicy may not work as expected without root privileges for NFS only [https://github.com/kubernetes/examples/issues/260](https://github.com/kubernetes/examples/issues/260) | To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter |
+| When both iSCSI IQNs and FC WWNs are present, host registrations on Unity systems will include all initiators. If only FC WWNs are present, a warning message will appear: **‘iSCSI Initiators’ cannot be retrieved.**| Ensure only desired initiators are configured on the worker nodes to limit the initiators included in the host registrations |
diff --git a/content/v2/deployment/helm/drivers/installation/unity.md b/content/v2/deployment/helm/drivers/installation/unity.md
@@ -54,6 +54,10 @@ If you use the iSCSI protocol, set up the iSCSI initiators as follows:
 
 For more information about configuring iSCSI, see [Dell Host Connectivity guide](https://www.delltechnologies.com/asset/en-us/products/storage/technical-support/docu5128.pdf).
 
+**Note**: The Dell CSI driver supports both iSCSI and FC protocols simultaneously.If both iSCSI IQNs and 
+FC WWNs are present, then the Host registrations on the Unity system will include all initiators. 
+    To limit the initiators, ensure only the desired initiators are configured on the worker nodes.
+
 ### Linux multipathing requirements
 Dell Unity XT supports Linux multipathing. Configure Linux multipathing before installing the CSI Driver for Dell
 Unity XT.

diff --git a/content/v3/csidriver/troubleshooting/unity.md b/content/v3/csidriver/troubleshooting/unity.md
@@ -16,3 +16,4 @@ description: Troubleshooting Unity XT Driver
 | When a node goes down, the block volumes attached to the node cannot be attached to another node | 1. Force delete the pod running on the node that went down <br /> 2. Delete the VolumeAttachment to the node that went down. <br /> Now the volume can be attached to the new node. |
 | Standby controller pod is in crashloopbackoff state | Scale down the replica count of the controller pod's deployment to 1 using ```kubectl scale deployment <deployment_name> --replicas=1 -n <driver_namespace>``` |
 | fsGroupPolicy may not work as expected without root privileges for NFS only [https://github.com/kubernetes/examples/issues/260](https://github.com/kubernetes/examples/issues/260) | To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter |
+| When both iSCSI IQNs and FC WWNs are present, host registrations on Unity systems will include all initiators. If only FC WWNs are present, a warning message will appear: **‘iSCSI Initiators’ cannot be retrieved.**| Ensure only desired initiators are configured on the worker nodes to limit the initiators included in the host registrations |
diff --git a/content/v3/deployment/helm/drivers/installation/unity.md b/content/v3/deployment/helm/drivers/installation/unity.md
@@ -50,6 +50,10 @@ If you use the iSCSI protocol, set up the iSCSI initiators as follows:
 
 For more information about configuring iSCSI, see [Dell Host Connectivity guide](https://www.delltechnologies.com/asset/en-us/products/storage/technical-support/docu5128.pdf).
 
+**Note**: The Dell CSI driver supports both iSCSI and FC protocols simultaneously.If both iSCSI IQNs and 
+FC WWNs are present, then the Host registrations on the Unity system will include all initiators. 
+    To limit the initiators, ensure only the desired initiators are configured on the worker nodes.
+
 ### Linux multipathing requirements
 Dell Unity XT supports Linux multipathing. Configure Linux multipathing before installing the CSI Driver for Dell
 Unity XT.