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]

Interesting, it does sound like they are doing trunking. That simply means that although the traffic is coming in on the same physical interface, it is separated logically inside the router on different subinterfaces.

If that's what they're doing then you will need a separate subnet for each connection. A /30 would work just fine for each virtual link, but it's not necessary to make your subnet that small. You could easily use /24s to make the math easier in your head. It's not like you're going to run out of space!

And they're right that dynamic routing does make sense, but I'm just lazy and hate adding tons of static routes.

 

[dearingkr]

AaronBeau:
I have three MetroE networks just like yours in Miami, Orlando, and Tampa.

Configure it the way we've recommended, it will work just fine. It's the way mine are set up.
The ISP's concerns about broadcast storms are old-school. With the new equipment nowadays, the chances of a broadcast storm are very rare. In fact I haven't seen one in the last five years.

One other thing to note: you may not be able to use VLANs over the MetroE. It depends on how the ISP implements their MetroE. All your sites are just a single VLAN on their network. So unless you are able to use Q-in-Q (VMAN), any tagged traffic will not work. My Miami network is that way.

MCSE CCNA CCDA