<div>Jason,</div>
<div>Thanks for your detailed response. Basically this means that the "peer firmware sharing" feature is not useful for new installs coming on line. Now that we have that figured out. I wish there was a doc from Cisco with the detailed information that you stated below. I have been unable to find one.<br>
<br></div>
<div class="gmail_quote">On Wed, Nov 5, 2008 at 1:24 PM, Jason Roysdon <span dir="ltr"><<a href="mailto:cisco-voip.20081105@jason.roysdon.net">cisco-voip.20081105@jason.roysdon.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Sorry that this message won't be threaded right. I just joined the list<br>so I'm pasting this from the web archive.<br>
<br>The trick is that you need the phones to not upgrade right out of the<br>box. But that's the first thing they check on when they hit the TFTP<br>server ("Do I have the latest version?"). If you were really desperate<br>
to do this, you could set up a temp CUCM server to point the new phones<br>to that matched the same firmware as the phones. That's if the phones<br>all shipped with the same firmware. They will check with that CUCM<br>
server and see they already have the latest firmware and not upgrade.<br>Have the phones already BAT'd in with their MAC addresses and the Peer<br>Firmware Sharing set to on. Now the phones will all get this setting<br>
enabled, and you can re-home them to the real CUCM TFTP server.<br><br>However, I don't think you'd want to do this unless you had a really,<br>really slow WAN. The Peer Firmware Sharing only has one "root" phone on<br>
a LAN sharing at a time, and I believe that phone can only share to 5<br>phones at a time (I cannot find any docs supporting this 5 phone limit,<br>but I recall hearing this at a Cisco Partner meeting from a badged Cisco<br>
CUCM developer). That'd run very slow for 200 phones. I suppose a<br>trick you could use would be to set up a VLAN for 200 / 6 phones (34<br>VLANs). Each VLAN would have one "root" that would download the<br>
software and then share to the other 5. You could even get a<br>complicated system going where you upgraded 5, then moved them over to 5<br>different VLANs. Keeping the ports shutdown until you had a "root"<br>
ready to move to one of the VLANs would keep the phones from coming up<br>too soon. Sounds very convoluted to me (but I love coming up with<br>elaborate hacks to solve things like this).<br><br>If you were going to set up a temp server, you might as well just have<br>
it local and have the latest firmware (even, say, on a laptop in a VM<br>setting). Then they can all upgrade right away at 100+mb/s speeds. You<br>don't even need a CUCM server to do this, just the right files on a TFTP<br>
server (or even IOS router running CME, but a router cannot support a<br>huge amount of TFTP upgrades at once either).<br><br>Given this silliness to get something like this to work, Cisco should<br>have designed the Peer option to be more intelligent and have it on by<br>
default - but with it checking to see if it has a 10+mbit connection (or<br>whatever speed seems reasonable) to the TFTP server first. If it does<br>and is able to download that fast, skip trying to download from a peer<br>
and get it from the source. If not, fall back to selecting a root and<br>having it download from the TFTP server and share - but then also have<br>other roots that can handle the load and share to more phones if the<br>first root is already "full" upgrading 5 phones.<br>
<br>Jason Roysdon.<br><br>> So if I'm deploying 200 phones at a brand new site, how to I use this<br>> feature to speed the deployment of the phones? If the feature is<br>> disabled by default, then when the phone gets auto registered the<br>
> feature goes away instantly. (since it found its config, with the option<br>> disabled)<br>><br>><br>><br>> How would I make the feature enabled by default?<br><br>_______________________________________________<br>
cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div><br>