switch can't ping but everything works

[Milosz Jablonski]

hi guys

weird issue

I have just replaced a 3560 switch with a newer box 3650.

PC-based clients are working fine, can access both local and remote resources over the trunk port. My laptop is also getting online, but...

The new switch cannot be seen on the snmp nor can be managed from the other end via SSH. Doesn't reply to pings
I guess this might be something silly I lost in translation of the config.

so brief summary

I can see as per sh CDP neighbour (4500 box) which gives me IP 192.168.9.221 via DHCP, but cannot ping it and that CDP-4500 can't  ping me either

all ports 1-24 are within vlan 1 and 3,  and trunk allows all vlans 1-4094, active vlans 1&3, native 3

any suggestions are highly appreciated

config (bulk parts of it) below

vtp domain mydomain
vtp mode transparent
authentication mac-move permit
ip subnet-zero
no ip domain-lookup
ip domain-name mydomain
vlan 3
name VOIP

!
ip ssh version 2
!
class-map match-any rtp-stream
match access-group name rtp-stream
!
policy-map voice
class rtp-stream
set dscp ef

interface range FastEthernet0/1-24
switchport mode access
switchport voice vlan 3
switchport port-security maximum 3
switchport port-security
switchport port-security aging time 5
switchport port-security violation restrict
no logging event link-status
no snmp trap link-status
spanning-tree portfast
spanning-tree bpduguard enable

interface GigabitEthernet0/1
description connected to 4500
switchport trunk encapsulation dot1q
switchport mode trunk
mls qos trust dscp
!
interface Vlan1
ip address 192.168.9.245 255.255.255.0
!
ip default-gateway 192.168.9.254
ip classless
no ip http server
no ip http secure-server
!

can't even ping the gateway from the switch console, but can from laptop (windows cmd) connected

any help much appreciated

[Reza Sharifi]

Hi,

Can you try removing "mls qos trust dscp" from the trunk port and test again?

Also, what is the PC's IP that can ping the gateway?

HTH

[Milosz Jablonski]

Thanks Reza for looking into it
192.168.9.221 - IP that my laptop got, will get on site and do it - cant do that remotely as yet...

[chrihussey]

Why is the default gateway IP the same as the VLAN 1 interface on the switch? The switch has only one interface and it isn't configured to perform routing. Shouldn't the default gateway be the 4500 or whatever the default gateway is that is provided by DHCP?

Finally you said the trunk's native VLAN is 3, yet on the 3560 it is 1. I think it is best to have the native VLAN be 1 on both sides since that is where the management interface of the 3560 is.

Hope this helps.

[Milosz Jablonski]

resolved - didn't noticed that the VLAN 1 was shut on L3 thus it worked on L2 wit dhcp etc but once noshut command was issued it worked
thanks

[chrihussey]

Appreciate the update and glad to hear it is working.

BTW, with the default gateway being the same as the VLAN 1 interface I'm not sure you'll be able to access it from anything not on that subnet.

Have a good day

[amikat]

Hi,

Please disregard this post as I have not noticed it has been solved.

Thanks & Regards,

Antonin