x460-48t experience "Packet transmit error"

[Josh_Huynh]

Dealing with this issue past 5 years plus after many calls with TAC, engaged local Extreme SE and still no resolution of the issue.

We have this X460-24t in our lab networks experience "Packet transmit error" every 60 days or less. The only way to get the network back online is to reboot the switch.

When the issue occurred, we can still remote access to the switch by telnet or ssh, ICMP (ping) to VLAN interface(s) IP address response okay from other networks.

Here's the issue,

After login the switch and ping failed at local VLAN interface IP address; it get an error "Packet transmit error".

SVPerf-R5-2_SW1.11 # ping 10.52.0.1
Ping(ICMP) 10.52.0.1: 4 packets, 8 data bytes, interval 1 second(s).
Packet transmit error
Packet transmit error
Packet transmit error
Packet transmit error

--- 10.52.0.1 ping statistics ---
0 packets transmitted, 0 packets received, 0% loss
round-trip min/avg/max = 0/0/0 ms
SVPerf-R5-2_SW1.12 # ping 10.52.16.1
Ping(ICMP) 10.52.16.1: 4 packets, 8 data bytes, interval 1 second(s).
Packet transmit error
Packet transmit error
Packet transmit error
Packet transmit error

Has anyone experience this?

[BrandonC]

Hi Josh,

This looks to be the same issue as described in xos0066921 and the article I linked above. This fix is not included in EXOS 16.1.4.2-patch1-7. Please upgrade to one of the fixed releases as was recommended in the last case you opened for this issue in February.

[BradP]

Hi Josh,

It sounds like the switch needs to be updated then. The versions on the switch don't include the fix. The fix is included in the following versions:

• EXOS 22.3.1
• EXOS 21.1.3.7 Patch 1-7
• EXOS 16.2.3
• EXOS 15.3.5.2 Patch 1-14

The current recommended version for the X460-48t is EXOS 16.2.5.4-patch1-3.

Thank you,
Brad

[BradP]

Hi Josh,

It looks like in the last case created for this, the Support Engineer recommended a code upgrade based on xos0066921. Have you been able to update the switches yet?

Thanks
Brad

[BrandonC]

There is a GTAC Knowledge article created for this as well.

https://extremeportal.force.com/ExtrArticleDetail?n=000013072

[Sushruth_Sathya]

Hi Josh,

Usually when ARP is not resolved for an IP, we see this error. Any number of reasons can cause this - including bugs, network issues, etc. We would need to know the full picture before a cause can be deduced. What is the version of code running on the switch? And is this IP 10.52.16.1 directly connected? Does the same VLAN exist on the switch? Is the ARP resolved correctly during the time of the issue?