[cisco-voip] FYI: FN - 63255 - MCS-7815-I2 and MCS-7825-I2, BIOS error prevents a system from booting if rebooted after October 1, 2009
Ryan Ratliff
rratliff at cisco.com
Mon Nov 2 10:05:50 EST 2009
Sounds like an upgrade via the CLI is the way to go. I'm not sure why
your OS page wouldn't load with the date reverted though, that's a bit
odd.
-Ryan
On Nov 2, 2009, at 9:52 AM, Anthony Kouloglou wrote:
Hi all,
unfortunately,
i set the time back and then booted.
Then i flashed the BIOS but as soon as the 5.1.3f started, it
downgraded the BIOS back to 1.43!!
No i am thinking of rebuilding using a backup file that i have.
The backup is from 5.1.3f. Shall i install it on the 5.1.3f fresh
installation or the 5.1.3g that included the correct BIOS.
Or,try install the 5.1.3g on the publisher via the CLI!!!
Thanks
Anthony
Fuermann, Jason wrote:
>
> Sounds like issues I would expect if time were in the past on the
> server. I agree upgrading the BIOS first will probably save you a
> ton of headaches.
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-
> bounces at puck.nether.net] On Behalf Of Ryan Ratliff
> Sent: Monday, November 02, 2009 8:29 AM
> To: Anthony Kouloglou
> Cc: cisco-voip at puck-nether.net
> Subject: Re: [cisco-voip] FYI: FN - 63255 - MCS-7815-I2 and MCS-7825-
> I2, BIOS error prevents a system from booting if rebooted after
> October 1, 2009
>
> Before you do anything I'd recommend upgrading the BIOS to get the fix
> for the bug and then setting the date back.
>
> -Ryan
>
> On Nov 2, 2009, at 4:28 AM, Anthony Kouloglou wrote:
>
> Well good morning,
> i have not see it coming and now i am facing the bug!
> I run 5.1.3f on a 7825I2 server and got the problem after a reboot on
> friday!
> So, i did what cisco describes, got into BIOS, changed the clock to a
> 2005 day and the server rebooted correctly(?)
> 1.I can navigate to the CCM administration page
> 2. i can access the cli
>
> but,
> 3.when i navigate to the OS administration, i enter username password
> and it does nothing!!
> 4. also, in the serviceability web page, there are 2 columns missing!!
> Start time and UP-time!!
>
> What can i do now?
> Shall i proceed to the 5.1.3g upgrade through the CLI or shall i
> install my cucm from scratch?
>
> Thanks and kind regards,
> Anthony
>
> Erick Bergquist wrote:
>
>> FYI,
>>
>> Update on this. Working with TAC on this and the MCS-7815-I2 server
>> is
>> not effected by this issue, and Cisco is in process of updating the
>> field notice with corrections and more information about the fixes
>> for
>> the various applications.
>>
>> On Fri, Sep 18, 2009 at 12:37 PM, Erick Bergquist
>> <erickbee at gmail.com> wrote:
>>
>>
>>> Does anyone know what version of CER 7.x has the IBM 1.45 BIOS to
>>> fix
>>> this issue?
>>>
>>> I ran the newest FWUCD 2.3(1) on a effected IBM Server and it
>>> updated
>>> the BIOS from 1.4(3) to version 1.4(5) but when CER booted up it had
>>> forced the BIOS to downgrade back to 1.4(3) and rebooted
>>> automatically
>>> like part of the documentation states for this issue.
>>>
>>> I have a TAC Case open. It would be nice if the readme the Field
>>> Notice links to doesn't have the two conflicting sections and also
>>> have something in the field notice so that if you're on a Linux
>>> product that you don't need the firmware CD but you need to upgrade
>>> your CER/CUCM/etc to whatever version of CER/CUCM/etc has the new
>>> BIOS
>>> with fix for this problem.
>>>
>>>
>>> On Wed, Sep 16, 2009 at 4:40 PM, Erick Bergquist
>>> <erickbee at gmail.com> wrote:
>>>
>>>
>>>> Has anyone applied this to a IBM server yet running Linux versions
>>>> of software?
>>>>
>>>> I have a CER 7.x server I'm needing to apply this to, and have the
>>>> CD
>>>> but the docs are not clear in some spots and just wanted some
>>>> clarification.
>>>>
>>>> Under Section 3, the scope section...
>>>>
>>>> 3.5.5 CRITICAL NOTE - This update may NOT be applied to any Linux
>>>> based products.
>>>> If Linux users attempt the upgrade the BIOS,
>>>> the BIOS will be
>>>> downgraded after a subsequent reboot. Linux users should
>>>> reference
>>>> the defect CSCta43460 in bug
>>>> toolkit to find the appropriate version to
>>>> upgrade to that contains the fix.
>>>>
>>>>
>>>> But under Section 2.0 for Resolved Caveats it has the following,
>>>> which
>>>> indicates the above issue is fixed?
>>>>
>>>> Note: If Linux users attempt to use the FWUCD to upgrade the BIOS,
>>>> the
>>>> BIOS will be downgraded after a subsequent reboot. Linux users
>>>> should
>>>> reference CSCta43460 in bug toolkit to find the appropriate
>>>> version to
>>>> upgrade to.
>>>>
>>>> Erick
>>>>
>>>> On Tue, Sep 8, 2009 at 9:54 AM, Wes Sisk <wsisk at cisco.com> wrote:
>>>>
>>>>
>>>>> <snip>
>>>>> Field Notices-Voice and Unified Communications-09/05/2009 09:25
>>>>> GMT-09/06/2009 07:30 GMT
>>>>>
>>>>> Title: Field Notice: FN - 63255 - MCS-7815-I2 and MCS-7825-I2,
>>>>> BIOS error
>>>>> prevents a system from booting if rebooted after October 1, 2009
>>>>> [Cisco
>>>>> 7800 Series Media Convergence Servers]
>>>>> Url: http://www.cisco.com/en/US/ts/fn/632/fn63255.html
>>>>> Description: A defect in the HostRAID BIOS 2106 (included with
>>>>> System BIOS
>>>>> version 1.42 and 1.43) will prevent a server from booting
>>>>> successfully if
>>>>> the server is rebooted after October 1, 2009. This is caused by a
>>>>> defect in
>>>>> the IBM BIOS and is documented in IBM RETAIN Tip: H182636
>>>>> Date: 2009-09-04 06:55:21.0
>>>>> </snip>
>>>>>
>>>>> Anyone running IBM servers make certain you are updated before
>>>>> Oct 1.
>>>>>
>>>>> /Wes
>>>>> _______________________________________________
>>>>> cisco-voip mailing list
>>>>> cisco-voip at puck.nether.net
>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>
>>>>>
>>>>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091102/cd83bc99/attachment.html>
More information about the cisco-voip
mailing list