So, it seems like the general rule that folks around here use is more like 6-8 to one. I suspected as much. Very interesting to hear how everybody is doing it. What about CLEC's in other states -- I would imagine that you are not backhauling directly, but rather using something like frame to tie the remote POP into your network. -- Scot
-----Original Message----- From: owner-usr-tc@lists.xmission.com [mailto:owner-usr-tc@lists.xmission.com]On Behalf Of Mike Andrews Sent: Saturday, February 19, 2000 12:55 AM To: usr list Subject: Re: (usr-tc) OT: Survey - Backhauling traffic from POP's
3 to 1 is ridiculously low. We've got 6 PRI's worth of dialup traffic in one remote pop, and the T1 heading there peaks at 880 kbps. That carries only dialup traffic; no dedicated lines or DSL or anything else. I figure I can get to at least 9 PRI's before I worry about getting a second T1 down there...
Here in Bellsouth land, running a T1 out to this site was the most cost effective way to do it. Call Forwarding doesn't scale past 10 lines in Bellsouth land. The alternative was Bellsouth's Extended Reach PRI, which becomes uneconomical with only 2 PRI's... at that point it was cheaper to run a T1 ($458/month for 12 miles) than pay $400+/month PER PRI extra.
Running separate backbone connectivity into this particular location wasn't economical either, because it was really a remote switch that Bell backhauls to the one our main office is on anyway... and we would have had to put in something like a Cisco 3640 (for running BGP internally) rather than the 2511 we have now. (And the async ports on the 2511 hook up to the console ports on the Total Control nicely, so I can get into the cards if the ethernet dies.)
Mike Andrews (MA12) * mandrews@dcr.net * http://www.bit0.com/ VP, sysadmin, & network guy, Digital Crescent Inc, Frankfort KY Internet services for Frankfort, Lawrenceburg, Owenton, Shelbyville "Don't sweat the petty things, and don't pet the sweaty things."
On Fri, 18 Feb 2000, Scot Desort wrote:
Off-topic survey:
I am investigating some POP alternatives for our network. These POPs will be dialup only. They will be co-located within the CLEC switch or remote central office.
I am looking for information on how most of you backhaul the dialup traffic to your networks. I find it curiously strange that more CLECs do not have fiber in their facilities that connect them to IP backbones like UUNET, Sprint or CW (at least that's the way it is here in NJ). My first inclination was not to backhaul, but obtain a separate feed to one of the backbones right in the colo/switch, but this is not an option. So, I am left to backhaul.
What is the most cost-effective way to do this? Assuming that these POPs will be relatively small, not requiring A DS3 to backhaul, how many PRI dialup trunks can be supported for each T1 backhaul to my network? Or, is there a more efficient way to do it? The CLEC's use a 3 to 1 rule -- 3 PRI's with relatively moderate traffic can be supported by 1 T1 backhaul. I have my doubts here as well.
Thoughts, comments, suggestions are welcomed, off-list if you prefer.
-- Scot Desort Network Operations Manager NJ Internet Access scot@njaccess.net
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.