I have a 3620 directly connected to a 2611, all connections are up and running correctly and each router can ping the directly connected interface of its neighbour. The problem I have is that I cannot ping from a client on the LAN side of the 2611 to the 3620. RIP is set up, though the 3620 uses RIP V2. Default routing is also set up on each router to allow access to the internet.
I can ping from a client node of 192.168.0.101 to e0/1 192.168.0.100 and also ping to e0/0 22.214.171.124 but thats it! I cannot ping on to the next hop of 3620 e1/3 192.168.100 even though if I ping from the 2611 router CLI I can ping the 3620 e1/3 192.168.100. What gives?
It looks like you're right. I did a show ip route 192.168.0.101 and its not in the routing table. The 2611 is using an old IOS so I'll have to update the image. I had hoped that RIP V2 would be backward compatible, obviously not though!
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...