Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

CCM 7 Publisher/Subscriber Issue

Hello

I'm trying to install Publisher/Subscriber Cluster, when I install the publisher server with no problem but when I installing Subscriber server in the authentication for the connection with the publisher is not connecting with the publisher, but I'm able to ping the server but the subscriber doesn't see the publisher. I have a doubt regarding the installation in the part of the hostname i could put ip address instead a name, since we don't used dns server.

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Red

Re: CCM 7 Publisher/Subscriber Issue

Hi Yancy,

If this is a new build, I would start over from scratch

It won't take long to re-build the Publisher using IP addresses rather

than Hostname/DNS config. If not there is a proper process for changing

IP address/Hostnames in this good doc;

Changing the IP Address and Host Name for Cisco Unified Communications Manager Release 7.0(1)

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/install/7_0_1/ipchange/ipchg701.html#wp185050

Cheers!

Rob

Please support CSC Helps Haiti

https://supportforums.cisco.com/docs/DOC-8895

https://supportforums.cisco.com/docs/DOC-8727

3 REPLIES
Hall of Fame Super Red

Re: CCM 7 Publisher/Subscriber Issue

Hi Yancy,

Using IP addresses vs DNS is a supported method of configuration

Domain Name System (DNS)

DNS enables the mapping of host names and network services to IP addresses within a network or networks. DNS server(s) deployed within a network provide a database that maps network services to hostnames and, in turn, hostnames to IP addresses. Devices on the network can query the DNS server and receive IP addresses for other devices in the network, thereby facilitating communication between network devices.

Complete reliance on a single network service such as DNS can introduce an element of risk when a critical Unified Communications system is deployed. If the DNS server becomes unavailable and a network device is relying on that server to provide a hostname-to-IP-address mapping, communication can and will fail. For this reason, in networks requiring high availability, Cisco recommends that you do not rely on DNS name resolution for any communications between Unified CM and the Unified Communications endpoints.

For standard deployments, Cisco recommends that you configure Unified CM(s), gateways, and endpoint devices to use IP addresses rather than hostnames. For endpoint devices, Cisco does not recommend configuration of DNS parameters such as DNS server addresses, hostnames, and domain names. During the initial installation of the publisher node in a Unified CM cluster, the publisher will be referenced in the server table by the hostname you provided for the system. Before installation and configuration of any subsequent subscribers or the definition of any endpoints, you should change this server entry to the IP address of the publisher rather than the hostname. Each subscriber added to the cluster should be defined in this same server table via IP address and not by hostname. Each subscriber should be added to this server table one device at a time, and there should be no definitions for non-existent subscribers at any time other than for the new subscriber being installed.

During installation of the publisher and subscriber, Cisco recommend that you do not select the option to enable DNS unless DNS is specifically required for system management purposes. If DNS is enabled, Cisco still highly recommend that you do not use DNS names in the configuration of the IP Communications endpoints, gateways, and Unified CM servers. Even if DNS is enabled on the servers in the cluster, it is never used for any intra-cluster server-to-server communications and is used only for communications to devices external to the cluster itself.

Cisco Unified CM 5.0 and later releases do not permit the manual configuration of HOSTS or LHOSTS files. A local version of the HOSTS table is automatically built by the publisher in each cluster and distributed to all subscriber nodes via a secure communications channel. This local table is used for managing secure intra-cluster communications and does not contain addresses or names of any endpoints other than the Unified CM servers themselves. LMHOSTS files do not exist and are not used by Cisco Unified CM 5.0 and later releases.

http://www.ciscosystems.net.mu/en/US/docs/voice_ip_comm/cucm/srnd/7x/netstruc.html#wpmkr1043811

Hope this helps!

Rob

Please support CSC Helps Haiti

https://supportforums.cisco.com/docs/DOC-8895

https://supportforums.cisco.com/docs/DOC-8727

Community Member

Re: CCM 7 Publisher/Subscriber Issue

Thanks for your answer

When i finish to install the first node, in the web administration i change the name for the ip address of the server, but when I installing the second node in the configuration for the sincronization in the hostname i need to enter a name i tried to put the ip address in the name field but is not posible. How do i especify for the second node the ip address the first one? that's my doubt.

Thanks

Hall of Fame Super Red

Re: CCM 7 Publisher/Subscriber Issue

Hi Yancy,

If this is a new build, I would start over from scratch

It won't take long to re-build the Publisher using IP addresses rather

than Hostname/DNS config. If not there is a proper process for changing

IP address/Hostnames in this good doc;

Changing the IP Address and Host Name for Cisco Unified Communications Manager Release 7.0(1)

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/install/7_0_1/ipchange/ipchg701.html#wp185050

Cheers!

Rob

Please support CSC Helps Haiti

https://supportforums.cisco.com/docs/DOC-8895

https://supportforums.cisco.com/docs/DOC-8727

932
Views
0
Helpful
3
Replies
CreatePlease to create content