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.

 

[burtsbees]

Is there something already at those IP addresses? Is there a public IP on the outgoing interface?

Burt

 

[AaronBeau]

We are using a new ISP which is handing us Ethernet at each of our locations. Therefore the I wanted the Cisco FastEthernet0/1 to be divided up into 18 different IP's
10.0.10.1 /30 - 10.0.28.1 /30

And the IP Address on the router at each location will be:
10.0.10.2 /30 - 10.0.28.2 /30

 

[jneiberger]

I have a suspicion that you're going about this all wrong. You had a multipoint serial configuration before, probably frame relay. Now you have some sort of metro ethernet connection. Most likely, the routing is going to be very different. The only way you'd do it the way you're doing it is if you were using a trunk interface to connect with the ISP and each remote site had its own VLAN ID.

If that's how you're doing it then you do sort of have the right idea. If that's not how they're doing it, we need to know more about the specifics in order to help.

 

[AaronBeau]

Thank you for your patience with me. I am a Systems Guy, not a network guy. (I know I know!!)

-We are getting a Metro Ethernet Connection.

-Each of our 18 locations has a router.

-Our corporate location has a Cisco.

-The Cisco's FastEthernet0/1 interface is what we are planning on plugging the Metro Ethernet Connection into.

-Our ISP is leaving the networking up to us, therefore I wanted to divide the FastEthernet interface into 18 different IP Addresses.

EXAMPLE
This is how I imagined this working:
LOCATION WAN IP LAN IP CISCO INT CISCO IP
A 10.0.10.2 192.168.10.1 FE-0/1:0 10.0.10.1
B 10.0.11.2 192.168.11.1 FE-0/1:1 10.0.11.1
C 10.0.12.2 192.168.12.1 FE-0/1:2 10.0.12.1
R 10.0.28.2 192.168.28.1 FE-0/1:17 10.0.28.1

I hope this is descriptive enough

 

[brianinms]

With metro ethernet you should be using switches and not routers. Are you going to tag vlans across the metro E or are you going to use routed interfaces?

 

[jneiberger]

I'd be interested to know how the ISP is configuring this. Are all of these sites connected to the same LAN as if they were all bridged together? If so, you will only need one LAN IP address per location and they'll be in the same subnet.

If the ISP is doing trunking and tagging at the main site, and giving each site its own VLAN, then you'll need to configure subinterfaces on your Fast Ethernet interface at the hub. Each subinterface will have its own IP address in its own subnet and will associated with individual VLAN IDs.

 

[AaronBeau]

I believe routed interfaces?? Like I said, I am a Systems Guy.

Each location has a different IP Address scheme.
Corporate - 192.168.1.0 /24
Location A - 192.168.10.0 /24
...and so on

 

[jneiberger]

Hmm...something about this isn't adding up. Is your ISP assigned your LAN addresses that face them?

 

[AaronBeau]

We have assigned our LAN IP's (192.168.XX.0 /24). In addition we also came up with the (10.0.XX.0 /30).

I will try to explain this another way. Our ISP is going to hand us 1 Cat5e cable to plug into our network at Corporate. At each location, they will have 1 Cat5e cable to plug into their local networks. I want the 1 Cat5e cable to plug into our Cisco's FastEthernet0/1 interface. I then want to divide that interface according to my previous post.

 

[brianinms]

Using a router defeats the purpose for using metro ethernet. However, if you insist on using a router you would configure it ....

interface FastEthernet0/0
no ip address
duplex auto
speed auto
!
interface FastEthernet0/0.2
encapsulation dot1Q 2
ip address 10.10.11.1 255.255.255.0

You would then have to configure the corresponding router with the same configuration and use a different IP address.

For what its worth, why isnt a network engineer doing this project?

 

[jneiberger]

Aaron,

I understand the physical connectivity. It's the logical connectivity that we need to understand. If all of your LAN IPs are in the same subnet then there is no reason to further configure additional addresses at your main site.

What problem are you trying to solve?

 

[AaronBeau]

Each LAN is on it's own subnet.
Corporate's LAN subnet is 192.168.1.1
Each location's subnet starts with 192.168
then the third octet is incremental by 1 starting at 10.

 

[AaronBeau]

We don't have a network engineer, we are a small private real estate company.

 

[jneiberger]

Okay, so, the ISP must be handling the routing for you. You just need to have default routes at your remote sites that point toward the ISPs gateway address that they should have given you.

Your hub site will need static routes pointing toward the ISP in order to get to your other sites unless they are allowing you to run some sort of routing protocol. Is this a static routing setup or did they offer to use OSPF or BGP?

 

[brianinms]

You mention your ISP is handing you off an ethernet connection. Is the service actually metro ethernet or are they using a managed router?

 

[AaronBeau]

Here is a part of the current way it is setup:

interface Serial1/0:0
 description Brewster News
 bandwidth 128
 ip address 192.168.254.18 255.255.255.252
 ip helper-address 192.168.1.15
 encapsulation ppp
 fair-queue 64 256 0
!
interface Serial1/0:1
 description Carousel Park
 bandwidth 128
 ip address 192.168.254.74 255.255.255.252
 ip helper-address 192.168.1.15
 encapsulation ppp
 fair-queue 64 256 0
!
interface Serial1/0:2
 description Elmwood Square
 bandwidth 128
 ip address 192.168.254.58 255.255.255.252
 ip helper-address 192.168.1.15
 encapsulation ppp
 fair-queue 64 256 0
!
interface Serial1/0:3
 description Liberty Square
 bandwidth 128
 ip address 192.168.254.62 255.255.255.252
 ip helper-address 192.168.1.15
 encapsulation ppp
 fair-queue 64 256 0

Instead of Serial I want to use the FastEthernet interface

 

[AaronBeau]

This service is Metro Ethernet.

 

[jneiberger]

The new service does not work quite the same way as the old service, so the configuration style you see currently will not work with the new setup.

 

[AaronBeau]

So there isn't a way to divide the FastEthernet interface like the Serial interface?