[Ietf-62] Re: Network Requirements and Equipment
Jim Martin <jim@daedelus.com> Tue, 08 February 2005 10:13 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22141; Tue, 8 Feb 2005 05:13:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CySgW-00007p-Hz; Tue, 08 Feb 2005 05:33:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CySLU-0005ie-56; Tue, 08 Feb 2005 05:11:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CySJ9-0001ab-5Q for ietf-62@megatron.ietf.org; Tue, 08 Feb 2005 05:09:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21848 for <ietf-62@ietf.org>; Tue, 8 Feb 2005 05:09:21 -0500 (EST)
Received: from uillean.fuaim.com ([206.197.161.140]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CySci-0008Tc-Ce for ietf-62@ietf.org; Tue, 08 Feb 2005 05:29:37 -0500
Received: from localhost (localhost.fuaim.com [127.0.0.1]) by uillean.fuaim.com (Postfix) with ESMTP id C93A0B859 for <ietf-62@ietf.org>; Tue, 8 Feb 2005 02:09:18 -0800 (PST)
Received: from uillean.fuaim.com ([127.0.0.1]) by localhost (uillean.fuaim.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 73557-01-25 for <ietf-62@ietf.org>; Tue, 8 Feb 2005 02:09:14 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [IPv6:3ffe:1200:3033:1::158]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id B302BB81E for <ietf-62@ietf.org>; Tue, 8 Feb 2005 02:09:14 -0800 (PST)
Received: from [192.108.76.68] (DHCP-76-68.Netzwert.AG [192.108.76.68]) (authenticated bits=0) by clairseach.fuaim.com (8.12.8/8.12.8) with ESMTP id j18AK54J026035 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for <ietf-62@ietf.org>; Tue, 8 Feb 2005 02:20:08 -0800
Mime-Version: 1.0 (Apple Message framework v619.2)
In-Reply-To: <2B15512F43C63E40284CDB6C@uncas.brevis.net>
References: <38c55b7f33ba98347bff8cc18fb37531@daedelus.com> <2B15512F43C63E40284CDB6C@uncas.brevis.net>
Message-Id: <2e4fb9e888678244ecf2876962fad7e2@daedelus.com>
From: Jim Martin <jim@daedelus.com>
Date: Tue, 08 Feb 2005 11:09:02 +0100
To: IETF 62 Network List <ietf-62@ietf.org>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21be852dc93f0971708678c18d38c096
Subject: [Ietf-62] Re: Network Requirements and Equipment
X-BeenThere: ietf-62@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-62 Mailing List <ietf-62.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-62>, <mailto:ietf-62-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ietf-62>
List-Post: <mailto:ietf-62@lists.ietf.org>
List-Help: <mailto:ietf-62-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-62>, <mailto:ietf-62-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0772357635=="
Sender: ietf-62-bounces@ietf.org
Errors-To: ietf-62-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 86f85b2f88b0d50615aed44a7f9e33c7
Dennis, Again, thanks for the advance work.... Comments inline below... On Feb 6, 2005, at 12:49 AM, Dennis Fazio wrote: > --On February 5, 2005 05:12:42 PM +0100 Jim Martin <jim@daedelus.com> > wrote: > > [...] >> streaming from each of the breakout rooms, we'll need an additional >> ethernet In addition to what we need for the APs. > > There should be two ethernet drops in each of the rooms, one for WiFi, > one for wired unicast audio. We will be heading to the Hilton > Wednesday (9th) to verify wiring and jack locations in each room. Great. Could you also verify a few other things while you're there? - What do we have running down from the roof to the 3th floor cloak closet? I seem to remember two pair of Cat5, but I'm not positive. If it's fiber, what is it terminated with? - What do we have running up from the demarc room in the car park? I honestly don't remember if this is fiber or copper. Also, does it terminate on the 3rd floor closet? And, as always, if fiber, what does it terminate in? - I'm assuming the gig from Onvoy will be delivered in that demarc room in the car park. Do we know what type of connector they're delivering on? Last time we had to scramble for the cable. What gig standard are they going to be using? ZX-IR or LR? >> >> We have the bar and lobby area on the ground floor, 5 rooms (6 if you >> count the NOC) on the 2nd floor, and the usual Grand Ballroom split >> into up >> to 7 Salons with airwalls (ugh!), plus the perimeter rooms (Directors >> Row >> 1-4, and Board Room 1-3, as well as Duluth and Rochester) on the 3rd >> floor. > > It wasn't clear from Marcia's chart that we needed access in > Director's Row 1-4 and the Board rooms. I don't think we included them > in our Access Point estimate. Will there be events in those rooms that > require coverage? I'll let Marcia answer that conclusively, but often these are offices and such that people would appreciate the wireless, but don't demand it. > >> We also have the Ramsey room, which I can't seem to find on the >> floorplans, >> but I'd expect it to be on the 3rd floor (anyone know for sure?). > > Ramsey is the room marked "Retail" adjacent to the Carver room on the > second floor. Ah, thank you! > >> several Onvoy upstreams as well as UMN. ChrisL has arranged a pair of >> Junipers from Lenny, and Dave has a "pile of Cat 3750's" (20-30) from >> UMN >> that we can use. > > Dave was of the opinion that we could use the 3750s as access routers > and the Junipers would not be needed, so we should settle on what our > preferences are for that. Right, this is exactly the discussion I wanted to get to. I'm hesitant to use the 3750s as our sole source of routing for several reasons. The biggest one is probably their limited ability to handle encaps/decaps duty. This means that if we need to bring up a tunnel to anywhere, for any purpose, we're SOL. It also means that they'll be more limited as to being able to act as a PIM RP, since this also involves a bunch of encaps/decaps (think register packets). While we're not doing /tons/ of multicast, we might as well build something solid :-) Also, the v6 code for the 3750 was just released something like 10 days ago ... it seems to work, but I not sure I want to bet the IETF on it :-) Finally, we really like to keep full BGP tables, so we can do optimal egress routing (which makes even more sense with lots of upstream peers, like we have this time). I've not tried this on a 3750, but I'd be worried about memory and CPU utilization. So, that all said, I personally feel much better using the Junipers. How's this for a proposed design. We place one M10 in the roof room, one in the car park. The roof one gets the wireless external (if that works out) and the car park gets the external Gig. We then place a pair of stacked 3750s in the 3rd floor cloak room (which I'll call the core switches). We run two pair from each of the M10s to the stack, terminating one in each physical switch, using 802.3ad link aggregation. That way, we can't go down due to any one single failure. If we want to be paranoid, we can dual attach any fanout switches back to both core switches, and do 802.3ad (or cisco EtherChannel) to ensure that even the edge stays up in a single failure. From a routing perspective, we could ether drag all the vlans out to the Junipers, and do the usual VRRP trick, or we could use the Junipers solely as external routers and have the 3750's do all our internal routing. I'd kinda like to do the latter, but I'm open to other thoughts on the matter! What do you guys think? - Jim
_______________________________________________ Ietf-62 mailing list Ietf-62@lists.ietf.org https://www1.ietf.org/mailman/listinfo/ietf-62
- [Ietf-62] Re: Network Requirements and Equipment Dennis Fazio
- [Ietf-62] Network Requirements and Equipment Jim Martin
- [Ietf-62] Re: Network Requirements and Equipment Jim Martin
- Re: [Ietf-62] Re: Network Requirements and Equipm… Dennis Fazio
- Re: [Ietf-62] Re: Network Requirements and Equipm… Dennis Fazio
- Re: [Ietf-62] Re: Network Requirements and Equipm… Dennis Fazio
- Re: [Ietf-62] Network Requirements and Equipment David Farmer