Upgrading Core or MEP Components

Depending on your current configuration, you may choose to upgrade the release version (core), ecosystem components, clients, or monitoring components.

Getting Started with Upgrades

Most upgrades involve moving from one version of core to another version and upgrading Ecosystem Pack (MEP) components at the same time. To learn about the different methods you can use to execute this kind of upgrade, see Upgrade Workflows (Release 6.1.x to 6.2).

Upgrading a MEP

To upgrade an ecosystem component, you must upgrade the MEP to which it belongs. MEPs can be upgraded when you upgrade core or independently of a core upgrade. If your core release supports multiple MEP versions, you might be able to upgrade to a different MEP without upgrading core. See MEP Support and Lifecycle Status.

If a component is supported by your current MEP, you can add the component at any time by using manual steps or the Incremental Install function of the Installer. See Upgrading Ecosystem Packs.

Upgrading Data Fabric Clients

The Data Fabric client is a part of core. You upgrade client nodes after you upgrade the cluster nodes but before enabling new features. See Planning Upgrades to Data Fabric Clients.

Upgrading Monitoring

Monitoring components are available as part of the Ecosystem Pack (MEP) that you selected for the cluster. Once Monitoring is installed, you can upgrade Monitoring components as part of the MEP upgrade process. You can upgrade a MEP without having to upgrade core, provided the MEP you plan to upgrade to is supported by the current release. See Upgrading Ecosystem Packs.