12-03-2012
HMC Upgrade Question
I have an HMC that I'm looking to upgrade from V7.3.4.0 SP2 to the latest version V7.7.6.0. I'm looking at the firmware levels of the systems attached to this HMC, and all of the systems have compatible firmware revisions but there are two that have been update recently and the platform IPL level is still showing the older/incompatible revision. However the Activated level is showing a compatible revision.
My question is, can I still upgrade the HMC software to the newest version? Or do I have to re-IPL the 2 systems in question?
9 More Discussions You Might Find Interesting
1. Solaris
Hi all, I hava an ULTRA-5 machine at work, runing Solaris8, and I'm thinking of downloading the free version of Solaris9, and runing an upgrade, is this possible? And the free version of Solaris 9, is the same as the payed version?
Thx. (0 Replies)
Discussion started by: Zarnick
0 Replies
2. AIX
Hello everybody, am new to AIX. can someone help me with below
i was trying to do an ml upgrade on AIX5.2 from 01-09
when i do a lppchk -v, i get
X11.base.rte 5.2.0.10 (usr: COMMITTED, root: not installed)
i tried to remove the fileset using smitty remove and it says... (1 Reply)
Discussion started by: karthikosu
1 Replies
3. AIX
I have an IBM pseries 7028-6E1 server with a six drive bay that is currently plugged into the scsi backplane of the motherboard. I am going to install a PCIX Ultra320 scsi raid adapter, and swing the drive bay over to it. I am just wondering how this is going to work. Should I power the server... (1 Reply)
Discussion started by: markper
1 Replies
4. Solaris
I have an old sun v890 server running solaris 9. Apparently we need to be running solaris 10. I don't know much about the server history, there isn't any documentation. I hesitant to rebuild from scratch and loose user configuration settings etc...
How difficult is it to upgrade to solaris... (10 Replies)
Discussion started by: Kjons76
10 Replies
5. AIX
Hi all,
i would like to know if it's possible upgrade AIX 5.3 to 6.1 on a LPAR without use the HMC.
so i would like to know if i must use the console to do it or i can do all from the up&running system on LPAR.
Thanks in advance.
Mario (4 Replies)
Discussion started by: Zio Bill
4 Replies
6. Solaris
I want to basically update an ABE that someone created a few months back.
I'm sure stuff has changed since it was made, and I was going to delete it and create a new one.
But from what I'm looking at, the lumake appears like it would be a faster approach.
I want to use live upgrade to... (0 Replies)
Discussion started by: BG_JrAdmin
0 Replies
7. AIX
Hi all,
I want to upgrade a clustered AIX 5.3 TL10 with PowerHA 5.5.0.4.
To both AIX 6.1 and PowerHA 6.1 in an wasy way.
Any guidelines or procedures in an easy way to accomplish this task safely?
Note : fdown time is an acceptable option. (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies
8. Solaris
Currently we are having solaris 11.1 SRU 11.1.21.4.1 installed on server. We need to upgrade it to solaris 11.2 SRU 11.2.9.5.0
Is it possible to upgrade to SRU 11.2.9.50 directly by downloading repo files or do I need to upgrade to 11.2 first and then upgrade to SRU 11.2.9.5.0? (1 Reply)
Discussion started by: sureshsun
1 Replies
9. AIX
Hi Experts
So we have two data center .I upgraded the HMC in one datacenter, very easy no problem, but in the second datacenter we have dual HMC connection. I am looking at the document from the ibm documentation. I found something that I am not comfortable following. which is this : Physically... (2 Replies)
Discussion started by: JME2015
2 Replies
relup(5) Files relup(5)
NAME
relup - Release upgrade file
DESCRIPTION
The release upgrade file describes how a release is upgraded in a running system.
This file is automatically generated by systools:make_relup/3,4 , using a release resource file ( .rel ), application resource files ( .app
) and application upgrade files ( .appup ) as input.
FILE SYNTAX
In a target system, the release upgrade file should be located in the OTP_ROOT/erts-EVsn/Vsn directory.
The relup file contains one single Erlang term, which defines the instructions used to upgrade the release. The file has the following syn-
tax:
{Vsn,
[{UpFromVsn, Descr, Instructions}, ...],
[{DownToVsn, Descr, Instructions}, ...]}.
* Vsn = string() is the current version of the release.
* UpFromVsn = string() is an earlier version of the release to upgrade from.
* Descr = term() is a user defined parameter passed from the systools:make_relup/3,4 function. It will be used in the return value of
release_handler:install_release/1,2 .
* Instructions is a list of low-level release upgrade instructions, see appup(5) .
It consists of the release upgrade instructions from the respective application upgrade files (high-level instructions are translated
to low-level instructions), in the same order as in the start script.
* DownToVsn = string() is an earlier version of the release to downgrade to.
When upgrading from UpFromVsn with release_handler:install_release/1,2 , there does not have to be an exact match of versions, but
UpFromVsn can be a sub-string of the current release version.
SEE ALSO
app(5), appup(5), rel(5), release_handler(3erl), systools(3erl)
Ericsson AB sasl 2.1.9.3 relup(5)