Upgrading Extended Operating System (EOS) Images

CloudVision Portal (CVP) provides the functionality to upgrade the EOS image on a device. Typically, you upgrade the image on a device to change the version of the image from an unsupported image version to a supported image version.

You upgrade device images by associating an EOS image with a device or a container (the association is referred to as an image association). Image associations follow the same container inheritance rules as configlet associations. This means that the image you select to be associated is automatically inherited (assigned) to all devices under the level in the hierarchy at which you associate the image.

Note: When performing an image push, CloudVision checks if the target EOS image is already present on flash. If the .swi file is available, CloudVision uses the same file instead of downloading a new image from the network. This reduces network costs and time incurred during image upgrades.

For more information, see:

Example of Image Association

This example shows the behavior of image associations in a multi-level network hierarchy. The hierarchy in this example contains a tenant container named Demo-Lab. The Demo-Lab container has five child containers named CVX, Host-TOR1, Leaf, Spine, and TOR2.

Figure 1: Same Task Scheduled for Every Device in CVX Container

Based on the rules for image association inheritance, the Demo-Lab container could have selected the 4.18.8M device EOS image.

Figure 2: Example of image Association (Example 1)

The CVX container could override that image selection (4.18.8M image) for its devices by selecting the 4.20.7M image. As a result, all of the devices under CVX are assigned the 4.20.7M image, and the devices under Host-TOR1, Leaf, Spine and TOR2 inherit the 4.18.8M image from the Demo-Lab container.

Figure 3: Example of image Association (Example 2)

If an image association is changed at any level, and the change is saved in the Network Provisioning page, the following occurs:

  • The change impacts all devices under that level.
  • A task is automatically created to upgrade the impacted devices.

For example, if the image selection was removed at the CVX level, the following would occur:

  • All of the devices under the CVX level would inherit the Demo-Lab image.
  • A task would be scheduled for every device in CVX to use the Demo-Lab image.

Related topics:

Tip for Handling Multiple Image Association Tasks

When several image association tasks are scheduled to be completed, use the following steps to execute the tasks. These steps help you to execute the tasks more efficiently.

  1. Search on “Pending” in the Tasks page to find the tasks to be executed (status is “Pending”).
  2. Select them all by clicking the checkbox next to the Task ID heading.

    If the search results returns multiple pages of tasks, then click the checkbox at the top of each page to select the tasks so they can be executed.

    Figure 4: Selecting Multiple Tasks to be Executed
  3. Click the Play icon to execute the selected tasks all at once.