Discussion Locked

Frame Relay/56K/T1

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We currently have 2 56K Point to Point data lines. They have been working fine, however we are planning on running more data over our lines. We are going to have 2 remote locations (32 employees and 8 employees) access the internet and access our OEM through headquarters. Would a 128K Frame(32K CIR) and a 56K Frame (16K CIR)give us enough speed, or should we consider something else? I need to keep costs down, but I am not going to sacrifice speed for costs. Please give me any advice you can.

11 replies

by road-dog

Run a fractional T1 at the main site with 256k (4 DS0's). Drop in a fractional T1 at 128K at each remote. Map DLCI channels to the main site. If you want to manage / monitor Internet activity from remotes at the main site, route external traffic to the main over another DLCI, run it through the firewall at the main. What you spend on additional equipment will be offset by centralized security and bandwidth management.

Make sure that the CIR at the main site equals the total of the CIRs of the remotes!

bob.ackler@kebocon.com

by shanghai sam

You do not mention how much data is exchanged on the current lines and if either site is complaining of slow through-put.

You have increments of bandwidth you can use in both 56K and 64K steps. Most CSU/DSU's are both 56 and 64K configurable (unless they specify). The CIR is restricted by the PVC not the access circuits, thus your maximum access circuit required for the master site is 112K if both remotes are 56K. The size of the access circuit at the remote sites will depend on where yourpower users are located.

Another factor is BC (Burst committed) this allows you to burst data upto whatever is selected (IE 32K cir + 32K BC = 64K). Add in BE which is usually set as smaller access circuit - cir - BC, this allows you to burst upto the size of the smaller access circuit.

2-128K and 1-56K access circuit should give you enough speed with the CIR's specified and would keep your costs down if this network is inter-state.

by dlafrombois

Everything that was said is true and accurate, except I do not believe that 128k FR with a 32k CIR is enough. Especially, with 32 users at one site and internet at both sites. I would do one of two different designs:

1) Use local internet access at each site. It would look at either a 512k adsl or something with this speed or faster. Install a firewall/router/vpn soltuion, for example a sonicwall, and VPN company traffic across the internet and Send internet traffic out the local internet link.

2) If this is still not good enough look at T1 FR at each site with at least a 768 cir and a T1 FR with the same.

by shanghai sam

I agree with the above reply, I would probably not recommend F/R, unless you need the WAN to be comletely private.

One thing you did not mention was whether each branch requires access to the other branch. Using your existing setup, you already have this capability. If so, using F/R you would have to either setup an additional PVC between the branches, or implement each spoke of the F/R circuit as a sub interface off the HQ router (hub) using 2 seperate TCP/IP networks to allow them to routeback thru HQ (hub)due to F/R's split horizon nature without implementing multipe / meshed PVC's

Sub Interface ex. with 1 PVC per site to allow intra branch routing:

HQRouterPVC1(DLCI x)-----F/R PVC1-----BR1 (DLCI y)
192.168.1.1/30---------------------192.168.1.2/30
HQRouterPVC2(DLCI a)-----F/R PVC2-----BR1 (DLCI b)
192.168.1.1/30----------------------192.168.1.2/30

As you can see, there is a bit more complexity

Here are the two options I would suggest:

1. PPP T-1's from each site to HQ. The prices of T-1's have really dropped in the past couple years. This would provide you with more than 24x the bandwidth (64 KbS x 24 versus 1 56 KbS DDS circuit) and would be the simplest to setup / maintain. You can route your Internet traffic thru the F/R to your front end router / firewall and/or proxy.

2. Install DSL / Cable modem or T-1 circuits at each of the locations and implement a VPN solution, such as Nortel's Contivitiy switches or SonicWalls, or Cisco's. There are many to choose from, but I prefer the Nortel Contivity switches.

Let us know what you think

by gauchodude

*******Re Post of my answer due to typo********

I agree with the above reply, I would probably not recommend F/R, unless you need the WAN to be comletely private.

One thing you did not mention was whether each branch requires access to the other branch. Using your existing setup, you already have this capability. If so, using F/R you would have to either setup an additional PVC between the branches, or implement each spoke of the F/R circuit as a sub-interface off the HQ router (hub) using 2 seperate TCP/IP networks to allow them to route back thru HQ (hub)due to F/R's split horizon nature without implementing multipe / meshed PVC's

Sub Interface ex. with 1 PVC per site to allow intra branch routing:

HQRouterPVC1(DLCI x)-----F/R PVC1-----BR1 (DLCI y)
192.168.1.1/30---------------------192.168.1.2/30
HQRouterPVC2(DLCI a)-----F/R PVC2-----BR1 (DLCI b)
192.168.1.5/30---------------------192.168.1.6/30

As you can see, there is a bit more complexity

Here are the two options I would suggest:

1. PPP T-1's from each site to HQ. The prices of T-1's have really dropped in the past couple years. This would provide you with more than 24x the bandwidth (64 KbS x 24 versus 1 56 KbS DDS circuit) and would be the simplest to setup / maintain. You can route your Internet traffic thru the F/R to your front end router / firewall and/or proxy.

2. Install DSL / Cable modem or T-1 circuits at each of the locations and implement a VPN solution, such as Nortel'sContivitiy switches or SonicWalls, or Cisco's. There are many to choose from, but I prefer the Nortel Contivity switches.

Let us know what you think

This discussion is closed to new replies.