#MCC-IP: Is there any version dependency between ONTAP version and Mediator version?

1 messages · Page 1 of 1 (latest)

inner cave
#

I'm looking for anything official (like in docs.netapp.com or kb.netapp.com), can't find anything.

Customer's MCC-IP is on 9.11.1 and we're planing update to 9.16.1. Mediator is quite old and question is if we need to update (redeploy on newer OS) the Mediator before or after all the ONTAP-updates.

inner cave
#

Only show the OS version dependency. Not the ONTAP version.

gray talon
#

Yeah. Seeing that now

inner cave
#

For example: Customer is running CentOS 7.9 with Mediator version 1.4. Is that supported with a MCC-IP running ONTAP 9.16.1?

gray talon
#

On the mediator download there is a link to IMT.

Try looking in there (it’s useless to look on a mobile device)

inner cave
#

not in IMT (at least couldn't find it there)

gray talon
#

If that’s your scenario the only choice is mediator 1.2-1.5 anyway

inner cave
#

They are on CentOS 7.9 but since that's EOL I of course recommended to update/migrate to a supported OS. Just need to know if we need to deploy a new Mediator before updating ONTAP or if we can wait until we're on 9.16.1 and then care about the Mediator.

#

Deploying a new RHEL VM needs other ressources at the customer's side. Would make it easier if we can postpone that after the MCC-IP updates.

dawn pendant
#

There is no documented version dependency between ONTAP and ONTAP Mediator for MetroCluster IP. NetApp explicitly states that any ONTAP Mediator version can monitor any ONTAP release. See: https://docs.netapp.com/us-en/ontap/mediator/

The only enforced compatibility is between Mediator and its underlying OS. Therefore, ONTAP can be upgraded independently, and Mediator redeployment on a newer OS can be safely postponed until after the ONTAP upgrade, assuming no new Mediator‑dependent features are being enabled. This is an OS lifecyle issue for the Mediator that should be addressed sooner than later (for security reasons, if nothing else).