inter vlan issue

[Ranjith_Kumar]

core switch 1
vlan 10 -10.2.0.200/16
vlan 0 -10.3.0.2/16

tagged port 23 connected to core switch 2 port 23

access switches:(all access switch is connected to core switch 1)
10.3.0.3
10.3.0.4
10.3.0.5
10.3.0.6

core switch 2
vlan 10 -10.2.0.2/16
vlan 0 -10.3.0.101/16

tagged port 23 connected to core switch 1 port 23

access switches:(all access switch is connected to core switch 1)
10.2.0.3
10.2.0.4
10.2.0.5
10.2.0.6

core switch to core switch communication is ok.

problem is core sw1 not pinging to core sw2 access switch

[Ranjith_Kumar]

any solutions???

[Ranjith_Kumar]

any access switch can able to ping tocore switch,but 10.3.0.0 access switch cant access to 10.2.0.0 access switch

[Tomasz]

Hi Ranjith,

looking at this:

core switch 1
vlan 10 -10.2.0.200/16
vlan 0 -10.3.0.2/16

tagged port 23 connected to core switch 2 port 23

access switches:(all access switch is connected to core switch 1)
10.3.0.3
10.3.0.4
10.3.0.5
10.3.0.6

core switch 2
vlan 10 -10.2.0.2/16
vlan 0 -10.3.0.101/16

tagged port 23 connected to core switch 1 port 23

access switches:(all access switch is connected to core switch 1)
10.2.0.3
10.2.0.4
10.2.0.5
10.2.0.6

I don't get which VLAN ID is for core-core communication.
IMHO it would be good to have point-to-point VLAN between routers with no other ports in that VLAN and with unique addressing (VLAN 101 with IPs 10.10.1.0/30 for instance: 10.10.1.1/30, 10.10.1.2/30).

Core 1 should have its access ports to the access switches (LAN1, let's call those) added to VLAN that is compliant with local address space, ie. 10.3.0.1(/16?) for instance.
Core 2 should have this VLAN with 10.2.0.1(/16?) (let's call its access switches LAN2).
Then you can be sure that the addressing scheme is consistent across the entire network. Having LAN1 addressing on a VLAN at Core 2 router might turn routing tables misleading.

Then, are access switches equipped with IP addressing just for management or do they route? I assume no.

Just to sum up what colleagues wrote above, your both core routers need to have:
a) enable ipforwarding
or enable ipforwarding - for all VLANs you want to route between, here two would be of your interest - local LAN VLAN and core-core VLAN
b) statically od dynamically defined route to a "distant" network (that is not directly connected), for Core 1 it would be conf iproute add 10.2.0.0/16 10.10.1.2 (if you agree with my addressing suggestion for core-core)

Then with your access switches you can either set default route (that's better) or static route that will point to your core router directly attached interface; for example on LAN1 switches it would be conf iproute add default 10.3.0.1 (Core 1 IP for that VLAN).

Please explain your target and directions so we can guide you further.

Hope that helps,
Tomasz

[Eric_Burke]

By default, the switch won't forward/route between vlan's without ipforwarding enabled. The routes alone will net get you between subnets.

[Ranjith_Kumar]

default route is configured on both core switch
SW1
configure iproute add 10.2.0.0 255.255.0.0 10.3.0.221
SW2
configure iproute add 10.3.0.0 255.255.0.0 10.2.0.200