IBM System i User manual

System i
Connecting to System i
Operations Console
Version 5Release 4


System i
Connecting to System i
Operations Console
Version 5Release 4


Note
Before using this information and the product it supports, read the information in “Notices,” on
page 113.
Seventh Edition (February 2006)
This edition applies to version 5, release 4, modification 0of IBM i5/OS (product number 5722–SS1) and to all
subsequent releases and modifications until otherwise indicated in new editions. This version does not run on all
reduced instruction set computer (RISC) models nor does it run on CISC models.
©Copyright International Business Machines Corporation 2000, 2006. All rights reserved.
US Government Users Restricted Rights –Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.

Contents
Operations Console .........1
What’s new for V5R4 ...........1
Printable PDFs..............2
Planning considerations for Operations Console ..3
Planning considerations for your configuration ..3
Console planning considerations......4
Planning considerations for your backup
console ..............6
Scenarios: Selecting your configuration ...8
Scenario: Asingle console directly attached
to the system without remote support ...8
Scenario: Asingle console directly attached
to the system with remote support ....9
Scenario: Consoles for multiple systems or
partitions ............10
Preparation for your network environment ..11
Security of your Operations Console
configuration ............13
Preparation for your Operations Console and
iSeries Navigator configuration ......16
Verification of Operations Console
requirements ............18
Operations Console hardware requirements 18
Operations Console software requirements 21
Operations Console cable requirements ..21
Verification of available communications
port ..............22
Planning considerations for your Operations
Console installation or upgrade.......23
Planning considerations for your control panel 24
Remote control panel .........25
Virtual control panel .........26
Limitations of the virtual control panel ..26
Installing the virtual control panel ....27
PC preparations for Operations Console .....30
Completing the setup prerequisite checklist...30
Setting up alocal console directly attached to
the server .............31
Completing prerequisite checklist for
Windows 2000: Local console directly
attached to the server ........31
Completing prerequisite checklist for
Windows XP: Local console directly
attached to the server ........31
Setting up alocal console directly attached to
the server with remote access allowed ...31
Completing prerequisite checklist for
Windows 2000: Local console directly
attached to the server with remote access
allowed.............31
Completing prerequisite checklist for
Windows XP: Local console directly
attached to the server with remote access
allowed.............32
Setting up alocal console on anetwork ...32
Completing prerequisite checklist for
Windows 2000: Local console on anetwork.32
Completing prerequisite checklist for
Windows XP: Local console on anetwork .32
Setting up aremote console through dial-up
support..............33
Completing prerequisite checklist for
Windows 2000: Remote console through
dial-up support ..........33
Completing prerequisite checklist for
Windows XP: Remote console through
dial-up support ..........33
Completing required prerequisite tasks ....33
Installing iSeries Access for Windows....33
Applying iSeries Access for Windows
service packs ...........34
Installing Operations Console connection
modem ..............35
Installing Operations Console connection
modem for Windows 2000 ......35
Installing Operations Console connection
modem for Windows XP .......36
Installing PC modem .........36
Installing PC modem for Windows 2000 ..36
Installing PC modem for Windows XP ..37
Granting remote access ........37
Granting remote access for Windows 2000 37
Granting remote access for Windows XP..38
Creating and configuring incoming
connections ............38
Creating and configuring incoming
connections for Windows 2000 .....38
Creating and configuring incoming
connections for Windows XP .....39
Installing an Operations Console cable ...39
Cabling amodel 830 or amodel 840
Operations Console.........41
Configuring Operations Console on the PC ..42
Managing Operations Console ........43
Managing your console configuration.....43
Changing aconsole configuration .....43
Changing alocal console .......44
Changing aremote console ......44
Changing alocal console on anetwork
(LAN) .............44
Deleting aconsole configuration .....44
Deleting alocal console .......45
Deleting remote console .......45
Windows 2000/XP users .......45
Connecting alocal console to asystem ...45
Connecting alocal console on anetwork to
asystem ............45
Connecting to another system .....46
Connecting alocal console directly attached
to the system ...........47
©Copyright IBM Corp. 2000, 2006 iii

Connecting aremote console to alocal console
by modem.............48
Control tasks between users .......49
Granting or refusing control to aremote
console .............49
Identifying user in control of asystem ..51
Displaying the remote control panel in
read-only mode ..........52
Requesting and releasing control at the
local console ...........52
Sending amessage to acontrolling remote
console .............53
Requesting control at the remote console 54
Releasing control at the remote console ..54
Sending amessage to acontrolling local
console or remote console ......55
Transferring control between users ...55
Using the Properties page .......56
Customizing the Operations Console window 57
Management of multiple consoles ......58
Multiple local PC consoles on anetwork ..58
Multiple remote consoles through dial-up
support connecting to the same local console
directly attached to the system ......59
Switching from one console type to another
when aconsole is currently available ....59
Switching from one console type to another
when the current console is not operational .60
Takeover or recovery of an Operations
Console connection ..........60
Takeover details ..........61
Recovery details ..........62
Enabling console takeover ......63
Scenarios: Takeover and recovery ....63
Changing from one console type to another ..66
Changing from alocal console directly
attached to alocal console on anetwork
(LAN) ..............66
Changing the console from alocal console
directly attached to alocal console on a
network (LAN) in anon-partitioned or
primary partitioned system ......67
Changing the console from alocal console
directly attached to alocal console on a
network in alogical partition .....67
Configuring the PC to use the new console
type when changing from alocal console
directly attached to alocal console on a
network ............69
Changing from alocal console on anetwork
(LAN) to alocal console directly attached ..70
Changing the console from local console on
anetwork (LAN) to alocal console directly
attached for anon-partitioned system or a
primary partition .........70
Changing the console from local console on
anetwork (LAN) to alocal console directly
attached for alogical partition .....71
Configuring the PC to use the new console
type ..............73
Changing from atwinaxial console to an
Operations Console..........73
Changing the console from atwinaxial
console to an Operations Console in a
non-partitioned or primary partitioned
system .............73
Changing the console from atwinaxial
console to an Operations Console in a
logical partition ..........74
Configuring the PC to use the new console
type after changing from atwinaxial
console to an Operations Console ....76
Changing from an Operations Console to a
twinaxial console ..........76
Changing the console from an Operations
Console to atwinaxial console in a
non-partitioned or primary partitioned
system .............76
Changing the console from an Operations
Console to atwinaxial console in alogical
partition ............77
Performing optional steps on the PC when
changing from an Operations Console to a
twinaxial console .........79
Managing your local console on anetwork ...79
Considerations for changing the service tools
device ID passwords .........79
Changing the service tools device ID
password on the PC and system .....80
Changing the access password ......80
Resynchronizing the PC and service tools
device ID password .........81
Resetting the service tools device ID
password on the system .......81
Resetting the service tools device ID
password on the PC ........83
Creating service tools device IDs on the
system ..............84
Configuring aservice host name (interface
name) ..............85
Deallocating or moving the LAN adapter card
from use by Operations Console .....86
Changing network values for Operations
Console (LAN) ...........87
Completing the PC changes ......89
Common tasks ............90
Changing keyboard definitions ......90
Starting the system using amanual IPL ...90
Activating the asynchronous communications
line on the system ..........91
Deactivating the asynchronous
communications line on the system ....92
Using the console service functions (65+21)..92
Using the OPSCONSOLE macro .....95
Using service tools device IDs in system
service tools ............96
Troubleshooting Operations Console connection ..96
Troubleshooting status message.......97
Status messages when configuration is
running normally ..........97
iv System i: Connecting to System iOperations Console

Status messages when you have connection
problems .............98
Troubleshooting connection problems.....99
Local console connection problems ....99
Console fails to connect .......99
Network connection errors ...... 100
Error message: The connection to the
system is not asecure connection.... 100
Local or remote console status remains
Connecting ........... 100
Console fails to connect and port detection
fails ............. 101
Performance degradation on local console 101
Unable to make aconnection when
infrared devices are installed ..... 101
Unexpected disconnections ...... 101
Using HyperTerminal to validate
connectivity between client and the
system ............ 102
Remote console connection problems ... 104
Remote console through dial-up fails to
connect to local console ....... 104
Local console name mismatch when
remote console connects to the local
console ............ 104
Troubleshooting authentication problems ... 104
Authentication errors ......... 104
Troubleshooting emulator problems ..... 104
PC5250 window does not display user data 105
Troubleshooting system reference code data .. 105
System reference code A6nn500x ..... 105
System reference code A6005001, A6005004,
and A6005007 ........... 105
System reference code A6005008 ..... 106
System reference code A9002000 ..... 107
System reference code A6005082 ..... 108
Failure to display D1008065 and D1008066
automatically after calling the function ... 108
IPL step C6004031 takes longer than expected 108
Troubleshooting remote control panel and
virtual control panel problems....... 108
Remote control panel fails to start .... 108
Unable to use the mode function ..... 109
Authentication problems ....... 109
Troubleshooting configuration wizard problems 109
Local console does not detect console cable 110
Old network data interfering with
reconfiguration of network connectivity ..110
Troubleshooting other Operations Console
problems ..............110
Operations Console remains in QCTL ...110
System requests do not work ......110
Unable to sign on because of alost or expired
password or disabled user ID ...... 111
Appendix. Notices .........113
Trademarks ..............114
Terms and conditions...........115
Contents v

vi System i: Connecting to System iOperations Console

Operations Console
The Operations Console acts as asystem console for you to access and administer your systems.
IBM®facilitates interaction with your systems by providing management consoles that can be accessed
through terminals and PCs. The Operations Console is an installable component of iSeries™Access for
Windows®.Using Operations Console, you can access and control the console and control panel functions
either locally or remotely through one or many PCs, which facilitates many administrative functions.
Operations Console uses 5250 emulation provided by either iSeries Access for Windows or IBM Personal
Communications to emulate aconsole. To emulate asystem control panel, Operations Console provides a
graphical remote control panel or virtual control panel. To enable communications between asystem and
aPC, Operations Console can use alocal area network (LAN) and TCP/IP connections, or can use direct
cable attachment. It supports dial-in connections from remote PCs to PCs that are directly attached to
systems. These remote PCs can then function as aconsole, which allows easier system management and
access.
Operations Console support is available with V5R2 and later releases of the i5/OS®operating system.
IBM iSeries 270 and 8xx models support only Operations Console as their PC console.
Enhanced authentication and data encryption provide network security for console procedures.
Operations Console network connections use avariety of Secured Sockets Layer (SSL), that supports
device and user authentication without certificates.
If you plan to use Operations Console to manage System i™hardware, see the Managing Operations
Console topic collection in the IBM Systems Hardware Information Center.
Related information
Managing Operations Console
What’s new for V5R4
This topic highlights the changes made to the Operations Console topic collection for V5R4.
New system-side functions have been added in V5R4 to make it easier to manage your system using
Operations Console.
The system no longer requires apassword when creating adevice ID. Systems can now accept console
service functions in D-mode even in the event that there is an uninitialized disk unit present. Asystem
can now force an exit at C6004508 in D-mode with function 21 if needed.
The take over and recovery option takes effect immediately now. Also, take over and recovery functions
are supported in D-mode now. The Console Information Status window during console take over or
recovery has been changed to make it easier to see if Take over the console is YES or NO.Finally, the
DST signon window associated with take over /recovery (ATTENTION: This device can become the
console)no longer has any PF keys since the only function allowed is signon.
Only iSeries 270 and 8xx are supported. This means that only parallel direct attached RPC can be used.
Also, in V5R4, older SPD-bus cards are no longer supported even in migration towers. The code is still in
place so that users can take advantage of it, however there is no support for its usage.
Client-side functionality also has some added features for Operations Console.
©Copyright IBM Corp. 2000, 2006 1

Operations Console now has more functions and additions to client-side functions to make it easier to
use. In V5R4 there now are more descriptive error and status messages to facilitate management and
troubleshooting. The Operations Console client now no longer requires apassword when specifying a
device ID.
Operations Console functions more easily on your network. It allows for the user to specify the base IP
address of the console connection.
Operations Console no longer supports Windows NT®in V5R4.
How to see what’s new or changed
To help you see where technical changes have been made, this information uses:
vThe
image to mark where new or changed information begins.
vThe
image to mark where new or changed information ends.
To find other information about what’s new or changed this release, see the Memo to Users.
Printable PDFs
Use this to view and print aPDF of this information.
To view or download the PDF version of this document, select Operations Console (1,105 KB).
Manuals
vSetting Up Your Twinaxial System
The twinaxial console uses acommand line interface to access and manage your System ienvironment,
and it does not require the use of apersonal computer to act as aconsole. You access the System i
platform through aconsole screen, akeyboard, and twinaxial cables.
Web site
viSeries Access Web site
This web site includes online product information about iSeries Access and Operations Console.
Other information
viSeries Access for Windows: Installation and setup
This topic describes how to install and configure iSeries Access for Windows on both the system and
the PC. Installation and configuration are necessary on both the system and the PC.
vControl panel
Operate the system by directly manipulating the control panel. You can use the control panel to turn
on or off the system, perform an initial program load (IPL), or determine processor activity.
vLogical partitions
Logical partitions let you distribute resources within asingle system to make it operate as if it were
two or more independent systems.
vUpgrade your iSeries
This topic describes how to upgrade hardware features, upgrade to adifferent system model, or
upgrade to amore current release of the i5/OS operating system. During an upgrade, the source
system and the target system keep the same serial number.
vData migrations
2System i: Connecting to System iOperations Console

This topic describes how to migrate data from one system or partition to another system or partition.
When performing adata migration, the source system and the target system must have different serial
numbers.
vPlanning for your physical environment
Good planning is essential for the successful setup and use of your system. It ensures that you have
everything you need and meet all prerequisites. The planning information in this topic helps you place
the system, plan power needs, print any special cabling or setup instructions, meet any PC
requirements, and prepare for unique configurations based on how you will use the system (for
example, clustering of systems, Internet connections, and rack mounting).
vPrint server and rack cabling instructions
Cabling instructions are available to print for your system.
Saving PDF files
To save aPDF on your workstation for viewing or printing:
1. Right-click the PDF in your browser (right-click the link above).
2. Click the option that saves the PDF locally.
3. Navigate to the directory in which you want to save the PDF.
4. Click Save.
Downloading Adobe Reader
You need Adobe Reader installed on your system to view or print these PDFs. You can download afree
copy from the Adobe Web site (www.adobe.com/products/acrobat/readstep.html) .
Planning considerations for Operations Console
Before you begin setting up your Operations Console, determine how to best configure it.
After you complete the planning requirements, you can create asetup checklist that will list the
Operations Console prerequisites for your system.
Related concepts
“PC preparations for Operations Console” on page 30
After you complete the planning requirements and know which configuration and PC operating
system you will be using, you can create and go through achecklist for setting up Operations
Console.
Planning considerations for your configuration
To plan for your Operations Console configuration, you need to find out the specific connectivity types
that are allowed by the various Operations Console configurations.
The scenarios included offer specific configurations examples to help you select aconsole configuration
most suited to your needs. If you plan ahead, you can include additional features in your configuration.
Important:
vIf you call aservice representative to set up your new system, you must have the PC that
you are going to use as aconsole ready to be connected to your system. This includes
having all cables ready and all software installed. For example, you must already have
your Windows operating system and iSeries Access for Windows installed on the PC.
vIf you are configuring Operations Console for an i5/OS logical partition running the
Linux®operating system, see the Configure the LAN console for aguest partition topic.
Related information
Operations Console 3
|
|
|

Configure the LAN console for alogical partition
Console planning considerations
When you plan for Operations Console for one or more of your systems, consider these points.
The following information applies to all systems:
vUnlike previous versions of i5/OS, this release and subsequent releases will support only the console
type that is currently configured. If no console type is specified, such as when anew logical partition is
being created, the supporting hardware IOP specified during the creation process takes precedence. If
the available hardware contains more than one adapter for aselected console type, then the first
console workstation to connect will be configured to become the console.
vThere is also aspecial set of console options called Allow console recovery and console can be taken
over by another console.This set of functions allows Operations Console to take control from another
console device. The default value of this console option is disabled.
–When the option is enabled:
The first Operations Console device connected becomes the console. Additional LAN-connected
Operations Console devices will have aspecial DST signon.
All other 5250-based connections will have the new Console Information Status window.
Console recovery without the loss of the job is available.
–When the option is disabled:
All 5250-based connections will be presented the new Console Information Status window.
Console recovery without the loss of the job is not available.
v
Operations Console, both direct attached and network (LAN), and twinaxial workstations, can coexist
as console devices if you remember these rules:
–Only one device can be active at atime.
–Atwinaxial workstation on any twinaxial workstation controller adapter with port 0(addressed
either 0or 1) or port 1(addressed either 0or 1) can become aconsole device if twinaxial console is
the console type selected. If twinaxial console is selected as the console type then Operations
Console devices may not be started.
vOperations Console allows multiple LAN connections to asingle system or logical partition, but only
one 5250 session can have control of asystem at atime. An active console is the command interface to
asystem through 5250 emulation or IBM Personal Communications that is currently interacting with
the system. More than one Operations Console device might have data on the screen but only one is
truly active.
vIBM System i5™and eServer™i5 models start counting logical partitions with the number 1(even if it
is the only partition) instead of a0. iSeries 270 and 8xx models start counting logical partitions with
the number 0. For the console to connect properly, your logical partitions must also begin numbering at
1instead of 0. This is especially true if you rely on the BOOTP process to configure the system with its
network data.
vThe client PC also allows multiple local console connections but allows only one local console directly
attached to the system configuration (or local console directly attached to the system with remote
access allowed) for asingle PC.
vThere is amaximum of 26 Operations Console emulator sessions available per Operations Console PC
client.
vTry to avoid putting your Operations Console on the same IOP as the storage devices.
–There might be configurations when this cannot be avoided.
–During very heavy usage of storage devices, the console might appear to stop working temporarily,
but it should resume operation shortly. If the console is placed on the same IOP as the storage
devices, enable the console option Allow console recovery and console can be taken over by
another console.
4System i: Connecting to System iOperations Console
|
|
|
|
|
|
|
|
|
|
|
|
|
|

The following information pertains to console takeover and recovery:
In V5R4 and later releases, there is aspecial set of functions known as console take over and recovery,
that allows aLAN-connected Operations Console to take control from another console device. Use the
following information to help determine what console devices are best for your work environment and
how to deploy these devices to take advantage of the new functions.
vTakeover is the process used for aLAN-connected console device to take control from the current
console device. The user signed on to the PC that wishes to take control requires special authority and
is initiating the takeover from anew menu. This takeover function is not used for directly attached
consoles.
vRecovery is the process of regaining control of the job running on the console after aproblem with the
console was encountered. The recovery process may be to the same console device or adifferent
console device and may be facilitated by additional work to enable adevice using adifferent
connectivity. The exception is twinaxial console which does not use the same type of 5250 emulation
and thus cannot recover the console without data loss.
When the takeover option is enabled and the device is properly connected, each console capable device
running 5250 emulation, regardless of connectivity, will be presented ascreen of data regardless of
whether or not it is the active console. In V5R3 and later releases, more than one device will have data on
the screen after the console has been established. There will be no more blank console screens showing
Disconnected when initially connecting adevice. The new function now allows the job at the console to
be transferred to another device without causing loss of data.
This function is accomplished by suspending the data stream to aconsole that loses aconnection or is
being taken over, save further data and then send that data to the next device to become the console,
even if the device is the same former console. Recoverability is essentially taking over the console from
the same or different qualified device regardless of what the former console was doing.
The following information pertains to independent and primary partitions:
vConsole supporting hardware may be required to be located in specific slot locations, based on model.
vMultiple IOPs capable of supporting aconsole workstation can interfere with the selection of the
desired LAN adapter. Consider the following:
–Having asecond IOP on the bus before your intended console adapter card, when the first IOP
contains atwinaxial adapter card, may fail to provide aLAN-connected console. For example, a
model 890 uses eligible card locations C04, and C06 through C10 and if an IOP were placed in C08
and atwinaxial adapter preceded this IOP on the bus then the LAN adapter card located at C09 or
C10 will fail to provide aLAN-connected console. The LAN adapter card must be in alocation
preceding the second IOP, such as C06 or C07.
–Typically, the card location used for Operations Console directly attached configurations, commonly
referred to as the Electronic Customer Support (ECS) slot, is located close to the beginning of the
bus. When the card location is alow number, for example C02, then C03 is further from the
beginning of the bus than C02. When the card location is ahigh number, for example C07, then C06
is further from the beginning of the bus than C07. There may be exceptions to this numbering
scheme based on specific models and expansion units. Contact your service representative if you
have questions about the placement of the ECS.
The following information pertains to amulti-partitioned environment:
vIf you plan to use Operations Console as your primary console or as abackup console, you must tag
the IOP to support the primary console and Electronic Customer Support (slot), even if you do not
plan to use Electronic Customer Support. For example, if you are planning to use Operations Console
on adirect connection, you must tag an IOP with the console tag and the ECS tag. These steps are also
necessary if you are planning to use Operations Console with aLAN connection.
vWhen more than one console adapter is available for asingle IOP, the adapter with the lowest bus
address will be chosen for use by Operations Console. For example, you tag an IOP that has two LAN
Operations Console 5

adapters installed. The system will use the first adapter found on the bus. However, during an IPL the
first adapter may not be ready in time and the system could select the second adapter. This could
prevent the console from starting immediately or you might not be able to use that resource for your
intended purposes. It is recommended that you install only one console-capable adapter that matches
your configurations for asingle IOP. This situation also will affect asynchronous adapters used by a
local console directly attached to the system.
vThe term alternate console is referring to atwinaxial console type located in another IOP tagged as the
alternate console. Operations Console and HMC type consoles do not use resources tagged as the
alternate console.
Note: Tagging the same IOP as both the primary console and the alternate console may result in the
inability to select aconsole. If you have atwinaxial adapter in the same IOP as your primary
console’s adapter, consider the twinaxial adapter to be abackup console, not an alternate
console. You only have to change the console type to take advantage of the twinaxial adapter for
the console.
Related reference
“Takeover or recovery of an Operations Console connection” on page 60
You can use these functions to take control of another console device.
“Planning considerations for your backup console”
Most system plans include alevel of redundancy to allow for the event of hardware failures; however,
many people do not consider the console in their plans. To recover quickly from an unexpected loss of
your console, you need to plan for abackup console.
Planning considerations for your backup console
Most system plans include alevel of redundancy to allow for the event of hardware failures; however,
many people do not consider the console in their plans. To recover quickly from an unexpected loss of
your console, you need to plan for abackup console.
Considerations for abackup console
vThe adapter location is fixed, or at least limited, for independent systems or primary partitions. Based
on your system’s hardware requirements, you might have limited choices of console types. Try to
accommodate at least one additional console type, if possible.
vConsider using the take over and recovery option as part of your backup console strategy. However,
the hardware used for the new console type must exist and be available at the time of recovery.
vIf you are working in apartitioned environment, consider:
–In alogical partition environment, the term alternate console refers to the twinaxial console type
located in another input/output processor (IOP) that is tagged as the alternate console. If afailure of
the primary console (twinaxial only) is detected, the system automatically tries the alternate
console’s IOP. This function gives you another level of protection. Tagging asingle IOP as both the
primary console and the alternate console can result in errors when selecting aconsole. Further
isolation can be planned by placing the alternate console IOP on adifferent bus so that failures of
the primary console’s bus cannot prevent aconsole from being available.
–Models 270 and 8xx are tagged for aconsole type only at the IOP level. Tagging an IOP that has two
alike console adapters reporting to it, for example two 2849s or two 2771s, for the same IOP can
sometimes make it difficult to determine, in advance, which adapter will be used for the console.
When tagging the IOP, be sure that it only has one console-capable adapter per connectivity. For
example, only one 2849 and one 2771. Each adapter can support adifferent console type but only
one adapter type should be present. The lowest addressed adapter on the bus is attempted first. But
if that adapter is slow in reporting to the system, another adapter might get selected instead, when
two adapters of the same connectivity are present. Another example of this might be that the IOP
has both a2838 and a2849 Ethernet adapter reporting to it. They are different adapters but have the
same connectivity for the console.
6System i: Connecting to System iOperations Console
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|

–Consider ashared resource environment in which you can allocate and deallocate aconsole
supporting IOP to apartition on apart-time basis. Many work environments rarely need aconsole
device on afull-time basis and you can reduce your initial cost of dedicated hardware by
implementing this concept.
–If the load source storage device fails and the system recovery includes the use of the IBM
distribution Licensed Internal Code media instead of acustomer backup, and the system is using
Operations Console (LAN), you might have to use another console type for the initial portion of the
system recovery.
Configuration types for backup consoles
When planning the configuration of the backup console or consoles remember that recovering from the
loss of the console depends on many factors. Some of these factors include, the model and series, the
hardware resources available, the previous console type, and the intended console type. Recovery might
consist of repairing the currently failed console or temporarily replacing it with another console type.
Most changes of aconsole type can be performed without the need for an IPL but there may be
circumstances in which an IPL will still be necessary. When using the console service functions (65+21),
console-supporting hardware must be installed and available prior to performing the function. Any
partition tagging of resources must also have been done already.
Important: If you plan to use Operations Console local console on aLAN as abackup to another console
type, the network adapter must be located in aconsole designated slot or in aproperly
tagged IOP. If not previously configured, the BOOTP process is used to configure the system.
Backup console configuration considerations
vIf you access your system remotely, consider off-site console capability or another type of connectivity
for the console. Alocal console on anetwork can be backed up with an additional local console on a
network PC. If the network adapter were to fail, consider alocal console directly attached to the server
as abackup. By changing the console type to alocal console directly attached to the server with remote
access, you can add the ability for aremote PC to become the console.
vIn alogical partition or multiple-system environment, you will most likely be using multiple local
consoles on anetwork (LAN) configuration on asingle PC as your primary consoles. Consider
additional PCs using this same type configuration. Avoid supporting too many consoles on the same
PC if possible. The PC resources can be easily overwhelmed when supporting multiple consoles and
remote control panels.
vConsider multiple local console on anetwork configurations in large environments so that each PC has
acore set of console responsibilities and the overlap coverage of backup configurations with each
other. For example, if you have aPC that supports 10 local consoles on anetwork configuration and
another PC with the same number of primary consoles for another 10 partitions, instead of backing up
each PC with the other’s configuration, you add athird PC and spread the 20 consoles out so that two
PCs back up aportion of each PC’s primary console configurations. Another consideration is a
dedicated PC to be the backup of acertain number of consoles, but not connected until necessary.
vWhen you mostly use consoles on anetwork, consider setting up alocal console directly attached to
the server on aPC and place it on arollaway cart with aconsole cable. If you have supporting
adapters, you can quickly roll the cart with the PC near the system or partition in need of the console.
After connecting the cable and changing the console type value, you have aconsole to replace the
currently failed console. This same concept can be implemented for twinaxial workstations just as
easily.
Note: If more than one local console on anetwork is planned, be certain to create additional service tools
device IDs on the system before you start configuring the Operations Console PC. Each PC
connecting to the same target system or logical partition must have aunique service tools device
ID.
Operations Console 7
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|

In summary, consider incorporating as much redundancy as possible into your console configuration. You
can reduce your exposure to acatastrophic console failure by using another method to provide aconsole
in place, or by making compromises and adjustments for the various hardware requirements necessary to
overcome the various levels of failures.
For more information on switching between console devices, see the Managing your multiple consoles
topic.
Related reference
“Console planning considerations” on page 4
When you plan for Operations Console for one or more of your systems, consider these points.
“Takeover or recovery of an Operations Console connection” on page 60
You can use these functions to take control of another console device.
“Preparation for your network environment” on page 11
To prepare for your network environment, you need to identify and comply with the minimum
network configuration required to set up an Operations Console local console on anetwork (LAN)
configuration.
“Management of multiple consoles” on page 58
If you have more than one workstation that is capable of being the console to the same system or
partition, there might be more than one way of using those devices as the console, depending on your
configuration and circumstances.
“Scenario: Consoles for multiple systems or partitions” on page 10
This scenario discusses asituation in which you want to manage multiple systems or partitions.
“Takeover or recovery of an Operations Console connection” on page 60
You can use these functions to take control of another console device.
“Preparation for your network environment” on page 11
To prepare for your network environment, you need to identify and comply with the minimum
network configuration required to set up an Operations Console local console on anetwork (LAN)
configuration.
Scenarios: Selecting your configuration
These scenarios help you decide which configuration works best in your environment.
Use the following scenarios to help assist you in choosing your Operations Console configuration. Keep
in mind that these scenarios apply only to nonpartitioned systems.
Scenario: Asingle console directly attached to the system without remote support:
This scenario discusses asituation in which you might want asingle console attached to the system.
Your company owns aSystem iproduct, and you want to use aPC to manage your system. You need
one console directly connected to the system to physically access the console to manage your system.
8System i: Connecting to System iOperations Console

For this scenario, you should configure alocal console directly attached to the system.
Advantages:
vThe administrator will have access to his console in the event of anetwork failure. With alocal console
on anetwork configuration, anetwork failure will cause you to lose the ability to access your console.
vYou can use this PC to become the System iconsole.
vThe console can be securely placed behind locked doors in the system room.
Disadvantages:
vYou must be close to the system to manage or access the console.
vAconsole cable is required.
vThis configuration does not support remote connections.
vThis configuration does not support adirectly connected remote control panel.
vThis configuration does not support remote control panel function for logical partitions.
vOnly one directly attached configuration is allowed per PC.
Related concepts
“PC preparations for Operations Console” on page 30
After you complete the planning requirements and know which configuration and PC operating
system you will be using, you can create and go through achecklist for setting up Operations
Console.
“Planning considerations for your control panel” on page 24
To make aconnection to the control panel, you need to configure aremote control panel (RCP) or a
virtual control panel (VCP). All IDs that want access need proper authority.
Related reference
“Scenario: Asingle console directly attached to the system with remote support”
This scenario discusses the ability to dial-in to the console from aremote location.
Scenario: Asingle console directly attached to the system with remote support:
This scenario discusses the ability to dial-in to the console from aremote location.
Your company owns aSystem iproduct, and you want to use aPC to manage your system. You need a
console connected to this system, which allows you to manage the console from aremote location. Then
you can perform an IPL from home over the weekend or check to see if the job you started has
completed.
For this scenario, on the PC attached to the system, configure alocal console directly attached to the
system with remote access allowed.
Operations Console 9
|
|

Then configure aremote console through dial-up on the remote PC.
Advantages:
vThe administrator does not have to be near the system to perform console tasks.
vYou can use this PC only as the System iconsole.
vThe remote console can gain access to the system with or without operator intervention depending on
your configuration.
Disadvantages:
vOnly one incoming connection is allowed at atime.
vAconsole cable is required.
vOnly one directly attached configuration is allowed per PC.
Related concepts
“PC preparations for Operations Console” on page 30
After you complete the planning requirements and know which configuration and PC operating
system you will be using, you can create and go through achecklist for setting up Operations
Console.
Related reference
“Scenario: Asingle console directly attached to the system without remote support” on page 8
This scenario discusses asituation in which you might want asingle console attached to the system.
“Operations Console cable requirements” on page 21
You need to meet these cable requirements for supported models, cables and card locations.
Scenario: Consoles for multiple systems or partitions:
This scenario discusses asituation in which you want to manage multiple systems or partitions.
Your company owns aSystem iproduct, and you want to use the PC to manage your system. You need
to manage multiple systems or partitions from one console. You have asecured network that you can
configure your console on.
10 System i: Connecting to System iOperations Console
|
|

For this scenario, configure alocal console on anetwork.
Advantages:
vYou can configure asingle PC to be the console for several different systems or partitions as long as
they are connected to the service connection network. There are amaximum of 26 active consoles at a
time but you might have avirtually unlimited number of configurations.
vThe administrator does not need to be physically near the system to manage the console.
vSecurity features are available to protect your console connections.
vAlocal console on anetwork is the connectivity of choice for partitions in an LPAR environment.
vMultiple PCs can be configured as aconsole to asystem or partition, but only one PC can act as an
active console at atime.
Disadvantages:
vNo console is available in the event that anetwork failure takes place unless abackup console is
available. Configure alocal console directly attached to the server or atwinaxial console for backup.
vYour system will need aseparate LAN card to be used by the console or other service tools.
Related concepts
“PC preparations for Operations Console” on page 30
After you complete the planning requirements and know which configuration and PC operating
system you will be using, you can create and go through achecklist for setting up Operations
Console.
Related reference
“Operations Console hardware requirements” on page 18
You need to meet the PC and System ihardware requirements for an Operations Console
configuration.
“Planning considerations for your backup console” on page 6
Most system plans include alevel of redundancy to allow for the event of hardware failures; however,
many people do not consider the console in their plans. To recover quickly from an unexpected loss of
your console, you need to plan for abackup console.
Related information
Plan for logical partitions
Preparation for your network environment
To prepare for your network environment, you need to identify and comply with the minimum network
configuration required to set up an Operations Console local console on anetwork (LAN) configuration.
Important: You need to install the LAN adapter for Operations Console according to your model.
Operations Console 11

If your system is new and you chose alocal console on anetwork configuration, the adapter is already
allocated for use by the system. The LAN adapter is dedicated for service tools. It is suggested that you
restrict LAN topologies for LAN-attached local consoles to asingle, physical ring, hub, switch, or router
environment. In the event that the local console on anetwork is used in alarger network topology, it is
suggested that you use broadcast (DHCP) packet filtering. This might be as simple as connecting the PC
and system using acrossover cable or using an inexpensive hub with only the PC and system attached.
When you have only asingle PC or asmall number of devices connected to the system using ahub, and
these devices do not connect to another network or the Internet, you can then use any numeric numbers
for addresses, for example, 1.1.1.x or 10.220.215.x (where xcan be 2through 255, but avoid x.x.x.1,which
might cause problems in some hubs). However, if you have anetwork that many users share, or in which
the devices are connected to the Internet, then you should consult anetwork administrator for addresses.
Network security
It is suggested that you treat the console over aLAN connection with the same physical security
considerations and controls as alocal console directly attached to the system or atwinaxial console. For
instance, consider configuring alocal console on anetwork separate from the main network (or the
company intranet) and strictly controlling access to the PC that acts as the console.
BOOTstrap Protocol
Alocal Operations Console on anetwork uses the BOOTstrap Protocol (BOOTP) to configure the system
service IP communications stack. The IP stack configuration plus the system serial number and the
partition ID are requested in the Operations Console configuration wizard. The system broadcasts a
BOOTP request. The Operations Console PC replies with the information submitted during the
configuration wizard. The system then stores and uses the configuration information for the service IP
communications stack.
The Operations Console PC must be placed on anetwork that can be accessed by the system. This can be
the same physical network or anetwork that permits broadcast packets to flow. This is an initial setup
requirement; normal Operations Console operation does not require this. It is suggested that this setup
occur on the same physical network.
The BOOTP request carries the system serial number and partition ID. The system serial number and
partition ID are used to assign the IP configuration information. If you are having problems configuring
the service IP communications stack, verify that the Operations Console PC is on the same physical
network, and that the system serial number and partition ID are correct in the configuration.
Alocal console on anetwork (LAN) uses ports 2323, 3001, and 3002. To use Operations Console in a
different physical network the router and firewall must allow IP traffic on these ports.
The success of BOOTP is dependent on the network hardware used to connect the system and the PC. In
some cases, you might need adifferent device to configure aconsole connection using system service
tools (SST). To use BOOTP, the network hardware used must be capable of autonegotiation of speed and
duplex when using the 2838 Ethernet Adapter for the Operations Console connection.
Related reference
“Planning considerations for your backup console” on page 6
Most system plans include alevel of redundancy to allow for the event of hardware failures; however,
many people do not consider the console in their plans. To recover quickly from an unexpected loss of
your console, you need to plan for abackup console.
“Operations Console hardware requirements” on page 18
You need to meet the PC and System ihardware requirements for an Operations Console
configuration.
12 System i: Connecting to System iOperations Console
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|