03-18-2009
Quote:
Originally Posted by
DukeNuke2
the patch is a new fw for your service processor. download the patch to your management mashine and unzip it. inside the unpacked directory is a file with the new firmware. the patch you need is 139439-01. the file inside is "Sun_System_Firmware-7_2_0-SPARC_Enterprise_T5120+T5220.pkg".
open a browser and enter your sp ip. login and go to the "maintenace" tab. the mashine has to be powered off for the update! enter the path to the pkg file and click upload...
Not that I am ungrateful,
This is again confusing because 139439-01 is Dec 23,08 release while 136932-09 is Mar2, 2009 release. I am ready to do any of of these if it helps take care of the SC> hanging issue. Another issue is I can not use this method of browser to update because I only can ssh to SC/ILOM while ports like 80 and any other is blocked in firewall...what is the other easier method ?
by the way I am sure commands like poweroff or any other are not going to work from the SC/ILOM, I just hope init 5 works from system but this is the case when I am sure which patch to install and how.
Question remains , is updatemanage not doing its job and we have to ignore this sh^%%^ from sun? and follow other methods using forums
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi, am a new comer to the AIX side.
i had 3 specific questions.
1) what is firmware
2) how to locate the firmware running on a unix server
3) how to do firmware update(is it something i download from IBM site)
thanks everybody for taking the time and plz reply.
karthik (5 Replies)
Discussion started by: karthikosu
5 Replies
2. Solaris
I have solaris X4500 with ILOM version 1.1.1. I want to update the firmware. I know that we need to use
load -source tftp://tftpserver/image file
But I do not understand what is the IP address of the tftp server that we need to type in there.
Kindly, help me with this.
Thank you (5 Replies)
Discussion started by: bharu_sri
5 Replies
3. AIX
Hello
I have a question
I have several partitions P550 Aix 5.3 and I need to update the HBA firmware, in some partitions I have two HBA and in others I have one HBA only.
My question is if I have to reboot my partitions after update the firmware level. and If I can do it online or I have... (2 Replies)
Discussion started by: lo-lp-kl
2 Replies
4. Solaris
how can we download the firmware form the host to the XSCF , My host is not configured with either FTP,HTTPS or proxy server. Someone told me we can do it with getflashimage but i did not find any info getflashimage man page to do it.
Any help will be appreciated. (3 Replies)
Discussion started by: fugitive
3 Replies
5. AIX
I am interested whether should AIX Admin make upgrade of firmware on power systems or IBM support should do it thanks in advance :-) (3 Replies)
Discussion started by: Vit0_Corleone
3 Replies
6. Solaris
Hi,
Can you pls. provide me detailed procedure on how to update system BIOS and ILOM Firmware for x4100 M2 servers.
Thanks. :) (1 Reply)
Discussion started by: chozie
1 Replies
7. Hardware
Hi Guys and Gals,
does anyone know how to update the firmware on the drives in a storagetek 2540?
Thanks in advance
Rgrds
Martin (0 Replies)
Discussion started by: callmebob
0 Replies
8. Solaris
Hello there!
I am familiar with Linux, FreeBSD, but relatively new to Solaris. Because I wanted to play a little with servers and networks, I got a used SunFire v20z with AMD Opteron processors and installed OpenIndiana 151a8 on top of that. This is the first machine of this kind I have ever... (1 Reply)
Discussion started by: guru987
1 Replies
9. AIX
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
LEARN ABOUT OSX
svk::command::patch
SVK::Command::Patch(3) User Contributed Perl Documentation SVK::Command::Patch(3)
NAME
SVK::Command::Patch - Manage patches
SYNOPSIS
patch --ls [--list]
patch --cat [--view] PATCHNAME
patch --regen [--regenerate] PATCHNAME
patch --up [--update] PATCHNAME
patch --apply PATCHNAME [DEPOTPATH | PATH] [-- MERGEOPTIONS]
patch --rm [--delete] PATCHNAME
OPTIONS
--depot DEPOTNAME : operate on a depot other than the default one
DESCRIPTION
To create a patch, use "commit -P" or "smerge -P". To import a patch that's sent to you by someone else, just drop it into the "patch"
directory in your local svk repository. (That's usually "~/.svk/".)
svk patches are compatible with GNU patch. Extra svk-specific metadata is stored in an encoded chunk at the end of the file.
A patch name of "-" refers to the standard input and output.
INTRODUCTION
"svk patch" command can help out on the situation where you want to maintain your patchset to a given project. It is used under the
situation that you have no direct write access to remote repository, thus "svk push" cannot be used.
Suppose you mirror project "foo" to "//mirror/foo", create a local copy on "//local/foo", and check out to "~/dev/foo". After you've done
some work, you type:
svk commit -m "Add my new feature"
to commit changes from "~/dev/foo" to "//local/foo". If you have commit access to the upstream repository, you can submit your changes
directly like this:
svk push //local/foo
Sometimes, it's useful to send a patch, rather than submit changes directly, either because you don't have permission to commit to the
upstream repository or because you don't think your changes are ready to be committed.
To create a patch containing the differences between "//local/foo" and "//mirror/foo", use this command:
svk push -P Foo //local/foo
The "-P" flag tells svk that you want to create a patch rather than push the changes to the upstream repository. "-P" takes a single flag:
a patch name. It probably makes sense to name it after the feature implemented or bug fixed by the patch. Patch files you generate will be
created in the "patch" subdirectory of your local svk repository.
Over time, other developers will make changes to project "foo". From time to time, you may need to update your patch so that it still
applies cleanly.
First, make sure your local branch is up to date with any changes made upstream:
svk pull //local/foo
Next, update your patch so that it will apply cleanly to the newest version of the upstream repository:
svk patch --update Foo
Finally, regenerate your patch to include other changes you've made on your local branch since you created or last regenerated the patch:
svk patch --regen Foo
To get a list of all patches your svk knows about, run:
svk patch --list
To see the current version of a specific patch, run:
svk patch --view Foo
When you're done with a patch and don't want it hanging around anymore, run:
svk patch --delete Foo
To apply a patch to the repository that someone else has sent you, run:
svk patch --apply - < contributed_feature.patch
perl v5.10.0 2008-08-04 SVK::Command::Patch(3)