A Custom Heartbeat Must Exist on Both the Remote and Local Cluster Before the Heartbeat Can Join a Partnership (6263692)

Problem Summary: If a partnership is created on a remote cluster by using a custom heartbeat, then a heartbeat by the same name must exist on the local cluster before it can join the partnership. You cannot create a heartbeat by using the GUI, so the appropriate heartbeat will not be available to choose on the Join Partnership page.

Workaround: Use the command-line interface (CLI) to create the custom heartbeat, and then use either the CLI or SunPlex Manager to join the partnership.