Upgrade to Metro-E

[wlhj]

My employer is in the process from upgrading from frame relay to metro-e for 10 locations. Three of the locations have been brought up. I have very little router experience but was told metro-e was basically ethernet, but I would need a router at each location.

I am trying to connect two of the offices. I have Cisco 2801 routers which have two ethernet ports. They also have the CSU/DSU for the frame relay. My in house networks are 192.168.100.0 and 192.168.1.0. My routers are using .1 addresses for the LAN.

I have subnetted the second ethernet port out as follows 192.168.40.1 255.255.255.252 and 192.168.40.2 255.255.255.252. I have enabled egrip. I have a link from the A T & T equipment to the rouger at one office but not at the other office. AT & T has tested the line at the office that is not working and it is fine.

I can't ping the ethernet port 192.168.40.1 from my network(192.168.100.0) This is the port that does have a link.

My frame relay is still working fine. A T & T is going to leave it up until we tell them to turn it off.

Does anyone have an idea what I am doing wrong?

 

[wlhj]

One other thing I forgot to mention. At the main site we will continue to run our frame relay as one branch will not be converted over for three months due to new construction.

This is what my router configuration looks like at the main office:

hostname Main-Frame

enable secret 5 $1$Ik7T$tEQZlaA03L1xE.H/ja.RW0
enable password library

interface FastEthernet0/0
ip address 192.168.100.1 255.255.255.0
no ip mroute-cache
speed auto
no cdp enable

interface FastEthernet0/1
ip address 192.168.40.1 255.255.255.252
no ip mroute-cache
speed auto
no cdp enable

interface Serial0/0/0
description Frame-Relay Connection to Remote Sites
no ip address
encapsulation frame-relay
no ip mroute-cache

interface Serial0/0/0.1 point-to-point
description PVC to Boyce
ip address 192.168.20.1 255.255.255.252
no ip mroute-cache
frame-relay interface-dlci 101

interface Serial0/0/0.2 point-to-point
description PVC to Fuhrer
ip address 192.168.20.5 255.255.255.252
no ip mroute-cache
frame-relay interface-dlci 102

interface Serial0/0/0.3 point-to-point
description PVC to Glenmora
ip address 192.168.20.9 255.255.255.252
no ip mroute-cache
frame-relay interface-dlci 103

interface Serial0/0/0.4 point-to-point
description PVC to Gunter
ip address 192.168.20.13 255.255.255.252
no ip mroute-cache
frame-relay interface-dlci 104

interface Serial0/0/0.5 point-to-point
description PVC to Hineston
ip address 192.168.20.17 255.255.255.252
no ip mroute-cache
frame-relay interface-dlci 105

interface Serial0/0/0.6 point-to-point
description PVC to Johnston
ip address 192.168.20.21 255.255.255.252
no ip mroute-cache
frame-relay interface-dlci 106

interface Serial0/0/0.7 point-to-point
description PVC to King
ip address 192.168.20.25 255.255.255.252
no ip mroute-cache
frame-relay interface-dlci 107

interface Serial0/0/0.8 point-to-point
description PVC to Martin
ip address 192.168.20.29 255.255.255.252
no ip mroute-cache
frame-relay interface-dlci 108

interface Serial0/0/0.9 point-to-point
description PVC to Robertson
ip address 192.168.20.33 255.255.255.252
no ip mroute-cache
frame-relay interface-dlci 109

router eigrp 10
redistribute connected
redistribute static
network 192.168.20.0
network 192.168.30.0
network 192.168.40.0
no auto-summary

ip classless
ip route 0.0.0.0 0.0.0.0 192.168.100.2


line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
password library
login
transport input pad udptn telnet rlogin

 

[bobbyforhire]

I have metro-e here, think of it as a large Crossover cable from site to site. no PPP or anything like that just a large Crossover cable..I was somewhat shocked with how easy it was. And I did the same thing as you. One of the sites was still using it's T1'S to get from one place to another and we had to use the router at the other end to still process that.

for your site to site connections i would use something like

10.100.100.1 - 10.100.100.2
Subnet: 255.255.255.253
I pick that subnet to reduce the "fat" in the network.

Just set it up on both sides as if you were just hooking up one router to another using..well...a crossover cable

R1)
INTERFACE FA0/0
IP address 10.100.100.1 255.255.255.253
no shut
duplex full

r2)
INTERFACE FA0/0
ip address 10.100.100.2 255.255.255.253
no shut
duplex full

or something along those lines to that effect. Then when you are wanting to pass something along those lines use an ip route

If R1 has the internet then on R2 use this

ip route 0.0.0.0 0.0.0.0 10.100.100.1

If this does not help can you please pass along the other configs for your other routers i could help you map it all out.

 

[burtsbees]

you can't have 255.255.255.253
not trying to be anal, but i'm sure that was a typo...

Burt

 

[bobbyforhire]

burt - thanks, yes , 252 sorry

 

[wlhj]

Thanks for your help. I have added the route to the remote router. I added the entry ip route 0.0.0.0 0.0.0.0 192.168.40.1

I unplugged the frame relay connection to test this configuration. I was not able to ping the port (192.168.40.1) at the main office.

Here is the current configuration of the remote office.

urrent configuration : 1680 bytes

version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption

hostname Boyce

boot-start-marker
boot-end-marker

enable secret 5 $1$HdtM$5udMQNyyLvme5FjxEH8pk.
enable password library

no aaa new-model
memory-size iomem 25
no ip source-route
ip cef

no ip domain lookup
ip name-server 192.168.100.5

interface FastEthernet0/0
description Connection to LAN
ip address 192.168.1.1 255.255.255.0
no ip mroute-cache
speed auto
half-duplex
no cdp enable
!
interface FastEthernet0/1
description *** To Metro-E circuit ***
ip address 192.168.50.1 255.255.255.0
no ip redirects
no ip mroute-cache
speed 100
full-duplex
cdp enable

interface Serial0/1/0
description Frame-Relay connection to Main
no ip address
encapsulation frame-relay
no ip mroute-cache

interface Serial0/1/0.1 point-to-point
description Frame-Relay Connection to Main
ip address 192.168.20.2 255.255.255.252
no ip mroute-cache
no cdp enable
frame-relay interface-dlci 101

router eigrp 10
network 192.168.1.0
network 192.168.2.0
network 192.168.7.0
network 192.168.20.0
network 192.168.40.0
network 192.168.50.0
auto-summary

ip route 0.0.0.0 0.0.0.0 192.168.40.1

no ip http server
!
access-list 10 permit 192.168.2.0 0.0.0.255
access-list 10 permit 192.168.7.0 0.0.0.255
access-list 10 permit 192.168.4.0 0.0.0.255
access-list 10 permit 192.168.1.0 0.0.0.255
access-list 20 permit 192.168.100.0 0.0.0.255
access-list 20 permit 192.168.40.0 0.0.0.255
no cdp run

control-plane


line con 0
password rpl
login
line aux 0
line vty 0 4
password rpl
login

scheduler allocate 20000 1000
end