IBM Support

Failed to configure the SNMP settings on the BMC of the node

General Page

This hotfix must be applied to all IBM Fusion HCI racks that use Lenovo servers and that are upgraded to version 2.10.0.


After upgrading the rack to version 2.10.0, a call home event (BMYCO0006: Failed to configure the SNMP settings on the BMC of the node) is being triggered for all nodes due to the inclusion of a new additional manufacturer field in the configmap.

Follow the instructions to apply the hotfix:
  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 compute operator image to be patched.
  5. Click YAML tab.
     It opens a YAML editor screen.
  6. In the YAML editor screen, search for the string isf-compute-operator@sha256.
  7. In the control-plane: isf-compute-operator label, edit the isf-compute-operator@sha256 image with the new compute operator image under the manager container field. 

    For example:
    command:
      - /manager
    image: <image-goes-here>

    Online Installation:
    Compute operator image - cp.icr.io/cp/fusion-hci/isf-compute-operator@sha256:d90ea2c47f79d36757384147c180354a6ae0b30e6472f08c144afee281a0a96e

    Offline Installation:
    • Run the following command to mirror the isf-compute-operator image.

      skopeo copy --insecure-policy --preserve-digests --all docker://cp.icr.io/cp/fusion-hci/isf-compute-operator@sha256:d90ea2c47f79d36757384147c180354a6ae0b30e6472f08c144afee281a0a96e docker://$TARGET_PATH/cp/fusion-hci/isf-compute-operator@sha256:d90ea2c47f79d36757384147c180354a6ae0b30e6472f08c144afee281a0a96e
    • For example, if the TARGET_PATH is docker-na-public.artifactory.swg-devops.com/hyc-abell-devops-team-dev-offline-docker-local/hci-auto-ga-210, then the command would be:

      skopeo copy --insecure-policy --preserve-digests --all docker://cp.icr.io/cp/fusion-hci/isf-compute-operator@sha256:d90ea2c47f79d36757384147c180354a6ae0b30e6472f08c144afee281a0a96e docker://docker-na-public.artifactory.swg-devops.com/hyc-abell-devops-team-dev-offline-docker-local/hci-auto-ga-210/cp/fusion-hci/isf-compute-operator@sha256:d90ea2c47f79d36757384147c180354a6ae0b30e6472f08c144afee281a0a96e
  8. Click Save.
  9. Verify whether the isf-compute-operator pod is running with a new production image of the compute operator.

    Alternatively, you can also verify the new production image of the compute operator by using the following commands:
     
    • Run the following command to get the list of pods.
      oc get po
    • Run the following command to get the details of the isf-compute-operator pod.
      oc describe po isf-compute-operator-pod-name
    • Verify whether the container manager image is updated with the new production image.

      Note: Already raised Critical events for this issue can now be resolved from the IBM Fusion events page.

[{"Type":"MASTER","Line of Business":{"code":"LOB69","label":"Storage TPS"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSXEFDS","label":"IBM Fusion HCI Appliance Software"},"ARM Category":[{"code":"a8m3p0000000rX7AAI","label":"HW"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.10.0"}]

Document Information

Modified date:
16 July 2025

UID

ibm17238921

Page Feedback