IP Routing

[rob1456657]

Hoping someone can provide some clarity here.

OK, so here is where I am at with this configuration.

• 3750 – VTP Server (VLANs 4, 7, and 50) – VTP Domain (MDC)
• 9200 – VTP Client (VLANs 4, 7, and 50) – VTP Domain (MDC)
• 9300 – VTP Server (VLANS 601-603) – VTP Domain (NEWMDC)

I manually added the VLANS from each side to the other side, so basically, both VTP Servers have VLANs 4, 7, 50, and 601-603.

I have a fiber connection between the 9200 and 9300 which is a trunk. I successfully configured a port on the 9200 for VLAN 603 and the client connected to that port got a DHCP IP from the DHCP server on VLAN 603.

When I check the mac address-table on bot the 9200 and 9300 I can see devices in all the VLANS, and CDP Neighbors shows me the switches on either side.

However, my problem is the 3750 is the router for our original network, the 9300 is the router for the new network. If I add a static route for the interface on VLAN601 on the 3750 it does not work ( I am unable to ping), and vice versa on the 9300.

Examples:

3750 -

ip route 10.60.1.0 255.255.255.0 192.168.50.2 (This is the 9200 with the fiber connection)

9300 -

ip route 192.168.50.0 255.255.255.0 192.168.50.2 (This is the 9200 with the fiber connection)

I also attempted to point the subnet to the VLAN interface on either side. (i.e., 10.60.1.1 or 192.168.50.1)

Is this incorrect, or how should I go about this?

[Georg Pauwen]

Hello,

post a schematic drawing of your topology, as well as the running configurations of all three switches.

[paul driver]

Hello

---

@rob1456657 wrote:
However, my problem is the 3750 is the router for our original network, the 9300 is the router for the new network. If I add a static route for the interface on VLAN601 on the 3750 it does not work ( I am unable to ping), and vice versa on the 9300.

---

I assume you are in the process of a lan migration?
You cannot have these two switchs routing for the same vlan, one of the other unless that is you have some FHRP(hsrp,vrrp,glbp) between them, which you dont mention in your OP

[rob1456657]

Sorry for the confusion, the two switches are not routing for the same VLANs, but separate VLANs.

Both Switches know about all the VLANs (Manually configured).

The 3750 routes only for VLANs 4, 7, and 50 (192.168.50.x). (VTP Domain – MDC)

The 9300 routes only for VLANs 601-603 (10.60.x.x). (VTP Domain – NEWMDC)

This is not a LAN Migration, both sides will remain, but we need to marry the two so we can get to the 10.60.x from the 192.168.50.x and vice versa.

Attached I put a simple topology for the visual look and attached the 3 configs for each device.

[rob1456657]

Hi everyone, just wanted to let everyone know where I am at with the config.

Our goal has changed since we are now looking to reduce a few things. For one the two sides have their own internet connections, and we are looking to reduce the internet connectivity at the old network in the future. For now, we are making use of both internet connections.

In the interim here is what I have done.

I configured VLAN interfaces on the 9200 and 9300 for the networks I needed. I then configured static routes on the 3750 for the 10.60.x.x network that lives on the 9300 via the 9200 connected VLANs. By creating the VLAN interfaces on the 9200 and 9300 they become connected routes making routing possible between the two sides.

This permits access to both locations via the 9200 trunks and allows us to continue to use the internet connections at each building. Access between the two sides works flawlessly, and I have full access to the VLANs on either side.

Our future configuration will be to move the 192.168.50.x VLAN interfaces to the 9300, remove the internet connection from the old building and all internet access occurs from the 9300 side. I can then remove IP routing from the 3750 and allow the 9300 to be the core router for the entire campus.