Re: Help with Lan-P2P-Lan routing

cpcrouter · ‎03-10-2005

everybody,

I am having a bit of trouble getting traffice to flow from one lan across a P2P to certain hosts on the remote lan.

I am using two 1720s over a T1.

Two sites NC and NJ

NJ = 10.239.140.0/22

NC = 10.239.134.0/24

WAN = 192.168.100.0/30

I'm trying to use EIGRP and RIP

The NJ and NC configs are attached.

The problem is when I try to ping certain hosts on the NJ lan from the NC router. Say ping 10.239.140.125 I get 0 replys. If I do an extended ping using an address on the NC lan I am successful.

I can ping anything I want from the NJ router or my host which is on NJ lan. The NC router cannot ping 10.239.141.x or 10.239.142.x ect. So I'm thinking a subnet issue but its not entirely clear where. I'll provide more info if you need. I'm stumped.

amikat · ‎03-11-2005

Hi,

I feel a bit confused with your configuration (which may be completely my own problem).

Will you please clarify:

Is your T1 p2p link the only connection betwee two sites?

Is your T1 p2p link up and operational?

Are your serial0 and fastethernet0 intefaces in up/up status (both routers)?

If answers to these questions are "yes" then:

Will you please try to ping the serial and fastethernet interfaces (NC from NJ and vice versa).

If success, will you please make sure that your fastethernet hosts have their assigned ip addresses with proper mask and that their default gateway parameters are set properly (10.239.134.1 in NC and 10.239.140.25 in NJ).

If everything is correct you should be able to ping your hosts from the router and any host on the opposite site (provided you have not installed any additional device between your fastethernet hosts and router interfaces).

Almost certainly you would experience problems with the EIGRP and RIP distributions as both protocols are using very dissimilar metrics and these need to be adjusted - but this can wait: your static routes should be sufficient for connecting both sites.

Will you please let me know the results.

Best regards,

Antonin

cpcrouter · ‎03-11-2005

Thanks Antonin,

The T connects only the two sites.

Up and operational(thank goodness).

All interfaces are up and operational.

I can ping both interfaces from each side.

Funny thing, I can now ping the host I initially needed to. I happened a little while after I gave up and posted this message. If it was a routing issue I could understand rip taking a little bit to learn routes, but I specifically used static routes and it was not working before. This had me scratching my head. I know getting the to routing protocols in harmony will be a task, but and explicit route should be the end of the ping problems. And should be as soon as I enter it in the config which it wasn't. So I still don't understand why it happens.

I still cannot ping some address' like 10.239.142.16 ,x.x.142.12 which are a switches. I can do it using an extended ping from the NC router using either interface. Nor can I ping the x.x.142.16 ect from the external interface of the NJ box.

I have other sites that have the same problem. Those sites are use Frame Relay. But even so, static routes are in place as the NJ-NC are, but no ping.

NJ is the main site. In NJ there are 3 routers of conciquece. The NJ-NC, a cisco 1100 handling the Frame Relay to 3 other sites, and a Nortel VPN router that we use as a backup for the remote sites. There is a firewall on the NJ lan.

I contend that the 1100 with 3 FR's is underspec'd but the we only do telnet sessions and 'light' web browsing traffic over them.

I was thinking about just ditching EIGRP and using OSPF so it will be compatible with the Nortel router and future expansion plans.

amikat · ‎03-11-2005

Hi,

I am glad to hear there is a progress.

These are my comments:

- As I cannot see any routing problem as configured on your NJ, NC routers I suspect that the problem to ping your switches MAY be with their configuration. I am not aware whether these are L2 or L3 and if they are Cisco at all. They have clearly problem to reach the 192.168.1.0/30 subnet. Provided they are Cisco and you would like to get further help, will you please provide more information, I will be glad to try,

- FR may be different story. There are issues like split horizon, mappings, etc. Again if you believe you need help more information would be necessary to post,

- Your dynamic routing protocols: as I have already mentioned you need to pay attention when redistributing. This may be your start link to look at:

http://www.cisco.com/univercd/cc/td/doc/cisintwk/ics/cs004.htm#xtocid1232010

Good luck!

Best regards,

Antonin

mhussein · ‎03-11-2005

Also, could you please post "show ip route" for both routers?

Regards,

Mustafa

cpcrouter · ‎03-11-2005

Sure thing, here you go.

Seabrook2MtHome#sh ip rout

Codes: C - connected, S - static, I - IGRP, 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, E - EGP

i - IS-IS, 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 10.239.140.2 to network 0.0.0.0

10.0.0.0/8 is variably subnetted, 12 subnets, 6 masks

R 10.239.170.0/23 [120/1] via 10.239.140.24, 00:00:18, FastEthernet0

S 10.239.134.0/24 [1/0] via 192.168.100.2

C 10.239.140.0/22 is directly connected, FastEthernet0

R 10.239.138.3/32 [120/3] via 10.239.140.21, 00:00:00, FastEthernet0

S 10.239.138.0/24 [2/0] via 10.239.140.21

R 10.239.144.8/30 [120/1] via 10.239.140.22, 00:00:14, FastEthernet0

R 10.239.152.0/24 [120/1] via 10.239.140.24, 00:00:18, FastEthernet0

S 10.239.150.240/28 [1/0] via 192.168.100.2

R 10.239.145.240/28 [120/1] via 10.239.140.24, 00:00:18, FastEthernet0

R 10.239.139.252/30 [120/1] via 10.239.140.21, 00:00:00, FastEthernet0

R 10.239.139.248/30 [120/1] via 10.239.140.21, 00:00:00, FastEthernet0

R 10.239.139.244/30 [120/1] via 10.239.140.21, 00:00:00, FastEthernet0

R 146.145.0.0/16 [120/1] via 10.239.140.24, 00:00:18, FastEthernet0

192.168.100.0/30 is subnetted, 1 subnets

C 192.168.100.0 is directly connected, Serial0

S* 0.0.0.0/0 [1/0] via 10.239.140.2

Seabrook2MtHome#

MountHomePt-Pt#sh ip rout

Codes: C - connected, S - static, I - IGRP, 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, E - EGP

i - IS-IS, 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 10.239.140.25 to network 0.0.0.0

10.0.0.0/8 is variably subnetted, 6 subnets, 5 masks

S 10.239.170.0/23 [1/0] via 192.168.100.1

R 10.239.134.3/32 [120/1] via 10.239.134.2, 00:00:13, FastEthernet0

C 10.239.134.0/24 is directly connected, FastEthernet0

S 10.239.140.0/22 [1/0] via 192.168.100.1

S 10.239.138.0/24 [1/0] via 192.168.100.1

S 10.239.150.240/28 [1/0] via 10.239.134.100

192.168.100.0/30 is subnetted, 1 subnets

C 192.168.100.0 is directly connected, Serial0

S* 0.0.0.0/0 [1/0] via 10.239.140.25

MountHomePt-Pt#