06-30-2010
You can certainly do just the HBA upgrade. All the jumbo patch bundle is is a collection of individual patches applied in a particular order. You just need to determine which patch(es) are the HBA firmware you need then download those specific patches and install them.
10 More Discussions You Might Find Interesting
1. Solaris
Hi ,
How can I collect information about any Hardware , specially HBA (Host Bus Adapter) ....
I tried prtdiag but it is not shoing the HBA details.
Regards (4 Replies)
Discussion started by: adel8483
4 Replies
2. UNIX for Advanced & Expert Users
Hi,
I'm trying to determine which HBA cards are installed on my Solaris 10 (Sun-Fire-V240) machine.
The relevant data I have is below, but from it I cannot ascertain for sure if I have Emulex 10000 or 11000 HBA cards.
Can anyone suggest how to determine my HBA hardware ?
Thanks,
Ron.
... (3 Replies)
Discussion started by: ronbarak
3 Replies
3. Solaris
Hi,
I'm trying to determine which HBA cards are installed on my Solaris 10 (Sun-Fire-V240) machine.
The relevant data I have is below, but from it I cannot ascertain for sure if I have Emulex 10000 or 11000 HBA cards.
Can anyone suggest how to determine my HBA hardware ?
Thanks,
Ron.
... (4 Replies)
Discussion started by: ronbarak
4 Replies
4. News, Links, Events and Announcements
two articles related to live upgrades that i found useful and noteworthy.
Solaris 10 5/08 Live Upgrade Gotcha :: Col’s Tech Stuff
Solaris Live Upgrade and Patches :: Col’s Tech Stuff (0 Replies)
Discussion started by: pupp
0 Replies
5. 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
6. AIX
Lets says I have 2 HMC's A and B, connected to a p570 managed system.
Right now the firmware level of the p570 is EM320_076 and that needs to be upgraded to EM340_095.
Now the HMC's are at V7R3.3 and as per the code matrix the HMC's needs to be upgraded to V7R3.4 Servicepack 2.
Now my... (5 Replies)
Discussion started by: balaji_prk
5 Replies
7. Solaris
Hello,
In Solaris 10 I can use fcinfo to find what speed the hba ports are running at, am I able to find this out using Solaris 9? I have tried a few variations on luxadm but cant find anything relevant.
Thanks. (1 Reply)
Discussion started by: Actuator
1 Replies
8. AIX
Hi All,
I have a task to complete on several server, I need advice from u guys,i need to know that , how can i check the following thing in AIX server.
1)HBA vendor, HBA model, HBA driver version & HBA firmware.
2) Multipath software & multipath version.
3) Cluster software & cluster... (2 Replies)
Discussion started by: gulamibrahim
2 Replies
9. AIX
Hi all:
I have a need to down-rev my AIX HBA firmware due to storage instability after upgrading, but IBM support only makes the latest version of firmware available for download.
Can anyone provide pointer/tips for obtaining old HBA firmware ?
Specifics:
280B HBA
df1000fa driver... (1 Reply)
Discussion started by: kwachtler
1 Replies
10. Solaris
I have one disk that is reporting I/O errors but the same LUN mounted on a different node is able to access it without issue, is there a way to identify which HBA is being used for the LUN without swapping each out at a time? (4 Replies)
Discussion started by: thmnetwork
4 Replies
cleanup(1M) cleanup(1M)
NAME
cleanup - HP-UX patch cleanup utility
SYNOPSIS
DESCRIPTION
The command provides functions useful when dealing with HP-UX patches on HP-UX.
The command logs all information to
Options
recognizes the following options:
Preview the task but do not actually perform the requested action.
Notify the user of
tasks and request confirmation before performing the requested action.
Commit patches superseded at least
number times. This option is a front-end to the option of (see swmodify(1M)) that provides an easier interface to commit
multiple patches at once.
Remove patches in the specified software depot that have been superseded by
patches also available from the depot.
Specifies whether the software depot contains patches for HP-UX 10.X or 11.X
releases. This option is only valid with the option. If the option is not specified, it defaults to HP-UX 11.X patches.
Specifies whether patches in the software depot that contain a corequisite or
prerequisite attribute specifying one of the superseded patches as a dependency should also be removed. This option is valid
only with the option. If the option is not specified, it defaults to true.
Remove HP-UX 10.X patches that remain in the Installed Product Database
after an upgrade to HP-UX 11.X. These patches are removed from the IPD so that they are no longer displayed in the output of
the command (see swlist(1M)). The HP-UX 10.X patch files are also removed from
Correct the
attribute for HP-UX 11.X patches.
Recommendations
The command should be executed after updating to HP-UX 11.X from HP-UX 10.20. It is not necessary to execute after updating from one ver-
sion of HP-UX 11.X software to another because SD-UX will properly remove 11.X patch information from the IPD in these situations.
The command should be executed whenever patches are added to a software depot. It is not a requirement that superseded 11.X patches be
removed from a software depot, but it is a recommendation to conserve disk space and to avoid confusion. If superseded patches exist in
the same depot as patches that supersede them, SD-UX on HP-UX 11.X will handle the situation properly.
The command can be executed to commit all patches that have been superseded at least the specified number of times. The only benefit from
committing patches is that disk space will be recovered in the
The command can be executed to insure that the attribute of all patch filesets is set correctly. There are several known situations where
the attribute will be set incorrectly. This command can be run at any time, but will be most useful after a system has been installed
using Ignite-UX.
AVAILABILITY
This command is standard on HP-UX 11i v3. On 11i v2 it is available in patch PHCO_32220 or a superseding patch. On 11i v1 it is available
in patch PHCO_27780 or a superseding patch.
WARNINGS
Extreme care should be used when committing patches. Once a patch has been committed, it cannot be removed from the system. Patches
should only be committed when you are satisfied with their behavior. Recovering disk space should not be the only factor considered when
committing patches.
AUTHOR
was developed by HP.
SEE ALSO
show_patches(1), sysdiff(1), check_patches(1M), swlist(1M), swmodify(1M), swremove(1M), sd(4).
cleanup(1M)