GroupStudy.com GroupStudy.com - A virtual community of network engineers
 Home  BookStore  StudyNotes  Links  Archives  StudyRooms  HelpWanted  Discounts  Login
Re: placement of L3 switches in campus network (wa [7:91736] posted 08/14/2004
[Chronological Index] [Thread Index] [Top] [Date Prev][Date Next] [Thread Prev][Thread Next]


Howard.... That's a butt load of WAP's!!!!!

LOL - wait untill someones pacemaker stops from all the RF/EMF!

Howard C. Berkowitz wrote:
> 
> At 6:01 PM +0000 8/12/04, "Chuck Whose Road is Ever Shorter"
> wrote:
> >a LOT snipped to make it easier to make my relevant point
> 
> And it's a good and appropriate snip, because it brings us
> directly
> to the one part of the problem that makes L3 switching a
> nightmare.
> 
> >
> >""Howard C. Berkowitz""  wrote in message
> >news:200408121625.i7CGPUUm017160@xxxxxxxxxxxxxxxxx
> >
> >snip
> >>
> >>  Then, I realized I still had a problem: the flat WLAN. I
> could handle
> >>  this in OSPF with redistribute connected, but the heart of
> the
> >>  problem was that there was an assumption that the WLAN
> ports on each
> >>  3550 were trunked together via 802.1.  This is one thing
> very much
> >>  like the lab -- the hardware that you are forced to use,
> under
> >>  certain design assumptions, may not be an optimal
> combination.
> >>
> >>  Otherwise, things get messy. I know I could make it work by
> bridging
> >>  the WLAN interfaces and running a tree of
> bridging-over-IP-tunnels
> >>  among the 3550s to a pair of 6509s, one running as backup
> root, but
> >>  that's incredibly ugly.
> >
> >Howard, if it makes you feel any better, no one I know is
> comfortable with
> >large wireless infrastructures. Mobile IP works sorta, but I
> hear the
> >stories about lost connections, inability to rapidly reconnect
> and roam, and
> >then there's the issue of mobile IP support and
> interoperability for PDA's,
> >let alone laptops
> >
> >So most of us default to these massive single L2 single VLAN
> domains for
> >wireless and hope for the best
> >
> >Cisco has recently introduced their wireless LAN manager card
> for the 65xx
> >box. Of course at this time it can only support a max of 300
> APs and you
> >need a sup720, and you cannot cluster, but what the heck -
> it's only money,
> >and who knows, it may even solve the Mobile IP issues people
> seem to be
> >running into.
> >
> >Best of wishes. How many AP's? how many mobile stations?
> 
> Not an exact number, but probably somewhere between 900 and
> 1800 AP's.
> 
> Don't have any idea on number of mobile nodes, which is
> literally
> uncontrolled. You see, one hospital across town offered
> wireless
> Internet access to its patients and visitors, and the business 
> managers for this (larger) hospital decreed that "we have to
> have
> universal wireless to be able to compete for patients."  From a 
> medical standpoint, I think this is completely insane -- while
> there
> have been times I have dialed up in a hospital, the insurance
> and
> doctor credentials factor select hospitals. There might be a
> very
> small number
> of wealthy, self-insured patients that actually make decisions
> on
> Internet availability in hospitals, but I can't see that as 
> significant.
> 
> Any thoughts on how best to make the One Big Subnet ubiquitous
> on the
> access router/switches of a hierarchical routed network?  I
> keep
> coming back, in horror, to running two GRE tunnels, one from
> each
> 3550 to each distribution 6509. If there's some way to make the 
> uplink act as both a routable subnet while simultaneously
> letting me
> do 802.1q trunking, I haven't found it--although I don't see
> any real
> technical reason (other than sheer ugliness) why it should be 
> impossible with subinterfaces on trunk ports, if that were
> allowed.
> 
> 




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=91768&t=91736
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html