Networking geeks wanted !!

ok to sum it up....im having a problem coming up with a diagram and a list of specific hardware to complete a fake network...Los angeles is HQ and houses 400 workers. Frankfurt, Tokyo, and Rio consists of 15-25 per building. New york center houses 40 workers. Singapore, Chicago, Miami, Rome, and London has 5-10 workers each. The average file size is 25mb. THe company has intranet servers in los angeles, new york, london and tokyo. Each building needs internet access, telephone and confrencing. I need to chose protocols for the lans & wans......Ive come up with a t3 line in los angeles, t1 line in new york, t1 line in london, and t1 line in tokyo. 64k leased lines in singapore, rio, miami, rome, frankfurt, and chicago. Im confused as to which protocols i should choose for the wans. Why cant i use vpn?

Chicago New York
Frankfurt
Los Angeles London
Miami Rome

Tokyo

Singapore Rio de Janeiro



thatsthe diagram given......can anyone help me?

crap...the diagram didnt work.........pretty much its...
chicago and new york at the top side by side.....to the west of chicago is losa angeles, than tokyo than singapore.......to the south of new york is miami.....to the east is london, frankfurt to the north east......rome to the southeast....and rio de janiero is south of miami...

hopefully this works

Originally posted by hitznrunz
ok to sum it up....im having a problem coming up with a diagram and a list of specific hardware to complete a fake network...Los angeles is HQ and houses 400 workers. Frankfurt, Tokyo, and Rio consists of 15-25 per building. New york center houses 40 workers. Singapore, Chicago, Miami, Rome, and London has 5-10 workers each. The average file size is 25mb. THe company has intranet servers in los angeles, new york, london and tokyo. Each building needs internet access, telephone and confrencing. I need to chose protocols for the lans & wans......Ive come up with a t3 line in los angeles, t1 line in new york, t1 line in london, and t1 line in tokyo. 64k leased lines in singapore, rio, miami, rome, frankfurt, and chicago. Im confused as to which protocols i should choose for the wans. Why cant i use vpn?

Chicago New York
Frankfurt
Los Angeles London
Miami Rome

Tokyo

Singapore Rio de Janeiro



thatsthe diagram given......can anyone help me?

VPN isn't a network protacol. It creates a "virtual" network, using an existing network like the internet. It uses security and encryption to help keep other from seeing into it. It isn't a real network, as the name say "VIRTUAL private networking". You would still need a connection to connect to the internet, but you can use a leased line, Which is your own PRIVATE line which isn't a part of anouther network, which will be more secure than a VPN.

ok...any more help hehe

?

Look at this.

[SHWoff]

Frame Relay would be my first choice. You could get T-1s or fractional T-1s with lower CIRs (lowers the cost) and burst up to line rate when needed. The newer IP enabled networks are the fad now. Kinda like a private Internet. It's based on MPLS technology - sometimes called VPN...giving you any-to-any connectivity as opposed to the hub-n-spoke networks of the past.... The only issue here is, if you use legacy protocols or anything other than IP, you have to tunnel it in IP (additional overhead...)....

[Senwolf]

ok what the heck is this for anyway?

[DocTrebor]

I Like Eggs.

shut your trap doc....go gators....its for this dang project im trying to do...its pissing me off..any suggestions anyone...what type of hardware would i need in the buildings..

[SHWoff]

Routers: Cisco 3745 or the new ISR

Los Angeles: Cisco 6513 (Core) and 6509 (distribution and access layer) switches. Gig or 10Gig blades for trunks. 48-port line cards with 802.3af (for wireless and/or IP telephony)

New York: Cisco 4500 or 3500 switch(es)

Frankfurt, Tokyo, Singapore, Chicago, Miami, Rome, and London and Rio: Cisco 3500 switches

Originally posted by SHWoff
Frame Relay would be my first choice. You could get T-1s or fractional T-1s with lower CIRs (lowers the cost) and burst up to line rate when needed. The newer IP enabled networks are the fad now. Kinda like a private Internet. It's based on MPLS technology - sometimes called VPN...giving you any-to-any connectivity as opposed to the hub-n-spoke networks of the past.... The only issue here is, if you use legacy protocols or anything other than IP, you have to tunnel it in IP (additional overhead...)....

I don't like the idea of VPN. The fact that it travels over public to get from point A to point B, even with security and encrptyion someone could still get ahold of it easier than having to tap a leased lineto intercept it.

ANyways, it may be cheaper to goto OC instead of T connections. OC would be faster too. AT east for from tokyo, las angels, and new york.

[SHWoff]

I don't like the idea of VPN.

I agree. The VPN that I alluded to is basically private IP - not Internet. Usually, it's based on MPLS and you can get guaranteed QoS and CoS - something that you can't get over the public Internet. It's like having your own private Internet. You get the any-to-any connectivity without having to tail-circuit or order a mesh of PVCs (and try to guess the necessary CIR for each).

Since MPLS/IP Networks are a relatively new offering, there is not a lot of info on how well they actually work. We're in the beginning stages of migrating our 180-site network from ATM/Frame Relay to IP-Enabled (SBC's NVPN service). The design is complete. We'll use BGP to peer with SBC and EIGRP internally. We'll see how it goes....

As far as OC vs. DS goes, the telcos usually price them so that you'd have to have a number of the lower speed lines before it becomes cost-effective to bump up. For example, 6-8 DS-1s before DS-3 looks like a better alternative. Usually, 2-3 DS-3s before OC-3 looks good...

[Face]

Start with a few tin cans and a ball of string, then...