|
|
 |
|
IBM i integration with BladeCenter® and System x™ code fixes come in two types: code fixes to the i5/OS® side and code fixes to the Windows®, VMware® ESX or Linux® side.
- IBM® distributes the code fixes to the IBM i side in IBM i PTFs.
Use the normal IBM i service mechanisms to get, load and apply these PTFs.
- The code fixes to the Windows, VMware® ESX or Linux side are in packages called service packs. Service packs are cumulative - the most recent service pack contains all the fixes from prior service packs in addition to new fixes. IBM distributes these service packs in IBM i PTFs. Use the normal IBM i service mechanisms to get, load and apply these PTFs. Then, you must install that service pack from IBM i to each Windows, VMware® ESX or Linux Server.
|
| |
|
| |
Once the service pack PTF is installed on IBM i,
it must then be installed on each Windows, VMware ESX or Linux server. Do this as follows:
- For Windows servers, synchronize the integration software level using the integrated Windows server console.
For more information, see Updating the integration software level: integrated Windows server console in the Information Center.
Note: Server integration fixes can be provided either
within a service pack or separate from a service pack.
In either case, use the service pack installation process to load the fixes on the Windows server.
When a service pack PTF is loaded on the Windows server, the service level will show the service pack PTF number.
When a fix that is not part of a service pack PTF is loaded on the Windows server,
the service level will continue to show the most recent service pack PTF number that has been loaded on the Windows server.
- For VMware ESX servers, use the i 6.1 ibmlsvupdt or i 5.4 ixsupdt command from the VMware ESX Server console. For more information, see Updating the integration software for VMware ESX Server in the IBM i 6.1 Information Center or Maintaining the integrated server software for the ESX Server in the
 VMware ESX Server on iSCSI attached integrated servers for IBM i 5.4 document.
- For Linux servers, use the i 6.1 ibmlsvupdt or i 5.4/V5R3 ixsupdt command from the Linux console.
For more information, see
Maintaining the Linux integration code in the i 6.1 or i 5.4 Information Center.
Note: You can also update the Linux kernel on an IXS or IXA attached server in i 5.4 or V5R3. If you are updating the kernel,
the ixsupdt command must be run immediately after applying the kernel update.
See the Linux kernels tested on IXS/IXA page for additional information.
|
| |
|
| |
|
Below are the service packs available in IBM i PTFs,
along with the cumulative PTF package that contains the service pack.
You can order PTFs via Electronic Customer Support (ECS) or
Fix Central,
or find more information on the
System i Fixes
web page. Additional System i service and support information can be found at
http://www.ibm.com/systems/support/i/.
|
| |
|
| Windows 2000 and Windows Server 2003 |
 |
|
None
|
|
|
|
|
| VMware ESX3 |
|
|
SI30994
|
None |
17 March 2008 |
|
|
| RHEL5 on iSCSI attached servers |
|
|
SI31003
|
None |
17 March 2008 |
|
|
| SLES10 on iSCSI attached servers |
|
|
SI31004
|
None |
17 March 2008 |
|
|
| RHEL5 on logical partitions |
|
|
SI31005
|
None |
17 March 2008 |
|
|
| SLES10 on logical partitions |
|
|
SI31006
|
None |
17 March 2008 |
|
|
| |
|
| Windows 2000 and Windows Server 2003 |
|
| SI26556 |
C7107540 |
11 January 2007 |
|
| SI28014 |
None |
24 July 2007 |
|
|
| Linux |
|
|
SI22565
|
None |
14 February 2006 |
|
|
SI23345
|
None |
11 April 2006 |
|
|
SI25139
|
None |
22 September 2006 |
|
|
| VMware ESX |
|
|
SI28340
|
None |
14 September 2007 |
|
|
| |
|
|
| |
|
|
|
Last Modified: 21 March 2008
|
| |
|
|
