03-25-2025 02:07 AM - edited 03-25-2025 02:07 AM
Hi All,
My journey through VLAN hell continues, and I've progressed to the point where I've isolated things and realised I must be making some fundamental mistake. Can anyone give me any advice?
Attached is my testing setup. Two switches connected by a trunk, however my testing is all on the 250 switch. All test systems are General switch ports, l with VLAN1 untagged and VLAN10 tagged where needed.
Here's what I am seeing:
It gets weirder:
Clearly there is something amiss with the VLAN10 config but I'm unable to find the issue.
I've attached a sanitised copy of the running-config.
I'm losing my mind after 10 days of this ...
Any help really appreciated.
Paul
03-25-2025 02:19 AM
Just to add some more info .. the switch itself can't ping target on 192.168.10.45 .. see below from CLI I also added show ip routes
DSW01#ping 192.168.10.45
Pinging 192.168.10.45 with 18 bytes of data:
PING: no reply from 192.168.10.45
PING: timeout
PING: no reply from 192.168.10.45
PING: timeout
PING: no reply from 192.168.10.45
PING: timeout
PING: no reply from 192.168.10.45
PING: timeout
----192.168.10.45 PING Statistics----
4 packets transmitted, 0 packets received, 100% packet loss
DSW01#ping 192.168.1.45
Pinging 192.168.1.45 with 18 bytes of data:
18 bytes from 192.168.1.45: icmp_seq=1. time=0 ms
18 bytes from 192.168.1.45: icmp_seq=2. time=0 ms
18 bytes from 192.168.1.45: icmp_seq=3. time=0 ms
18 bytes from 192.168.1.45: icmp_seq=4. time=0 ms
----192.168.1.45 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
DSW01#show ip route
Maximum Parallel Paths: 1 (1 after reset)
IP Forwarding: enabled
Codes: > - best, C - connected, S - static
C 192.168.1.0/24 is directly connected, vlan 1
C 192.168.10.0/24 is directly connected, vlan 10
DSW01#
03-25-2025 02:35 AM - edited 03-25-2025 02:36 AM
Update - I got things working by changed from switcher General to Access, then once I realised that I went back to General but set the correct VLAN as the Access (untagged) and PVID then it works.
I need to learn more about Access vs General.
I was always of the view that you wanted tagged traffic to flow not untagged.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide