Operations Console hardware requirements

For correct Operations Console configurations, verify that you have satisfied the server, adapter, cable, and PC requirements.

Important: IBM® System i5® and eServer™ i5 models start counting logical partitions with the number 1 (even if it is the only partition) instead of a 0. For the console to connect correctly, your logical partitions must also begin numbering at 1 instead of 0. This is especially true if you rely on the BOOTP process to configure the server with its network data.

Operations Console default console port when not using an HMC

Operations Console defaults to the first embedded Ethernet port as the default console port in systems not using a Hardware Management Console (HMC). This includes the 5706/5707 adapters. However, the server will not check for the 5706/5707 adapter unless support for the default embedded Ethernet port has been disabled. Support for the default embedded Ethernet port is disabled in manufacturing for systems where the embedded ports do not exist, for example, the 9406-595. To disable support for the default embedded Ethernet port or 5706/5707 adapters, see Disabling support for the default embedded Ethernet port or 5706/5707 adapters.

Adapter requirements

You must install an adapter for Operations Console in all of the following situations:

You want to use a local console on a network (LAN) and have elected to disable support for the default embedded Ethernet port
You have a system where the embedded ports do not exist
You want to use a local console that is directly attached

Operations Console supports the following adapters:

Operations Console (LAN): 2744, 2838, 2849, and 5706/5707 (IOP-less)
Note: The 2744 and 2849 adapters require an input/output processor (IOP) and can be located only in an expansion unit.
Operations Console (direct): 2742 (IOP-less), 2793/2794 (IOP-less), 4745, and 9771

The adapter locations pertain to servers without an HMC. Using an HMC to manage the server excludes using adapters by location. Instead, you should use the HMC to designate hardware resources.

Important: If you are running Licensed Internal Code (LIC) prior to V5R4M5 and you want to move the 2793/2794 asynchronous adapter from its manufacturing default location to use Operations Console (direct), you must also use the console service functions (65+21) or the OPSCONSOLE macro to select an individual asynchronous adapter for use with the console. For more information, see Using the console service functions (65+21) or Using the OPSCONSOLE macro.

Table 1. Operations Console adapter requirements
Model	Operations Console (LAN)	Operations Console (direct)	Notes
Model	LAN adapter locations	Asynchronous adapter locations	Notes
520, 525, and 515	C2 or C5 disable support for the default embedded Ethernet port or 5706/5707 adapters. If you use C2 or C5, you must disable support for the default embedded Ethernet port or 5706/5707 adapters. See Note 2 and 3 below.	C2 or C3 C4 is also available. Refer to Note 1 below. The system can have asynchronous adapters located in multiple slots simultaneously. Refer to Note 1 below.	If your LAN adapter is located in C2, then the IOP must be located in C1. If your LAN adapter is located in C5, then the IOP must be located in C3 or C6. If your asynchronous adapter is located in C2, the IOP must be located in C1. If your asynchronous adapter is located in C3, the IOP must be located in C6. If an IXS is installed, it must be located in C5/C6, the LAN adapter or asynchronous adapter must be located in C2, and the IOP must be located in C1, if needed.
550	C4	C2 or C5 The system cannot have asynchronous adapters located in both slots simultaneously.	When your LAN adapter is located in C4, the IOP can be located in C3 or C5 (except when an IXS is installed). If your asynchronous adapter is located in C2, the IOP must be located in C1 (except when an IXS is installed). If an IXS is installed, it must be located in C2/C3, the asynchronous adapter must be located in C5, and the IOP can be located in C1 or C4, if needed. Console support using a LAN connection is provided by the embedded port only.
570	C4 or C6	C2	When your LAN adapter is located in C4 or C6, the IOP must be located in C3 (when using an IOP-driven IOA). When your asynchronous adapter is located in C2, the IOP must be located in C1. If an IXS is installed, it can be located in C4/C5, the LAN adaptor or asynchronous adapter can be located in C6, and the IOP can be located in C3, if needed. If there are multiple CECs, the CEC with the load source DASD is used for console support.
595			This model requires an HMC. Tagging the desired IOA directly is used to specify the console instead of by card location.

Notes:

This note applies to the IBM System i5 520, 525, and 515 models that are not managed by an HMC and have an IOA that does not require an IOP. For the 520, you can install PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0) so that your system can have asynchronous adapters located in multiple slots simultaneously, including locating the 2793 asynchronous adapter in slot C4. Slot C4 allows an IOA that does not require an IOP. For the 525 and 515, these PTFs should already be installed.
With these PTFs, you are able to select an individual asynchronous adapter for use with the console and remote service by using either a native macro or the console service functions (65+21). The console and remote service functions must all remain on a single asynchronous adapter. If you have a system that was shipped with Licensed Internal Code (LIC) prior to V5R4M5, you cannot select slot C4 for use with the console when using the 2793, but you can select slot C4 for use with remote service.

Example: If you have an asynchronous adapter located in both C2 and C3 for use by Operations Console (direct), you can choose to use either slot for console and remote service, without having to remove the asynchronous adapter from the other slot.
If you are using i5/OS® Version 5 Release 4 Modification 5 or later, both network (LAN) and asynchronous communications adapters can be individually selected using the OPSCONSOLE macro or console service functions (65+21).
If you plan to use a 5706/5707 adapter in a card slot, you must disable support for the embedded Ethernet port by using the OPSCONSOLE macro or console service functions (65+21).

For more information about adapters, see Configuration tables for IBM System i5 and eServer i5 system units and expansion units.

These systems do not support a remote control panel directly attached to the server. However, you can use the virtual control panel or the remote control panel connected over LAN for most control panel functions. For more information, see Remote and virtual control panels.

Operations Console (direct) cable requirements

To connect your local console that is directly attached, you must use the correct cable, 97H7557 or 39J5835. The 39J5835 cable complies with the European Union Directive 2002/95/EC on the Restriction of the Use of Certain Hazardous Substances in Electrical and Electronic Equipment. For more information, see Installing an Operations Console cable.

Related information: Step 1. Cabling the Operations Console to your server

Operations Console (direct) PC communications port requirement

To use the configuration wizard to configure Operations Console (direct) successfully, you must verify that you have an available communications port. You will need a connector for a serial port communications interface. Operations Console supports serial COM ports 1-9. One COM port is required for system console support.

Notes:

Operations Console does not use any embedded serial ports located on the server.
These systems do not support a remote control panel directly attached to the server. For other connectivity options, see Remote and virtual control panels.

To check that you have an available communications port, view the documentation for your PC or check with the PC manufacturer. Also, when you configure Operations Console, the wizard searches for a port for the console.

The use of a Universal Serial Bus (USB) to serial port adapter is supported with Operations Console. The adapter is placed at the PC end of the console serial cable and connects to the USB port on the PC. When installing the USB adapter, follow the manufacturer's instructions. The operating system then assigns a serial port to that adapter, COM 4, for example. This adapter is used exclusively for the console. Operations Console supports serial COM ports 1-9.

Important: The adapter must plug directly into a USB connector on the PC. Neither the use of a USB hub to share connections nor the use of USB extension cables is supported. However, these devices might function correctly in some situations.

If a failure occurs with your adapter, you can try another adapter. You can also contact the manufacturer of the adapter or your PC, or contact your hardware service provider.

Related information: Remote and virtual control panels

PC processor and memory requirements

Use the following table to ensure that your PC is ready for Operations Console. If you are using iSeries® Navigator, see Requirements for installing iSeries Navigator. For updated PC requirements, see the iSeries Access for Windows® Web site.

Table 2. Processor and memory requirements
Operating System (1,2)	Operations Console PC
Microsoft Windows Vista (Local console on a network (LAN) configuration only)	Pentium® 800 MHz 512 MB memory minimum
Microsoft Windows XP Professional	Pentium 500 MHz (P6 or equivalent compatible microprocessor) 256 MB memory minimum
Microsoft Windows 2000	Pentium 500 MHz recommended 128 MB memory minimum (256 MB recommended)