cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
234
Views
0
Helpful
2
Replies

InterVLAN routing on CBS 350 and 250

palouis
Level 1
Level 1

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:

  • PAL on VLAN 10 can ping the target on its VLAN10 address is 192.68.10.20 ---> 192.168.10.45
  • PAL on VLAN 10 cannot ping the target on ist VLAN1 address ie 192.68.10.20 xxxxx 192.168.1.45
  • HAL on VLAN1 can ping the target on its VLAN10 address is 192.68.1.20 ---> 192.168.1.45
  • HAL on VLAN 10 cannot ping the target on ist VLAN1 address ie 192.68.10.20 xxxxx 192.168.1.45

It gets weirder:

  • HAL on VLAN1 can ping the the local switch on both 192.168.1.253 and 192.168.10.253 as well as the upstream switch on 192.168.1.254 and 192.168.10.254
  • PAL on VLAN10 cannot ping the the local switch on both 192.168.1.253 and 192.168.10.253 and is cannot ping the upstream switch on either 192.168.1.254 or 192.168.10.254

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

2 Replies 2

palouis
Level 1
Level 1

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#

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.