IBM Fusion 2.11.0 network issues: Non-Reserved VLAN IDs and Switch Upgrade Precheck Blocks

1. Run the following commands to get the switch list.
   oc get switch -n ibm-spectrum-fusion-ns
    

   Example output:

   % oc get switch -n ibm-spectrum-fusion-ns
   NAME              AGE
   hspeed1-f32l007   8h
   hspeed2-f32l007   7h23m
   mgmt1-f32l007     16d
   mgmt2-f32l007     16d  

2. Run the following command to get YAML output of the high speed switch and check the environment readiness.
   
   oc get switch <switch_name> -n ibm-spectrum-fusion-ns -o yaml

   Example output:

   oc get switch hspeed1-f32l007 -n ibm-spectrum-fusion-ns -o yaml
   environmentReadiness: 
     - category: SwitchOpenshiftVLANPorts
       message: Openshift Vlan 1510 is tagged on all the ports on hspeed1-f32l007.
       messageCode: BMYPC6051
       messageType: INFO
       noRedirection: true
       prechecks:
       - switch
     - category: SwitchCustomVLANPorts
       message: Vlan 4001 is not tagged on the ports [b_1 b_3 b_4 b_5 b_6 b_7 b_8 b_9 b_10 b_11 b_12 b_13 b_14 b_15 b_16 b_17 b_ 18] on hspeed2-f321007.
       messageCode: BMYPC6050
       messageType: ERROR
       noRedirection: true
       prechecks:
       - switch
     - category: SwitchCustomVLANPorts
       message: Vlan 4002 is not tagged on the ports [b_1 b_3 b_4 b_5 b_6 b_7 b_8 b_9 b_10 b_11 b_12 b_13 b_14 b_15 b_16 b_17 b_ 18] on hspeed2-f321007.
       messageCode: BMYPC6050
       messageType: ERROR
       noRedirection: true
       prechecks:
       - switch
     - category: SwitchCustomVLANPorts
       message: Vlan 39 is tagged on all the ports on hspeed1-f32l007.
       messageCode: BMYPC6049
       messageType: INFO
       noRedirection: true
       prechecks:
       - switch
     - category: SwitchCustomVLANPorts
       message: Vlan 4003 is not tagged on the ports [b_1 b_3 b_4 b_5 b_6 b_7 b_8 b_9 b_10 b_11 b_12 b_13 b_14 b_15 b_16 b_17 b_ 18] on hspeed2-f321007.
       messageCode: BMYPC6050
       messageType: ERROR
       noRedirection: true
       prechecks:
       - switch
     - category: SwitchCustomVLANPorts
       message: Vlan 399 is tagged on all the ports on hspeed1-f32l007.
       messageCode: BMYPC6049
       messageType: INFO
       noRedirection: true
       prechecks:
       - switch

3. If you see output like above, then follow the resolution steps.

Unable to add VLAN with VLAN ID starting with 39:

• When adding a VLAN on the IBM Fusion user interface network VLAN page, a webhook error message might appear, similar to the following:
  
  Error: VLAN “<vlanname>“ could not be added. admission webhook “vvlan.kb.io“ denied the request: VLAN ID <vlanID> should not be in reserved VLAN range. Reserved VLAN range is 3725-3999. 
   

1. Log in to the cluster using oc login command.

2. Run the following command to get the CSV.
   oc get csv -n ibm-spectrum-fusion-ns

3. Choose the correct IBM Fusion CSV to patch it with a new network operator image using the following command.
   oc edit csv <ibm-fusion-name> -n ibm-spectrum-fusion-ns

4. Enter the text /control-plane: isf-network-operator to find the occurrence.

5. In the control-plane: isf-network-operator label, scroll down to the image field, and replace the value with the following image.
   
   cp.icr.io/cp/fusion-hci/isf-network-operator@sha256:dc23f40918bf0eaa0235be561c6ed48d98e4f8bd69f6d878af20f6887794e244

1. Run the following commands to export the variables.
   export LOCAL_ISF_REGISTRY="<Your enterprise registry host>:<port>"
export LOCAL_ISF_REPOSITORY="<Your image path>"
export TARGET_PATH="$LOCAL_ISF_REGISTRY/$LOCAL_ISF_REPOSITORY"
echo "$TARGET_PATH"

2. Log in to the IBM Entitled Container Registry by using the IBM entitlement key:
   docker login cp.icr.io -u cp -p <your entitlement key>

3. Run the command to log in to the docker registry with your enterprise registry credentials.
   docker login $LOCAL_ISF_REGISTRY -u <your enterprise registry username> -p <your enterprise registrty password>

4. From the mirroring host, run the following commands to copy the below image to the artifactory.
   skopeo copy --insecure-policy --preserve-digests --all docker://cp.icr.io/cp/fusion-hci/isf-network-operator@sha256:dc23f40918bf0eaa0235be561c6ed48d98e4f8bd69f6d878af20f6887794e244 docker://$TARGET_PATH/cp/fusion-hci/isf-network-operator@sha256:dc23f40918bf0eaa0235be561c6ed48d98e4f8bd69f6d878af20f6887794e244

5. Run the following steps either using OCP user interface or CLI:
   
   OpenShift Container Platform user interface:
   1. Log in to the OpenShift Container Platform web console.
   2. Go to Operators > Installed Operators.
   3. In the Project drop-down, select ibm-spectrum-fusion-ns namespace.
   4. Click the IBM Storage Fusion installed operator that contains the CSV for the network operator image to be patched.
   5. Click YAML tab.
       It opens a YAML editor screen.

   6. In the YAML editor screen, search for the label control-plane: isf-network-operator.

   7. In the control-plane: isf-network-operator label, scroll down to the image field, and replace the value with the following image.
      
      $TARGET_PATH/cp/fusion-hci/isf-network-operator@sha256:dc23f40918bf0eaa0235be561c6ed48d98e4f8bd69f6d878af20f6887794e244

   
   Command Line Interface (CLI):
   1. Log in to the cluster using oc login command.

   2. Run the following command to get the CSV.
      oc get csv -n ibm-spectrum-fusion-ns

   3. Choose the correct IBM Fusion CSV to patch it with a new network operator image using the following command.
      oc edit csv <ibm-fusion-name> -n ibm-spectrum-fusion-ns

   4. Enter the text /control-plane: isf-network-operator to find the occurrence.

   5. In the control-plane: isf-network-operator label, scroll down to the image field, and replace the value with the following image.
      $TARGET_PATH/cp/fusion-hci/isf-network-operator@sha256:dc23f40918bf0eaa0235be561c6ed48d98e4f8bd69f6d878af20f6887794e244