Well, it's kind of a beefy one for sureThank you! adding a 330µF cap removed the whining noise.
BTW, is that an 122K? Nice find!
Well, it's kind of a beefy one for sureThank you! adding a 330µF cap removed the whining noise.
This is it! This is exactly the problem I'm having with my 6450-48 non PoE. The sound is amplified much more once the case lid is on and that noise is maddening.I'm also having the same problem as noise850 with the switch stuck in high speed fan mode...There is also some kind of whining noise running in low. It may be present at high too just non audible when the fans are a bit louder.
Enhancements in FastIron 08.0.30u
FastIron 08.0.30u release contains defect fixes. There are no enhancements in this release.
Power supply 1 detected in standby mode.
Power supply 2 detected.
Power supply 2 detected.
Power supply 2 is up.
PoE: Stack unit 1 Power supply 2 with 748000 mwatts capacity is up
PoE Info: Adding new 55V capacity of 748000 mW, total capacity is 748000, total free capacity is 748000
PoE Info: PoE module 1 of Unit 1 on ports 1/1/1 to 1/1/48 detected. Initializing....
PoE Event Trace Log Buffer for 2000 log entries allocated
PoE Event Trace Logging enabled...
lost arbitration, dev=50
i2c controller reset, dev=50
lost arbitration, dev=50
i2c controller reset, dev=50
lost arbitration, dev=50
i2c controller reset, dev=50
lost arbitration, dev=50
i2c controller reset, dev=50
lost arbitration, dev=50
i2c controller reset, dev=50
M:9 L:0 - PS EEPROM Offset Read: i2c cmd failed, i2c addr 0x50 error 4, ps 1
------------------------------------------------------------------
lost arbitration, dev=50
i2c controller reset, dev=50
PoE Info: PoE module 1 of Unit 1 initialization is done.
I'm not sure but I'd say no, that's not the expected behaviour. It seems it struggles to read the PoE module EEPROM; can you enable power and confirm it is powering up some PD?Is the "i2c cmd failed message" normal?
Below are some tips when you are in the market for a rack in US.Next step - it's finally time to pull the trigger on a rack cabinet...!
Totally off topic, but recently got a full depth rack and actually couldn't fit any of my SM Rails in it- Also make sure it is full depth (1070mm) or close to it. (Speaking from experience)
I have that problem with the rack I am trying to give away.. fits my SM crap (before I got rid of the SM stuff, but all the DL 360 and 380s are too long.Totally off topic, but recently got a full depth rack and actually couldn't fit any of my SM Rails in it![]()
I have short and regular ones, but none have the required length![]()
@hmw
Download the offical release notes to see closed defects and known issues.
Yeah downloaded them and that’s all that the official release notes sayCode:Enhancements in FastIron 08.0.30u FastIron 08.0.30u release contains defect fixes. There are no enhancements in this release.
Look again. I made the same mistake in the past. For a lot of enterprise release notes enhancements, fixes, and known issues are in separate sections. That entry you quoted is on page 6 (of 226). Scroll up 2 pages before that and you will see "Closed defects with code changes in Release 08.0.30u" on page 29 and "Known Issues in Release 08.0.30u" on page 34.Yeah downloaded them and that’s all that the official release notes say updated anyways![]()
Look again. I made the same mistake in the past. For a lot of enterprise release notes enhancements, fixes, and known issues are in separate sections. That entry you quoted is on page 6 (of 226). Scroll up 2 pages before that and you will see "Closed defects with code changes in Release 08.0.30u" on page 29 and "Known Issues in Release 08.0.30u" on page 34.
Most of the times you can adjust the posts, moving them forward or backward untill you find a spot where all the rails align and can snap into the mounting holes. It's fine if the tail of the server is behind the rear post, if you need it.I have that problem with the rack I am trying to give away.. fits my SM crap (before I got rid of the SM stuff, but all the DL 360 and 380s are too long.
What do you mean? If you don't define any VE on a VLAN it will just act as a "pure" L2 device.Good day all, new here, so my apologies if I’m posting in the wrong location ...
Question, after following these instructions, all went well, however the switch is now in router mode, and I can’t figure out for the life of me how to get it back to switch mode
Any help would be great !
The CLI wizards here will probably scoff at my simple approach of using the Web administrative interface for doing this. But I'm pretty sure you can fix this by loading the Web GUI and insuring 'L2 Switching' is enabled on the General System Configuration page, and 'Route Only' is disabled on its 'Advanced Settings' page.Good day all, new here, so my apologies if I’m posting in the wrong location ...
Question, after following these instructions, all went well, however the switch is now in router mode, and I can’t figure out for the life of me how to get it back to switch mode
Any help would be great !
THANK YOU !The CLI wizards here will probably scoff at my simple approach of using the Web administrative interface for doing this. But I'm pretty sure you can fix this by loading the Web GUI and insuring 'L2 Switching' is enabled on the General System Configuration page, and 'Route Only' is disabled on its 'Advanced Settings' page.View attachment 14544
View attachment 14545
The CLI wizards here will probably scoff at my simple approach of using the Web administrative interface for doing this. But I'm pretty sure you can fix this by loading the Web GUI and insuring 'L2 Switching' is enabled on the General System Configuration page, and 'Route Only' is disabled on its 'Advanced Settings' page.View attachment 14544
View attachment 14545