Hi Paul,

I took a look at your case.  In looking at the two show config files 
you provided from the 4.1(2) and 4.1(3) cluster I see the following:

When you point to the 4.1(2) cluster there are two CCM's listed
port_0_cm_1_ip_addr 0x00000000
port_0_cm_1_name "LABCM02"
port_0_cm_1_port 0x000007D0
port_0_cm_2_ip_addr 0x00000000
port_0_cm_2_name "LABCM01"
port_0_cm_2_port 0x000007D0


When you point to the 4.1(3) cluster there is one CCM server listed
port_0_cm_1_ip_addr 0x00000000
port_0_cm_1_name "LABCM01"
port_0_cm_1_port 0x000007D0
port_0_cm_2_ip_addr 0x00000000
port_0_cm_2_name "LABCM01"
port_0_cm_2_port 0x000007D0
port_0_cm_noof 0x00000001

What I find interesting is that both clusters are using the same name 
"LABCM01".  When you change the TFTP server to the 4.1(3) cluster you 
are still pointing to the same DNS server.  I would suspect that this 
is leading up to your problem.  Try changing the name of your 4.1(3) 
server to IP Address under System > Server.  You will need to restart 
the server after this change.

If this change doesn't help then we will need to see a packet capture 
of the VG248 registering with the 4.1(3) cluster.

HTH,
Kevin

On Aug 30, 2005, at 2:41 PM, Paul Yago wrote:
 
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]