2507 Hub problem

[Mforkash]

Hi all,

I really hope someone can help me with this. I have 2 Cisco 2507's connected back to back, and a Catalyst 1924 switch connected to one of the routers through the hub.

RouterA: Ethernet0 IP 192.168.1.1 255.255.255.0
Serial0 IP 192.168.2.1 255.255.255.0

RouterB: Serial0 IP 192.168.3.1 255.255.255.0
Ethernet0 IP 192.168.4.1 255.255.255.0

Catalyst IP 192.168.4.2 255.255.255.0

RouterA and B are set up and communicating perfectly via a DTE/DCE cable with PPP encapsulation.

From the switch, I can ping either Ethernet0 address by connecting directly to either hub, but cannot ping either Serial0 address, nor obviously get over the DCE/DTE to the remote network.

From either of the routers, I can ping the local ethernet, serial and remote serial but not the remote ethernet.

Can someone tell me what I'm not doing right?

Thanks in advance.

Mike

 

[routerman]

Mike,

From your description this sounds like a missing default gateway on the Cat. When you ping from the Cat it will find the local Ethernet port by ARP, but to get to another IP sub-net it needs to have the default gateway set to point to its local router Ethernet interface.

 

[Mforkash]

This clears up one piece of the problem. I plugged the Catalyst into the other router and forgot to change it back to 192.168.4.1.

Now I can ping both local interfaces from the Catalyst (3.1 and 4.1) but have no luck pinging the remote ethernet or serial (1.1 and 2.1).

 

[routerman]

Router A and B WAN link are on different Ip subnets.

Set them up this way:
RouterA: Ethernet0 IP 192.168.1.1 255.255.255.0
Serial0 IP 192.168.2.1 255.255.255.0

RouterB: Serial0 IP 192.168.2.2 255.255.255.0
Ethernet0 IP 192.168.4.1 255.255.255.0

Then check the switch, if you go into the switch management do you have the default gateway set to 192.168.4.1.


Finally check the IP route table in router A , do you see network 192.168.4.0? If not you'll need to add a static route in this router,
ip route 192.168.4.0 255.255.255.0 192.168.2.2

Connect the cat to router B lan port and it should work.

Just one other point, do you have a connection into routerA Ethernet?, if not them the interface will be down, you cannot ping it. You can force the interface into the up state by adding the command no keepalive to the interface.

 

[Mforkash]

...and Routerman saves the day again.

I added a static route on both routers covering the respective remote ethernet addresses and it works flawlessly.

Thank you from the bottom of my heart. Also, thanks for the heads up on the hub ports being down. I did have my Netgear FVS318 plugged in to RouterA, so there was activity, although I can't ping the Netgear. That's a problem for later though.

I guess I can see the command usage a thousand times in theory, but in actual practice it sticks (hopefully).

Now if I could get you to take my CCNA test for me ;-)

Seriously - thanks again.