IBM E Server i Series User manual

iSeries
iSeries Access for Windows
Operations Console
ERserver


iSeries
iSeries Access for Windows
Operations Console
ER s e r v e r


© Copyright International Business Machines Corporation 2002, 2003. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.

Contents
Part 1. Operations Console .....1
Chapter 1. What’s new for V5R2 ....3
Chapter 2. Print this topic .......5
Chapter 3. Plan for Operations Console 7
Plan for your configuration .........7
Plan for your backup console ........8
Scenarios: Select your configuration .....10
Prepare for your network environment ....15
Secure your Operations Console configuration. . 15
Plan for your Operations Console migration . . . 20
Migrate from a local console directly attached to
alocalconsoleonanetwork(LAN).....21
Migrate from a twinaxial console to Operations
Console...............24
Migrating from an Operations Console to a
twinaxial console ...........27
Plan for your Operations Console install or upgrade 30
Plan for your control panel .........31
Chapter 4. Set up Operations Console 33
Complete the setup prerequisite checklist ....33
Set up a local console directly attached to the
server ...............33
Set up a local console directly attached to the
server with remote access allowed......35
Setupalocalconsoleonanetwork.....37
Set up a local console through dial-up support 38
Set up a remote console through dial-up support 40
Complete required prerequisite tasks ......41
Run prerequisite checking program .....43
Meet Operations Console hardware requirements 43
Meet Operations Console software requirements 44
Meet Operations Console cable requirements . . 45
Verify available communications port.....47
Install iSeries Access for Windows ......47
Install AS400 Operations Console Connection
Modem...............48
InstallPCmodem...........51
Confirm installation of TCP/IP on the PC . . . 53
InstallDial-upNetworkingonthePC ....53
Install or configure Remote Access Service (NT
only) ...............54
Install Microsoft service pack .......57
Set up the server for a local console through
dial-up...............57
Grant remote access ..........64
Create and configure incoming connections. . . 65
Install an Operations Console cable .....67
Configure Operations Console on the PC . . . 68
Chapter 5. Manage Operations Console 71
Manage your console configuration ......71
Change a console configuration.......72
Delete a console configuration .......73
Connect a local console to a server .....74
Connect a remote console to a local console by
modem ...............76
Control tasks between users ........77
Change keyboard definitions .......83
Start the system using a manual IPL .....83
Activate the communications line on the server 84
Deactivate the communications line on the server 84
Dial the server ............85
Manage your multiple consoles........85
Manage your local console on a network ....87
Considerations for changing the service tools
deviceIDpasswords..........87
Changing the service tools device ID password
on the PC and server ..........88
Change the access password........88
Resynchronize the PC and service tools device ID
password..............89
Create service tools device IDs on the server . . 92
Configure a service host name .......93
Deactivate or move the LAN card from use by
Operations Console...........94
Changing network values for Operations Console
(LAN)...............95
Chapter 6. Troubleshoot Operations
Console connections ........97
Troubleshoot status messages ........97
Status messages when configuration is running
normally..............98
Status messages when you have connection
problems..............99
Troubleshoot connection problems ......100
Local console connection problems .....100
Remote console connection problems ....106
Troubleshoot authentication problems .....107
Authentication errors ..........107
Internal authentication errors when connecting
Windows 98/Me remote consoles to Windows
2000 ...............108
Authentication errors with Windows NT Service
Pack6...............108
Troubleshoot emulator problems .......108
Local console emulator goes to Disconnected
state...............108
PC5250 window does not display user data . . 108
Troubleshoot system reference code (SRC) data . . 109
SRCs A6005001, A6005004, A6005007, B6005001,
B6005004, and B6005007 .........109
System reference code A6005008 and B6005008 110
System reference code A9002000 ......111
System reference code A6005082 ......111
© Copyright IBM Corp. 2002, 2003 iii

Failure to display D1008065 and D1008066
automatically after calling the function ....111
IPL step C6004031 takes longer than expected 111
Troubleshoot remote control panel and virtual
control panel problems ..........111
Remote control panel fails to start .....112
Unable to use the mode function ......112
Troubleshoot configuration wizard problems . . . 112
Local console does not detect cables .....113
Old network data interfering with
reconfiguration of network connectivity . . . 113
Console options not available in configuration
wizard...............113
Unable to find correct modem at Add RAS
Device selection ...........114
Troubleshoot other Operations Console problems 114
Operations Console remains in QCTL ....114
Local console receives message: Remote Access
Service server did not start ........115
System requests will not work.......115
Chapter 7. Related information ....117
iv iSeries: iSeries Access for Windows Operations Console

Part 1. Operations Console
You can interact with your iSeries
™
through a console. Use iSeries Operations
Console as a system console to access and administer your iSeries.
Operations Console is an installable component of iSeries Access for Windows
®
.It
allows you to use one or more PCs to access and control, either remotely or locally,
the iSeries console and control panel functions.
Operations Console uses 5250 emulation provided by either iSeries Access for
Windows or IBM
®
Personal Communications to emulate a console. To emulate an
iSeries control panel, Operations Console provides a graphical remote control panel
or virtual control panel. Operations Console can use a local area network (LAN),
TCP/IP-based connectivity in addition to direct cable attachment, and dial-up
connections to enable communications between an iSeries server and a PC. It
supports dial-in connections from remote PCs to PCs that are directly attached to
iSeries servers. These remote PCs can then function as an iSeries console. A local
console through dial-up support enables communications to iSeries servers running
without a local console. These PCs can then function as iSeries consoles.
This topic provides you with information and instructions to plan, set up, and
manage Operations Console:
What’s new for V5R2
New Operations Console functions and enhancements.
Print this topic
Print a PDF of all the information included in the Operations Console topic.
Plan for Operations Console
Plan for your Operations Console configuration with scenarios and
information on security, migration, upgrades, and control panels.
Set up Operations Console
Complete required setup tasks for your Operations Console configuration
with personal checklist.
Manage Operations Console
Maintain and operate Operations Console after you have successfully
installed it.
Troubleshoot Operations Console connections
Solve connection, authentication, and emulator problems when using
Operations Console.
Related information
View additional information related to Operations Console.
Operations Console support is available on V4R5 and later releases of the OS/400
operating system. The only type of PC console that IBM iSeries Models 270, 810,
820, 825, 830, 840, 870, and 890 support is Operations Console.
© Copyright IBM Corp. 2002, 2003 1

Enhanced authentication and data encryption provide network security for console
procedures. Operations Console network connections uses a version of Secured
Sockets Layer (SSL), which supports device and user authentication but without
using certificates.
Before using this information and the product it supports, be sure to read the
information in Safety and Environmental Notices and Electronic Emission Notices
for Class A products and Class B products.
2iSeries: iSeries Access for Windows Operations Console

Chapter 1. What’s new for V5R2
New functions for Operations Console include:
Virtual control panel
Virtual control panel support is the recommended alternative to the parallel
cable remote control panel.
Improved Configuration Wizard
The Installation Wizard has been redesigned and new graphics have been
added to improve usability. Comprehensive help text has been added to the
configuration wizard.
PC prerequisite checking program
A pre-installation program is available to help you ensure the PC you choose
will have all of the prerequisite function needed to support Operations
Console.
Support for Windows XP
Operations Console now supports the Windows XP Professional Operating
System.
Enhancements for Operations Console include:
Documentation
The Operations Console topic now includes your planning, setup, managing,
and troubleshooting information in one location. The iSeries Operations Console
Setup, SC41–5508, is no longer available for releases V5R2 and later.
Additional hardware support
Operations Console has added adapter support for feature codes 2742 and
2793.
Error messages
Additional error messages have been added to the configuration wizard.
Terminology
Changes have been made to the configuration terminology to clarify
configuration data.
Table 1. Terminology changes
Previous term New term
Stand-alone local controlling system (LCS) Local console directly attached to the server
LCS with remote support Local console directly attached to the server
with remote access allowed
LAN LCS Local console on a network
Dial-up LCS Local console through dial-up support
Remote controlling system (RCS) Remote console through dial-up support
Discontinued functions for Operations Console include:
© Copyright IBM Corp. 2002, 2003 3

Support for Windows 95 dropped
Operations Console no longer supports Windows 95.
Support for 4xx and 5xx models dropped
Operations Console no longer supports models 4xx and 5xx.
4iSeries: iSeries Access for Windows Operations Console

Chapter 2. Print this topic
To view or download the PDF version, select Operations Console (about 713 KB or
116 pages).
To save a PDF on your workstation for viewing or printing:
1. Open the PDF in your browser (click the link above).
2. In the menu of your browser, click File.
3. Click Save As...
4. Navigate to the directory in which you would like to save the PDF.
5. Click Save.
If you need Adobe Acrobat Reader to view or print this PDF, you can download a
copy from the Adobe Web site
(www.adobe.com/prodindex/acrobat/readstep.html) .
© Copyright IBM Corp. 2002, 2003 5

6iSeries: iSeries Access for Windows Operations Console

Chapter 3. Plan for Operations Console
Before you begin setting up your Operations Console, you should determine how
to best configure your Operations Console:
Plan for your configuration
Planning information assists you in selecting the correct configuration; this
topic includes scenarios and graphics.
Plan for your Operations Console migration
Planning information assists you in migrating from one Operations Console
choice to another.
Plan for your Operations Console upgrade
Planning information assists you in upgrading your Operations Console
configurations from previous releases.
Plan for your control panel
Planning information assists you in selecting a remote control panel or a
virtual control panel.
After you complete the planning requirements, you can create a setup checklist
that lists the Operations Console prerequisite. For more information, see Set up
Operations Console.
Plan for your configuration
The information in this section illustrates the connectivity allowed by the various
types of Operations Console configurations. The scenarios offer specific
configurations to help you select a console configuration. If you plan ahead, you
can include additional features in your configuration.
Plan for your backup console
Plan for your backup console in the event of hardware or network failures.
Scenarios: Select your configuration
Scenarios help you decide which configuration will work in your
environment.
Prepare for your network environment
Plan for your minimum network configurations.
Secure your Operations Console configuration
Plan for your Operations Console network security.
Prepare for your Operations Console and iSeries Navigator configuration
Plan for how Operations Console works with iSeries Navigator.
Important:
vOperations Console allows multiple connections to a single iSeries server, but
only one 5250 session can have control of an iSeries server at a time. It also
allows multiple local console connections but allows only one local console
© Copyright IBM Corp. 2002, 2003 7

directly attached to the server configuration (or local console directly attached to
the server with remote access allowed). There is a maximum of 26 emulator
sessions available per PC.
vIf you call a service representative to set up your new server, you must have the
PC that you are going to use as a console ready to be connected to your iSeries
server. 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 OS/400
®
partition running
Linux, see Configure the LAN console for a guest partition.
Plan for your backup console
This topic covers backup console information you might want to consider to
quickly recover from the unexpected loss of your console. Many system plans
include a level of redundancy to allow for hardware failures, but some do not
consider the console in those plans. Here are some suggestions if you would like to
plan for a backup for your console:
Operations Console, both direct attached and network (LAN) and twinaxial
workstations can coexist as console devices if you remember these rules:
vOnly one device can be active at a time. An active console is a command
interface to an iSeries server (5250 emulation) that is currently interacting with
the server.
vA twinaxial workstation on any twinaxial work station controller with port 0
(address 0 or 1 or with port 1 (address 0 or 1) can be a console device.
vTo prevent interactions between eligible console types, be sure you do not have
more than one workstation available during an IPL. To prevent a device enabled
as an Operations Console from becoming the console, you need to disconnect
any active connections and leave it disconnected during the IPL. For twinaxial
workstations, it is suggested that you power off the workstation. Note that on
some models the on/off switch actually only powers off the display portion of
the workstation and the workstation electronics are still active, which would
allow the device to become the console. If you are not sure, remove the power
cord from the rear of the workstation.
vFor independent and primary partitions, multiple IOPs capable of supporting a
console workstation can interfere with the selection of the desired LAN adapter.
Consider the following:
–Having a 2nd IOP on the bus before your intended console adapter card,
when the first IOP contains a twinaxial adapter card, will 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 2nd IOP, such as C06 or C07.
–Typically, the card location used for Operations Console directly attached
configurations, commonly referred to as the ECS slot, is located close to the
beginning of the bus. When the card location is a low number such as C02,
then C03 is farther from the beginning of the bus than C02. When the card
location is a higher number such as C07, then C06 is farther from the
beginning of the bus than C07. This may not be true for all models and
expansion units. When in doubt contact your service representative.
Considerations for a backup console:
8iSeries: iSeries Access for Windows Operations Console

vThe adapter location is fixed or at least limited for independent servers or
primary partitions. Based on your server’s hardware requirements you may have
limited choices of console types. Try to accommodate at least one additional
console type, if possible.
vFor secondary partitions consider:
–In an LPAR environment, the term alternate console is referring to a console
type located in another IOP tagged as the alternate console. If a failure of the
primary console is detected, the system will automatically try the alternate
console’s IOP. This gives you another level of protection. Tagging a single IOP
as both the primary console and the alternate console does not give you this
protection from an IOP-type failure. Further isolation can be planned by
placing the alternate console IOP on a different bus so that failures of the
primary console’s bus will not prevent a console from being available.
–The current implementation for tagging a console type is only at the IOP
level. Placing two network adapters for the same IOP can sometimes make it
difficult to determine, in advance, which network adapter will be used for the
console. IBM recommends only one network adapter for the IOP tagged as
the primary console to support Operations Console local console on a
network.
–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.
–If the load source storage device fails and the system recovery will include
the use of the IBM distribution Licensed Internal Code media instead of a
customer backup, and the system is using Operations Console (LAN), you
may have to use another console type for the initial portion of the system
recovery.
Planning configuration types for additional backup consoles:
Note: If you plan to use Operations Console local console on a network (LAN) as
a backup to another console type, you must have the console type set to
Operations Console (LAN) and have the associated network adapter
configured prior to needing this device. Setting the console to Operations
Console (LAN) does not prevent an Operations Console (direct) or twinaxial
from becoming the console during an IPL. Just make certain only one
console type is available during the IPL.
Backup console configuration types:
vIf your server is accessed remotely, consider off-site console capability or another
connectivity for the console. A local console on a network can be backed up with
additional local console on a network PC. If the network adapter were to fail,
consider a local console directly attached to the server as a backup. By changing
the console type to a local console directly attached to the server with remote
access, you can add the ability for a remote PC to become the console.
vIn an LPAR or multiple server environment you will most likely be using
multiple local console on a network configurations 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
Chapter 3. Plan for Operations Console 9

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 is not using it until necessary.
vWhen using mostly networked consoles, consider setting up a local console
directly attached to the server 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 server or partition in need of the console. After connecting
the cable, and activating the line, you have a console 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 a network is planned, be certain to create
additional service tools device IDs on the server before you start configuring
the Operations Console PC. Each PC connecting to the same target server or
logical partition must have a unique service tools device ID.
In summary, consider as much redundancy as possible for your console needs. If
you consider ″what if this fails″and you have another route to provide a console,
and also make compromises for the hardware requirements necessary to overcome
the various levels where a failure might occur, you will be reducing your exposure
to a catastrophic console failure condition.
See Managing your multiple consoles for information on the ability to switch
between console devices.
Scenarios: Select your configuration
The following scenarios assists you in choosing your Operations Console
configuration.
Scenario: A single console directly attached to the server without remote
support
A scenario that discusses a situation in which you may want a single console
attached to the server.
Scenario: A single console directly attached to the server with remote
support
A scenario that discusses the ability to dial-in to the console from a remote
location.
Scenario: Consoles for multiple servers or partitions
A scenario that discusses a situation in which you want to manage multiple
servers or partitions.
Scenario: Directly dial-up a server from a remote location
A scenario that discusses a situation in which you might need to access the
server without a console from a console at a remote location.
The table provides an overview of the advantages and disadvantages of each
scenario.
10 iSeries: iSeries Access for Windows Operations Console

Table 1. Scenario configuration
Advantages and
Disadvantages
Scenarios
A single console
directly attached
to the server
without remote
support
A single console
directly attached
to the server
with remote
support
Consoles for
multiple servers
or partitions
Directly dial up
a server from a
remote location
Requires cable
hardware
Yes Yes No No
Supports
connections from
another location
No Yes No Yes
Must be in the
server room to
access the
console
Yes Yes No No
Easily manage
multiple servers
or partitions
No No Yes No
Can access
iSeries console
and perform
control panel
functions, or
both.
Yes Yes Yes No
Access in the
event of a
network failure
Yes Yes No Yes
Scenario: A single console directly attached to the server
without remote support
Your company owns an iSeries server and you want to use a PC to manage your
server. You need one console physically or directly connected to the iSeries server
to physically access the console to manage your iSeries.
For this scenario, you should configure a local console directly attached to the
server. See Set up Operations Console to complete an interview that will produce a
checklist specific to your configuration.
Advantages:
vThe administrator will have access to his console in the event of a network
failure. With a local console on a network configuration, a network failure will
cause you to lose the ability to access your console.
Chapter 3. Plan for Operations Console 11

vYou can use this PC to become the iSeries console, to perform control panel
functions, or both provided you have a control panel cable, or you set up virtual
control panel support. For more information, see the Plan for your control panel.
vThe console can be securely placed behind locked doors in the server room.
Disadvantages:
vIt can be cumbersome to manage multiple servers or partitioned servers with
this configuration.
vYou must be close to the server to manage or access the console.
vA console cable and a remote control panel cable is required to support their
corresponding functions.
vThis configuration does not support remote connections. If you desire remote
connections, see Scenario: A single console directly attached to the server with
remote support.
vThis configuration does not support remote control panel function for secondary
partitions.
vOnly one directly attached configuration is allowed per PC.
Scenario: A single console directly attached to the server with
remote support
Your company owns an iSeries server and you want to use a PC to manage your
server. You need a console connected to this iSeries server that will allow you to
manage the console from a remote 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, configure a local console directly attached to the server with
remote access allowed on the PC attached to the server.
12 iSeries: iSeries Access for Windows Operations Console

Then configure a remote console through dial-up on the remote PC. See Set up
Operations Console to complete an interview that will produce a checklist specific
to your configuration.
Advantages:
vThe administrator will not have to be near the server to perform console tasks.
vControl panel functions can be performed from a remote location provided they
are set up on a local console PC.
vYou can use this PC as the iSeries console, to perform control panel functions, or
both.
vThe remote console can gain access to the iSeries server with or without operator
invention depending on your choices during the configuration wizard.
Disadvantages:
vOnly one incoming connection is allowed at a time.
vThe local PC must be running Windows NT
®
, Windows 2000, or Windows XP.
Windows 98/Me PCs cannot be used to support the remote console.
vYou need a console cable and a remote control cable to support their
corresponding functions. For more information, see Meet Operations Console
cable requirements.
vOnly one directly attached configuration is allowed per PC.
Scenario: Consoles for multiple servers or partitions
Your company owns an iSeries server and you want to use the PC to manage your
server. You need to manage multiple iSeries or partitioned servers from one
console. You have a secured network that you can configure your console on.
For this scenario, configure a local console on a network. See Set up Operations
Console to complete an interview that will produce a checklist specific to your
configuration.
Advantages:
vYou can configure a single PC to be the console for several different servers or
partitions as long as they are connected to the service connection network.
vThe administrator will not need to be physically near the server to manage the
console.
vSecurity features are available to protect your console connections.
vIf you ordered Operations Console local console on a network, your iSeries
should already be configured for this console type.
Chapter 3. Plan for Operations Console 13

vA local console on a network is the connectivity of choice for secondary
partitions in an LPAR environment. For more information on consoles on
partitioned servers, see Plan for logical partitions.
vMultiple PCs can be configured as the console to a server or partition, but only
one can be active at a time.
Disadvantages:
vNo console is available in the event that a network failure takes place unless a
backup console is in place. Configure a local console directly attached to the
server or a twinaxial console for backup. For more information, see Plan for
your backup console.
vYou will need a separate LAN card to be used by the console. For more
information, see Meet Operations Console hardware requirements.
Scenario: Directly dial-up a server from a remote location
Your company owns an iSeries server but plan to manage it from a remote
location. There will be no local console connected to the server locally.
For this scenario, a local console through dial-up support should be configured.
See Set up Operations Console to complete an interview that will produce a
checklist specific to your configuration. This method has severe restrictions and
should be considered carefully.
Advantage:
vThe server is managed remotely, reducing the skill necessary to interact with the
server during daily activities.
Disadvantage:
vA remote PC can only dial into the iSeries server if there is an operator at the
iSeries allowing the PC console access.
vThe modem on the server needs to be operational.
vThe remote control panel and virtual control panel is not supported.
vA temporary console is necessary, locally, to set up the server properly.
vIn the event of a communications line drop any jobs running on the server that
was submitted by the remote console will be terminated abnormally. Also,
someone will be needed at the server to re-establish the connection.
vPlacing the server in restricted mode from the console dialed into the server
carry additional risks in the event of a communications line drop. This could
result in a necessary IPL to recover.
14 iSeries: iSeries Access for Windows Operations Console