Networking issues

Use these troubleshooting information to know the problem and workaround when you work with the networking aspects for IBM Storage Fusion.

List of all troubleshooting and known issues about networking are stated as follows.

Sometimes, the VLANs list does not show all the available VLANs for a brief time

Problem

When you click Edit link to edit a link, you notice that sometimes the VLANs list does not show all the available VLANs. This problem occurs only for a brief time.

Resolution

After a couple of minutes, cancel the edit operation and run it again to see all the available VLANs in the VLANs list.
Clag status shows bridge-priority-mismatch for the bonds on management switches running cumulus 4.3.0
Switch running Cumulus 4.3.0, after reboot, MLAG ports might go down and net show clag might report bridge-priority-mismatch. Do the following workaround steps:
1. Run the following command on both peers Sudo ifreload -a
2. If it does not solve the problem, then configure bridge-bridgeprio to be the same value as mstpctl-treeprio on the bridge interface in the /etc/network/interfaces file.
3. Run the following command: Sudo ifreload -a

Configuring F5 load balancer

You can use an external load balancer in place of the default load balancer to access OpenShift® cluster after IBM Storage Fusion HCI System installation.

Workaround:

You can use node placement and toleration to place router-default pods to the infrastructure nodes on your environment, then you can configure external load balancer to route traffic to the infrastructure nodes.

Run the following command to label worker nodes as infrastructure nodes. Ensure that use the correct worker nodes for your environment.

oc label nodes compute-1-ru5.rackd.mydomain.com node-role.kubernetes.io/infra=''
oc label nodes compute-1-ru6.rackd.mydomain.com node-role.kubernetes.io/infra=''

Create a default.yaml file to place router-default pods to the infrastructure nodes.

apiVersion: operator.openshift.io/v1
kind: IngressController
metadata:
  name: default
  namespace: openshift-ingress-operator
spec:
  nodePlacement:
    nodeSelector:
      matchLabels:
        node-role.kubernetes.io/infra: ""
    tolerations:
    - effect: NoSchedule
      operator: Exists
  replicas: 2
status: {}

Run the following command to apply the change.
```
oc apply -f default.yaml
```

Run the following command to verify that router-default pods are running on the infrastructure nodes.

oc -n openshift-ingress get pod -o wide

Example output:

NAME                            READY   STATUS    RESTARTS   AGE   IP              NODE                               NOMINATED NODE   READINESS GATES
router-default-6c8f978c-9bd9j   1/1     Running   0          23m   172.20.240.29   compute-1-ru6.rackd.mydomain.com   <none>           <none>
router-default-6c8f978c-zglxz   1/1     Running   0          23m   172.20.240.28   compute-1-ru5.rackd.mydomain.com   <none>           <none>

Configure your external load balancer. For more information, see Configuring an external load balancer.