[cisco-voip] Migrating from v7 to v9 (same cluster IPs) - getting phones to recognize new v9 cluster

Sat Jan 25 13:02:29 EST 2014

Hi,

if you are comfortable with unix you can install rancid in a linux box, put
the ip addresses of the switches in a file and then do something like:
for i in  `cat switchips.file`
do
  clogin -c "show cdp nei" $i > $i.cdp
done

This will give you the mapping of switch port to phone. You could even use
these files to do massive shut/no shut on the ports.

if you have also some scripting skills you could get the list of phones and
the associated status/IPs using AXL.

Also pay attention to the phones that support ITL.

Cheers,
John

On Sat, Jan 25, 2014 at 5:16 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:

> I hear ya about pre- and post-reporting. I'm not sure we have the budget
> for those tools (I'll have to check the cost), but at least I can do a few
> basic reports. I've modified the URL in a device listing to get about 1000
> results. A few of those, cut and paste into a text file with a diff and I
> should be good. It will have IP addresses so we'll know the location/switch
> info with a bit of work.
>
> Sent from my iPhone
>
> On 2014-01-23, at 5:01 PM, Tim Smith <tim.smith at enject.com.au> wrote:
>
>  I think best approach is to have patience here, and go with the flow J
>
>
>
> If you go with pre and post reporting approach then you can quantify
> exactly what you need to fix, versus trying to fix a rough number of
> non-compliant phones.
>
> I track down the trouble makers to their switch port and then give them a
> shut no shut to reset them.
>
>
>
> As Matthew said, you may still end up on the floor doing some factory
> resets.
>
>
>
> Cheers,
>
>
>
> Tim.
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<cisco-voip-bounces at puck.nether.net>]
> *On Behalf Of *Lelio Fulgenzi
> *Sent:* Friday, 24 January 2014 8:40 AM
> *To:* Matthew Loraditch
> *Cc:* cisco-voip voyp list
> *Subject:* Re: [cisco-voip] Migrating from v7 to v9 (same cluster IPs) -
> getting phones to recognize new v9 cluster
>
>
>
> I hear ya about kickstarting the gateways and such. We're planning on do
> restarts of all those.
>
> My main concern is getting the phones back on line as soon as possible.
> I'm not a fan of just letting them go and hope they connect, especially if
> some take 30 min. I like the idea of the ACLs so it kick starts the phones
> to sort of. And it's very little work.
>
> I'm going to be doing some mock migrations in the lab, we'll see how it
> goes.
>
> Lelio
>
>  ---
> Lelio Fulgenzi, B.A.
> Senior Analyst, Network Infrastructure
> Computing and Communications Services (CCS)
> University of Guelph
>
> 519‐824‐4120 Ext 56354
> lelio at uoguelph.ca
> www.uoguelph.ca/ccs
> Room 037, Animal Science and Nutrition Building
> Guelph, Ontario, N1G 2W1
>
>
>  ------------------------------
>
> *From: *"Matthew Loraditch" <MLoraditch at heliontechnologies.com>
> *To: *"Lelio Fulgenzi" <lelio at uoguelph.ca>, "cisco-voip voyp list" <
> cisco-voip at puck.nether.net>
> *Sent: *Thursday, January 23, 2014 4:11:15 PM
> *Subject: *RE: [cisco-voip] Migrating from v7 to v9 (same cluster IPs) -
> getting phones to recognize new v9 cluster
>
> I operate in environments no larger than 1000 phones but I have never
> changed IPs. I just shut down the old servers switch ports. As long as we
> do firmware ahead of time, the change hasn’t taken longer than 30 minutes.
> Some older routers have needed a manual kick in the pants to switch over to
> the new servers but it’s usually very easy. Occasionally a phone needs a
> factory reset. We can also revert if need be.  It’s a lot less work to shut
> down some switch ports than it is to setup a bunch of ACLs, reprogram DHCP
> scopes and dial peers, mgcp, etc. Since the new servers are VMs you can
> just change the network on their adapter from your lab vlan where you’ve
> upgraded and restored from backup to your production vlan.
>
>
>
> The biggest concern would be if you have to revert, you are going back to
> before Security by Default. If you need to prepare for that it would
> probably be setup the new cluster with rollback enabled until you are sure
> everything is working. There are plenty of caveats to that, but I think
> we’ve covered them on the list.
>
>
>
> HTH!
>
>
>
>
>
> Matthew G. Loraditch – CCNP-Voice, CCNA-R&S, CCDA
>
> 1965 Greenspring Drive
> Timonium, MD 21093
>
> direct voice. 443.541.1518
> fax.  410.252.9284
>
> Twitter <http://twitter.com/heliontech>  |  Facebook<http://www.facebook.com/#!/pages/Helion/252157915296>
> | Website <http://www.heliontechnologies.com/>  |  Email Support<support at heliontechnologies.com?subject=Technical%20Support%20Request>
>
> Support Phone. 410.252.8830
>
>
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<cisco-voip-bounces at puck.nether.net>]
> *On Behalf Of *Lelio Fulgenzi
> *Sent:* Thursday, January 23, 2014 3:43 PM
> *To:* cisco-voip voyp list
> *Subject:* Re: [cisco-voip] Migrating from v7 to v9 (same cluster IPs) -
> getting phones to recognize new v9 cluster
>
>
>
> ok, i needed to wait, just a bit longer... 8 1/2 minutes before the phones
> re-request their cnf file.
>
> I'm still interested in hearing what others have done.
>  ------------------------------
>
> *From: *"Lelio Fulgenzi" <lelio at uoguelph.ca>
> *To: *"cisco-voip voyp list" <cisco-voip at puck.nether.net>
> *Sent: *Thursday, January 23, 2014 3:40:06 PM
> *Subject: *Migrating from v7 to v9 (same cluster IPs) - getting phones to
> recognize new v9 cluster
>
>
> So, still planning our v7 to v9 migration. The last time we did this, we
> went from v4 to v7 and changed the IP addresses of the servers. To ensure
> phones would go that way, we applied an ACL which blocked access to the
> servers, which forced a DHCP and they brought down the new TFTP address and
> voila, things went well.
>
> I was thinking of doing something similar during my migration to v9. In my
> testing of the ACLs though (still on v7), I noticed that the phones are not
> really bringing down a new copy of their configuration, just re-registering.
>
> I still have to test how phones behave when I complete the process, i.e.
> block ACL, unplug v7, plug in v9, allow ACL.
>
> Will the server and phone communication be sufficient to tell the phones
> to download a brand new configuration file?
>
> What have others done to migrate their phones from v7 to v9 when using the
> same cluster IPs?
>
> Lelio
>
>  ---
> Lelio Fulgenzi, B.A.
> Senior Analyst, Network Infrastructure
> Computing and Communications Services (CCS)
> University of Guelph
>
> 519‐824‐4120 Ext 56354
> lelio at uoguelph.ca
> www.uoguelph.ca/ccs
> Room 037, Animal Science and Nutrition Building
> Guelph, Ontario, N1G 2W1
>
>
>
>
>
>
>
>
> _______________________________________________
> 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/20140125/d89c6508/attachment.html>