[cisco-voip] is all traffic endpoint initiated?

Ryan Ratliff rratliff at cisco.com
Mon Oct 26 10:53:19 EDT 2009


Don't worry about network connectivity for accessing the DMA files,  
since that's going to be during the install and no services will be  
running to either accept connections or initiate them.

When changing the IP address I'd highly recommend your System->Server  
entries be hostnames and not IP addresses, since bad things happen  
when the IP address in System->Server doesn't match the one that's  
actually on the box.

You are correct that you don't have to configure DNS or NTP until  
after everything is built.   In fact unless you are going to have a  
DNS server on the dead network then you will cause problems by  
configuring a DNS server.

Since the servers get their hosts files configured during the sub  
install as long as no DNS is configured and your System->Server  
entries are hostnames then you can leave the new servers on a live  
network (just with different IPs than the production servers).   They  
won't talk to anything they can't resolve and without DNS the only  
thing they will resolve is the other nodes of the cluster.  You'll  
want to watch out for multicast MOH if you do this, but otherwise it  
should be safe.

The rest of your procedure looks fine, maybe a bit of overkill, but  
definitely the safe way to go.

-Ryan

On Oct 23, 2009, at 11:08 PM, Lelio Fulgenzi wrote:

Thanks Ryan,

Our plan was to:
install the new publisher using DMA with a new IP address on a new VLAN
reconfigure callmanager groups so they all use the publisher and only  
the publisher
delete call park numbers on all subscribers
remove all previous subscriber information from the new publisher
start installing the new subscribers
rebuild callmanager groups and call park numbers
I'm not sure how I can do that on a dead network, since the install  
process goes out and does DNS tests and NTP tests etc. Plus I need to  
access my DMA upgrade file too, right?

I guess I could skip enabling DNS, NTP, etc, until just before step 5  
once I put the publisher on a live network, and perform steps 1 thru 4  
on an isolated VLAN with SFTP access to my DMA file?

What do you think?

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Bad grammar makes me [sic]" - Tshirt


----- Original Message -----
From: "Ryan Ratliff" <rratliff at cisco.com>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
Cc: "cisco-voip voyp list" <cisco-voip at puck.nether.net>
Sent: Friday, October 23, 2009 10:14:35 PM GMT -05:00 US/Canada Eastern
Subject: Re: [cisco-voip] is all traffic endpoint initiated?

The CUCM servers themselves initiate connections to each other and I  
have seen post-DMA servers initiating connections (SDL, media  
resources) to the 4.x servers because they were reachable.  I'd highly  
advise keeping your post-DMA servers on a dead-net until you can get  
new IP addresses on them.

-Ryan

On Oct 23, 2009, at 8:53 PM, Lelio Fulgenzi wrote:

We are planning on building a new 7.1 cluster using DMA. I want to  
make sure that we don't cause any service interruptions in our  
production network. Can anyone confirm that any traffic, i.e.  
registration is end point initiated? We only have SCCP and MGCP and  
SRST devices out there. There's no reason for the new cluster to try  
to talk to any of the devices out there is there?

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Bad grammar makes me [sic]" - Tshirt

_______________________________________________
cisco-voip mailing list
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/20091026/83e8cfc0/attachment.html>


More information about the cisco-voip mailing list