I have a router and I have the chance to receive the WAN connection either from a Serial port (Smart Serial) or T1/E1. I have both cards for Serial and E1/T1 interfaces. I really don't know what are the pros/cons from one to another.
Can anyone help me?
My company currently has only a Covad T1 that connects the main office to the internet. This line is mainly for our billing office (located across the state) to connect to us for our Terminal Server. Our future plans for our main office include having a company E-Mail Server as well as a Web Site for employee access, applications, information, PR, etc. Our normal day to day internet access doesn't include much besides a GPS program(which gets replaced by google maps if it goes down, which it does a lot), various people in the office using their personal(professional) email, streaming music, typical office business use with nothing too critical relying on the actual internet and a majority of our connections are for internal use. With our future plans in mind my question breaks down to some parts.
What are the steps (after figuring out who we're going with, what package, etc) in order to get a cable line working with a T1 in order to have the T1 as a back-up. I have done some research and either I'm more terrible at searching than I thought or there is no concrete documentation on this.
What kind of bandwidth should I spec out or expect to get by adding in these features in the future for our business. I don't expect facebook level traffic but we do have a huge contract with the local hospitals (we do all of their medical transport) and the company is well known in the area so I'm not quite sure what to expect as it will mostly be local (by local think NJ, PA, DE, I expect nothing should be coming from beyond that area)
And also, who do you think has the best support or way of going about this process and keeping a reliable cable connection working? But also allows a back-up T1 to kick in should anything go wrong. Options here include Comcast, Verizon, and a few local companies that probably just work off of them.
I should also add that the only guaranteed time the company needs to be connected to the internet is for our billing office which is between 8A-4:30P M-F so this is more for convenience than anything (downloading updates is a nightmare on the network, even during off-hours) and nightly downtime on the cable line is a non-issue.
We've been using T1's for years and never changed the connection to a faster Cable Modem. I am concerned about support, return to service. I cannot find in legalese Cable vs T1's FCC Regulations SLA's.
I'm very interested in what the current regulations are for returning T1 and Cable service to a business. I've not had too many issues with my T1's and when I have they've jumped on the issue immediately and stayed with it until resolved.
If I get a high speed cable modem for my business and it fails I'm wondering how I'm protected by the FCC for return to service.
We recently started leasing a small new site and part of the agreement was to have the owner of the building provide a point to point link between our main site and this building and we would purchase configure and maintain the hardware. The job fell on me to configure the two routers (1841s with CSU/DSU cards).
I unfortunately am not very Cisco savvy and I'm hoping to find some help here. I'm hoping to configure the two routers to essentially work like a standard ethernet cable. They need to be on the same subnet as one of our other departments (not NAT'd). The only examples I can find online involve both ends of the router being on separate subnets.
On our main site I have a port ready with the subnet I need. Can anyone out there provide me with some help?
I have a dedicated T1 line that runs between my office and my data center. Both ends have public IP addresses.
On both ends, we have AdTran T1 routers which connect to SonicWall firewalls.
The SonicWalls do a site-to-site VPN and handle the network translation, so the computers on the office network (10.0.100.x) can access the servers in the rack (10.0.103.x).
So the question: can I just add a static route to the SonicWalls so each network can access each other with out the VPN? Are there security problems (such as, someone else adding the appropriate static route and being able to access either the office or the datacenter)? Is there another / better way to do it?
The reason I'm looking at this is because the T1 is already a pretty small pipe, and having the VPN overhead makes connectivity really slow.
--
Clarifications (thanks for the answers so far):
The stumbling block for me is that the T1 has a public IP address. If I set up a route on at the office that says "you can find the gateway for 10.0.103.0 at 200.X.Y.Z", can some dude on the internet also set up the same route and also be able to access my 10.0.103.0 network?
With the VPN, I know it's not possible because there are authorization protocols which prevent outside people from getting in.
Alternatively, I guess the question is "What is the correct way to route between two remote networks over a T1 line?"
The T1 in question has a physical endpoint in my office, and another physical endpoint somewhere at the datacenter, but again, the IP address is public.
I'm not concerned that the telco or datacenter people are sniffing my passwords (if they were, that would sure suck, but that situation is above my paranoia threshold :).