Is this a new configuration setup, or it's been awhile, and it started behaving wrong.
Yes, you can try #no switchport voice detect auto to check if it helps the issue. By the way, the command that you gave on your post is reversed.
If that doesn't help and since you have already updated the firmware, I would suggest to contact support to check on the switch logs to find any configuration issue or any clue that is leading to the vamped utilization.
We have installed the stack 6 months ago, but the issue occurs since 1 month... We recently have installed snom voip so maybe it's related...
I have tested the "no switchport voice detect auto" on lab and after that, I have noticed that the process "voipTask" appears less often... So maybe it's a good clue.
I see in a lot of DELL documentation that this problem has normally been solved for a long time on this switch model (version 4.1.0.6), however, despite the fact that we are up to date, the problem remains
this isn't necessarily a misbehavior as the PowerConnect 8024s do have a pretty weak CPU for the OS to run. Any traffic or control protocol which needs to get processed in software is stressing the CPU. This will add up in a stacked topology as only the master switch does provide control plane intelligence.
As you observed the issue started with the introduction of a VoIP system it probably came with a control protocol or traffic type introduced. There is not much we can do about this but limiting the tasks processed by the switch CPU.
You may try disabling not needed features step by step:
> snooping features like DHCP, IGMP, MLD > DCB, iSCSI features > any IP/VLAN interfaces not needed > STP if not needed (ensure the network is loop-free) > dynamic routing protocols
jonbel
1 Message
0
November 17th, 2022 00:00
Bonjour, j'ai trouvé cela qui y ressemble : https://www.dell.com/support/home/fr-lu/drivers/driversdetails?driverid=xtj1x
DELL-Joey C
Moderator
•
4.1K Posts
0
November 17th, 2022 01:00
Hi @nanoupi42,
Is this a new configuration setup, or it's been awhile, and it started behaving wrong.
Yes, you can try #no switchport voice detect auto to check if it helps the issue. By the way, the command that you gave on your post is reversed.
If that doesn't help and since you have already updated the firmware, I would suggest to contact support to check on the switch logs to find any configuration issue or any clue that is leading to the vamped utilization.
Hello @jonbel,
Apologies, but I can only reply in English. So far, have you tried any troubleshooting to isolate the issue?
nanoupi42
2 Posts
0
November 17th, 2022 08:00
Hi Joey,
Thanks !!
We have installed the stack 6 months ago, but the issue occurs since 1 month... We recently have installed snom voip so maybe it's related...
I have tested the "no switchport voice detect auto" on lab and after that, I have noticed that the process "voipTask" appears less often... So maybe it's a good clue.
I see in a lot of DELL documentation that this problem has normally been solved for a long time on this switch model (version 4.1.0.6), however, despite the fact that we are up to date, the problem remains
DELL-Tim G
3 Apprentice
•
73 Posts
0
November 20th, 2022 07:00
Hello nanoupi42,
this isn't necessarily a misbehavior as the PowerConnect 8024s do have a pretty weak CPU for the OS to run.
Any traffic or control protocol which needs to get processed in software is stressing the CPU.
This will add up in a stacked topology as only the master switch does provide control plane intelligence.
As you observed the issue started with the introduction of a VoIP system
it probably came with a control protocol or traffic type introduced.
There is not much we can do about this but limiting the tasks processed by the switch CPU.
You may try disabling not needed features step by step:
> snooping features like DHCP, IGMP, MLD
> DCB, iSCSI features
> any IP/VLAN interfaces not needed
> STP if not needed (ensure the network is loop-free)
> dynamic routing protocols
Hope this helps a bit.
Tim