- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
first some information about the Intel Modular Server system this issue is about:
Chassis: MFSYS25
Compute Modules: 3 x MFS5000SI
Firmware: 5.5.100.20091202.19584
Now our issue:
We upgraded the system to the mentioned firmware. Now we want to add another compute module (MFS5520VI). The CMM notices a new compute module and seems to start a firmware update. But for 30 minutes and more nothing happens. Also the new compute module seems to be classified as a MFS5000SI compute module (only 2 USB slots shown in chassis front dashboard).
Now my question:
If a firmware update is applied to a system, are just the needed parts of the firmware uploaded and updated? Do we have to apply the firmware update again in order to install the new compute module?
Many thanks for any suggests solving this issue.
Marco
- Tags:
- Modules
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't think it's necessary to apply the firmware to the chassis again. If you go to the Firmware page, what's the status of the new server? Also you may want to update to FW 6.5.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Edward,
thanks for your quick answer. You are right, I do not have to apply the firmware to the chassis again.
Speaking to our reseller this morning we noticed, that the new compute module is a MFS5520VIBR (not MFS5520VI as I wrote down). According to that I am applying firmware 6.1 (6.5 is not tested by our reseller yet) at the moment. I will post the result later on.
Marco.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, I have similar problem.... My SB5000.86B.10.10.0048 won't update to 6.0.100.20100317.20104 and I can't back to older firmware
Any ideas ???? :/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Do you mean your CMM firmware is already 6.0.100.20100317.20104 but your MFS5000SI BIOS version is still SB5000.86B.10.10.0048? What happens when you power on the MFS5000SI? Connect a monitor to see the output if possible, but don't press any key until the update completes... Also, grab a screenshot of the firmware page as well as the system diagnostic file would help...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monitor is sleeping .... After put in i get request "Updates Pending power on required" (Photo 0.png) and then I get "Updates Pending reboot required" (Photo 1.png). Server 1 is working without any problem :/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It seems the MFS5000SI failed POST... If possible please check if CPU and memory works on a known good server... Also check the events and see if there're any errors related.
Has the compute module ever worked before? Or you just encounter this after applying the new firmware?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When I switch force update jumper to enable Module starts normaly, so I can boot systems etc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
First the date/time seems not set correctly on your CMM. The latest log I saw is 3/27/2010.
Now for Server 2, it seems that it was removed from the chassis during the process of BMC update, which may cause BMC corruption:
1992010-03-25 16:14:26BMC Firmware Update StartedServer 2 InfoSystemFirmware Update Started: BMC BMC Firmware Update Started3408System Array ( [entity] => BMC ) 2022010-03-25 16:16:44Server 2 removedServer 2 InfoIPMIA server was removed from server slot 2.Server removedReplace the ServerServer 2 removed1000System Array ( [number] => 2 )s:68:"Raw IPMI (hex): Gen:2000 Num:60 Type:c0 EDir:ef ED1:04 ED2:ff ED3:ff";There are also FRB2 watchdog and processor error logged on Server 2. It may relate to the board, BIOS or CPU.
Then after an insertion of Server 2 at CMM timestamp 2010-03-26 16:46:27, Server 2 started generating "Component Unfit" error.
Please set correct date/time on the CMM and reboot. Once the CMM is up and running, insert Server 2 and see what happens. If you still get the "Component Unfit" error, try the jumpers one at a time: CMOS CLR, BMC Force Update, BIOS Bank Select. Move only one jumper and leave the others in default position.
If issue can't be resolved then you may need to get the server replaced.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page