Native IOS, right?
(create vlan in layer 2)
(create Layer 3 interface)
interface vlan 2
ip address 10.10.10.1 255.255.255.252
(advertise network in routing protocol)
router eigrp 100
network 10.10.10.0 0.0.0.255
Repeat the same for each vlan. Build it in layer 2, create the routed SVI interface for the vlan, and advertise it under the routing protocol.
Yes, it's using native IOS. Can you please explain further re: create the routed SVI interface for the vlan. Thanks again for your response.
you dont necessarily need a routing protocol like eigrp.
just create vlan interface for each vlan - the IP address you assign to these vlan interfaces should be the default gateway for the hosts on each of those vlan's.
turn on routing on your switch:
You need to create the layer 3/routed interface for the vlan. That is the SVI (switched virtual interface). Just think of that interface as the gateway into and out of your vlan. If a host on the vlan needs to send traffic to another host in another vlan, the traffic will have to be routed out the layer 3/SVI interface. Just think of an ethernet port on a router with all the hosts in that LAN sitting "behind" it.
And yes, turn on ip routing.
And as far as the routing protocol, you dont need it if you are going to route traffic between directly connected hosts, of course. I gave you the eigrp 100 part of the config as just a general approach, with the underlying assumption that you will want other areas of your network and beyond to reach the hosts in your vlans. Hence, the advertisement under a routing protocol. Pretty standard stuff...
As already mentioned "ip routing" would do the trick when multiple SVI or vlan exists in a switch.
While you have to run a routing protocl if you need to communicate with subnets other than this switch e.g. on some other L3 switch or router.