02-12-2021 01:18 AM
Hi, i configurated half a dozen of sites with SG350X switches connected in stack mode.
Every time i close the ring (topology change from chain to ring) the system immediately notify fan acceleration and every switch reach level 5 fan speed:
%STCK SYSL-I-UNITTRP: UNIT ID 2,Trap:%Environment-I-FANS-SPEED-CHNG: FAN'S speed level - 4 changed to level - 5.
%STCK SYSL-I-UNITTRP: UNIT ID 3,Trap:%Environment-I-FANS-SPEED-CHNG: FAN'S speed level - 4 changed to level - 5.
%STCK SYSL-I-UNITTRP: UNIT ID 3,Trap:%Environment-I-FANS-SPEED-CHNG: FAN'S speed level - 3 changed to level - 4.
%STCK SYSL-I-UNITTRP: UNIT ID 2,Trap:%Environment-I-FANS-SPEED-CHNG: FAN'S speed level - 3 changed to level - 4.
%STCK SYSL-I-UNITTRP: UNIT ID 2,Trap:%Environment-I-FANS-SPEED-CHNG: FAN'S speed level - 2 changed to level - 3.
The systems are in native stacking, on Gigabit Ethernet ports XG1 and XG2, firmware 2.5.5.47
Is that an expected behaviour?
It seems weird to me, because the CPU load remains very low.
Thank you in advance for every suggestion.
Solved! Go to Solution.
03-02-2021 02:31 AM
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvq41525/?rfs=iqvred
02-12-2021 02:13 AM
seems to be bug still persists in new version, if you have contract raise a SMB Tac case ?
02-12-2021 02:58 AM
Thanks Balaji, i had read the post you linked but i hadn't figured out that the problem was due to the same reason.
03-02-2021 02:31 AM
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvq41525/?rfs=iqvred
03-02-2021 05:44 AM
Just to sum-up the behavour:
Setup:
Once the second stack link is connected and activated:
Immediately after disconnection of one of stack links:
Reverting back to 2.4.5.71 version restores normal working state with having both stack links active and FAN speed at level 1.
What I dont understand is whether FAN speed is just related to increased temperature (+15C) on PHY sensor (to 78C value) (but it shouldnt be as we are not hitting warning (95) or critircal (98) threshold), or it simply relates to fact that second 10G interface was activated...
Unfortunately original bugreport CSCvq41525 is closed with workaround about reverting back to 2.4.x. branch, but no info about plans for fixing in future releases.
For time being the only recommendation for similar setups is to keep your software updated to latest version of 2.4.x.x branch.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide