Sponsored Content
Operating Systems AIX AIX 5.2 and 5.3 hardware support questions... Post 302260749 by dig1tal on Friday 21st of November 2008 01:55:33 PM
Old 11-21-2008
I'm not sure I follow your question.

There are components like the Advanced Management Module (AMM) and Integrated Virtualization Manager (IVM) of the JS22 and the Bladecenter that are different from your typical pSeries server. Other than that, AIX remains the same on either piece of hardware.
 

8 More Discussions You Might Find Interesting

1. Solaris

Sun server hardware questions

I have no experience with sun servers but for fun and experience I would like to buy a low-end server and play with things. I have a few questions that maybe some of you who use these things will be able to answer: - I believe they are also called PCI slots in the sun server, but are they the... (2 Replies)
Discussion started by: Synbios
2 Replies

2. AIX

AIX Hardware commands

Hi All, Needed commands to find Monitor , chassis & keyboard related information on AIX. Please please please help. Thanks VK (2 Replies)
Discussion started by: Veenak15
2 Replies

3. Solaris

hardware support for solaris 9 or 10

Hi boss, i want to purches one second hand system intel P3 for practice.vender having mercury mother board.it will support sun 9 or 10. if any problem will create while configure like (ex:-apache) .tell me which configuration (intel) is best for practice.In intel system what are the... (2 Replies)
Discussion started by: rjay.com
2 Replies

4. AIX

AIX Hardware Configuration *I'm very new*

I'd like to start by saying how extremely new I am to any UNIX OS, although I've been dealing with Linux systems off and on for roughly a year now, and am trained primarily on Windows Servers. Our company has an old AIX system, running AIX version 4. The server we are using is more then 10... (6 Replies)
Discussion started by: webers
6 Replies

5. Hardware

Where can I get support on old SUN hardware

Oracle has put all SUN hardware related downloads into Oracle Support which not free for an old SUN workstation user. Now I am looking for a new version BIOS for upgrade but nowhere to download. P.S. it is SUN java workstation w1100z I'd APPRECIATE any information if someone could give me... (1 Reply)
Discussion started by: Leland
1 Replies

6. AIX

AIX 5.2.0 on own hardware -> i550 LPAR

We are running into a problem that we thought had solved but no go... We have multiple machine types but 1 AIX and 2 i550 (AS/400) with 4 lpar each. Existing AIX is an old (2004 vintage) machine with 5.2 on it for historical use only. Existing Power6 i550 running code that will used... (6 Replies)
Discussion started by: jackb_guppy
6 Replies

7. AIX

New to AIX and IBM Hardware. Need some info

Hello all. I'm new to AIX and IBM hardware and I have a question around the configuration of the service processor on the power series. I need to know: 1) How do I get into the service processor from the serial console when AIX is up and running. I come from the Sun world and I tried all I know.... (1 Reply)
Discussion started by: glenc2004
1 Replies

8. AIX

Migrate AIX to new Hardware

Hello Friends/AIXgurus, When you have time, could you please look into below. We're planning to migrate AIX LPARs on to new Hardware. Requirement: Migrate AIX LPARs from POWER 6 to POWER 8 Hardware (*everything should run as is after the transition) Below is our thought process. Ours... (5 Replies)
Discussion started by: System Admin 77
5 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 04:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy