IBM eServer iSeries Manual page 91

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

Advertisement

If you made a change that caused the network IP address or service host name (interface name) to
|
|
be different for the currently configured connections, this change must be reflected on all PCs that
connect to this service host name (interface name). Since you cannot modify the network IP address
|
or service host name (interface name) of an existing connection's configuration on the client you will
|
|
have to delete the current connection and recreate a new connection using the new network IP
address. Continue with step 10.
|
10. Reset the service tools device ID password on the server. To do this, follow these steps:
|
Note: You must unlock the SST option before the option is usable. See Using Service Tools Device
|
IDs in System Service Tools (SST).
|
a. Select Work with DST environment.
|
|
b. Select Service tools device IDs.
|
c. Type 2 in front of the service tools device ID to be reset, and press Enter.
d. Press Enter again to confirm the reset.
|
|
Note: When you reset the password in DST, the device ID password becomes the device ID
name in uppercase. If you will be using a password other than the device name, you will
|
have to delete the current device ID and create a new ID with your desired password.
|
|
Important: If more than one PC connects to this service host name (interface name) using a
network connection you will have to delete the configurations and therefore reset the service
|
tools device IDs of those PCs as well. To reset another service tools device ID, repeat this step.
|
|
e. Press F3 until the DST main menu appears.
|
11. There are 2 methods for completing the necessary work in order to allow a new IP address or service
host name (interface name). The first is using an IPL. This is the recommended method because you
|
will have more control over when you do the remaining work on the PC. The system will continue
|
|
to use the old values until an IPL or manual intervention. The second method is to perform the
manual intervention, at this time. Perform one of the sets of steps below to complete the network
|
changes.
|
|
v Using an IPL
|
This method requires that the client reconfiguration be complete prior to establishing the next
connection using Operations Console on a network. If you are currently using the console
|
connected via LAN you would normally start an IPL, it is recommended that the IPL be an
|
|
attended IPL, and you can reconfigure the client during the initial stages of the IPL. You could, for
example, use a different PC as the console instead of the one you currently have connected. You
|
|
could do the configuration on that PC using the steps here, then after the IPL has been started you
|
could disconnect the current console PC's connection and start a connection on the other PC with
the newly created configuration. In this manner you could reconfigure the existing client at your
|
|
leisure, before the next reconnection to the server.
|
a. Start an attended IPL on the server. See Start the system using a manual IPL.
b. Go to Completing the client changes.
|
v Perform the manual intervention
|
Perform these steps from the DST or SST main menu.
|
Notes:
|
|
a. To perform the following procedure using SST, select the option Work with service tools user
|
IDs and Devices everywhere it says select Work with DST environment and skip the step
Select System Devices.
|
a.
Select Work with DST environment.
|
|
b. Select System Devices (skip this step if using SST).
|
c.
Select Console.
d. Select Operations Console (LAN). The LAN adapter currently in use should be shown.
|
85
Operations Console

Advertisement

Table of Contents
loading

Table of Contents