cannot route to remote LAN over metro ethernet

Answered Question
Jun 22nd, 2010
User Badges:

I have a new metro ethernet connection installed between HQ and a remote site and while the metro ethernet connection is working properly and I can route between the two Cisco 891 routers at each location, I cannot route to the remote LAN from either device.


To clarify, consider the following:


HQ Site:


Cisco 891 Router


WAN (VLAN100) Interface: 192.168.220.1

LAN (VLAN 1) Interface: 192.168.200.6


Secondary Site:


Cisco 891 Router


WAN (VLAN 100) Interface 192.168.220.2

LAN (VLAN 1) Interface 192.168.209.32



I can ping the WAN and LAN interfaces at the secondary site from the HQ site 891 and vice-versa, but I cannot ping any other addresses in the LAN subnet on either side.


To clarify further, from the HQ Site, I can ping 192.168.220.2 and 192.168.209.32, but I cannot ping 192.168.209.1. However, I can ping 192.168.209.1 from the Secondary Site.


Any help would be greatly appreciated. Configs are attached for your viewing pleasure.


Regards,


Maynard

Correct Answer by djh278778 about 7 years 1 week ago

If you are testing with the 192.168.209.1, and it is a L3 switch, it must have routes pointing to the 891. Or if it is not currently routing like I think you may have said then it should, at a minimum have a default gateway (in the switch) of 192.168.209.32, for return traffic to 192.168.220.x

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
John Blakley Tue, 06/22/2010 - 12:33
User Badges:
  • Purple, 4500 points or more

Can you post your routing table?


HTH,

John

vansmaq77 Tue, 06/22/2010 - 13:09
User Badges:

j. blakley:


here are the route tables:


HQ SIte:


NMCC-LG-1#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route


Gateway of last resort is 0.0.0.0 to network 0.0.0.0


S    192.168.209.0/24 is directly connected, FastEthernet8.100
C    192.168.200.0/24 is directly connected, Vlan1
     192.168.220.0/24 is variably subnetted, 2 subnets, 2 masks
C       192.168.220.0/30 is directly connected, FastEthernet8.100
D       192.168.220.0/24 is a summary, 01:47:41, Null0
S*   0.0.0.0/0 is directly connected, FastEthernet8.100




Secondary Site:


ROUTER#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route


Gateway of last resort is 192.168.220.1 to network 0.0.0.0


C    192.168.209.0/24 is directly connected, Vlan1
S    192.168.200.0/24 [1/0] via 192.168.220.1
     192.168.220.0/24 is variably subnetted, 2 subnets, 2 masks
C       192.168.220.0/30 is directly connected, GigabitEthernet0.100
D       192.168.220.0/24 is a summary, 02:21:31, Null0
S*   0.0.0.0/0 [1/0] via 192.168.220.1




Thanks,


Maynard

John Blakley Tue, 06/22/2010 - 13:18
User Badges:
  • Purple, 4500 points or more

Maynard,


Here's what I would do:


Your HQ router is 192.168.220.1 and your remote site router is 192.168.220.2. I would first get in your remote site router and try to ping a host on the 192.168.220.x subnet sourcing from int g0.100 to see if your vlan interface is working as expected.


You're running eigrp. Can you post your topology table? (sh ip eigrp topo)


You don't need the static route for 192.168.209.0 if you're running eigrp. You can still have it, but I'd change it to point the remote routers ip address and not the outgoing interface: ip route 192.168.209.0 255.255.255.0 192.168.220.2


The static route on the secondary router is incorrect. Again, you can remove this since you're running eigrp, but you need to change the route to be 192.168.200.0 255.255.255.0 192.168.220.1


HTH,

John

vansmaq77 Tue, 06/22/2010 - 13:37
User Badges:

j.blakley:


I can ping the WAN interface on  the remote 891 from the HQ site as shown in the following:


HQ-ROUTER#ping 192.168.220.2 source 192.168.220.1


Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.220.2, timeout is 2 seconds:
Packet sent with a source address of 192.168.220.1
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms


I have removed the static routes, relying now on EIGRP. Here is the topology from both routers:


HQ-ROUTER#sh ip eigrp topo

IP-EIGRP Topology Table for AS(1)/ID(192.168.220.1)


Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
       r - reply Status, s - sia Status


P 192.168.200.0/24, 1 successors, FD is 28160
        via Connected, Vlan1
P 192.168.220.0/24, 1 successors, FD is 28160
        via Summary (28160/0), Null0
P 192.168.220.0/30, 1 successors, FD is 28160
        via Connected, FastEthernet8.100
P 192.168.209.0/24, 0 successors, FD is Inaccessible
        via 192.168.220.2 (30720/28160), FastEthernet8.100


SECONDARY-ROUTER#sh ip eigrp topo

IP-EIGRP Topology Table for AS(1)/ID(192.168.220.2)


Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
       r - reply Status, s - sia Status


P 192.168.200.0/24, 0 successors, FD is Inaccessible
        via 192.168.220.1 (30720/28160), GigabitEthernet0.100
P 192.168.220.0/24, 1 successors, FD is 28160
        via Summary (28160/0), Null0
P 192.168.220.0/30, 1 successors, FD is 28160
        via Connected, GigabitEthernet0.100
P 192.168.209.0/24, 1 successors, FD is 28160
        via Connected, Vlan1


Thanks for your help.


Maynard

djh278778 Tue, 06/22/2010 - 12:49
User Badges:

Hello


Your ip route is incorrect in the secondary site router. instead of reading: 192.168.200.0 255.255.255.0 192.168.200.6, it should read" 192.168.200.0 255.255.255.0 192.168.220.1, that should fix it. If it does not fix it consider the following. What is 192.168.209.1, I am assuming it is a firewall or another router or something because it is defined as the default-gateway in the 891. If so does it have the correct routes in it (192.168.220.0 255.255.255.0 192.168.209.32) and (192.168.200.0 255.255.255.0 192.168.209.32)? What is the default gateway that your LAN hosts are using? Do they point to the 891's or to another routing device? I noticed too that you have a default route at each 891 pointing back to each other. You might want to double check that. Also you shouldnt have to specify a route for 192.168.200.0 in the HQ router because it is directly connected.

vansmaq77 Tue, 06/22/2010 - 13:18
User Badges:

djh278778:


I tried changing the route for the 192.168.200.0/24 subnet to 192.168.220.1 with no luck.


To answer your other questions: 192.168.209.1 is the default gateway (L3 switch) at the secondary site and does not have any routes pointing to the 891 router (192.168.209.32 or 192.168.200.6). At this point, I have not routed any traffic over the new metro ethernet circuit and all of my testing has been on the routers themselves, not on any hosts connected to each individual LAN.


I agree that the routes on each 891 routing back to itself are uneccessary, because they are directly connected, this was just done to in the process of testing.


To give some more information, if I try to ping a local LAN address from the 891 at the HQ site using the WAN interface as the source, it also does not route.


For instance:


router#ping 192.168.209.1 source gi0.100 (192.168.220.2)


I get 100% packet loss.


Hope that helps shed some more light on this.


Thanks,


Maynard

Correct Answer
djh278778 Tue, 06/22/2010 - 13:31
User Badges:

If you are testing with the 192.168.209.1, and it is a L3 switch, it must have routes pointing to the 891. Or if it is not currently routing like I think you may have said then it should, at a minimum have a default gateway (in the switch) of 192.168.209.32, for return traffic to 192.168.220.x

vansmaq77 Tue, 06/22/2010 - 13:48
User Badges:

you are totally right! cannot believe I missed that.


Thanks a million!



Maynard

Actions

This Discussion

Related Content