Security

Hi,

So built a test 2 node cppm cluster  running 6.12.3  ( 2000V appliances) all working fine.

Then wanted to import  config from our.  production 6.11.9 cluster.

Again that worked ... except .... 

Now the  master publisher is there but thinks its a standalone publisher.

The original  subscriber  stil thinks its a subscriber to the master bublisher

Can log onto both of them using appamin

Can log onto  master publisher via gui

Cannot log into  subscriber using. gui

from CLI on  subscriber that was cannot. drop subscriber or reset database  from CLI

How do I rejoin the old secondary to the master publisher.

Annoyingly,  if I go into global cluster settings on the master publisher and  change the header that appears on the login page and then try logging into the (old)secondary, the change in header  appears, so theres some form of. sync there.

No haven't tried the  switch it off and on again yet

A

The easiest option?  Delete the VMs, start over.

Bring up one appliance, restore the backup from the publisher.

Bring up the second appliance, join the new cluster.

Hi,

So built a test 2 node cppm cluster  running 6.12.3  ( 2000V appliances) all working fine.

Then wanted to import  config from our.  production 6.11.9 cluster.

Again that worked ... except .... 

Now the  master publisher is there but thinks its a standalone publisher.

The original  subscriber  stil thinks its a subscriber to the master bublisher

Can log onto both of them using appamin

Can log onto  master publisher via gui

Cannot log into  subscriber using. gui

from CLI on  subscriber that was cannot. drop subscriber or reset database  from CLI

How do I rejoin the old secondary to the master publisher.

Annoyingly,  if I go into global cluster settings on the master publisher and  change the header that appears on the login page and then try logging into the (old)secondary, the change in header  appears, so theres some form of. sync there.

No haven't tried the  switch it off and on again yet

A

The easiest option?  Delete the VMs, start over.

Bring up one appliance, restore the backup from the publisher.

Bring up the second appliance, join the new cluster.

Hi,

So built a test 2 node cppm cluster  running 6.12.3  ( 2000V appliances) all working fine.

Then wanted to import  config from our.  production 6.11.9 cluster.

Again that worked ... except .... 

Now the  master publisher is there but thinks its a standalone publisher.

The original  subscriber  stil thinks its a subscriber to the master bublisher

Can log onto both of them using appamin

Can log onto  master publisher via gui

Cannot log into  subscriber using. gui

from CLI on  subscriber that was cannot. drop subscriber or reset database  from CLI

How do I rejoin the old secondary to the master publisher.

Annoyingly,  if I go into global cluster settings on the master publisher and  change the header that appears on the login page and then try logging into the (old)secondary, the change in header  appears, so theres some form of. sync there.

No haven't tried the  switch it off and on again yet

A

The command cluster reset-database should do the job, but sounds like you've managed to get in a state where such isn't possible.  You might reset the publisher and then try again on the other appliance.

The easiest option?  Delete the VMs, start over.

Bring up one appliance, restore the backup from the publisher.

Bring up the second appliance, join the new cluster.

Hi,

So built a test 2 node cppm cluster  running 6.12.3  ( 2000V appliances) all working fine.

Then wanted to import  config from our.  production 6.11.9 cluster.

Again that worked ... except .... 

Now the  master publisher is there but thinks its a standalone publisher.

The original  subscriber  stil thinks its a subscriber to the master bublisher

Can log onto both of them using appamin

Can log onto  master publisher via gui

Cannot log into  subscriber using. gui

from CLI on  subscriber that was cannot. drop subscriber or reset database  from CLI

How do I rejoin the old secondary to the master publisher.

Annoyingly,  if I go into global cluster settings on the master publisher and  change the header that appears on the login page and then try logging into the (old)secondary, the change in header  appears, so theres some form of. sync there.

No haven't tried the  switch it off and on again yet

A

The command cluster reset-database should do the job, but sounds like you've managed to get in a state where such isn't possible.  You might reset the publisher and then try again on the other appliance.

The easiest option?  Delete the VMs, start over.

Bring up one appliance, restore the backup from the publisher.

Bring up the second appliance, join the new cluster.

Hi,

So built a test 2 node cppm cluster  running 6.12.3  ( 2000V appliances) all working fine.

Then wanted to import  config from our.  production 6.11.9 cluster.

Again that worked ... except .... 

Now the  master publisher is there but thinks its a standalone publisher.

The original  subscriber  stil thinks its a subscriber to the master bublisher

Can log onto both of them using appamin

Can log onto  master publisher via gui

Cannot log into  subscriber using. gui

from CLI on  subscriber that was cannot. drop subscriber or reset database  from CLI

How do I rejoin the old secondary to the master publisher.

Annoyingly,  if I go into global cluster settings on the master publisher and  change the header that appears on the login page and then try logging into the (old)secondary, the change in header  appears, so theres some form of. sync there.

No haven't tried the  switch it off and on again yet

A