Catalyst 3650g + 2600 router help

[66catalina]

Hello,

  I have a huge network issue that I am hoping someone smarter than me will be able to solve.

I recently lost my configuration when attempting to reset the password for our Cisco 3560g switch, the switch connects

to a Cisco 4506 switch via fiber back to our main office.

I have the switch temporarily routing all traffic to our 4506 by using the default route of 0.0.0.0 0.0.0.0 10.10.10.254

but the same switch is connected to a cisco 2600 router that is on a 10.10.20.0 network and the 3560g is on a

10.0.0.0 network.

Host computers sit on the 10.0.0.0 network, but they need to go to the 10.10.10.0 network for internet, domain, etc

the same computers need to go to the 10.10.10.20 for remote connections and other services.

The address of the 3560g is: 10.0.0.254

The address of the 2600 is 10.10.20.2

When the default route is set to 0.0.0.0 0.0.0.0 10.10.10.254 (4560 switch) domain browsing works perfectly

When the default route is set to 0.0.0.0 0.0.0.0 10.10.20.2 (3560G) switch I can ping any ip address in that range and the address on the other

interface ip adresses on the 2600 (eg. 10.10.30.1 / eth2, 10.10.40.1/ eth3 etc.)

So I know the router is working, and it's configuration hasn't changed at all.

I have tried to weight the routes after adding them both to the configuration, but that doesn't seem to help at all.

The switch connects back to the office via vlan1 (10.10.10.253)

The 2600 is connected to port 1, which belongs to Vlan2 (10.10.20.1)

And client computers sit on ports 2-12 belonging to Vlan10 (10.0.0.240)

So in a nut shell, how would I go about setting it up so the machines on 10.0.0.0 can connect to 10.10.20.0 and 10.10.10.0 and vice versa at the same time? Everything was working fine until I rebooted the switch (3560g), which makes me think the person that configured this before me didn't save the running config to the start up config.

[John Blakley]

If they're internet connections on the 10.10.20.0 subnet, you'll probably need to use policy routing in order to be able to control what goes where. What specifically do you need to allow to go to your 10.10.20.0 subnet?

HTH,

John

[John Blakley · Accepted solution]

I reread this:

When the default route is set to 0.0.0.0 0.0.0.0 10.10.10.254 (4560 switch) domain browsing works perfectly

When  the default route is set to 0.0.0.0 0.0.0.0 10.10.20.2 (3560G) switch I  can ping any ip address in that range and the address on the other

interface ip adresses on the 2600 (eg. 10.10.30.1 / eth2, 10.10.40.1/ eth3 etc.)

On the switch, you could do 3 static routes:

ip route 10.10.10.0 255.255.255.0 10.10.10.254

ip route 10.10.0.0 255.255.0.0 10.10.20.2

ip route 0.0.0.0 0.0.0.0 10.10.10.254

The 2nd static route should cover your 10.10.30.x and 10.10.40.x subnets that you have listed above. You'll need the 1st route because if not, anything going to the 10.10.10.x subnet will try to go to the 10.10.20.2 next hop.

HTH,

John

[66catalina]

You, sir. Are brilliant! Thank you for your help, I did exactly as you described in your second post and it worked flawlessly.

Thank you.

[John Blakley]

Awesome Glad to be of some help!