Troubleshooting
Problem
This document describes how to change the IP address used for operations console LAN.
Resolving The Problem
This document describes how to change the IP address used for operations console LAN connection. It assumes the console type is already set to LAN (3).
Preparation:
a | Obtain the new network information: IP address: ________________________________________________________ Subnet mask: ______________________________________________________ Gateway: _________________________________________________________ Hostname/Connection name: _________________________________________ Note: The name used for the connection does not have to be registered in the DNS; however, it cannot be the same as host name already registered in the DNS. A good practice is to use the partition's (as400) host name with "con" (for console) appended. For example, Dev400Con |
b | Ping the new IP address. Verify there is no reply. If a reply is received, another device is using the IP address. Either that device must be disconnected or another IP address obtained. |
c | Ping the console name. Ping the name you plan to use for the new operations console connection. Verify that it returns an error indicating host is not found or, if it is registered in the DNS, verify that it returns the same IP address you plan to assign. If it returns an incorrect IP address, you must either correct the DNS entry or obtain a new name. |
d | (Optional) Record the existing connection Device ID. If the existing operations console connection is still available, note the device ID being used. - V5R4 only: If console connection status is "connected", disconnect the console connection. - Right click the connection, then click Properties. - Note the device ID being used. It is the unlabeled field on the line after Encryption. |
Note: For the procedure below, IBM support recommends using a normal (non-console) 5250 emulation session to make the change if possible. This allows easier recovery if a configuration error is made because the IP interface is not affected. If the console session is used, follow the steps carefully to ensure a successful change.
1. Reset the Device ID
Note: Skip this step and continue to step 2 if the OS is IBM i 6.1, 7.1 (or later) - auto create device ids is enabled by default at those levels.
a | Access service tools. Type STRSST, and press Enter. Log on with QSECOFR service tools ID/password. |
b | Option 8. Work with service tools user IDs and Devices. |
c | Option 2: Service tools device IDs. If you receive an error such as The user can not perform the option selected, it implies the option to Work with device IDs from SST has not been enabled. The operation must be done from the console using DST or by using the front control panel.
To reset a device ID using DST:
- Select 5. Work with DST environment, then select 5. Service tools device IDs.
|
d | Reset the device ID Note: The reset can be done on a device ID even while it is in use. - Locate the device ID to reset. This is the existing device (see preparation above) or the default device of QCONSOLE. - Type 2 (reset password), then press Enter. - When prompted, press Enter again to confirm the reset. Note: Do not disconnect, then reconnect the console prior to Step 3c or this will set the device ID causing a device ID mismatch error. |
a | Access SST or DST SST: 8. Work with service tools user IDs and Devices DST: 5. Work with DST environment 2. System devices |
b | SST: 4. Configure service tools LAN adapter DST: 7. Configure service tools LAN adapter |
c | Enter the new TCP configuration data: |
d | Press F7 (Store) to save your changes. |
e | Press F17 (F17=Deactivate followed by activate) to apply the changes. Note: When you press F17, the console connection will drop. The server will restart the console LAN adapter using the new configuration. It should be active within a few minutes (in other words, respond to ping or an operations console connection). |
a | Disconnect the existing operations console connection. |
b | Delete the existing operations console connection. Right mouse click the existing connection, then click Delete. |
c | Create a new connection Click Connection, New Connection. Enter the information as prompted by the wizard. Use the same network settings that were entered in Step 2 and the same device ID used/reset previously (in other words, QCONSOLE). |
d | Connect the new console connection. - Right mouse click the new connection, then click Connect. - When prompted, enter the Access password (if requested), Service Tools user ID and password (11111111/11111111). Click OK. |
If console LAN adapter cabling changed so that the LAN console connection now goes through a switch, IBM recommends enabling console takeover and recovery. Further information on takeover and recovery can be found in the Information Center at the following URL: http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/rzajr/rzajrconsoletakeoverandrecover.htm
To enable takeover and recovery:
a | Access service tools. Type STRSST, and press Enter. Log on with QSECOFR service tools ID/password. |
b | Select Option 8. Work with service tools user IDs and Devices. |
c | Select Option 3. Select console |
d | Set Allow console recovery and console can be taken over by another console to 1=Yes. Press Enter, press Enter again: |
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"6.1.0"}]
Historical Number
561389998
Was this topic helpful?
Document Information
Modified date:
18 December 2019
UID
nas8N1012279