Sponsored Content
Full Discussion: Update firmware HBA
Operating Systems AIX Update firmware HBA Post 302337683 by zxmaus on Friday 24th of July 2009 04:18:27 PM
Old 07-24-2009
Hi,
you can do it online (it will throw a few errors but these can safely be ignored) but I would highly recommend to reboot the server after you're done.
Kind regards
zxmaus
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

how to do firmware update

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

How do i update firmware on X4500??

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. Solaris

firmware update on t5120

Hi, I am using 3 t5120 sparc systems, OS solaris 10. I am confused by update manager behaviour and sun support. Sun support guy, tells me install patch : 136932-09 (#136932-09: Hardware/PROM: SPARC Enterprise T5120 & T5220 Sun System Firmware with LDOMS support) When I checked... (4 Replies)
Discussion started by: upengan78
4 Replies

4. Solaris

Update MX000 XCP firmware

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. Solaris

After update Solaris version, HBA driver still need to install?

Hi all I had update a server from Solaris 8 to Solaris 10 is it the HBA driver still need to reinstall? since i can get the driver info as below: root@sgerpdev # fcinfo hba-port HBA Port WWN: 21000003ba9b58a3 OS Device Name: /dev/cfg/c1 Manufacturer: QLogic Corp. ... (1 Reply)
Discussion started by: SmartAntz
1 Replies

6. AIX

I need command for HBA model & firmware please

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

7. AIX

How to obtain old version of HBA firmware ?

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

8. AIX

System P firmware update

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

9. Hardware

2540 firmware update

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
iobind(1M)																iobind(1M)

NAME
iobind - bind a driver to a device SYNOPSIS
instance] DESCRIPTION
The command may be used to perform online unbinding of a device LUN hardware path from its current driver and binding a new driver to it. As part of the binding operation, the specified driver will be bound to the LUN hardware path and also to its corresponding legacy hardware paths. The hardware path specified as the argument to the option must be of the form 64000/0x/0x. The driver name specified with the option will be bound to the LUN and legacy hardware paths. The optional option specifies an instance number to be assigned to the device associated with the hardware path. If this option is not used, the device will be assigned a new instance number in the new driver's class. The optional forces the binding to occur at the next reboot if it cannot be done online. The device must not be in use while the unbind operation is performed. The driver must support online unbinding and binding. If either of these requirements is false and the option is not given, the user will be asked if the binding can take effect at the next reboot. The user is given the option to proceed or not. If a driver supports online unbinding and binding, then after completes, a device will have one of the following software states as shown by the command: The specified driver was successfully bound to the hardware path. The specified driver cannot be used to claim the hardware at the specified hardware path. The device at the address is responding, but it is in an error state. The device at the specified hardware path is no longer responding. The specified hardware path is locked. Try again later. The driver failed. Options recognizes the following options: Force the binding even though a driver does not support online unbinding and binding or the device is in use. In this case, the binding will take effect at the next reboot. The LUN hardware path of a device must be of the form 64000/0x/0x. The instance number to be assigned to the device. The name of the driver that the LUN and legacy hardware paths are to be bound to. RETURN VALUE
Exit values are: Successful completion. An error condition occurred. EXAMPLES
Unbind the driver bound to the device at hardware path and bind the device to Use the default instance number of the driver's class. Unbind the driver bound to the device at hardware path and bind the device to Assign it the instance number Do a forced binding. If the driver does not support online binding or the device is busy, the binding will be deferred till next reboot. WARNINGS
The and commands should not be run at the same time because both commands attempt to bind drivers. In particular, there may be a short window while will leave a hardware path unbound. If runs during that window, it may bind a different driver to that hardware path. If this happens, must be executed again to bind the desired driver. may be executed only by the superuser. SEE ALSO
ioscan(1M), intro(7). iobind(1M)
All times are GMT -4. The time now is 07:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy