IBM i Series User manual

System i
Connecting to System i
Operations Console
Version 6 Release 1


System i
Connecting to System i
Operations Console
Version 6 Release 1


Note
Before using this information and the product it supports, read the information in Appendix A,
“Notices for software topics,” on page 105 and the IBM Systems Safety Information manual,
G229-9054.
This edition applies to version 6, release 1, modification 0 of IBM i5/OS (product number 5761–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, 2008.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
|
|
|

Safety and environmental notices
Safety notices
Safety notices may be printed throughout this guide:
vDANGER notices call attention to a situation that is potentially lethal or extremely hazardous to
people.
vCAUTION notices call attention to a situation that is potentially hazardous to people because of some
existing condition.
vAttention notices call attention to the possibility of damage to a program, device, system, or data.
World Trade safety information
Several countries require the safety information contained in product publications to be presented in their
national languages. If this requirement applies to your country, a safety information booklet is included
in the publications package shipped with the product. The booklet contains the safety information in
your national language with references to the U.S. English source. Before using a U.S. English publication
to install, operate, or service this product, you must first become familiar with the related safety
information in the booklet. You should also refer to the booklet any time you do not clearly understand
any safety information in the U.S. English publications.
Laser safety information
IBM®System i®models and System p®servers can use I/O cards or features that are fiber-optic based
and that utilize lasers or LEDs.
Laser compliance
All lasers are certified in the U.S. to conform to the requirements of DHHS 21 CFR Subchapter J for class
1 laser products. Outside the U.S., they are certified to be in compliance with IEC 60825 as a class 1 laser
product. Consult the label on each part for laser certification numbers and approval information.
CAUTION:
This product might contain one or more of the following devices: CD-ROM drive, DVD-ROM drive,
DVD-RAM drive, or laser module, which are Class 1 laser products. Note the following information:
vDo not remove the covers. Removing the covers of the laser product could result in exposure to
hazardous laser radiation. There are no serviceable parts inside the device.
vUse of the controls or adjustments or performance of procedures other than those specified herein
might result in hazardous radiation exposure.
(C026)
CAUTION:
Data processing environments can contain equipment transmitting on system links with laser modules
that operate at greater than Class 1 power levels. For this reason, never look into the end of an optical
fiber cable or open receptacle. (C027)
CAUTION:
This product contains a Class 1M laser. Do not view directly with optical instruments. (C028)
© Copyright IBM Corp. 2000, 2008 iii

CAUTION:
Some laser products contain an embedded Class 3A or Class 3B laser diode. Note the following
information: laser radiation when open. Do not stare into the beam, do not view directly with optical
instruments, and avoid direct exposure to the beam. (C030)
Product recycling and disposal
This unit must be recycled or discarded according to applicable local and national regulations. IBM
encourages owners of information technology (IT) equipment to responsibly recycle their equipment
when it is no longer needed. IBM offers a variety of product return programs and services in several
countries to assist equipment owners in recycling their IT products. Information on IBM product
recycling offerings can be found on IBM’s Internet site at http://www.ibm.com/ibm/environment/
products/prp.shtml.
Esta unidad debe reciclarse o desecharse de acuerdo con lo establecido en la normativa nacional o local
aplicable. IBM recomienda a los propietarios de equipos de tecnología de la información (TI) que reciclen
responsablemente sus equipos cuando éstos ya no les sean útiles. IBM dispone de una serie de programas
y servicios de devolución de productos en varios países, a fin de ayudar a los propietarios de equipos a
reciclar sus productos de TI. Se puede encontrar información sobre las ofertas de reciclado de productos
de IBM en el sitio web de IBM http://www.ibm.com/ibm/environment/products/prp.shtml.
Note: This mark applies only to countries within the European Union (EU) and Norway.
Appliances are labeled in accordance with European Directive 2002/96/EC concerning waste electrical
and electronic equipment (WEEE). The Directive determines the framework for the return and recycling
of used appliances as applicable throughout the European Union. This label is applied to various
products to indicate that the product is not to be thrown away, but rather reclaimed upon end of life per
this Directive.
In accordance with the European WEEE Directive, electrical and electronic equipment (EEE) is to be
collected separately and to be reused, recycled, or recovered at end of life. Users of EEE with the WEEE
marking per Annex IV of the WEEE Directive, as shown above, must not dispose of end of life EEE as
unsorted municipal waste, but use the collection framework available to customers for the return,
recycling, and recovery of WEEE. Customer participation is important to minimize any potential effects of
EEE on the environment and human health due to the potential presence of hazardous substances in EEE.
For proper collection and treatment, contact your local IBM representative.
Battery return program
This product may contain sealed lead acid, nickel cadmium, nickel metal hydride, lithium, or lithium ion
battery. Consult your user manual or service manual for specific battery information. The battery must be
recycled or disposed of properly. Recycling facilities may not be available in your area. For information
on disposal of batteries outside the United States, go to http://www.ibm.com/ibm/environment/
products/batteryrecycle.shtml or contact your local waste disposal facility.
In the United States, IBM has established a return process for reuse, recycling, or proper disposal of used
IBM sealed lead acid, nickel cadmium, nickel metal hydride, and other battery packs from IBM
Equipment. For information on proper disposal of these batteries, contact IBM at 1-800-426-4333. Please
have the IBM part number listed on the battery available prior to your call.
iv System i: Connecting to System i Operations Console

For Taiwan: Please recycle batteries.
For the European Union:
Note: This mark applies only to countries within the European Union (EU).
Batteries or packaging for batteries are labeled in accordance with European Directive 2006/66/EC
concerning batteries and accumulators and waste batteries and accumulators. The Directive determines
the framework for the return and recycling of used batteries and accumulators as applicable throughout
the European Union. This label is applied to various batteries to indicate that the battery is not to be
thrown away, but rather reclaimed upon end of life per this Directive.
In accordance with the European Directive 2006/66/EC, batteries and accumulators are labeled to
indicate that they are to be collected separately and recycled at end of life. The label on the battery may
also include a chemical symbol for the metal concerned in the battery (Pb for lead, Hg for mercury and
Cd for cadmium). Users of batteries and accumulators must not dispose of batteries and accumulators as
unsorted municipal waste, but use the collection framework available to customers for the return,
recycling, and treatment of batteries and accumulators. Customer participation is important to minimize
any potential effects of batteries and accumulators on the environment and human health due to the
potential presence of hazardous substances. For proper collection and treatment, contact your local IBM
representative.
For California: Perchlorate Material - special handling may apply. See www.dtsc.ca.gov/hazardouswaste/
perchlorate.
The foregoing notice is provided in accordance with California Code of Regulations Title 22, Division 4.5
Chapter 33. Best Management Practices for Perchlorate Materials. This product/part may include a
lithium manganese dioxide battery which contains a perchlorate substance.
Safety and environmental notices v

vi System i: Connecting to System i Operations Console

Contents
Safety and environmental notices . . . iii
Safety notices ..............iii
Operations Console .........1
What’s new for V6R1 ...........1
PDF file for Operations Console ........2
Planning considerations for Operations Console . . 2
Planning considerations for your configuration . . 2
Console planning considerations......3
Planning considerations for your backup
console .............5
Verification of Operations Console requirements 7
Operations Console hardware requirements 7
Operations Console software requirements . 9
Operations Console cable requirements . . 10
Verification of available communications
port ..............11
Planning considerations for your Operations
Console installation or upgrade......11
Preparation for your network environment . . 13
Security of your Operations Console
configuration ............14
Preparation for your Operations Console and
System i Navigator configuration .....18
Scenarios: Selecting your configuration . . . 20
Scenario: A single console directly attached
to the system without remote support . . 20
Scenario: Consoles for multiple systems or
partitions ............20
Planning considerations for your control panel 22
Remote control panel .........22
Virtual control panel .........23
Limitations of the virtual control panel . . 23
Installing the virtual control panel....24
PC preparations for Operations Console .....27
Completing the setup prerequisite checklist. . . 28
Setting up a local console directly attached to
the system.............28
Completing prerequisite checklist for
Windows 2000: Local console directly
attached to the system........28
Completing prerequisite checklist for
Windows XP: Local console directly
attached to the system........28
Setting up a local console on a network . . . 28
Completing prerequisite checklist for
Windows 2000: Local console on a network. 29
Completing prerequisite checklist for
Windows XP: Local console on a network . 29
Completing prerequisite checklist for
Windows Vista: Local console on a network 29
Completing required prerequisite tasks ....29
Installing System i Access for Windows . . . 29
Applying System i Access for Windows
service packs ...........30
Installing Operations Console connection
modem ..............31
Installing Operations Console connection
modem for Windows 2000 ......31
Installing Operations Console connection
modem for Windows XP .......32
Installing an Operations Console cable . . . 32
Configuring Operations Console on the PC . . 34
Configuring a local console on a network
(LAN) .............35
Configuring a local console directly
attached to the system........37
Managing Operations Console ........40
Takeover or recovery of an Operations Console
connection..............40
Takeover details ...........41
Recovery details ...........42
Enabling console takeover .......42
Scenarios: Takeover and recovery .....43
Scenario: LAN connected devices only with
takeover enabled .........43
Scenario: A normal IPL and
dual-connectivity configurations with take
over enabled ...........44
Scenario: Recovery of a console requiring a
new console type setting .......45
Scenario: How to recover the console
during a D-mode IPL with take over
enabled.............45
Managing your console configuration.....46
Connecting a local console to a system . . . 46
Connecting to another system .....46
Changing a console configuration .....46
Changing a local console .......47
Changing a local console on a network
(LAN) .............47
Deleting a console configuration .....47
Deleting a local console .......47
Windows 2000/XP users .......48
Changing the value of the autocreate device
ID option .............48
Using the Properties page .......48
Customizing the Operations Console window 49
Management of multiple consoles ......50
Multiple local PC consoles on a network . . 50
Switching from one console type to another
when a console is currently available ....51
Switching from one console type to another
when the current console is not operational . 51
Changing from one console type to another . . 52
Changing from a local console directly
attached to a local console on a network
(LAN) ..............52
© Copyright IBM Corp. 2000, 2008 vii
|
||
|
||
|
||

Changing the console from a local console
directly attached to a local console on a
network (LAN) in a nonpartitioned or
primary partitioned system ......53
Changing the console from a local console
directly attached to a local console on a
network in a logical partition .....53
Configuring the PC to use the new console
type when changing from a local console
directly attached to a local console on a
network ............55
Changing from a local console on a network
(LAN) to a local console directly attached . . 56
Changing the console from local console on
a network (LAN) to a local console directly
attached for a nonpartitioned system or a
primary partition .........56
Changing the console from local console on
a network (LAN) to a local console directly
attached for a logical partition .....58
Configuring the PC to use the new console
type ..............59
Changing from a twinaxial console to an
Operations Console..........61
Changing the console from a twinaxial
console to an Operations Console in a
nonpartitioned or primary partitioned
system .............61
Changing the console from a twinaxial
console to an Operations Console in a
logical partition ..........62
Configuring the PC to use the new console
type after changing from a twinaxial
console to an Operations Console ....63
Changing from an Operations Console to a
twinaxial console ..........64
Changing the console from an Operations
Console to a twinaxial console in a
nonpartitioned or primary partitioned
system .............64
Changing the console from an Operations
Console to a twinaxial console in a logical
partition ............65
Performing optional steps on the PC when
changing from an Operations Console to a
twinaxial console .........66
Managing your local console on a network . . . 67
Operations Console simplification .....67
Considerations for changing the service tools
device ID passwords .........69
Changing the service tools device ID
password on the PC and system .....69
Changing the access password ......70
Resynchronizing the PC and service tools
device ID password .........70
Resetting the service tools device ID
password on the system .......71
Resetting the service tools device ID
password on the PC ........73
Creating service tools device IDs on the
system ..............74
Configuring a service host name (interface
name) ..............75
Deallocating or moving the LAN adapter card
from use by Operations Console .....77
Changing network values for Operations
Console (LAN) ...........78
Completing the PC changes ......80
Common tasks ............80
Changing keyboard definitions ......80
Starting the system using a manual IPL . . . 81
Using the console service functions (65+21). . 82
Using the OPSCONSOLE macro .....84
Unlocking service tools device IDs in SST . . 84
Method 2: Unlocking the service tools
device IDs ............85
Changing the mode of the emulator between
3179 and 3477 ...........85
Troubleshooting Operations Console connection . . 86
Troubleshooting status message.......87
Status messages when configuration is
running normally ..........87
Status messages when you have connection
problems .............88
Troubleshooting connection problems.....89
Local console connection problems ....89
Console fails to connect .......89
Network connection errors ......90
Error message: The connection to the
system is not a secure connection ....90
Local console status remains Connecting . 90
Console fails to connect and port detection
fails ..............91
Performance degradation on local console 91
Unable to make a connection when infrared
devices are installed ........91
Unexpected disconnections ......91
Using HyperTerminal to validate
connectivity between client and the system . 91
Troubleshooting authentication problems . . . 94
Authentication errors .........94
Troubleshooting emulator problems .....94
PC5250 window does not display user data . 94
Troubleshooting system reference code data . . 95
System reference code A6nn500x .....95
System reference code A6005001, A6005004,
and A6005007 ...........95
System reference code A6005008 .....96
System reference code A6005082 .....97
System reference code A9002000 .....97
System reference code D1008065 .....98
Failure to display D1008065 and D1008066
automatically after calling the function . . . 98
IPL step C6004031 takes longer than expected 99
Troubleshooting remote control panel and virtual
control panel problems .........99
Remote control panel fails to start .....99
Unable to use the mode function .....99
Authentication problems .......100
Troubleshooting configuration wizard problems 101
Local console does not detect console cable 101
viii System i: Connecting to System i Operations Console
||
|
||
||

Old network data interfering with
reconfiguration of network connectivity . . 101
Troubleshooting other Operations Console
problems ..............101
Operations Console remains in QCTL . . . 101
System requests do not work ......102
Unable to sign on because of a lost or
expired password or disabled user ID . . . 102
The user cannot perform the option selected 102
Related information for Operations Console . . . 102
Appendix A. Notices for software
topics...............105
Programming interface information ......106
Trademarks ..............107
Terms and conditions...........107
Appendix B. Notices for hardware
topics...............109
Electronic emission notices .........110
Class A Notices............110
Contents ix
||
||

xSystem i: Connecting to System i Operations Console

Operations Console
The Operations Console acts as a system 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 the System i Access
for Windows®licensed program. 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 System i Access for Windows or IBM
Personal Communications to emulate a console. To emulate a system control panel, Operations Console
provides a graphical remote control panel or virtual control panel. To enable communications between a
system and a PC, Operations Console can use a local area network (LAN) and TCP/IP connections, or
can use direct cable attachment. These remote PCs can then function as a console, which allows easier
system management and access.
Operations Console support is available with i5/OS®V5R3, or later. IBM iSeries®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 a variety 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 V6R1
Read about new or significantly changed information for the Operations Console topic collection.
Simplified console setup for network connected consoles
The initial console setup process is more automated in this release. During the setup, the system
automatically detects some of your system settings, for example, the system serial number or your IP
address if the system is capable of providing it.
The traditional setup wizard is still available for use, if the system is not able to be contacted.
Models not supported
As of i5/OS V6R1, the following hardware models are no longer supported: models 270, 820, 830, and
840.
How to see what’s new or changed
To help you see where technical changes have been made, the information center uses:
vThe image to mark where new or changed information begins.
vThe image to mark where new or changed information ends.
© Copyright IBM Corp. 2000, 2008 1
|
|
|
|
|
|

In PDF files, you might see revision bars (|) in the left margin of new and changed information.
To find other information about what’s new or changed this release, see the Memo to users.
PDF file for Operations Console
You can view and print a PDF file of this information.
To view or download the PDF version of this document, select Operations Console (1,105 KB).
Saving PDF files
To save a PDF on your workstation for viewing or printing:
1. Right-click the PDF link in your browser.
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 a free
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 a setup checklist that will list the
Operations Console prerequisites for your system.
Related concepts
“PC preparations for Operations Console” on page 27
After you complete the planning requirements and know which configuration and PC operating
system you will be using, you can go through one of the predefined checklists for setting up
Operations Console. You can also create a customized checklist and complete that.
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 a console configuration
most suited to your needs. If you plan ahead, you can include additional features in your configuration.
Important:
vIf you call a service representative to set up your new system, the PC that you are going to
use as a console must be 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 System i Access for Windows installed on the PC.
vIf you are configuring Operations Console for an i5/OS logical partition that runs the
Linux®operating system, see the Configuring the LAN console for a logical partition topic.
Related information
Configure the LAN console for a logical partition
2System i: Connecting to System i Operations Console

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 a new 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 a selected console type, then the first
console workstation to connect will be configured to become the console.
vThere is also a special 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 a special 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.
vOperations 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 a time.
– A twinaxial workstation on any twinaxial workstation controller adapter with port 0 (addressed
either 0 or 1) or port 1 (addressed either 0 or 1) can become a console 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 a single system or logical partition, but only
one 5250 session can have control of a system at a time. An active console is the command interface to
a system 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
actually active.
vIBM System i5®and eServer™i5 models start counting logical partitions from 1 (even if it is the only
partition) instead of 0. iSeries 8xx models start counting logical partitions from 0. For the console to
connect properly, 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 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 for a single PC.
vThere is a maximum 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.
The following information pertains to console takeover and recovery:
For i5/OS V5R3, or later, there is a special set of functions known as console takeover and recovery,
which allows a LAN-connected Operations Console to take control from another console device. Use the
Operations Console 3
|
|
|
|
|
|

following information to help determine what console devices are best for your work environment and
how to deploy these devices to take advantage of these functions.
vTakeover is the process used for a LAN-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 a new 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 a problem with the
console was encountered. The recovery process may be to the same console device or a different
console device and may be facilitated by additional work to enable a device using a different
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 a screen 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 a device. 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 a console that loses a connection 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 a console workstation can interfere with the selection of the
desired LAN adapter. Consider the following:
– Having a second IOP on the bus before your intended console adapter card, when the first IOP
contains a twinaxial adapter card, may fail to provide a LAN-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 a twinaxial adapter preceded this IOP on the bus then the LAN adapter card located at C09 or
C10 will fail to provide a LAN-connected console. The LAN adapter card must be in a location
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 a low number, for example C02, then C03 is further from the
beginning of the bus than C02. When the card location is a high 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 a multi-partitioned environment:
vIf you plan to use Operations Console as your primary console or as a backup 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 a direct 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 a LAN connection.
vWhen more than one console adapter is available for a single 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
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
4System i: Connecting to System i Operations Console
|
|

intended purposes. It is recommended that you install only one console-capable adapter that matches
your configurations for a single 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 a twinaxial 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 a console. If you have a twinaxial adapter in the same IOP as your primary
console’s adapter, consider the twinaxial adapter to be a backup 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 40
You can use these functions to take control of another console device.
“Planning considerations for your backup console”
Most system plans include a level 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 a backup console.
Planning considerations for your backup console:
Most system plans include a level 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 a backup console.
Considerations for a backup 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 a partitioned environment, consider:
– In a logical 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 a failure 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 a single IOP as both the
primary console and the alternate console can result in errors when selecting a console. Further
isolation can be planned by placing the alternate console IOP on a different bus so that failures of
the primary console’s bus cannot prevent a console from being available.
– Models 8xx are tagged for a console type only at the IOP level. Tagging an IOP that has two similar
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, make sure that it only has one console-capable adapter per connectivity (for
example, only one 2849 and one 2771). Each adapter can support a different 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 a 2838 and a 2849 Ethernet adapter reporting to it. They are different adapters but have the
same connectivity for the console.
– Consider a shared resource environment in which you can allocate and deallocate a console
supporting IOP to a partition on a part-time basis. Many work environments rarely need a console
device on a full-time basis and you can reduce your initial cost of dedicated hardware by
implementing this concept.
Operations Console 5
|
|
|
|
|
|
|
|
|
|

– If the load source storage device fails and the system recovery includes the use of the IBM
distribution Licensed Internal Code media instead of a customer 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 a console 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 a LAN as a backup to another console
type, the network adapter must be located in a console designated slot or in a properly
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. A local console on a network can be backed up with an additional local console on a
network PC. If the network adapter were to fail, consider a local console directly attached to the
system as a backup.
vIn a logical partition or multiple-system environment, you will most likely be using multiple local
consoles on a network (LAN) configuration on a single 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 a network configurations in large environments so that each PC has
a core set of console responsibilities and the overlap coverage of backup configurations with each
other. For example, if you have a PC that supports 10 local consoles on a network 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 a third PC and spread the 20 consoles out so that two
PCs back up a portion of each PC’s primary console configurations. Another consideration is a
dedicated PC to be the backup of a certain number of consoles, but not connected until necessary.
vWhen you mostly use consoles on a network, consider setting up a local console directly attached to
the system on a PC and place it on a rollaway cart with a console 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 a console to replace the
currently failed console. This same concept also applies to twinaxial workstations.
Note: If more than one local console on a network 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 a unique service tools device
ID.
In summary, consider incorporating as much redundancy as possible into your console configuration. You
can reduce your exposure to a catastrophic console failure by using another method to provide a console
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.
6System i: Connecting to System i Operations Console

Related reference
“Console planning considerations” on page 3
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 40
You can use these functions to take control of another console device.
“Preparation for your network environment” on page 13
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 a network (LAN)
configuration.
“Management of multiple consoles” on page 50
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 20
This scenario discusses a situation in which you want to manage multiple systems or partitions.
“Takeover or recovery of an Operations Console connection” on page 40
You can use these functions to take control of another console device.
“Preparation for your network environment” on page 13
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 a network (LAN)
configuration.
Verification of Operations Console requirements
Before using Operations Console, ensure that you have met all the hardware, software, and cabling
requirements for Operations Console.
Operations Console hardware requirements:
You need to meet the PC and System i hardware requirements for an Operations Console configuration.
Note: This topic covers only models 8xx and earlier. For models 5xx, go to the Operations Console
hardware requirements topic in the IBM Systems Hardware Information Center.
Table 1. PC requirements - processor and memory
Operating System (1,2) Operations Console PC
Windows 2000 vPentium®500 MHz recommended
v128 MB memory minimum (256 MB recommended)
Windows XP Professional vPentium 500 MHz (P6 or equivalent compatible
microprocessor)
v256 MB memory minimum
Windows Vista vPentium 800 MHz
v512 MB memory minimum
Notes:
1. See the System i Access Web site for any updated PC requirements.
2. If your PC has power management capabilities, it can turn the PC off. The PC might reset the
communications port when power management is started, which can end any connections
already established. Certain types of power management on the PC and in the operating
system might cause system reference code (SRC) 0000DDDD to appear in the System i control
panel or remote control panel. This SRC data should be cleared when PC activity resumes.
3. Windows Vista only supports a local console on a network.
Operations Console 7
|
|
|
|
|
|

Important: IBM System i5 and eServer i5 models start counting logical partitions from 1 (even if it is the
only partition) instead of 0. iSeries 8xx models start counting logical partitions from 0. For the
console to connect properly, 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 system with its
network data.
If you want to use an Operations Console local console on a network (LAN), you need to install the LAN
adapter for Operations Console according to your model. IBM supports a local console on a network
(LAN) only on models 800, 810, 825, 870 and 890. To find out the specifics of your system, you can use
the Display Hardware Resources (DSPHDWRSC) command. Table 2 shows the supported cards for LAN
connectivity. Table 3 shows the correct location for the LAN card.
Note: Supported cards and locations are only for nonpartitioned systems or primary partitions. For
logical partitions in an LPAR environment, any Operations Console-supported adapter can be
used.
Important: In case an emergency arises where your LAN connection fails, you need to configure an
Operations Console local console directly attached to the system. For instructions, see the
Planning considerations for your backup console topic. Table 3 shows the correct location for
the directly cabled console.
Table 2. Supported cards for LAN connectivity
Card name or number Description
2744 PCI 100 Mbps Token ring Adapter
2838 PCI 100/10 Mbps Ethernet IOA
2849 PCI 100/10 Mbps Ethernet IOA
Integrated Ethernet Port PCI 100/10 Mbps Integrated LAN IOA (model 825 only)
Note: The Integrated Ethernet Port is the only LAN-connectivity for the Operations Console local console on a
network option for model 825.
Table 3. System i requirements - LAN card location
Model Operations Console (LAN) - LAN
adapter locations
Operations Console (Direct) -
Asynchronous adapter locations
800, 810 C06, second C05 C07
825 Integrated Ethernet Port (C03, C02,
C01)(1) C06
870, 890 C04, C06, C07, C08, C09 C02
1These locations are only available if the Integrated Ethernet Port is not operational.
Related tasks
“Changing the console from a local console directly attached to a local console on a network (LAN) in
a nonpartitioned or primary partitioned system” on page 53
To change from an Operations Console with local console directly attached to a local console on a
network (LAN), follow these steps on the system, using the existing console.
“Changing the console from a local console directly attached to a local console on a network in a
logical partition” on page 53
To change from an Operations Console with a local console directly attached to a local console on a
network (LAN), follow these steps on the system using the existing console.
“Changing the console from a twinaxial console to an Operations Console in a nonpartitioned or
primary partitioned system” on page 61
To change from a twinaxial console to an Operations Console, you must use the existing console to
complete these steps on the system.
8System i: Connecting to System i Operations Console
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|||
||
|
|
|||
|
|