[cisco-voip] 7925s across campus

Wed Oct 13 16:13:12 EDT 2010

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.

http://www.cisco.com/en/US/docs/wireless/technology/controller/deployment/gu
ide/dep.html#wp1053827

Thanks,

Go0se

My blog:

 <http://atc.go0se.com> http://atc.go0se.com

--------------------------------------------

Help Hopegivers International

Feed the orphans of Haiti and India

 <http://www.hopegivers.org> http://www.hopegivers.org

--------------------------------------------

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Scott Voll
Sent: Wednesday, October 13, 2010 2:30 PM
To: Lelio Fulgenzi
Cc: cisco-voip (cisco-voip at puck.nether.net)
Subject: Re: [cisco-voip] 7925s across campus

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?

Yes it burns 4 or 5 WLANs but then the subnet size would be smaller.

But as Mike also pointed out.... there are features to take care of it as a
large WLAN.

Scott

On Wed, Oct 13, 2010 at 11:12 AM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:

We do something similar on our wireless network, granted, without voice so
far.

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. 

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it. 
                              - LFJ (with apologies to Mr. Popeil)

  _____  

From: "Mike King" <me at mpking.com>
To: "cisco-voip (cisco-voip at puck.nether.net)" <cisco-voip at puck.nether.net>
Sent: Wednesday, October 13, 2010 2:06:47 PM
Subject: Re: [cisco-voip] 7925s across campus

Hey Jason.

The VLAN would be terminated on the Wireless LAN controller, so
technically the VLAN would not be across multiple buildings. (The AP's
take care of getting the traffic back to the WLAN controller)

The WLAN controller also does broadcast filtering, which would
alleviate the issue with having all those clients in a /16.

I can take a stab at the reasons they want them in the same Subnet.
A. They don't want to make more than 1 subnet for ease of ACL
B. They most likely want to use the PTT (Push to talk) button as a
walkie talkie/Nextel type service. The PTT requires multicast. They
might be mistakenly thinking that by being in the same subnet, they
won't have to enable multicast on the wireless LAN.

To throw some general advise, remember to disable ALL client load
balancing features on the WLAN controllers, as they will degrade
performance horribly. Also remember to turn Peer to Peer Blocking off,
as it will prevent phone calls to each other.

I'm in contact with several large colleges, and they routinely run /16
on they're wireless LAN. They haven't run into any specific issues
with Subnets being that large.  Personally, I think it might be a
little more sane to break it up into something smaller.

Mike

On Wed, Oct 13, 2010 at 1:04 PM, Jason Aarons (US)
<jason.aarons at us.didata.com> wrote:
> Customer is looking at about 800 7925s across a campus, they mentioned
> having a single 7925 voice vlan (10.x.x.x/16) across all Wireless LAN
> Controllers (4400s) for the whole campus for these 7925s.  This doesn't
> sound good having all 7925s on same subnet across multiple buildings.
>
>
>
> What are others doing as the Enterprise Mobility Guide 4.1 doesn't give
much
> thought.
>
> ________________________________
>
> 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.
>
> _______________________________________________
> 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

_______________________________________________
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/20101013/c8b25775/attachment.html>