[cisco-voip] Installing CUPS 9 Subscriber - fails on connectivity

[Tim Smith]

I’ve seen this with duplicate IP before. You’re talking to something, but maybe you’re trying to join a CUPS server to a domain controller.
Might not be an issue in your own lab, but thought it’s worth a mention.

I like to double check the basics, ping and check ARP or even disconnect the VM’s NIC and ping and make sure your ping stops.

Packet cap sounds like a good idea after that.

Cheers,

Tim


From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Brian Meade
Sent: Thursday, 26 June 2014 5:07 AM
To: Jeffrey Girard
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Installing CUPS 9 Subscriber - fails on connectivity

You can run a packet capture on the publisher while it does the connectivity test:
utils network capture eth0 size all count 100000 file cupsconntest

Then grab the file via:
file get activelog platform/cli/cupsconntest.cap

But you may need to run a capture on the sub side as well in case some traffic isn't making it to the pub.

On Wed, Jun 25, 2014 at 1:54 PM, Jeffrey Girard <jeffrey.girard at girardinc.com<mailto:jeffrey.girard at girardinc.com>> wrote:
Fails at the same location with the same error when using DNS as well…

Jeff

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Jeffrey Girard
Sent: Wednesday, June 25, 2014 12:45 PM
To: MManly at TEP.com<mailto:MManly at TEP.com>; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Installing CUPS 9 Subscriber - fails on connectivity

I was only using IP addressing.

However, I just stood up a MS DNS server and am re-running the install using that and I configured the CUPS Sub install to be a DNS client to see if that makes any difference….

------------------------------------------------------------------------------------
Dr. Jeffrey T. Girard (Jeff), PhD
Colonel, United States Army (Retired)
Senior Network Engineer / VoIP Engineer - WireMeHappy.com
reply to: jeffrey.girard at wiremehappy.com<mailto:jeffrey.girard at wiremehappy.com>
(607)835-0406<tel:%28607%29835-0406> (home office)
(845)764-1661<tel:%28845%29764-1661> (mobile)
(607)835-0458<tel:%28607%29835-0458> (fax)

From: MManly at TEP.com<mailto:MManly at TEP.com> [mailto:MManly at TEP.com]
Sent: Wednesday, June 25, 2014 12:42 PM
To: Jeffrey Girard; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: RE: Installing CUPS 9 Subscriber - fails on connectivity

Did you enable DNS on either of the servers upon install or are you strictly using IP addressing?

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jeffrey Girard
Sent: Wednesday, June 25, 2014 9:34 AM
To: cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>)
Subject: [cisco-voip] Installing CUPS 9 Subscriber - fails on connectivity

Trying to install a CUPS subscriber in a lab environment.  Version 9

CUPS publisher installed fine.

I started all the services on the Publisher and ran through the initial install wizard

I added the subscriber to the Publisher under System -> Cluster Topology -> DefaultCUPSubcluster

When I install the CUPS sub, it fails when checking connectivity to the Pub.

The error window says “Connectivity check to CUPSPub (172.16.57.59) failed
Is the network connection for CUPSSub up?
Is the network connection for CUPSPub up?
Is CUPSPub powered on?

These VMs are on different subnets.  From a third subnet, I was able to ping both CUPS VMs.  From the CUPSPub CLI, I was able to use utils network ping 172.16.41.251 (IP Address of the CUPSSub) and it was successful.

Any ideas?

Jeff

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140625/6114a6c3/attachment.html>