Upgrading Firmware

In general, firmware may be upgraded whenever new versions are made available for the system. Firmware upgrades can be applied in no particular order and independently of other components. Firmware is included in the ISO content for all component ILOMs, for the ZFS Storage Appliance, and for the switches. Select the instructions for the component type you want to upgrade.

Use the upgrade plan to check the progress of the appliance upgrade, and determine which firmware upgrades still need to be performed.

Upgrading ILOMs

ILOM upgrades can be applied to management nodes and compute nodes; the firmware packages might be different per component type. To upgrade one or more ILOMs outside of the full rack upgrade workflow, follow these instructions. You can either upgrade a single ILOM by providing its IP address, or the ILOMs of all management and compute nodes installed in the appliance.

If new firmware is available for the internal drives and network interface cards installed in the management and compute nodes, the updates are applied as part as the ILOM upgrade process.

Caution:

You must NOT upgrade the ILOM of the management node that holds the management virtual IP address, and thus the primary role in the cluster. To determine which management node has the primary role in the cluster, and make another node the primary, use the following Service CLI commands: 

PCA-ADMIN> getPrimaryMgmtNode
Data:
  data = pcamn01

PCA-ADMIN> updatePrimaryNode node=pcamn02
Data:
  message = Successfully issued update primary node command

PCA-ADMIN> getPrimaryMgmtNode
Data:
  data = pcamn02

Obtaining an ILOM IP Address

Using the Service Web UI

  1. In the navigation menu, click Rack Units.

  2. Click the name of the component that requires new ILOM firmware.

  3. Select the Rack Unit Information tab.

  4. Record the IP Address listed under ILOM IPs.

Using the Service CLI

  • To list the ILOM IP addresses of all management nodes or compute nodes, use these commands: 

    PCA-ADMIN> getCNIloms
Data:
  data 1 = 100.96.0.66
  data 2 = 100.96.0.64
  data 3 = 100.96.0.65
[...]

PCA-ADMIN> getMNIloms
Data:
  data 1 = 100.96.0.33
  data 2 = 100.96.0.34
  data 3 = 100.96.0.35

  • To obtain the ILOM IP address that corresponds with a specific node host name, use the following command: 

    PCA-ADMIN> getServerILOMIP hostName=<node_name>

    For example:

    PCA-ADMIN> getServerILOMIP hostName=pcacn002
Data:
  data = 100.96.0.65

PCA-ADMIN> getServerILOMIP hostName=pcamn03
Data:
  data = 100.96.0.35

  • To obtain the ID, IP addresses, and other key information about compute nodes or management nodes, use the following commands:

    PCA-ADMIN> list managementNode fields hostname,ipAddress,ilomIp,state,firmwareVersion orderby hostname ASCENDING
Data:
  id                                     Hostname   Ip Address    ILOM Ip Address   State   Firmware Version
  --                                     --------   ----------    ---------------   -----   ----------------
  22ae47d8-a57a-433c-988d-df62fd3548e1   pcamn01    100.96.2.33   100.96.0.33       On      5.1.4.25
  042693b6-3ddb-4fb0-914d-f3deea838c8f   pcamn02    100.96.2.34   100.96.0.34       On      5.1.4.25
  bd2563b8-e310-4fca-ba1b-0e19b8040fc6   pcamn03    100.96.2.35   100.96.0.35       On      5.1.4.25

PCA-ADMIN> list computeNode fields hostname,ipAddress,ilomIp,state,firmwareVersion,provisioningLocked,maintenanceLocked orderby hostname ASCENDING
Data:
  id                                     Hostname   Ip Address    ILOM Ip Address   State   Firmware Version           Provisioning Locked   Maintenance Locked
  --                                     --------   ----------    ---------------   -----   ----------------           -------------------   ------------------
  cf488903-fef8-4a51-8a41-c6990e4755c5   pcacn001   100.96.2.64   100.96.0.64       On      PCA Hypervisor:3.0.2-859   false                 false             
  42a7594d-1173-4dbd-4755-07810cc2d527   pcacn002   100.96.2.65   100.96.0.65       On      PCA Hypervisor:3.0.2-859   false                 false             
  bc0f37d5-ba77-423e-bc11-017704b47e59   pcacn003   100.96.2.66   100.96.0.66       On      PCA Hypervisor:3.0.2-859   false                 false             
  2e5ac527-01f5-4230-ae41-0522fcb57c9a   pcacn004   100.96.2.67   100.96.0.67       On      PCA Hypervisor:3.0.2-859   false                 false             
  5a6b61cf-7e99-4df2-87e4-b37c5fb0bfb8   pcacn005   100.96.2.68   100.96.0.68       On      PCA Hypervisor:3.0.2-859   false                 false             
  885f2aa4-f017-41e8-b2bc-e588cc0c6162   pcacn006   100.96.2.69   100.96.0.69       On      PCA Hypervisor:3.0.2-859   false                 false

Upgrading a Single ILOM

Using the Service Web UI

  1. Get the IP address of the component ILOM you intend to upgrade.

  2. In the navigation menu, go to the Maintenance section and click Upgrade Plan. This provides an overview of current and target component versions.

  3. Click Upgrade & Patching to display the Upgrade Jobs page.

  4. In the top-right corner of the Upgrade Jobs page, click Create Upgrade or Patch.

    The Create Request window appears. Choose Upgrade as the Request Type.

  5. Select the appropriate upgrade request type: Upgrade Rack.

  6. Fill out the upgrade request parameters:

    • Action: To perform the upgrade or patch operation, select Apply.

    • Type: For upgrade, select ISO. The ULN option applies to patching.

    • Component: For a single ILOM, select ILOM.

    • Qualifier: Enter the component's assigned IP address in the ILOM network. This is an IP address in the internal 100.96.0.0/23 range.

    • Verify Only: Enable this option to run the operation in verification only mode.

    • Force: Enable this option to force the operation. Use only when instructed by Oracle.

  7. Click Create Request.

    The new upgrade request appears in the Upgrade Jobs table.

  8. Confirm that the upgrade workflow is completed without errors.

    For more information, see Browse the Job Framework.

Using the Service CLI

  1. Enter the ILOM upgrade command.

    Syntax (entered on a single line):

    upgradeRack type=ISO action=APPLY component=ILOM qualifier=<component-ip>

    Example:

    PCA-ADMIN> upgradeRack type=ISO action=APPLY component=ILOM qualifier=100.96.0.34
JobId: caf53268-bfb5-4e63-b96d-5446728a1617
Data: Service request has been submitted. Upgrade Job Id = 1737620133356-ilom-632638 Upgrade Request Id = UWS-ffc59a65-04d1-49a3-b194-4055a34fd30f

  2. Use the job ID to check the status of the upgrade process.

    PCA-ADMIN> getUpgradeJob upgradeJobId=1737620133356-ilom-632638
Data:
  Upgrade Request Id = UWS-ffc59a65-04d1-49a3-b194-4055a34fd30f
  Name = ilom
  Pid = 632638
  Host = pcamn01
  Log File = /nfs/shared_storage/pca_upgrader/log/pca-upgrader_ilom_firmware_ilom-pcamn02_2025_01_23-08.15.33.log
  Arguments = {"component_names":null,"diagnostics":false,"display_task_plan":false,"dry_run_tasks":false,"expected_iso_checksum":null,"fail_halt":false,"fail_upgrade":null,"image_location":null,"online_upgrade":null,"precheck_status":false,"repo_config_override":null,"result_override":null,"task_time":0,"test_run":false,"upgrade":false,"upgrade_to":null,"user_uln_base_url":null,"verify_only":false,"host_ip":"100.96.0.34","log_level":null,"switch_type":null,"epld_image_location":null,"checksum":null,"composition_id":null,"request_id":"UWS-ffc59a65-04d1-49a3-b194-4055a34fd30f","uln":null,"patch":"false"}
  Status = Passed
  Execution Time(sec) = 627
[...]

  3. Confirm that the upgrade process is completed without errors.

    For more information, see Browse the Job Framework.

Upgrading All ILOMs

Using the Service Web UI

  1. In the navigation menu, go to the Maintenance section and click Upgrade Plan. This provides an overview of current and target component versions.

  2. Click Upgrade & Patching to display the Upgrade Jobs page.

  3. In the top-right corner of the Upgrade Jobs page, click Create Upgrade or Patch.

    The Create Request window appears. Choose Upgrade as the Request Type.

  4. Select the appropriate upgrade request type: Upgrade Rack.

  5. Fill out the upgrade request parameters:

    • Action: To perform the upgrade or patch operation, select Apply.

    • Type: For upgrade, select ISO. The ULN option applies to patching.

    • Component: For all ILOM in the system, select All ILOMs.

    • Qualifier: This parameter is not required when upgrading all ILOMs.

    • Verify Only: Enable this option to run the operation in verification only mode.

    • Force: Enable this option to force the operation. Use only when instructed by Oracle.

  6. Click Create Request.

    The new upgrade request appears in the Upgrade Jobs table.

  7. Confirm that the upgrade workflow is completed without errors.

    For more information, see Browse the Job Framework.

Using the Service CLI

  1. Enter the ILOM upgrade command. 

    PCA-ADMIN> upgradeRack type=ISO action=APPLY component=ALL_ILOMS
JobId: 948c4347-42d4-4d30-9f7e-bda0811786cf
Data: Service request has been submitted. Upgrade Request Id = UWS-3c4705f9-0018-4de8-832a-a48988f87ed4

  2. Use the request ID to check the status of this multi-component upgrade process.

    PCA-ADMIN> getUpgradeStatus requestId=UWS-3c4705f9-0018-4de8-832a-a48988f87ed4
Data:
  Request id = UWS-3c4705f9-0018-4de8-832a-a48988f87ed4
  Status = Passed
  Composition ID = all_iloms
  Type = ISO
  Previous Build = 3.0.2-b1300385
  Target Build = 3.0.2-b1301270
  Jobs 1 = 1737622769421-ilom-1113777
  Jobs 2 = 1737622777728-ilom-1115513
  Jobs 3 = 1737622846917-ilom-1136625
  Jobs 4 = 1737622914588-ilom-1152088
  Jobs 5 = 1737622981976-ilom-1165085
  Jobs 6 = 1737623062171-ilom-1180415
  Completed Components 1 = ilom(100.96.0.33)
  Completed Components 2 = ilom(100.96.0.34)
  Completed Components 3 = ilom(100.96.0.35)
  Completed Components 4 = ilom(100.96.0.64)
  Pending Components 1 = ilom(100.96.0.65)
  Pending Components 2 = ilom(100.96.0.66)

  3. Optionally, check the details of an individual ILOM upgrade job. 

    PCA-ADMIN> getUpgradeJobs requestId=UWS-3c4705f9-0018-4de8-832a-a48988f87ed4
Data:
  id                           Upgrade Request Id                         Command Name   Result
  --                           ------------------                         ------------   ------
  1737623062171-ilom-1180415   UWS-3c4705f9-0018-4de8-832a-a48988f87ed4   ilom           None  
  1737622981976-ilom-1165085   UWS-3c4705f9-0018-4de8-832a-a48988f87ed4   ilom           None  
  1737622914588-ilom-1152088   UWS-3c4705f9-0018-4de8-832a-a48988f87ed4   ilom           Passed
  1737622846917-ilom-1136625   UWS-3c4705f9-0018-4de8-832a-a48988f87ed4   ilom           Passed
  1737622777728-ilom-1115513   UWS-3c4705f9-0018-4de8-832a-a48988f87ed4   ilom           Passed
  1737622769421-ilom-1113777   UWS-3c4705f9-0018-4de8-832a-a48988f87ed4   ilom           Passed

PCA-ADMIN> getUpgradeJob upgradeJobId=1737622846917-ilom-1136625
Data:
  Upgrade Request Id = UWS-3c4705f9-0018-4de8-832a-a48988f87ed4
  Composition Id = all_iloms
  Name = ilom
  Pid = 1136625
  Host = pcamn01
  Log File = /nfs/shared_storage/pca_upgrader/log/pca-upgrader_ilom_firmware_ilom-pcamn03_2025_01_23-09.00.46.log
  Arguments = {"component_names":null,"diagnostics":false,"display_task_plan":false,"dry_run_tasks":false,"expected_iso_checksum":null,"fail_halt":false,"fail_upgrade":null,"image_location":null,"online_upgrade":null,"precheck_status":false,"repo_config_override":null,"result_override":null,"task_time":0,"test_run":false,"upgrade":false,"upgrade_to":null,"user_uln_base_url":null,"verify_only":false,"host_ip":"100.96.0.35","log_level":null,"switch_type":null,"epld_image_location":null,"checksum":null,"composition_id":"all_iloms","request_id":"UWS-3c4705f9-0018-4de8-832a-a48988f87ed4","uln":null,"patch":"false"}
  Status = Passed
  Execution Time(sec) = 767
[...]

  4. Confirm that the entire upgrade is completed without errors. Use the getUpgradeStatus and getUpgradeJob commands.

    For more information, see Browse the Job Framework.

Rebooting Nodes After ILOM Upgrade

At the end of the upgrade, the ILOM itself is rebooted automatically. However, the server component also needs to be rebooted for all changes to take effect. Wait 5 minutes to allow the ILOM workflow to complete first.

For minimum operational impact, schedule the compute node and management node reboot operations after all ILOMs have been upgraded.

Take into account that rebooting the compute nodes requires migrating the compute instances. For more information, see "Performing Compute Node Operations" in the Hardware Administration chapter of the Oracle Private Cloud Appliance Administrator Guide.

To reboot a compute node, get its ID and run the reset command. 

PCA-ADMIN> list ComputeNode
PCA-ADMIN> reset id=<compute-node-id>

A management node reboot is a delicate and lengthy process that involves several cluster operations. Ensure that operations on the entire management cluster are fully restored before rebooting another node.

To reboot a management node, use the restartServer command with the node host name.

Caution:

Always verify the cluster state before rebooting a management node. Consult the Oracle Private Cloud Appliance Release Notes for more information: refer to the known issue "Rebooting a Management Node while the Cluster State is Unhealthy Causes Platform Integrity Issues". 

Syntax: restartServer serverName=<pcamn01|pcamn02|pcamn03>

Example:
PCA-ADMIN> restartServer serverName=pcamn03
Data:
  status = true
  message = Successfully added pcamn03 to the queue to restart

Upgrading the ZFS Storage Appliance

To upgrade the operating software of the system's ZFS Storage Appliance, you enter the upgrade command with no additional parameters. The IP addresses of the storage controllers and the location of the firmware package are known, and a single upgrade command initiates a rolling upgrade of both controllers. If a new ILOM firmware version is included for the two controllers, it will be installed as part of this upgrade process.

Caution:

Ensure that no users are logged in to the ZFS Storage Appliance or the storage controller ILOMs during the upgrade process.

Do not make storage configuration changes while an upgrade is in progress. While controllers are running different software versions, configuration changes made to one controller are not propagated to its peer controller.

During firmware upgrade the storage controllers are placed in active/passive mode. They automatically return to active/active after the upgrade is completed.

Before You Begin

Before you initiate a ZFS Storage Appliance upgrade, you must disable the node state service to prevent errors in node states after the upgrade.

  1. From a management node, set the provisioning lock by issuing this command: 
    pca-admin locks set system provisioning
  2. Perform the ZFS Storage Appliance upgrade using either the Service Web UI or the Service CLI procedure below.
  3. Release the provisioning lock.
    pca-admin locks unset system provisioning
  4. Confirm the lock state.
    pca-admin locks show system

Upgrading the Operating Software

Using the Service Web UI

  1. In the navigation menu, go to the Maintenance section and click Upgrade Plan. This provides an overview of current and target component versions.

  2. Click Upgrade & Patching to display the Upgrade Jobs page.

  3. In the top-right corner of the Upgrade Jobs page, click Create Upgrade or Patch.

    The Create Request window appears. Choose Upgrade as the Request Type.

  4. Select the appropriate upgrade request type: Upgrade Rack.

  5. Fill out the upgrade request parameters:

    • Action: To perform the upgrade or patch operation, select Apply.

    • Type: For upgrade, select ISO. The ULN option applies to patching.

    • Component: For the ZFS Storage Appliance operating software, select ZFSSA.

    • Qualifier: This parameter is not required when upgrading the ZFS Storage Appliance.

    • Verify Only: Enable this option to run the operation in verification only mode.

    • Force: Enable this option to force the operation. Use only when instructed by Oracle.

  6. Click Create Request.

    The new upgrade request appears in the Upgrade Jobs table.

  7. Confirm that the upgrade process is completed without errors.

    For more information, see Browse the Job Framework.

Using the Service CLI

  1. Enter the upgrade command.

    PCA-ADMIN> upgradeRack type=ISO action=APPLY component=ZFSSA
JobId: 6e6afce0-31bf-47fa-9d82-04e0634cc22b
Data: Service request has been submitted. Upgrade Job Id = 1737620335404-zfssa-658852 Upgrade Request Id = UWS-19412b1f-002d-44cd-bc7c-9c8b5de14e2d

  2. Use the job ID to check the status of the upgrade process.

    PCA-ADMIN> getUpgradeJob upgradeJobId=1737620335404-zfssa-658852
Data:
  Upgrade Request Id = UWS-19412b1f-002d-44cd-bc7c-9c8b5de14e2d
  Name = zfssa
  Pid = 658852
  Host = pcamn01
  Log File = /nfs/shared_storage/pca_upgrader/log/pca-upgrader_zfssa_ak_2025_01_23-08.18.55.log
  Arguments = {"component_names":null,"diagnostics":false,"display_task_plan":false,"dry_run_tasks":false,"expected_iso_checksum":null,"fail_halt":false,"fail_upgrade":null,"image_location":null,"online_upgrade":null,"precheck_status":false,"repo_config_override":null,"result_override":null,"task_time":0,"test_run":false,"upgrade":false,"upgrade_to":null,"user_uln_base_url":null,"verify_only":false,"host_ip":null,"log_level":null,"switch_type":null,"epld_image_location":null,"checksum":null,"composition_id":null,"request_id":"UWS-19412b1f-002d-44cd-bc7c-9c8b5de14e2d","uln":null,"patch":"false"}
  Status = Passed
  Execution Time(sec) = 739
[...]

  3. Confirm that the upgrade process is completed without errors.

    For more information, see Browse the Job Framework.

Upgrading Switches

The appliance rack contains three categories of Cisco Nexus switches: a management switch, two leaf switches, and two spine switches. They all run the same Cisco NX-OS network operating software. You must perform the upgrades in this order: leaf switches first, then spine switches, and finally the management switch.

You can either upgrade a single switch category, or all switches installed in the appliance. Only one command per switch category is required. The leaf switches and the spine switches are upgraded in pairs.

Some versions of the network operating software consist of two files: a binary file and an additional EPLD (electronic programmable logic device) image. Both are automatically retrieved from their designated location during the upgrade process, and applied in the correct order.

Caution:

Verify that all required switch ports are operational. If ports are down, an outage will occur during switch upgrade/patching. For more information, see known issue Switch Upgrade or Patch Procedure Not Blocked When Ports Are Down in the "Oracle Private Cloud Appliance Release Notes".

Upgrading a Single Switch Type

Using the Service Web UI

  1. In the navigation menu, go to the Maintenance section and click Upgrade Plan. This provides an overview of current and target component versions.

  2. Click Upgrade & Patching to display the Upgrade Jobs page.

  3. In the top-right corner of the Upgrade Jobs page, click Create Upgrade or Patch.

    The Create Request window appears. Choose Upgrade as the Request Type.

  4. Select the appropriate upgrade request type: Upgrade Rack.

  5. Fill out the upgrade request parameters:

    • Action: To perform the upgrade or patch operation, select Apply.

    • Type: For upgrade, select ISO. The ULN option applies to patching.

    • Component: For a single switch type, select Switch.

    • Qualifier: Enter the switch type you intend to upgrade: leaf - spine - mgmt. The upgrade order is as follows: leaf switches first, then spine switches, and finally the management switch.

    • Verify Only: Enable this option to run the operation in verification only mode.

    • Force: Enable this option to force the operation. Use only when instructed by Oracle.

  6. Click Create Request.

    The new upgrade request appears in the Upgrade Jobs table.

  7. Confirm that the upgrade process is completed without errors.

    For more information, see Browse the Job Framework.

Using the Service CLI

  1. Enter the switch upgrade command.

    Syntax (entered on a single line):

    upgradeRack type=ISO action=APPLY
component=SWITCH qualifier=[leaf | spine | mgmt]

    Example:

    PCA-ADMIN> upgradeRack type=ISO action=APPLY component=SWITCH qualifier=leaf
JobId: 8855dcd2-5f24-41e9-8ad6-3c12ddec1458
Data: Service request has been submitted. Upgrade Job Id = 1737620242708-cisco-646097 Upgrade Request Id = UWS-7cf998f6-7077-4137-a325-02dd990ea64c

  2. Use the job ID to check the status of the upgrade process.

    PCA-ADMIN> getUpgradeJob upgradeJobId=1737620256788-cisco-646097
Data:
  Upgrade Request Id = UWS-7cf998f6-7077-4137-a325-02dd990ea64c
  Name = cisco
  Pid = 646097
  Host = pcamn01
  Log File = /nfs/shared_storage/pca_upgrader/log/pca-upgrader_cisco_firmware_leaf_2025_01_23-08.17.36.log
  Arguments = {"component_names":null,"diagnostics":false,"display_task_plan":false,"dry_run_tasks":false,"expected_iso_checksum":null,"fail_halt":false,"fail_upgrade":null,"image_location":null,"online_upgrade":null,"precheck_status":false,"repo_config_override":null,"result_override":null,"task_time":0,"test_run":false,"upgrade":false,"upgrade_to":null,"user_uln_base_url":null,"verify_only":false,"host_ip":null,"log_level":null,"switch_type":"leaf","epld_image_location":null,"checksum":null,"composition_id":null,"request_id":"UWS-7cf998f6-7077-4137-a325-02dd990ea64c","uln":null,"patch":"false"}
  Status = Passed
  Execution Time(sec) = 624
[...]

  3. Confirm that the upgrade process is completed without errors.

    For more information, see Browse the Job Framework.

Upgrading All Switches

Using the Service Web UI

  1. In the navigation menu, go to the Maintenance section and click Upgrade Plan. This provides an overview of current and target component versions.

  2. Click Upgrade & Patching to display the Upgrade Jobs page.

  3. In the top-right corner of the Upgrade Jobs page, click Create Upgrade or Patch.

    The Create Request window appears. Choose Upgrade as the Request Type.

  4. Select the appropriate upgrade request type: Upgrade Rack.

  5. Fill out the upgrade request parameters:

    • Action: To perform the upgrade or patch operation, select Apply.

    • Type: For upgrade, select ISO. The ULN option applies to patching.

    • Component: For all the switches installed in the system, select All Switches.

    • Qualifier: This parameter is not required when upgrading all switches.

    • Verify Only: Enable this option to run the operation in verification only mode.

    • Force: Enable this option to force the operation. Use only when instructed by Oracle.

  6. Click Create Request.

    The new upgrade request appears in the Upgrade Jobs table.

  7. Confirm that the upgrade workflow is completed without errors.

    For more information, see Browse the Job Framework.

Using the Service CLI

  1. Enter the switch upgrade command.

    PCA-ADMIN> upgradeRack type=ISO action=APPLY component=ALL_SWITCHES
JobId: 7c39653d-b490-4c7f-8a05-d7f137ed168e
Data: Service request has been submitted. Upgrade Request Id = UWS-ba897ac1-934d-476f-b3b5-be713cfbcdab

  2. Use the request ID to check the status of this multi-component upgrade process.

    PCA-ADMIN> getUpgradeStatus requestId=UWS-ba897ac1-934d-476f-b3b5-be713cfbcdab
Data:
  Request id = UWS-ba897ac1-934d-476f-b3b5-be713cfbcdab
  Status = Running
  Composition ID = all_switches
  Type = ISO
  Previous Build = 3.0.2-b1300385
  Target Build = 3.0.2-b1301270
  Jobs 1 = 1737622021772-cisco-979985
  Jobs 2 = 1737622029474-cisco-981089
  Jobs 3 = 1737622098759-cisco-989501
  Completed Components 1 = switch(leaf)
  Completed Components 2 = switch(spine)
  Pending Components 1 = switch(mgmt)

  3. Optionally, check the details of an individual switch upgrade job.

    PCA-ADMIN> getUpgradeJobs requestId=UWS-ba897ac1-934d-476f-b3b5-be713cfbcdab
Data:
  id                           Upgrade Request Id                         Command Name   Result
  --                           ------------------                         ------------   ------
  1737622098759-cisco-989501   UWS-ba897ac1-934d-476f-b3b5-be713cfbcdab   cisco          None
  1737622029474-cisco-981089   UWS-ba897ac1-934d-476f-b3b5-be713cfbcdab   cisco          Passed
  1737622021772-cisco-979985   UWS-ba897ac1-934d-476f-b3b5-be713cfbcdab   cisco          Passed

PCA-ADMIN> getUpgradeJob upgradeJobId=1737622021772-cisco-979985
Data:
  Upgrade Request Id = UWS-ba897ac1-934d-476f-b3b5-be713cfbcdab
  Composition Id = all_switches
  Name = cisco
  Pid = 979985
  Host = pcamn01
  Log File = /nfs/shared_storage/pca_upgrader/log/pca-upgrader_cisco_firmware_leaf_2025_01_23-08.47.01.log
  Arguments = {"component_names":null,"diagnostics":false,"display_task_plan":false,"dry_run_tasks":false,"expected_iso_checksum":null,"fail_halt":false,"fail_upgrade":null,"image_location":null,"online_upgrade":null,"precheck_status":false,"repo_config_override":null,"result_override":null,"task_time":0,"test_run":false,"upgrade":false,"upgrade_to":null,"user_uln_base_url":null,"verify_only":false,"host_ip":null,"log_level":null,"switch_type":"leaf","epld_image_location":null,"checksum":null,"composition_id":"all_switches","request_id":"UWS-ba897ac1-934d-476f-b3b5-be713cfbcdab","uln":null,"patch":"false"}
  Status = Passed
  Execution Time(sec) = 2209
[...]

  4. Confirm that the entire upgrade is completed without errors. Use the getUpgradeStatus and getUpgradeJob commands.

    For more information, see Browse the Job Framework.