Configuring interface FastEthernet 0/1 3

[AaronBeau]

I would like to start by saying I am not a Cisco guy. With that in mind, here is what I am trying to accomplish.

My FastEthernet 0/1 interface needs to be configured to allow our 18 remote locations to connect back to us. Previously they all came in through the serial interface.

I am not sure if I am going to explain this correct, but this is what I am trying to program:
FastEthernet0/1:0 10.0.10.1
FastEthernet0/1:1 10.0.11.1
....up to.....
FastEthernet0/1:17 10.0.28.1

Any guidance would be greatly appreciated.

 

[jneiberger]

It's not going to be necessary with the new configuration. In the current configuration, your main site actually is the hub site. In other words, the other sites have circuits (DS0 fractional T1 or ISDN BRI) that terminate directly at your site.

With the new configuration, the ISP is acting as the real hub. All of your sites--including the one you think of as the hub--simply attach to the ISP's network as spoke sites.

 

[AaronBeau]

This definitely is starting to sound like a typical Friday!

Ok, I want to flip this around and ask you a question. Since we were told that each location would be able to keep their local IP Subnets and that they would all connect back to corporate. How would you go about setting this up then?

This is the Hardware I have
Router (each location)
Switch (each location)
Cisco Pix and 2600 (corporate location)

 

[jneiberger]

That depends. Do your routers have two Fast Ethernet connections? (I'm assuming that you're getting Fast Ethernet from your provider.)

 

[jneiberger]

You probably already figured this out, but you probably should have a network engineer helping you with this. We're more than happy to help, of course, but that doesn't beat an on-site engineer who understands the design and the end goals. We'll get it working for you, though.

 

[AaronBeau]

OMG, I wish we had a Network Engineer, along with a few other things, but you know how small privately held companies are.

We do have 2 FastEthernet interfaces on the Cisco.
FastEthernet0/0 - is used for our LAN at Corp
FastEthernet0/1 - was intended to connect us to the other sites

 

[jneiberger]

Okay, this will be fairly easy with a couple of caveats. We really need to know more about the overall design. For example, do these remotes sites require Internet access? If so, do they go through the main site to get to the Internet or do they have their own Internet connections (DSL/cable)?

The first part is simple. At each location, configure FastEthernet0/1 with the IP address assigned to you by the ISP.

The second part, routing, is probably going to be fairly simple, as well. If each site goes through the main site to get to the Internet, all you need at each "remote" site is a static route like this:

ip route 0.0.0.0 0.0.0.0 <gateway>

...where <gateway> is the IP address of the gateway for that site. The ISP should have given you this information. If you have old static routes, you'll want to remove them once you've tested the new circuits.

At the main site, you probably already have a default route for your Internet access, so you can't add another one pointing back toward your ISP. You'll need to add individual static routes for each remote subnet you need to reach.

Let's say the gateway for the main site is 192.168.0.1. You'd need routes to tell it how to reach the subnets at your remote sites. Let's say your local LAN subnets at each site are in the 10.x.x.x range, you'd need something like the following:

ip route 10.10.1.0 255.255.255.0 192.168.0.1
ip route 10.10.2.0 255.255.255.0 192.168.0.1
ip route 10.10.3.0 255.255.255.0 192.168.0.1

and so on, one for each remote subnet that you need to reach. The tricky part that we also need to understand is how your ISP knows about your remote networks. If you're not sharing routing information via OSPF or BGP, they probably are doing static routing internally, which means they need to know the locations of your local IP subnets.

 

[AaronBeau]

Our internet connection comes in at our Corporate Office.

The Metro E connection going to each site is going to give us a 3 meg pipe between corp and the remote site.

I was told that when they hand us off the ethernet connection, we can set whatever IP address scheme we want. I chose 10.0.xx.0 /30 (xx being an incremental number)

All the remote sites browse the Internet through the corporate location, 10 meg pipe.

I have figured out how to program in the static routes on the Cisco and have started to configure them.

The only Cisco is at Corporate.

Each site has a Linksys WRT54GL which I converted over to DD-WRT. (This has a WAN and LAN)
WAN: 10.0.xx.2 and LAN: 192.168.xx.1

Maybe this is where I am going wrong. I am configuring each WAN to have a subnet of 255.255.255.252
My train of thought is the Corp Cisco has an IP address of 10.0.10.1 /30 and the remote site 10.0.10.2 /30
then the next remote site would be configured 10.0.11.2 /30 and the Cisco would have another IP address 10.0.11.1 /30

 

[jneiberger]

Oh, I misunderstood something. If they're letting you assign your own addressing to the Metro E connections, I'm betting that they're all on the same subnet. That makes the most sense and it means that our task is even easier.

You still will only need one IP address on each Metro E connection, and they all need to be in the same subnet. Forget static routing. You probably already have a routing protocol running, so it should be relatively quick and painless.

If your remote sites have static default routes, you may need to change them if those sites suddenly lose Internet access after the migration.

 

[AaronBeau]

If I am understanding you correctly, this is what you are saying.

Corporate:
interface FastEthernet0/1
ip address 10.0.0.1 255.255.255.0

Remote Locations:
WAN: 10.0.0.XX
LAN: 192.168.XX.1

 

[jneiberger]

Exactly!

Are you currently running a routing protocol or are you using static routes only?

 

[AaronBeau]

I believe static routes.
Currently this is our situation:

ip classless
ip route 0.0.0.0 0.0.0.0 192.168.1.254
ip route 172.30.1.0 255.255.255.0 192.168.1.254
ip route 192.168.10.0 255.255.255.0 Serial1/1:2
ip route 192.168.11.0 255.255.255.0 Serial1/1:1
ip route 192.168.12.0 255.255.255.0 Serial1/1:4
ip route 192.168.13.0 255.255.255.0 Serial1/1:3
ip route 192.168.14.0 255.255.255.0 Serial1/1:0
ip route 192.168.15.0 255.255.255.0 Serial1/1:5
ip route 192.168.16.0 255.255.255.0 Serial1/1:6
ip route 192.168.17.0 255.255.255.0 Serial1/0:0
ip route 192.168.18.0 255.255.255.0 Serial1/0:4
ip route 192.168.19.0 255.255.255.0 Serial1/0:5
ip route 192.168.20.0 255.255.255.0 192.168.1.254
ip route 192.168.21.0 255.255.255.0 Serial1/0:7
ip route 192.168.22.0 255.255.255.0 Serial1/0:8
ip route 192.168.23.0 255.255.255.0 Serial1/0:9
ip route 192.168.25.0 255.255.255.0 Serial1/0:3
ip route 192.168.26.0 255.255.255.0 Serial1/0:10
ip route 192.168.27.0 255.255.255.0 Serial1/0:11
ip route 192.168.29.0 255.255.255.0 Serial1/0:6
no ip http server

So would my new config would look like this?

ip classless
ip route 0.0.0.0 0.0.0.0 192.168.1.254
ip route 10.0.0.0 255.255.255.0 FastEthernet0/1
no ip http server

 

[jneiberger]

It won't quite be that simple, but we can turn on EIGRP as a routing protocol and all will be well. If you want to continue to use static routes, you'll need one for each remote site just as you currently do. If you turn on EIGRP, you'll only need the static default routes. The rest you'll be able to get rid of.

To turn on EIGRP, configure this on each router:

router eigrp 1
network 10.0.0.0
network 192.168.0.0

The static default route at your remote sites will probably change. If the IP address of your main site is 10.0.0.1, for example, the static route at the remote sites will be:

ip route 0.0.0.0 0.0.0.0 10.0.0.1

 

[brianinms]

They can't run eigrp.

"The only Cisco is at Corporate.

Each site has a Linksys WRT54G

 

[AaronBeau]

Our Cisco 2600 is what connects all our remote sites.
It's lan ip address (FastEthernet0/0) is 192.168.1.4

Our internet connection comes in on the Cisco Pix (192.168.1.254)

 

[jneiberger]

Oh, I didn't even catch that. Good catch, Brian.

Hmm...I have no idea what routing capabilities those Linksys routers have. You're probably going to be stuck doing static routing for everything. That just means that your corporate site will have static routes to every remote site, just as you have now.

 

[AaronBeau]

And btw, networking makes my brain hurt

 

[jneiberger]

That's okay. Systems stuff makes my brain hurt.

 

[AaronBeau]

Ok, with recent developments the new routes would look like:

ip classless
ip route 0.0.0.0 0.0.0.0 192.168.1.254
ip route 192.168.10.0 255.255.255.0 FastEthernet0/1
ip route 192.168.11.0 255.255.255.0 FastEthernet0/1
ip route 192.168.12.0 255.255.255.0 FastEthernet0/1
ip route 192.168.13.0 255.255.255.0 FastEthernet0/1
ip route 192.168.14.0 255.255.255.0 FastEthernet0/1
ip route 192.168.15.0 255.255.255.0 FastEthernet0/1
ip route 192.168.16.0 255.255.255.0 FastEthernet0/1
ip route 192.168.17.0 255.255.255.0 FastEthernet0/1
ip route 192.168.18.0 255.255.255.0 FastEthernet0/1
ip route 192.168.19.0 255.255.255.0 FastEthernet0/1
ip route 192.168.20.0 255.255.255.0 FastEthernet0/1
ip route 192.168.21.0 255.255.255.0 FastEthernet0/1
ip route 192.168.22.0 255.255.255.0 FastEthernet0/1
ip route 192.168.23.0 255.255.255.0 FastEthernet0/1
ip route 192.168.24.0 255.255.255.0 FastEthernet0/1
ip route 192.168.25.0 255.255.255.0 FastEthernet0/1
ip route 192.168.26.0 255.255.255.0 FastEthernet0/1
ip route 192.168.27.0 255.255.255.0 FastEthernet0/1
ip route 192.168.28.0 255.255.255.0 FastEthernet0/1
no ip http server

 

[jneiberger]

No, don't just send them out the interface. They need to know exactly where to go, so use the "WAN" IP addresses of your remote sites instead.

 

[AaronBeau]

Alright,
so it would be

ip classless
ip route 0.0.0.0 0.0.0.0 192.168.1.254
ip route 192.168.10.0 255.255.255.0 10.0.0.10
ip route 192.168.11.0 255.255.255.0 10.0.0.11
ip route 192.168.12.0 255.255.255.0 10.0.0.12
ip route 192.168.13.0 255.255.255.0 10.0.0.13
ip route 192.168.14.0 255.255.255.0 10.0.0.14
ip route 192.168.15.0 255.255.255.0 10.0.0.15
ip route 192.168.16.0 255.255.255.0 10.0.0.16
ip route 192.168.17.0 255.255.255.0 10.0.0.17
ip route 192.168.18.0 255.255.255.0 10.0.0.18
ip route 192.168.19.0 255.255.255.0 10.0.0.19
ip route 192.168.20.0 255.255.255.0 10.0.0.20
ip route 192.168.21.0 255.255.255.0 10.0.0.21
ip route 192.168.22.0 255.255.255.0 10.0.0.22
ip route 192.168.23.0 255.255.255.0 10.0.0.23
ip route 192.168.24.0 255.255.255.0 10.0.0.24
ip route 192.168.25.0 255.255.255.0 10.0.0.25
ip route 192.168.26.0 255.255.255.0 10.0.0.26
ip route 192.168.27.0 255.255.255.0 10.0.0.27
ip route 192.168.28.0 255.255.255.0 10.0.0.28
no ip http server

WOW this was a LONG day. Thank you so much for your help. This is the second time I had to configure something on a Cisco router and I give you guys tons of credit for knowing you stuff.