CUCM won't deploy as Publisher

[NickBecirovic66634]

I'm trying to deploy independent instance of CUCM for testing which I'm currently putting on same subnet as our existing Publisher.  When configuring the node it prompts me that it is not the first node in the cluster.  Is this because it is on the same subnet as my Publisher?

I do not want these on the same cluster.

[Roger Kallberg]

No it’s not a problem to have multiple CUCM clusters on the same network.

[NickBecirovic66634]

Roger do you know why it's being recognized as not a first node? I just want to stand it up as a standalone.

[Roger Kallberg]

I’m afraid no. I assume you did answer yes to the question about if it’s the first node?

[NickBecirovic66634]

There is no option to choose yes or no.  It comes up with this soon after I configure certificate:

[stevenlandon]

earlier in the process it asked you......

if you said it was not, it is telling you there that you need to verify connectivity to the first node (publisher) that you said existed.

the installation does not do any detection