[cisco-voip] is all traffic endpoint initiated?

Justin Steinberg jsteinberg at gmail.com
Mon Oct 26 10:16:28 EDT 2009


Lelio,

Are you planning to use new IP addresses for the entire cluster?  if so, I
would do install the new publisher via DMA, select to use a new IP address
on a new isolated VLAN that doesnt have connectivity to your production
environment.  Then once the ccmadmin page is up for the new publisher, just
go into the system>server menu and change the IP addresses from the current
4.1/production IPs to the new addresses you've allocated to the new
cluster.      Once you've changed the IPs of the subscribers, I would reboot
the system and then you should be fine to put it on the production network.

Renaming the IPs is much easier than deleting and recreated - since when you
delete you have to rebuild all the dependencies, etc.  I've also had
problems in the past with the old server names / IPs staying around in some
system configuration files that have required TAC assistance to root in and
manually edit these files.

Justin

On Fri, Oct 23, 2009 at 11:08 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:

> Thanks Ryan,
>
> Our plan was to:
>
>    1. install the new publisher using DMA with a new IP address on a new
>    VLAN
>    2. reconfigure callmanager groups so they all use the publisher and
>    only the publisher
>    3. delete call park numbers on all subscribers
>    4. remove all previous subscriber information from the new publisher
>    5. start installing the new subscribers
>    6. 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
>
>
> _______________________________________________
> 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/3b89d90c/attachment.html>


More information about the cisco-voip mailing list