Traceroute works on one port only (Summit x440-24t)

[Sangeeta_Ghanga]

I am creating a local network (not connected to the internet or another switch) with an extreme summit x440-24t switch. There are 3 devices connected to the switch, for some reason I can only ping one of the devices from the other 2 but the switch is not able to see the other 2 devices either. Below is the log, I setup a default vlan , added all ports and setup dhcp with a default gateway, what am I missing? (note - some of the commands I used to setup vr-default vlan and mgmt ipadress have not been captured)

* X440-24t.11 # configure vlan Default add ports 1-24 untagged

* X440-24t.9 # show vlan
-----------------------------------------------------------------------------------------------
Name VID Protocol Addr Flags Proto Ports Virtual
Active router
/Total
-----------------------------------------------------------------------------------------------
Default 1 169.254.200.10 /24 ------------T---------------- ANY 3 /24 VR-Default
Mgmt 4095 169.254.200.20 /24 ----------------------------- ANY 0 /1 VR-Mgmt
-----------------------------------------------------------------------------------------------

Total number of VLAN(s) : 2
* X440-24t.10 # enable dhcp ports 1-24 vlan Default
* X440-24t.11 # configure vlan Default dhcp-address-range 169.254.200.50 - 169.254.200.99
* X440-24t.12 # configure vlan Default dhcp-options default-gateway 169.254.200.30
* X440-24t.13 # configure vlan Default dhcp-options dns-server 169.254.200.40
* X440-24t.14 # traceroute 169.254.200.50
traceroute to 169.254.200.50, 30 hops max
1 169.254.200.50 3 ms 1 ms 6 ms

--- Packet Response/Error Flags ---
(*) No response, (!N) ICMP network unreachable, (!H) ICMP host unreachable,
(!P) ICMP protocol unreachable, (!F) ICMP fragmentation needed,
(!S) ICMP source route failed, (!u) Transmit error, network unreachable,
(!f) Transmit error, fragmentation needed, (!t) General transmit error
* X440-24t.15 # traceroute 169.254.200.51
traceroute to 169.254.200.51, 30 hops max
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

--- Packet Response/Error Flags ---
(*) No response, (!N) ICMP network unreachable, (!H) ICMP host unreachable,
(!P) ICMP protocol unreachable, (!F) ICMP fragmentation needed,
(!S) ICMP source route failed, (!u) Transmit error, network unreachable,
(!f) Transmit error, fragmentation needed, (!t) General transmit error
* X440-24t.16 # traceroute 169.254.200.52
traceroute to 169.254.200.52, 30 hops max
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

--- Packet Response/Error Flags ---
(*) No response, (!N) ICMP network unreachable, (!H) ICMP host unreachable,
(!P) ICMP protocol unreachable, (!F) ICMP fragmentation needed,
(!S) ICMP source route failed, (!u) Transmit error, network unreachable,
(!f) Transmit error, fragmentation needed, (!t) General transmit error
* X440-24t.17 # show version
Switch : 800471-00-04 1212G-01300 Rev 4.0 BootROM: 2.0.1.6 IMG: 16.2.5.4
PSU-1 : Internal Power Supply
PSU-2 :

Image : ExtremeXOS version 16.2.5.4 by release-manager
on Fri Jun 29 08:51:42 EDT 2018
BootROM : 2.0.1.6
Diagnostics : 6.4
* X440-24t.18 #

[EtherMAN]

hen you do a ping or traceroute from the switch you must define the VR you are using or it willdefault to the VR-Mgmt vr since you have configured an ip on it. It not connected to your network so pings will fail...

Command would be Ping vr vr-def 169.254.200.xx

You must tell the switch to use the vr-def...

[Robert_Cummins]

169.254.0.0/16 addresses are link-local. I'm pretty sure they are not meant to be routed.... ever.

https://en.wikipedia.org/wiki/Link-local_address

Oh wait, everything is on 169.254.200.0/24; somehow I saw a 169.254.100.? address.

Regardless, I would not use link-local addresses. Additionally, if you are not routing these packets then there is no need to create a gateway (router) or even assign an IP address to the VLAN.

Which interface are you using to try and reach the 169.254.200.5[1,2] addresses? Might it be your mgmt interface? The VLAN interface? Who knows since both are on the same network; most likely the default vr.

Since everything is on the same IP network, the switch should be sending ARP request packets out all interfaces configured in the VLAN. An ARP request is a broadcast packet. If you run tcpdump on any system in the VLAN, you should see the ARP request and you should see the device owning the IP address reply with an ARP reply packet. If you see one (request) without seeing the reply, then the problem is with the target system. If you do not see the ARP request then attach something to the mgmt port and see if the ARP request is going out the mgmt interface.

What does 'show fdb' tell you? What does 'show ip arp' tell you?