[cisco-voip] Adding a CUCM Subscriber
Joe Pollere (US)
Joe.Pollere at us.didata.com
Fri Aug 8 06:46:33 EDT 2008
Thanks Wes...The issue was a fat fingered security password and also a
routing issue at the remote site. After the pw recovery was run on the
Pub and the routing issue was resolved the Sub loaded fine.
Thanks
Joe
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Joe Pollere
(US)
Sent: Tuesday, August 05, 2008 10:21 AM
To: Wes Sisk
Cc: Steve Parrish; cisco-voip at puck.nether.net; Mike Hawley (AU)
Subject: Re: [cisco-voip] Adding a CUCM Subscriber
Ah ok I'll have the engineer verify that he's using the correct pw.
Thanks!
Joe
From: Wes Sisk [mailto:wsisk at cisco.com]
Sent: Tuesday, August 05, 2008 10:16 AM
To: Joe Pollere (US)
Cc: Mike Hawley (AU); Steve Parrish; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Adding a CUCM Subscriber
This usually is an indication that the security
password you are using to install the subscriber is different from that
on the publisher.
/wes
Joe Pollere (US) wrote:
Ah...I was using RTMT just didn't see them at the bottom of the list
under IPT Platform Cluster Manager...
So in it I see:
08/05/2008 06:22:02.348 clm|HMAC_SHA1 match failed
IP(10.52.100.10):|<NID::jmecoloccm01><LVL::Error><MASK::0001>
08/05/2008 06:22:12.348 clm|HMAC_SHA1 match failed
IP(10.52.100.10):|<NID::jmecoloccm01><LVL::Error><MASK::0001>
08/05/2008 06:22:22.348 clm|HMAC_SHA1 match failed
IP(10.52.100.10):|<NID::jmecoloccm01><LVL::Error><MASK::0001>
08/05/2008 06:22:32.348 clm|HMAC_SHA1 match failed
IP(10.52.100.10):|<NID::jmecoloccm01><LVL::Error><MASK::0001>
08/05/2008 06:22:42.348 clm|HMAC_SHA1 match failed
IP(10.52.100.10):|<NID::jmecoloccm01><LVL::Error><MASK::0001>
08/05/2008 06:22:52.349 clm|HMAC_SHA1 match failed
IP(10.52.100.10):|<NID::jmecoloccm01><LVL::Error><MASK::0001>
08/05/2008 06:23:02.349 clm|HMAC_SHA1 match failed
IP(10.52.100.10):|<NID::jmecoloccm01><LVL::Error><MASK::0001>
08/05/2008 06:23:12.349 clm|HMAC_SHA1 match failed
IP(10.52.100.10):|<NID::jmecoloccm01><LVL::Error><MASK::0001>
08/05/2008 06:23:22.349 clm|HMAC_SHA1 match failed
IP(10.52.100.10):|<NID::jmecoloccm01><LVL::Error><MASK::0001>
08/05/2008 06:23:32.349 clm|HMAC_SHA1 match failed
IP(10.52.100.10):|<NID::jmecoloccm01><LVL::Error><MASK::0001>
Is this indicative of the certificates getting corrupted? What would you
recommend?
Thanks,
Joe
From: Wes Sisk [mailto:wsisk at cisco.com]
Sent: Tuesday, August 05, 2008 9:12 AM
To: Joe Pollere (US)
Cc: Mike Hawley (AU); Steve Parrish; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Adding a CUCM Subscriber
Use RTMT to view/collect them.
/Wes
Joe Pollere (US) wrote:
I'm sorry but where do I find the Cluster manager logs. I've been
searching with no luck.
From: Wes Sisk [mailto:wsisk at cisco.com]
Sent: Tuesday, August 05, 2008 9:06 AM
To: Joe Pollere (US)
Cc: Mike Hawley (AU); Steve Parrish; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Adding a CUCM Subscriber
sounds like something is inspecting/corrupting the certificates
advertised by cluster manager. that communication takes place over
UDP:8500.
cluster manager logs may also show a bit more insight.
/Wes
Joe Pollere (US) wrote:
Were you able to get this resolved?
We are having the same issue. We have a 6.1.2 pub located in a Colo and
are trying to bring up a subscriber at another site. All licenses have
been loaded and the sub is in the DB as well as services turned on but
am getting the same error:
Configuration validation with jmecoloccm01 (10.10.100.10) failed.
Configured first node jmecoloccm01 is not first node.
I've checked the MTU on the PUB & it is set for the default 1500 as well
as the host names in Unified Reporting Tool. There are not any duplicate
names or IPs.
I do see this error in the application Event Log:
Aug 5 04:49:52, jmecoloccm01, Error, Cisco Cluster Manager, : 4348: Aug
05 11:49:52.235 UTC :
%CCM_CLUSTERMANAGER-CLUSTERMANAGER-3-CLM_MsgIntChkError: ClusterMgr
message integrity check error. Sender's IP address:10.52.100.10 Cluster
ID: Node ID:jmecoloccm01, 4642
Any Suggestions to troubleshoot this further?
Thanks,
joe
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Mike Hawley
(AU)
Sent: Saturday, August 02, 2008 7:04 PM
To: Wes Sisk
Cc: Steve Parrish; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Adding a CUCM Subscriber
Thanks Wes, I will give it a try and let you know.
All the best
Mike
From: Wes Sisk [mailto:wsisk at cisco.com]
Sent: Saturday, 2 August 2008 1:08 PM
To: Mike Hawley (AU)
Cc: cisco-voip at puck.nether.net; jonvoip at gmail.com; Steve Parrish
Subject: Re: [cisco-voip] Adding a CUCM Subscriber
check mtu settings on pub. if MTU on pub is < default then install will
silently fail.
other causes: subscriber name or IP has already been used.
Unified Reporting Tool from the web page will show existing hosts,
.rhosts, and sqlhosts entries allowing you to check for inconsistencies.
otherwise the certificate exchange between pub/sub is in plain text/xml
in a packet capture so you can watch the conversation and identify
problem.
clustermanager logs on the publisher may also be helpful.
/Wes
Mike Hawley (AU) wrote:
Hi Jon,
6.1.2 - yes 8 node licenses , it does join the local cluster if on the
local subnet ok, only when it is on different subnet.
We are not using DNS at this stage, relying on CUCM to create host files
for name resolution. It is possible to ping the ip address of the new
sub from the pub. But it is unable to join the cluster. No firewalls etc
between subnets.
Was thinking of setting up DNS and trying it again.
Thanks
________________________________
From: Jonathan Charles [mailto:jonvoip at gmail.com]
Sent: Sat 2/08/2008 12:58 a.m.
To: Mike Hawley (AU)
Cc: cisco-voip at puck.nether.net; Steve Parrish
Subject: Re: [cisco-voip] Adding a CUCM Subscriber
Do you have node and feature licenses loaded on the Publisher? Are the
services started (not just activated)... what version of CCM? I am
guessing 6.X...
Jonathan
On Fri, Aug 1, 2008 at 3:57 AM, Mike Hawley (AU)
<Mike.Hawley at didata.com.au> <mailto:Mike.Hawley at didata.com.au> wrote:
Hi, I have an issue when I am trying to add a Subscriber server
to a new
Publisher. They are in different subnets (10.111.128.x, and
10.111.144.x)
but within the same lab setup.
What happens is the first Subscriber server fails to add itself
to the new
database, and gives me an error of "Configuration validation
with ANBAK2-C1
(10.111.128.10) failed"
We get asked if it is the first node and we say no, but we still
get the
following message; "Configured 1st node ANBAK2-C1 is not a 1st
node "
I have done the following so far;
1. Setup SUB as a new server in database
2. Started all the CUCM services on Pub
We moved the sub server to the same subnet, which works
successfully. I
cannot leave it like this as my customer wants the servers in
different
geographic locations.
Any help appreciated...
Mike
************************************************************************
******
- NOTICE FROM DIMENSION DATA AUSTRALIA
This message is confidential, and may contain proprietary or
legally
privileged information. If you have received this email in
error, please
notify the sender and delete it immediately.
Internet communications are not secure. You should scan this
message and any
attachments for viruses. Under no circumstances do we accept
liability for
any loss or damage which may result from your receipt of this
message or any
attachments.
************************************************************************
******
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
This communication, including any attachments, is confidential. If you
are not the intended recipient, you should not read it - please contact
me immediately, destroy it, and do not copy or use any part of this
communication or disclose anything about it. Thank you. Please note that
this communication does not designate an information system for the
purposes of the Electronic Transactions Act 2002.
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
________________________________
Disclaimer: This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the designated
addressee(s) named above only. If you are not the intended addressee,
you are hereby notified that you have received this communication in
error and that any use or reproduction of this email or its contents is
strictly prohibited and may be unlawful. If you have received this
communication in error, please notify us immediately by replying to this
message and deleting it from your computer. Thank you.
________________________________
Disclaimer: This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the designated
addressee(s) named above only. If you are not the intended addressee,
you are hereby notified that you have received this communication in
error and that any use or reproduction of this email or its contents is
strictly prohibited and may be unlawful. If you have received this
communication in error, please notify us immediately by replying to this
message and deleting it from your computer. Thank you.
________________________________
Disclaimer: This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the designated
addressee(s) named above only. If you are not the intended addressee,
you are hereby notified that you have received this communication in
error and that any use or reproduction of this email or its contents is
strictly prohibited and may be unlawful. If you have received this
communication in error, please notify us immediately by replying to this
message and deleting it from your computer. Thank you.
________________________________
Disclaimer: This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the designated
addressee(s) named above only. If you are not the intended addressee,
you are hereby notified that you have received this communication in
error and that any use or reproduction of this email or its contents is
strictly prohibited and may be unlawful. If you have received this
communication in error, please notify us immediately by replying to this
message and deleting it from your computer. Thank you.
-----------------------------------------
Disclaimer:
This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only. If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful. If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080808/93f0e24b/attachment-0001.html>
More information about the cisco-voip
mailing list