RIP v2 Doesn't work - Cannot get to Route properly
Hello World.
I have the following:
Router A S0=192.168.0.2 /30 f0=10.86.205.3 /24
Router B S0=192.168.0.10 /30 f0=10.86.178.16
192.168.0.0 is new MPLS netwrok
10.86.205.0 is Main Office workstations
10.86.178.0 is branch workstations
attached is Main Office config+sh ip route & branch config+sh ip route
from workstations or router at main office, I cannot ping branch workstations
from router A, I cannot ping branch workstations
and vice versa
from router A, I cannot ping branch workstations
from Router B, I can
Tried Ripv1, it put routes in to go over old network, not the new one. Ripv2 didn't routre anything
I need all the worstations to talk over this MPLS network - Please help!!!
routera.txt
routerb.txt
I have the following:
Router A S0=192.168.0.2 /30 f0=10.86.205.3 /24
Router B S0=192.168.0.10 /30 f0=10.86.178.16
192.168.0.0 is new MPLS netwrok
10.86.205.0 is Main Office workstations
10.86.178.0 is branch workstations
attached is Main Office config+sh ip route & branch config+sh ip route
from workstations or router at main office, I cannot ping branch workstations
from router A, I cannot ping branch workstations
and vice versa
from router A, I cannot ping branch workstations
from Router B, I can
Tried Ripv1, it put routes in to go over old network, not the new one. Ripv2 didn't routre anything
I need all the worstations to talk over this MPLS network - Please help!!!
routera.txt
routerb.txt
Don Johnston
The two routers must be neighbors in order to exchange RIP updates. In other words, they have to be on a common network.
ASKER
They are, though.
Router A is 192.168.0.2 /30 and Router B is 192.168.0.10 /30.
I can ping between the two and can ping the f0 int of each from the opposite route. I just can't ping anything else on the same network of the f0 interface from the other end.
Router A is 192.168.0.2 /30 and Router B is 192.168.0.10 /30.
I can ping between the two and can ping the f0 int of each from the opposite route. I just can't ping anything else on the same network of the f0 interface from the other end.
ASKER
Correction - Router Setup above should read
Router B = S0=192.168.0.10 /30=10.86.178.3 /24
NOT
Router B S0=192.168.0.10 /30 f0=10.86.178.16
Router B = S0=192.168.0.10 /30=10.86.178.3 /24
NOT
Router B S0=192.168.0.10 /30 f0=10.86.178.16
Ben,
I've been having a look at the configs on your two routes and they dont quite match what you have in the original question. I am going to assume the following.
Router A and B are connected via Serial link over a LAN or WAN (as in the configs the netwroks are shown on a serial and an ethernet port).
You basically have two issues with your configs.
Firstly the two serial ports are not on the same subnet. 192.168.0.2/30 and 192.168.0.10/30 are on different subnets. You need to change the second IP address to 192.168.0.1/30
Secondly as the two office networks on router a and router b are "connected" and not learn via RIP you will have to redistribute them into the RIP protocol for them to be proopgated
I would suggest the following (assuming my assumption about your routeres are correct)
Router A
interface FastEthernet0
ip address 10.86.205.3 255.255.255.0
duplex auto
speed auto
!
interface serial0
ip address 192.168.0.1 255.255.255.252
duplex auto
speed auto
!
router rip
version 2
redistribute connected
network 10.0.0.0
network 192.168.0.0
Router B
interface FastEthernet0/0
ip address 10.86.178.3 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet1/0
ip address 192.168.0.2 255.255.255.252
duplex auto
speed auto
!
router rip
version 2
redistribute connected
network 10.0.0.0
network 192.168.0.0
Also i would remove the static routes that you have in the configs you supplied to 10.86.205.0 and 10.86.178.0
I think that should do it.
Doug
I've been having a look at the configs on your two routes and they dont quite match what you have in the original question. I am going to assume the following.
Router A and B are connected via Serial link over a LAN or WAN (as in the configs the netwroks are shown on a serial and an ethernet port).
You basically have two issues with your configs.
Firstly the two serial ports are not on the same subnet. 192.168.0.2/30 and 192.168.0.10/30 are on different subnets. You need to change the second IP address to 192.168.0.1/30
Secondly as the two office networks on router a and router b are "connected" and not learn via RIP you will have to redistribute them into the RIP protocol for them to be proopgated
I would suggest the following (assuming my assumption about your routeres are correct)
Router A
interface FastEthernet0
ip address 10.86.205.3 255.255.255.0
duplex auto
speed auto
!
interface serial0
ip address 192.168.0.1 255.255.255.252
duplex auto
speed auto
!
router rip
version 2
redistribute connected
network 10.0.0.0
network 192.168.0.0
Router B
interface FastEthernet0/0
ip address 10.86.178.3 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet1/0
ip address 192.168.0.2 255.255.255.252
duplex auto
speed auto
!
router rip
version 2
redistribute connected
network 10.0.0.0
network 192.168.0.0
Also i would remove the static routes that you have in the configs you supplied to 10.86.205.0 and 10.86.178.0
I think that should do it.
Doug
ASKER
Thanks for your posting - I'd gove you 100000 points if i could. I'd change the 2nd router's ip, but i'm on an MPLLS network where the ips are assigned by the provider.
Main Office=
Front-End IPs: Level 3 interface: 192.168.0.1/30
Customer interface: 192.168.0.2/30
Branch=
Front-End IPs: Level 3 interface: 192.168.0.9/30
customer interface: 192.168.0.10/30
Back-End IPs: static : 10.86.178.0/24
I'm going to try the config changes you suggested, but tell me your thoughts on this new info.
Thanks
Main Office=
Front-End IPs: Level 3 interface: 192.168.0.1/30
Customer interface: 192.168.0.2/30
Branch=
Front-End IPs: Level 3 interface: 192.168.0.9/30
customer interface: 192.168.0.10/30
Back-End IPs: static : 10.86.178.0/24
I'm going to try the config changes you suggested, but tell me your thoughts on this new info.
Thanks
Your two routers are NOT on a common network. Router B is on the 192.168.0.8/30 network and Router A is on the 192.168.0.0/30 network. Just because you can ping an address doesn't mean they're neighbors.
Since there are routers between your two routers, you will not be able to run RIP over their network unless you create a GRE tunnel between your two routers.
http://www.cisco.com/en/US/tech/tk86/tk89/technologies_configuration_example09186a008011520d.shtml
Otherwise, you'll have to use static routes or the routing protocol that your MPLS provider is using.
Since there are routers between your two routers, you will not be able to run RIP over their network unless you create a GRE tunnel between your two routers.
http://www.cisco.com/en/US/tech/tk86/tk89/technologies_configuration_example09186a008011520d.shtml
Otherwise, you'll have to use static routes or the routing protocol that your MPLS provider is using.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can also try:
router rip
no validate
on both sides, this disables RIPs requirement for the updates to come from a common network. The above GRE tunnel should work as well.
router rip
no validate
on both sides, this disables RIPs requirement for the updates to come from a common network. The above GRE tunnel should work as well.
Hi,
Can you let me know id this has worked for you?
Can you let me know id this has worked for you?