Change From One Console Type To Another - IBM eServer iSeries Manual

Access for windows operations console
Hide thumbs Also See for eServer iSeries:
Table of Contents

Advertisement

the only valid console after the console mode change. When the network problem is fixed, the LAN
|
|
connected devices would go directly to the Console Information Status screen and would not be able to
take control as the console without changing the console mode back to LAN. Take over is not available
|
when a device is directly connected as the console since only one connection of this type is allowed by
|
|
the server.
Another consideration for choosing the method to change the console mode will be the availability of
|
|
another workstation. If you are installing using the console then the only method available to you is the
console service functions (65+21).
|
|
Scenario: How to recover the console during a D-mode IPL with take over enabled: In this scenario you might
|
be installing Licensed Internal Code as part of a system recovery action and the configured console was a
local console on a network. However, the device did not become active and you have an A6005008 SRC
|
|
code. The system is large and it takes a long time to get to this point and you do not want to start over.
The proper asynchronous communications adapter is available without further configuration changes so
|
you could use the console service functions (65+21) to change the console mode. This automatically starts
|
|
the communications adapter associated with the local console directly attached to the server. If you want
to use the PC you were using for the network-attached console, you simply disconnect the network
|
configuration and create (or use a previously created configuration) a local console directly attached to
|
|
the server configuration. Once the console service functions (65+21) has successfully completed, you
connect the directly attached configured connection. This device should become the console automatically
|
and you will be at the step originally expected. If the network failure preceded the old console getting
|
|
the language screen, the new console will present that screen. If the failure happened after you started an
action the new console will either be running that action or the action may be complete, in which case
|
you will see the results of that action.
|

Change from one console type to another

|
If you already have a console connection, you can change to a different type of console in the following
|
ways.
|
Change from a local console directly attached to a local console on a network
|
|
Use these instructions to migrate from a local console directly attached to the server to a local
|
console on a network.
|
Change from a local console on a network (LAN) to a local console directly attached
Use these instructions to migrate from a local console on a network to a local console directly
|
attached to the server.
|
|
Change from a twinaxial console to an Operations Console
Use these instructions to migrate from a twinaxial console to Operations Console.
|
|
Change from an Operations Console to a twinaxial console
Use these instructions to migrate from Operations Console to a twinaxial console.
|
Tips:
|
|
Electronic customer support
If you are currently using electronic customer support and you need to directly attach your console, you
|
must move the electronic customer support cabling to another communications port before trying to
|
|
install an Operations Console local console directly attached to the server. For more information, see
Electronic customer support.
|
|
Note: This may require you to change the resource information used for electronic customer support.
|
As part of your migration, you may need to Deactivate the LAN card from use by Operations Console.
65
Operations Console

Advertisement

Table of Contents
loading

Table of Contents