I have 3550 which has a Gig access link connection to core switch 2(6513) on vlan253.
It also has another access-link connection to a 3524 switch on vlan 230.
3550 switch has a default gateway 192.168.253.1 (core 2) and no SVI for vlan230.
Core 2 has route to 192.168.230.0 network. Core 2 does not any SVI for 230
This is how the network looks
Host ---->3550(No SVi for vlan230) ------> 3524(NO SVI for valn 230)-------> 3750(192.168.230.5) --------> content service switch
Q1 How is traffic going to core 2 and ahead when there is no SVI on both Core 2 and 3550 when i do a trace to vlan 230 network?
I did a trace for 192.168.230.1 (vlan 230)and hits the core 2 and goes ahead . 3550 also has an access connection in vlan 230 to 3524.
The dafult gateway on 3550 is 192.168.253.1 (core 2) address.
Q2.why is traffic not going from 3550 to 3524 when i do a trace route to vlan 230 network
am attaching the config files of 3550,3524 and 3950 .
The above wouldn't work because of what we discussed earlier ie. you cannot route to the same vlan over a link that is not in that vlan.
Q1 why is this not possible as core 2 does not have vlan 230
host wii send packet for vlan 230 on 3550 it goes to vlan 230 SVI and then sent thru L2 access connection of vlan 253 to core 2
when packet arrives in vlan 253 at core it can route it to 192.168.230.0 network which sits on core 2. this is waht your below post said earlier.
As per your earlier post you stated the following
SW1 <--- VLAN 253 ----> SW2
SW1 has vlan 10
SW2 has vlan 11
for any clients in vlan 10 to communicate with clients in vlan 11 you would need to route them across the vlan 253 link.
Because it's not the same. In my example the vlans are different so traffic on SW1 with a destination IP of vlan 11 would be routed across the vlan 253 link.
In your example traffic on 3550 with a destination IP of vlan 230 is simply routed onto vlan 230 ie. you are trying to the to the same vlan at either end - vlan 230. In the example i gave the vlans at either end are not the same hence you can route to get there.
Q2. Also when i turned ip routing ON on 3550 from my workstation i lost connectivity to the 3550. As a solution i logged into core 2 and telneted to 3550 from core 2 which worked fine. Can anybody please explain why this happened?
This happened because when you turn on routing the "default-gateway" configured on the 3550 is no longer used. You need to replace the following line in your config
ip default-gateway 192.168.253.1
ip route 0.0.0.0 0.0.0.0 192.168.253.1
Thanks for the diagram. I have had a look and from the diagram there should be no reason why the server cannot get access on the 3550. Are you sure when you connected the server into the 3550 that the port you connected it into was allocated to vlan 230 eg.
int fa0/10 <-- this is the server port
switchport mode access
switchport access vlan 230