Hi,
I decommissioned a CDOT cluster and only then discovered it was in a SM relationship (in broken-off state), as a source. If I now try to delete the relationship, it fails with:
Warning: Unable to list entries in cluster "decommed-cluster". Failed to contact peer cluster "decommed-cluster" at addresses: 1.1.1.1, 2.2.2.. RPC: Remote system error [from mgwd on node "mynode" (VSID: -1) to mgwd at 3.3.3.3, 4.4.4.4] Error: command failed: Volume "my_volume" not found. (Failed to contact peer cluster "decommed-cluster" at addresses: 1.1.1.1, 2.2.2.2. RPC: Remote system error [from mgwd on node "my-node" (VSID: -1) to mgwd at 3.3.3.3, 4.4.4.4])
Any ideas maybe of how to unscrew it? "-force" flag does not help.
Cheers, Vladimir
I've never been in this situation, but is there a snapshot on the source that might make the operating system think there's a snapmirror?
On Mon, Mar 26, 2018 at 6:38 AM Momonth momonth@gmail.com wrote:
Hi,
I decommissioned a CDOT cluster and only then discovered it was in a SM relationship (in broken-off state), as a source. If I now try to delete the relationship, it fails with:
Warning: Unable to list entries in cluster "decommed-cluster". Failed to contact peer cluster "decommed-cluster" at addresses: 1.1.1.1, 2.2.2.. RPC: Remote system error [from mgwd on node "mynode" (VSID: -1) to mgwd at 3.3.3.3, 4.4.4.4] Error: command failed: Volume "my_volume" not found. (Failed to contact peer cluster "decommed-cluster" at addresses: 1.1.1.1, 2.2.2.2. RPC: Remote system error [from mgwd on node "my-node" (VSID: -1) to mgwd at 3.3.3.3, 4.4.4.4])
Any ideas maybe of how to unscrew it? "-force" flag does not help.
Cheers, Vladimir _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
The source doesn't exist at this point. I'm trying to clean the destination, and it complains it can't contact the source.
On Mon, Mar 26, 2018 at 12:41 PM, Basil basilberntsen@gmail.com wrote:
I've never been in this situation, but is there a snapshot on the source that might make the operating system think there's a snapmirror?
System Manager did the job, though it generated the same error message, but eventually it deleted the relationship.
On Mon, Mar 26, 2018 at 12:48 PM, Momonth momonth@gmail.com wrote:
The source doesn't exist at this point. I'm trying to clean the destination, and it complains it can't contact the source.
On Mon, Mar 26, 2018 at 12:41 PM, Basil basilberntsen@gmail.com wrote:
I've never been in this situation, but is there a snapshot on the source that might make the operating system think there's a snapmirror?
-
Basil -
Momonth