[cisco-voip] is all traffic endpoint initiated?

Mon Nov 9 12:53:51 EST 2009

Not in 7.1(3), it’s now mandatory.

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Monday, November 09, 2009 12:21 PM
To: Ryan Ratliff
Cc: cisco-voip voyp list
Subject: Re: [cisco-voip] is all traffic endpoint initiated?

doh. can i install (with DMA) a publisher without having an NTP server available on the network?

---
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: "Lelio Fulgenzi" <lelio at uoguelph.ca>
To: "Ryan Ratliff" <rratliff at cisco.com>
Cc: "cisco-voip voyp list" <cisco-voip at puck.nether.net>
Sent: Monday, November 9, 2009 11:46:31 AM GMT -05:00 US/Canada Eastern
Subject: Re: [cisco-voip] is all traffic endpoint initiated?

Thanks for your comments Ryan and Justin. They'll definitely help me build my new cluster. Some comments/questions:

*	Ryan: I'm a little concerned with using hostnames and not IP address in the System -> Server settings. Do you mean IP addresses don't match what's on the box on the other side? In the event of a DNS failure I don't want my phone system to go down. I understand that there will be more and more dependancies, but I'd like to minimize them.
*	Ryan: I'm a little confused as to you what you mean by your last paragraph. How can I use hostnames if I haven't configured DNS? Won't it come back with errors?
*	Justin: I would think it would be cleaner to delete and recreate rather than simply edit. 

To all:

*	how many are using hostnames rather than IP addresses in the System -> Server settings?
*	has anyone had to rename/delete a subscriber using Justin's suggested method?

Thanks again....

----- 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: Monday, October 26, 2009 10:53:19 AM GMT -05:00 US/Canada Eastern
Subject: Re: [cisco-voip] is all traffic endpoint initiated?

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

----- Forwarded Message -----
From: "Justin Steinberg" <jsteinberg at gmail.com>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
Cc: "Ryan Ratliff" <rratliff at cisco.com>, "cisco-voip voyp list" <cisco-voip at puck.nether.net>
Sent: Monday, October 26, 2009 10:16:28 AM GMT -05:00 US/Canada Eastern
Subject: Re: [cisco-voip] is all traffic endpoint initiated?

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 Oct 23, 2009, at 11:08 PM, Lelio Fulgenzi 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 

-----------------------------------------
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/20091109/eb95621c/attachment.html>