There are several important items to consider when planning to use Operations Console for one or more servers.
Read through the following considerations specifically for servers with and without a Hardware Management Console (HMC), and then the considerations for all servers.
Servers without an HMC
Servers with an HMC
All servers
When a server is not managed by an HMC, and the support for the default embedded Ethernet port has been disabled, the console-supporting hardware is required to be located in specific slot locations based on the server model. For Operations Console (LAN), there might be more than one location that can support a console. When more than one location is available for a server model, the locations are listed from highest priority to lowest priority when the console searches for console-capable hardware resources. By default, the first embedded Ethernet port is used for a local console on a network (LAN).
Also, the 5706/5707 adapters are able to run without an IOP. If you do not want to use the embedded Ethernet port, a 5706/5707, or either for the console, you can selectively turn this support on or off by following the steps in Disabling support for the default embedded Ethernet port or 5706/5707 adapters. You can also use the OPSCONSOLE native macro or the console service functions (65+21) to disable this support. For more information on either of these options, see Troubleshooting using the OPSCONSOLE macro or Using the console service functions (65+21).
When a server is not managed by an HMC, it is possible to have more than one console adapter available for activation. For example, the console type is set for Operations Console (LAN) and has a device connected and is the system console. If an Operations Console (Direct) adapter is also activated, the corresponding device can also connect at the same time. However, this device cannot become the console and only displays the Console Information Status window. Each of the adapters are dedicated to their designated function and are not available for use in i5/OS.
For the IBM System i5 520 models with IOPless functionality, but are not managed by an HMC, you can install either PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0) to allow your system the ability to have asynchronous adapters located in multiple slots simultaneously. These PTFs also include allowing the 2793 asynchronous adapter to be located in the IOPless slot C4. After you install these PTFs, you will be able to select an individual asynchronous adapter for use with the console, Electronic Customer Support (ECS), and remote service by using either a native macro or the console service functions (65+21). The console, ECS, and remote service functions must all remain on a single asynchronous adapter. Slot C4 cannot be selected for use with the console when using the 2793, but it can be selected for use with ECS and remote service.
Models i5/5xx support tagging only at an IOA level. The biggest advantage of this is that you can now specify the specific adapter to use for your console. If you need to change the console type, you can make the change without an IPL in most cases. For more information on how to change the console, see Changing consoles, interfaces, and terminals.
For more information about making console type changes without an IPL, see Changing console tags without an IPL.
The console tag requires an IOA to be specified. The Operations Console tag is required if you are using a directly connected console, if you are configuring for a directly connected backup console, or if you are using an asynchronous communications adapter for remote service. Tagging the IOA allows you to select the specific adapter used for the Operations Console. Therefore, if multiple console-capable adapters exist in the IOP, only the selected console-capable adapter is used for the console. Tagging the IOA automatically sets the console type during the IPL following the partition profile update.
You can use the HMC command window to specify the tag. This allows the change to be used immediately, although you might have to force the system to determine the new console in some instances. This can be performed using the same command window, the OPSCONSOLE native macro, or the console service functions (65+21). For more information on how to change the console, see Changing consoles, interfaces, and terminals.
For more information about making console type changes without an IPL, see Changing console tags without an IPL.
Not all console-supported adapters can run without the need for an IOP. The IOPless adapters supported with an Operations Console are the 5706/5707 adapters. When using these adapters, you can locate the LAN adapters in any of the remaining slots on your server if your server supports IOPless operation and is managed by an HMC. If the system is not managed by an HMC, the 5706/5707 LAN adapter must be located in one of the designated card locations that supports a local console on a network (LAN). Only the first port of this adapter can be used for the console. If you elect to use this adapter instead of the default embedded Ethernet port, you must disable the embedded port before the system can use the adapter. To disable support for the default embedded Ethernet port, see Disabling support for the default embedded Ethernet port or 5706/5707 adapters.
If no console type is specified, such as when a new partition is being created, the supporting hardware tagged by the HMC is used. If there is no HMC, then the console is determined by any eligible adapters by location. If more than one eligible adapter is found, then the first connected device determines the console. In the case of a server without an HMC, for example, if you use Operations Console (Direct) and you have a LAN adapter that is available to support a console, and has a valid configuration, then the console is the directly attached PC. However, the LAN adapter is started at IPL time and the connecting PC, one or multiple, displays the Console Information Status window. The option to take over the console displays NO and the message at the bottom of the screen indicates that this device is not the supported console type.
The service interface is a single adapter used for service tools. For a local console that is directly attached, if there is no network adapter selected, either by location or partition tagging, then this is the service interface. More commonly it is a network adapter to support either a local console on a network or the service tools server. In the case where there is a valid network adapter available, even if another console is selected and there is a valid service host name associated with the adapter, then this is the service interface. It can support a console, the service tools server, or both.
There might be times when the console is not connected using this network adapter, but the service tools server is configured to support iSeries™ Navigator's interface for hard disk drive configuration or similar functions. In this case the adapter is not capable of supporting a line description for use in i5/OS. It is possible that you can have a local console that is directly attached using a 2793 adapter, for example, and a 2849 network adapter configured for service tools server. Both of these adapters are then dedicated to support their respective function and not available in i5/OS.
Do not place your console adapter on the same IOP as storage devices. Having a dedicated IOP for the console adapter and one for the storage devices reduces possible connectivity problems. For example, during very heavy usage of storage devices, the console might appear to stop working temporarily. If this happens, it should resume operation shortly. If you must place the console adapter on shared resources, keep the other usages to a minimum for better console reliability and enable the console option, Allow console to be taken over by another console.
New servers and partitions are most likely using distribution media from IBM® and therefore, the only service tools device ID available is QCONSOLE. If you need to perform a recovery installation of a server or partition with the initialize option (scratch installation) and are using IBM distribution media, you only have QCONSOLE available. If you elect not to use QCONSOLE, or the configured connection (at the PC) is using a different service tools device ID, then you are forced to delete and re-create the configuration so that QCONSOLE can be used.
In a partitioned environment, alternate console refers to a twinaxial console connected to a different IOA or IOP that is tagged as the alternate console. The console tag must also specify a twinaxial console. An alternative console gives you an added layer of protection because if the system detects a failure of the primary console during an attended IPL, it automatically tries the alternate console's tagged resource. It is important to remember that tagging the same resource as the console and alternate console can result in an inability to select a console at all. For more information on using Operations Console as a console in the event that a twinaxial console is not available, see Backup console for i5/OS.
If you use Operations Console (LAN), you must create a service host name (interface). After this is created, the server is also ready to use the service tools server, for example, to support iSeries Navigator functions. However, you can have a network adapter for the service tools server when the console is something other than Operations Console (LAN). To do this, you need to configure the service host name (interface) so that the service tools server uses that connection. With a configured network adapter available at IPL, the system activates the adapter that supports the console, but also activates the adapter used for the service host name, if different. In this scenario, you now have two dedicated resources in your system that cannot be used by i5/OS. Conversely, if you previously had a service host name for iSeries Navigator and are now using Operations Console (LAN), you do not have to make any IP configuration changes because the same resource is used.
The console takeover and recovery function allows one local console on a network (LAN) to take control of the server from another local console on a network (LAN). This basic function is not available for any other console type. However, with this option there is also some recoverability. The HMC has the ability to share a console connection but does not actually perform the takeover. For more information, see Console takeover and recovery.
If you use Operations Console (LAN) with multiple PCs configured to become the console, all of these PCs are actively connected at IPL time. There is no way to know which PC will become the console because the first one connected will be the active console. If you enabled the console option, Allow console to be taken over by another console, then you are able to take over the console at the PC you want to use.
The maximum number of active emulator sessions available per PC is limited to 26. Active emulator sessions are identified by a single letter of the English alphabet (A through Z). You can have more than 26 configured connections, but only 26 of those sessions can be active. During the course of using these connections, you can close the emulator for a connected configuration to free up an emulator identifier. The next emulation session started can then use that identifier.
Another limitation for multiple connected emulators on the same PC is the amount of available PC resources, memory and video capability, to support a large number of connections. Since each connection and associated functions (console, control panel, or both) will use PC resources, you might need to add more memory to support more connected sessions. Each PC's hardware, operating system, and active programs vary so that there is no clear way to identify, in advance, how many sessions your particular usage supports.