<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Setting up that many wireless phones to function flawlessly will be a challenge no matter how you do it. Keep in mind with that many wireless phones that Cisco recommends no more than 7 active calls on a single AP. I believe I’d find some way to bust it up. If you build it wrong and there are problems, your first impression with endusers will be a bad one and battling that perception could keep you from ever getting it right – even if you eventually get it right. Once you’ve set it up I suggest that you test extensively before deploying to live mortal users.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="http://www.cisco.com/en/US/docs/wireless/technology/controller/deployment/guide/dep.html#wp1053827">http://www.cisco.com/en/US/docs/wireless/technology/controller/deployment/guide/dep.html#wp1053827</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Go0se<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>My blog:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="http://atc.go0se.com"><span style='color:blue'>http://atc.go0se.com</span></a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>--------------------------------------------<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Help Hopegivers International<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Feed the orphans of Haiti and India<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="http://www.hopegivers.org"><span style='color:blue'>http://www.hopegivers.org</span></a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>--------------------------------------------<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Scott Voll<br><b>Sent:</b> Wednesday, October 13, 2010 2:30 PM<br><b>To:</b> Lelio Fulgenzi<br><b>Cc:</b> cisco-voip (cisco-voip@puck.nether.net)<br><b>Subject:</b> Re: [cisco-voip] 7925s across campus<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>But what would keep you from having 4 or 5 different SSID and set 1/4 or 1/5 of them to a different SSID / Subnet?<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Yes it burns 4 or 5 WLANs but then the subnet size would be smaller.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>But as Mike also pointed out.... there are features to take care of it as a large WLAN.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Scott<o:p></o:p></p><div><p class=MsoNormal>On Wed, Oct 13, 2010 at 11:12 AM, Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>> wrote:<o:p></o:p></p><div><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'>We do something similar on our wireless network, granted, without voice so far.<br><br>One of the biggest advantages of having all hosts on the same subnet is roaming. Roaming across subnets begins to introduce some difficulty and complexity. <br><br><br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><br><o:p></o:p></span></p><div class=MsoNormal align=center style='text-align:center'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'><hr size=2 width="100%" align=center></span></div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'>From: </span></b><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'>"Mike King" <<a href="mailto:me@mpking.com" target="_blank">me@mpking.com</a>><br><b>To: </b>"cisco-voip (<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>)" <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br><b>Sent: </b>Wednesday, October 13, 2010 2:06:47 PM<br><b>Subject: </b>Re: [cisco-voip] 7925s across campus<o:p></o:p></span></p><div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'><br><br>Hey Jason.<br><br>The VLAN would be terminated on the Wireless LAN controller, so<br>technically the VLAN would not be across multiple buildings. (The AP's<br>take care of getting the traffic back to the WLAN controller)<br><br>The WLAN controller also does broadcast filtering, which would<br>alleviate the issue with having all those clients in a /16.<br><br>I can take a stab at the reasons they want them in the same Subnet.<br>A. They don't want to make more than 1 subnet for ease of ACL<br>B. They most likely want to use the PTT (Push to talk) button as a<br>walkie talkie/Nextel type service. The PTT requires multicast. They<br>might be mistakenly thinking that by being in the same subnet, they<br>won't have to enable multicast on the wireless LAN.<br><br><br>To throw some general advise, remember to disable ALL client load<br>balancing features on the WLAN controllers, as they will degrade<br>performance horribly. Also remember to turn Peer to Peer Blocking off,<br>as it will prevent phone calls to each other.<br><br>I'm in contact with several large colleges, and they routinely run /16<br>on they're wireless LAN. They haven't run into any specific issues<br>with Subnets being that large. Personally, I think it might be a<br>little more sane to break it up into something smaller.<br><br>Mike<br><br><br>On Wed, Oct 13, 2010 at 1:04 PM, Jason Aarons (US)<br><<a href="mailto:jason.aarons@us.didata.com" target="_blank">jason.aarons@us.didata.com</a>> wrote:<br>> Customer is looking at about 800 7925s across a campus, they mentioned<br>> having a single 7925 voice vlan (10.x.x.x/16) across all Wireless LAN<br>> Controllers (4400s) for the whole campus for these 7925s. This doesn’t<br>> sound good having all 7925s on same subnet across multiple buildings.<br>><br>><br>><br>> What are others doing as the Enterprise Mobility Guide 4.1 doesn’t give much<br>> thought.<br>><br>> ________________________________<br>><br>> Disclaimer: This e-mail communication and any attachments may contain<br>> confidential and privileged information and is for use by the designated<br>> addressee(s) named above only. If you are not the intended addressee, you<br>> are hereby notified that you have received this communication in error and<br>> that any use or reproduction of this email or its contents is strictly<br>> prohibited and may be unlawful. If you have received this communication in<br>> error, please notify us immediately by replying to this message and deleting<br>> it from your computer. Thank you.<br>><br>> _______________________________________________<br>> cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">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>><br>><br><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">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><o:p></o:p></span></p></div></div></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><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><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>