I am not very good at designing but here goes my try ..
1. Well, OC-x does not necessarily run ATM. There is a technology called POS
( Packet over SONET) and i have heard that MCI will be shifting over to POS
soon. And who said oyu would have to run LANE ?
2. I will go for OSPF too and since it is a hub and spoke topology why dont
you look into ODR ( On Demand Routing ). Whats bothering me is that how will
you terminate all the WAN connections to a single Cat 6000.
You do not need your own AS unless you plan to have a redundant ISP
connection from another carrier. In that case you will need to do some
extensive BGP policy making. If, however, you have no such plans then a
static default route will do <-- tell me guys if i am missing something
here..
3. the firewall needs to be in between the router that connects to the
outside world ( the internet ) and your internal network.
4. Not sure about that to be honest but i dont think a cat 6000 can
terminate all the T1s u r looking at but if it can then its the best choice.
Regards
Atif
-----Original Message-----
From: Jeff DeLoach <[EMAIL PROTECTED]>
To: '[EMAIL PROTECTED]' <[EMAIL PROTECTED]>
Date: Tuesday, May 30, 2000 8:55 PM
Subject: design question (long post)
>Hello all,
>
>I've recently been given the task of building my company's WAN from the
>ground up, and have been going over design after design, and finally think
>I've found a solution. I would be interested in some input from people on
>this list, though, who have more experience w/ this sort of thing than I
>do--I've been doing WAN stuff for nearly 2 years now, but nothing on this
>scale...Here's the scenario:
>
>We have nearly 200 sites that need to connect back to the central office, a
>number that is constantly growing. These sites are scattered all over the
>US--10 different states right now, with more to come as the year rolls on.
>I need to provide all the sites with internet access, as well as allow the
>staff here in the main office to communicate, both via email (and,
>eventually, w/ video via Netmeeting or ICQ), and with Reachout to remotely
>troubleshoot sites. Each site has a database that is between 10-50 Mb that
>needs to be backed up at the home office once a week ; additionally, each
>site also runs our proprietary software that we seem to constantly upgrade,
>so we need to be able to send updates across the wire as well. Down the
>road, the development team is looking at moving to an ASP-based model,
which
>would remove the need for each site to have an individual database or
>software upgrade, but would really increase the amount of traffic on the
WAN
>links. Additionally, the designers are also looking at employing streaming
>video to the desktop for the remote sites as well, so the bandwidth
>requirements are rather large, and multicast needs to be taken into
>consideration as well.
>
>Here's the scenario I proposed:
>
>We would get an OC-3 pipe from MCI-WorldCom here at our main site, which
>would then in turn connect to a Cisco 6000-series switch w/ a router module
>in it. The main OC pipe would then be broken into T1 links and sent out to
>each site via MCI's frame cloud. Each site will have a Cisco 2610 router
>that will connect to a lower-end switch, probably a Catalyst 1900, to allow
>all users at each site (usually between 30-60 people) to connect to the
>internet and be in touch w/ the home office. I want to set up queuing on
>the router to allow video traffic to have the highest priority. In effect,
>I'm setting up the main office as sort of an ISP--this is the way it has to
>be, for political and financial reasons. All the satellite sites must
>connect back to us, and then go out to the internet. All sites run only
>TCP/IP.
>
>Now, here are my questions.
>
>1. From what MCI tells me, OC-x links are ATM. I want to use frame relay
>to connect the remote sites, rather than have the 2610's at each site have
>to perform LANE--I don't even know if they do LANE or not. The 6000-series
>switch is a pretty powerful piece of equipment, but am I asking too much of
>it to handle all the work here? I've scoured Cisco's website, and I can't
>find out if the 6000 will do LANE either. How would I go about translating
>ATM cells to Frame Relay frames?
>
>2. What sort of routing protocol should I use? I was thinking of OSPF,
>simply because I don't want to clog up the links w/ routing table
>advertisements. The remote sites won't be talking to each other all that
>much--I'm envisioning more of a "hub-and-spoke" kind of arrangement. Also,
>will I need to use BGP at the main site, and make one big AS out of my home
>site and all my remote sites?
>
>3. Where would you put a firewall in this design?
>
>4. Is the 6000 switch/router idea the best way to go here, or should I
have
>a pure router, like a 7000-series?
>
>OK, that's all. Thanks for reading this far. All comments welcome, feel
>free to pick this design apart if you wish. Like I said, I've been doing
>this for nearly 2 years, but nothing on this sort of scale, and I'm feeling
>a bit overwhelmed, and I really don't want to screw this up, so all
>suggestions are welcome.
>
>Thanks in advance,
>
>Jeff DeLoach
>
>___________________________________
>UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
>FAQ, list archives, and subscription info: http://www.groupstudy.com
>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
