Marcia,
Since you were able to add a subscriber to the cluster, then I assume the publisher had a valid IP address at some point in time. That is a critical piece of information. I would recommend trying to get the publisher up using the IP address you had initially assigned, you can identify that IP address using the following command on the subscriber node.
show network cluster
This will kick out an IP address and hostname for your publisher node. At least the IP address and hostname that the subscriber "knew" when it was added to the cluster (assuming you haven't renamed and/or re-ip'd anything).
Are you able to create a static reservation in DHCP for the publisher node? If not, then do you have a cisco router on the VLAN that the publisher node is connecting to? The idea is to take the IP address identified by the subscriber node and then create a static reservation for the publisher node eth0 mac address in the DHCP server or local IOS router. You want the publisher to come online, recover its IP address via DHCP and then try to get back to a happy state.
Once you have the publisher on line then you can disable DHCP and assign the static address. If you are trying to change the publisher's IP address, then you will need to follow the procedure here:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/install/7_1_2/ipchange/ipchg712.html
If you are not trying to change the IP address then you simply need to disable DHCP and assign the IP using the command provided in my original reply.
BTW, I am assuming you have direct console access to the publisher node. Is that a correct assumption? I ask because I have had situations where I botched up the IP addressing but could still get to the admin prompt on the server directly from the console.
HTH.
Let me know if you need more help.
Regards,
Bill
Please remember to rate helpful posts.
