Sponsored Content
Full Discussion: Firmware on blade
Operating Systems AIX Firmware on blade Post 302225855 by broecker on Sunday 17th of August 2008 10:41:03 AM
Old 08-17-2008
yes (i saw the date of the posting, but that was my own actual problem), that's nearly all, first should the service-Processor of the blade been updated (web-based), then the image-File is not an ISO-Image but have to be burned with a file-system as single file on a second cd, vt320-Emulation works fine and F7 should start in the submenu the procedure, after that the blade should be configured/reseted webbased.
 

8 More Discussions You Might Find Interesting

1. Solaris

Anyone has problems with new Blade 2500????

Hi guys, I am a new member here. This is my first post. I try to purchase some new Blade 2500 for the company. However, the vendor suggests me to get Blade 2000 instead. The vendor said he has many problems with new Silver Blade 2500's. Has anyone here had simlar experience with blade 2500?... (4 Replies)
Discussion started by: facaizhu
4 Replies

2. Solaris

A1000 Solaris 10 on Blade 1000

I have a SUN Blade 1000 running Solaris 10 and an A1000 array. I know that this combo is not supported by SUN but will it work? The raid manager software is installed and it says that the firmware needs to be upgraded -it is at I think level 2.05 something. I can see all the disks in a... (13 Replies)
Discussion started by: tribbles
13 Replies

3. HP-UX

Help with firmware upgrade on blade BL870c

Hi gurus, I was more on the Sun side and now am getting exposure to the HP-UX side of the world. I have to upgrade firmware on BL870c blade. Can some one point to a url or give procedure to follow as I couldn't find much on the web. Thanks Momin (1 Reply)
Discussion started by: momin
1 Replies

4. Hardware

C-Class Blade storage

Hi, I have got a slot within my C3000 blade enclosure populated with a HP SB40c (StorageWorks). This is essentially a disk array for the blades to access within my C3000 enclosure. I can see from my OA that it is currently powered off. Can anybody suggest what is required in order to get... (0 Replies)
Discussion started by: Duffs22
0 Replies

5. UNIX for Dummies Questions & Answers

SUN BLADE T6340 - which OS ?

Hi, I have server SUN BLADE T6340 and i tried install debian sparc on this machine. Will it work ? In the specification is written only Solaris 10. (4 Replies)
Discussion started by: PtaQ
4 Replies

6. UNIX Benchmarks

Blade 1500 Silver

CPU/Speed: UltraSPARC-IIIi/1.5Ghz Ram: 1GB Motherboard: Sparc Bus: PCI Cache: Controller: Disk: ATA Load: 1 user Kernel: SunOS 5.10 Generic_137111-02 Kernel ELF?: yes pgms: gcc 2.95.3 compiled BYTE UNIX Benchmarks (Version 3.11) System -- SunOS aachen95 5.10... (0 Replies)
Discussion started by: MadeInGermany
0 Replies

7. AIX

IBM blade

How to access IBM server free of charge ? Is there such services provided by IBM ? I want to practice on AIX & learn about administration before go to exam soon Do you have idea what VLP ( Virtual Loaner Program ) is ? (4 Replies)
Discussion started by: arm
4 Replies

8. Red Hat

How to know full width blade or half width blade?

HI, How do we figure out if the server is half blade server or full blade server? Anything we need to look at to know on this? thanks in advance (9 Replies)
Discussion started by: snchaudhari2
9 Replies
fwupgrade(8)						      System Manager's Manual						      fwupgrade(8)

NAME
fwupgrade - Updates the system firmware from a loadable firmware image (*.exe or *.sys) SYNOPSIS
/sbin/fwupgrade [-a] [-e] [-ignore] [-q] [-r] [-s] [-v] [-t CD-ROM_path] [-i path] /sbin/fwupgrade [-v] -f firmware_filename OPTIONS
Forces a firmware update without comparing the current firmware with the source firmware. Updates only if the current firmware is not equivalent to the source firmware. Specifies the path of the (*.exe or *.sys) firmware image. This is only used when you use a firmware image that is not on the distribution CD-ROM. For example, an image obtained from a web site download. You must ensure that the firmware image is the correct one for the target system, and verify that the image has the necessary support. This is indicated by bit1 and bit2 in the Flags column of the smmtable.txt file. Specifies the mount point of the target disk during an installation. This switch is to be used exclusively by the Tru64 UNIX install program. This switch suppresses error messages that are displayed if no firmware files are found on the distribution media, and causes the fwupgrade program to exit successfully. Does not upgrade the firmware, but displays information about the success of the desired operation. This enables you to to query fwupgrade to verify planned actions, such as ensuring whether the firmware really needs to be upgraded, or finding out if the target system supports a soft-reset. Resets the machine by software and reboots after the upgrade. The utility will exit with an error status if the system hardware does not support this feature. Sets silent mode, in which the firmware is upgraded without prompting you. If there is an error, the program also exits silently without prompting you. When this switch is used, you are not prompted for confirmation for the upgrade to proceed. Specifies the path of the mounted Firmware CD. If the -s option is not specified, you will be prompted to enter this path. Sets verbose mode, in which additional information is dis- played. DESCRIPTION
The fwupgrade command provides a means of updating the system firmware when a (*.exe or *.sys) loadable firmware update image is available. A firmware upgrade will shut down the system and require a full hardware reset. If the source firmware image does not support the loadable firmware update functionality, fwupgrade will exit with error status. The system must provide a SAVE_ENV callback that complies with the Alpha SRM. You can tell if the SAVE_ENV callback exists by executing the command: # consvar -a The SAVE_ENV is supported on the target system if the following message is displayed: Console environment variables saved If the SAVE_ENV is not supported on the target system, the following message is displayed: Failed to save environment variables Your programs can either check the return status of consvar -a or the return status of: setsysinfo(SSI_PROM_SAVE_ENV,...). See the setsysinfo(2) reference page for more information. EXIT STATUS
If you confirm that the firmware is to be upgraded, and no errors occur setting up the upgrade process, then fwupgrade will reboot the sys- tem rather than exit. An exception is that there is no reboot performed when the -i option is used. Instead, a status of 0 is returned. If you query whether the process would be successful, or if an upgrade request fails, the exit values are: Success. Firmware is adequate and supported. Failure. Firmware is not supported. Firmware needs to updated (when queried). EXAMPLES
To find out all information about your current firmware, platform, and the source firmware: # /sbin/fwupgrade -v -q Current Firmware: 4.10-0 Platform: 17-2-1091 Unable to open smmtable.txt at '/'. What is the mount point for the firmware CD? /mnt Firmware CD Version: 4.0 Distribution Firmware: 4.10-0 LFU File: /dev/rz2a at alpha1000/as1000_e4_v4_8.exe LFU Support: Y Soft Reset: Y System Firmware does not need to be upgraded To upgrade the firmware: # ./fwupgrade -t /mnt Current Firmware: 4.7-0 Are you sure that you wish to update the system firmware from 4.7-0 to 4.10-0?(yes/no)yes fwupgrade:Rebooting to update the system firmware... Terminated # syncing disks... done rebooting.... (transferring to monitor) FILES
The loadable firmware update images provided by Compaq. Typically, these are distributed on a firmware CD-ROM. If you obtain firmware images from a source other than the firmware CD-ROM (such as a www server) you should verify that they are the correct images for the tar- get system. A file provided with the firmware CD-ROM, used to determine the presence of the firmware CD-ROM and information about source firmware. SEE ALSO
Commands: consvar(8) Functions: setsysinfo(2) fwupgrade(8)
All times are GMT -4. The time now is 08:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy