SX3008F V1 switch control loss
Hello.
After 80 days of continuous operation, the SX3008F V1 switch stopped responding to ARP, ICMP, and HTTPS requests, as well as via the console port.
The current firmware is 1.20.0 Build 20231011 Rel.42220.
I had to restart the switch by power.
Now I have updated the firmware to the current version 1.20.3 Build 20250121 Rel.53296.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Not sure what question here.
You mentioned you restarted it. So, did it work after the restart?
Or you mean even after the restart, any features you mentioned still don't work?
What did you do to verify that was not working?
- Copy Link
- Report Inappropriate Content
I mean that after some time the control is lost.
After a power reset the control is returned.
I would like to understand why the problem occurs and whether it is solved in the current firmware version.
- Copy Link
- Report Inappropriate Content
Hi @labynko
Thanks for posting in our business forum.
labynko wrote
I mean that after some time the control is lost.
After a power reset the control is returned.
I would like to understand why the problem occurs and whether it is solved in the current firmware version.
Do a Wireshark on it, as you described, it fails after some time. I cannot judge why based on the given information.
This Wireshark should be done for a long time and when this occurs, you gotta check the packets flow and see the specific protocols like you described. ICMP and ARP.
If ARP is blocked, this means something is extremely wrong in your network.
ARP should never be blocked under any circumstances.
In this situation, you gotta find out what devices could cause this or what IPs are involved at that timestamp when this happens.
- Copy Link
- Report Inappropriate Content
Hi @Clive_A
The switch, among other things, stops communicating via the console port.
The console port must be fault-tolerant.
How do you explain this?
- Copy Link
- Report Inappropriate Content
labynko wrote
Hi @Clive_A
The switch, among other things, stops communicating via the console port.
The console port must be fault-tolerant.
How do you explain this?
Do you rule out that it is not the session time that has been reached?
Without a clue, I don't think I would even try explaining it. I am not obliged.
I asked about your verification so as to learn if there is a misunderstanding.
If you believe it is a firmware issue, then downgrade to the previous one and test again. If this persists, you should consider whether it is your config or environment.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 493
Replies: 6
Voters 0
No one has voted for it yet.
