they also followed this up with the below
For your info,
UKIPCLU02::> cluster peer show -instance
Peer Cluster Name: UKDRCLU02
Remote Intercluster Addresses: 10.87.20.14, 10.87.20.15
Availability of the Remote Cluster: Partial
Remote Cluster Name: UKDRCLU02
Active IP Addresses: 10.87.20.15
Cluster Serial Number: 1-80-000011
Remote Cluster Nodes: UKDRCLU02-01, UKDRCLU02-02
Remote Cluster Health: true
Unreachable Local Nodes: -
Address Family of Relationship: ipv4
Authentication Status Administrative: use-authentication
Authentication Status Operational: ok
Last Update Time: 7/24/2019 15:08:51
IPspace for the Relationship: Default
Peer Cluster Name: UKIPCLU01
Remote Intercluster Addresses: 10.0.1.150, 10.0.1.151
Availability of the Remote Cluster: Unavailable
Remote Cluster Name: UKIPCLU01
Active IP Addresses: 10.0.1.151, 10.0.1.150
Cluster Serial Number: 1-80-012657
Remote Cluster Nodes: UKIPCLU01-01, UKIPCLU01-02
Remote Cluster Health: -
Unreachable Local Nodes: -
Address Family of Relationship: ipv4
Authentication Status Administrative: use-authentication
Authentication Status Operational: ok
Last Update Time: 7/24/2019 15:08:19
IPspace for the Relationship: Default
2 entries were displayed.
UKIPCLU02::> ping -node UKIPCLU02-01 10.87.20.14
UKIPCLU02::> ping -node UKIPCLU02-01 10.87.20.15
10.87.20.15 is alive