Sponsored Content
Operating Systems AIX IBM Power Pseries Open Firmware boot / VIOS POWERVM VET CODE Post 302748825 by filosophizer on Thursday 27th of December 2012 02:53:10 AM
Old 12-27-2012
[Solved] IBM Power Pseries Open Firmware boot / VIOS POWERVM VET CODE

Thank you Michael. You are right, it never crossed my mind to go through ASMI and restart.

Michael can check this post https://www.unix.com/aix/205807-solve...g-pseries.html
 

10 More Discussions You Might Find Interesting

1. AIX

new IBM pseries and new disks

Hello Gurus, i'm quite new person in AIX world, actually i'm SAP consultant. But due to my job faced with AIX. Trying to configure new server for installation SAP. We have 4 disks one of them (hdisk3) has VG rootvg. How i can extend rootvg with another disk? i tried: # extendvg rootvg hdisk0... (2 Replies)
Discussion started by: sapbcer
2 Replies

2. SuSE

VIOs and Linux for pSeries

Hi. I was wondering if there was a way to get the PVIDs from the disks on a SuSE Enterprise 9 box. I have 2 hdisks from a VIO setup that have specific PVIDs. I'd like to match those 2 disk to the disks within the Linux box. Any tips? thanks. (0 Replies)
Discussion started by: Stephan
0 Replies

3. Linux

Why does they use Linux on IBM pSeries

Anyone can help me answer the question. Why does they use Linux on IBM pSeries not AIX. I can't understand why, cause AIX is the best supporting from IBM pSeries. Tks you. (3 Replies)
Discussion started by: quan0509
3 Replies

4. AIX

power 6 VET activation code

Hello, I successfully entered VET activation key through HMC -> capacity on demand (CoD) -> advanced power virtualization -> activate VET Key . But the option for VIOS creation is still not appearing. VET information gives this : Type de système : 8203 Numéro de série du système : XX-XXXX CCIN... (2 Replies)
Discussion started by: astjen
2 Replies

5. AIX

Need IBM PowerVM

Hi all please give me a link for IBM PowerVM (4 Replies)
Discussion started by: babinlonston
4 Replies

6. AIX

IBM VIOS POWERVM IVM error

Hi, When I try to login on my vios ivm website http://vios through the browser -- all three of them -- firefox , chrome , Internet Explorer , i get this error http://vioserver/j_security_check I have java installed on the machine from where i am trying to open up the IVM/VIOS webpage. I... (2 Replies)
Discussion started by: filosophizer
2 Replies

7. AIX

CD-ROM issue with PowerVM IVM VIOS

I am facing problems in moving CD-ROM from one lpar to another. CDROM can be seen on the POWERVM (IVM) server , but through the web-access if I move it ( assign it ) to LPAR it will be assigned. I run cfgmgr , and the cdrom does not show up in the LPAR. I firmly believe this is the reason why I... (2 Replies)
Discussion started by: filosophizer
2 Replies

8. AIX

IBM Power 740 won't boot after firmware update

A team member installed the wrong version of License Code on a Power 740 system used in our Development environment. The system will no longer boot. Does anyone have IBM documentation or experience to share on recovering a system that currently reports "Unsupported License Code version... (1 Reply)
Discussion started by: kevinedailey
1 Replies

9. AIX

Revisiting IBM PowerVM VIOS AIX

coming from this thread: https://www.unix.com/aix/211107-ibm-power-pseries-open-firmware-boot-vios-powervm-vet-code.html PowerVM, formerly known as Advanced Power Virtualization (APV), is a chargeable feature of IBM POWER5, POWER6, POWER7, POWER8, and POWER9 servers and is required for support... (0 Replies)
Discussion started by: filosophizer
0 Replies

10. AIX

Powervm ivm vios

Hello, After installing on P6 which is POWERVM IVM VIOS enabled (VET CODE D21C77ACD9229817CA1F00002C10004164 ) i get this message "I/O hosting requires a hosting partition - boot not permitted". HMC was connected to the machine then HMC was removed through ASMI Searching on... (2 Replies)
Discussion started by: filosophizer
2 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 06:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy