18 bytes from 192.168.4.24: icmp_seq=1. time=0 ms 18 bytes from 192.168.4.24: icmp_seq=2. time=0 ms 18 bytes from 192.168.4.24: icmp_seq=3. time=120 ms 18 bytes from 192.168.4.24: icmp_seq=4. time=0 ms
Here is my configuration , with some extraneous config taken from the show run;
no passwords complexity enable
ip domain name nc.rr.com
ip name-server 126.96.36.199 188.8.131.52
ip telnet server
interface vlan 1
ip address 192.168.10.30 255.255.255.0
no ip address dhcp
interface vlan 2
ip address 184.108.40.206 255.255.255.0
interface vlan 3
ip address 220.127.116.11 255.255.255.0
switchport trunk native vlan 2
switchport trunk native vlan 3
ip route 0.0.0.0 0.0.0.0 192.168.10.1
Your configuration looks absolutely good, the differences between your config and mine is, that I left the switch ports in trunk mode rarther than change, as you did the switch ports to access mode.
That absolutely fine.
What I drew from Thomas' question was, that when I were to plug a PC into your switches port 2 or 3 in the case of your configuration, an interface route is created than then allows Layer 3 switching to occur between that VLAN.
In your configuration, when nothing is plugged into switchports 2 for example, you will not be able to ping 192.168.2.22 from a device connected onto VLAN3. When you plug a PC into switch port 2, within a few seconds you will able to ping 192.168.2.22 from a PC plugged into VLAN3.
The reason being, when you make VLAN2 active, by plugging a host into one of it's switch ports, a interface route is created that then allows that network to be reached.
Sx550X, Sx350X, Sx250: PSE will Supply Power to Catalyst PSE Ports
May 31, 2016
June 5, 2017
Configure Remote Network Monitoring (RMON) Events Control Settings on a Switch through the Command Line Interface (CLI)
Remote Network Monitoring (RMON) was developed by the Internet Engineering Task Force (IETF) to support...