Cannot ping to VLAN interfaces on N4032

Question

Hi there, I was hoping you could help me figure out an issue. I'm using N4032 stack as a core switch with all the vlans and default gateways configured. I've enabled ip routing on the switch and set the route to the backbone router. So the connection is as follows: n4032 ---------------- backbone_routerte1/0/19                  ether1 When I ping to the backbone router uplink interface on the switch (interface vlan 20) I am able to get a reply. However if I ping the management interface (interface vlan 280) I get TTL expired in transit message. --------------------------------------------------------------- Pinging 10.10.20.2 with 32 bytes of data:Reply from 10.10.20.2: bytes=32 time=3ms TTL=63Reply from 10.10.20.2: bytes=32 time=3ms TTL=63Reply from 10.10.20.2: bytes=32 time=4ms TTL=63Reply from 10.10.20.2: bytes=32 time=3ms TTL=63 Ping statistics for 10.10.20.2:Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:Minimum = 3ms, Maximum = 4ms, Average = 3ms C:\Users\muhannad>ping 192.168.28.1 Pinging 192.168.28.1 with 32 bytes of data:Reply from 10.10.20.2: TTL expired in transit.Reply from 10.10.20.2: TTL expired in transit.Reply from 10.10.20.2: TTL expired in transit.Reply from 10.10.20.2: TTL expired in transit. Ping statistics for 192.168.28.1:Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), --------------------------------------------------------------- I tested connecting a PC to te1/0/1 port on the switch setting it to an access vlan 280 and I am able to ping the PC, which indicates that inter-vlan routing is working. So any ideas as to why I can't ping the vlan interfaces on the switch except for one? --------------------------------------------------------------- Here's a snippet of the configuration if you need to refer: dr-coresw1#show running-config !Current Configuration:!System Description 'Dell Networking N4032, 6.3.2.7, Linux 3.7.10-20383c08'!System Software Version 6.3.2.7!Cut-through mode is configured as disabled!configurevlan 20,280,290exitvlan 20name 'v20-backbone-dr'exitvlan 280name 'v280-mgmt-dr'exitvlan 290name 'v290-lan-dr'exitip telnet server disablehostname 'dr-coresw1'slot 1/0 2 ! Dell Networking N4032slot 1/1 6 ! Dell QSFP Cardslot 2/0 2 ! Dell Networking N4032slot 2/1 6 ! Dell QSFP Cardsntp unicast client enablesntp server 'pool.ntp.org'clock timezone 5 minutes 0 zone 'MVT'stackmember 1 1 ! N4032member 2 1 ! N4032exitip name-server '8.8.8.8'system jumbo mtu 9216ip routinginterface vlan 1exitinterface vlan 20ip address 10.10.20.2 255.255.255.252exitinterface vlan 280ip address 192.168.28.1 255.255.255.0exitinterface vlan 290ip address 192.168.29.1 255.255.255.0exitip route 0.0.0.0 0.0.0.0 10.10.20.1ip ssh serverspanning-tree priority 8192application install SupportAssist auto-restart start-on-boot!interface Te1/0/1description 'link to computer system'spanning-tree portfastswitchport access vlan 280exit!interface Te1/0/2spanning-tree portfastswitchport mode trunkexit! --- snipped ---- interface Te1/0/19description 'uplink to backbone router'spanning-tree portfastswitchport access vlan 20exit! --- snipped ---

m_muhannad · Answer

I'm not sure what happened, but right now everything seems to be working fine. I am able to ping all the vlan interfaces on the switch. :emotion-42:

If you can let me know what could have been the cause that would be great. Otherwise you can mark the question answered.

Thanks.

m_muhannad · Answer

That might be the case. I had not connected any clients in the VLAN at the time since it was just configured. I was running ping test to the VLAN interface to make sure connectivity had been established. I decided to place the clients in their VLAN anyways since the routing was working fine.

Will try to test it out in a another deployment and see if the issue repeats. Thanks for the reply Daniel. Have a good day.

Networking General

Was this post helpful?