IBM E Server i Series Manual
  1. Manuals
  2. Brands
  3. IBM Manuals
  4. Server
  5. E Server i Series
  6. Manual

IBM E Server i Series Manual

Operations console, access for windows
Hide thumbs Also See for E Server i Series:
Table of Contents

Advertisement

Quick Links

Download this manual
ERserver
iSeries
iSeries Access for Windows
Operations Console

Advertisement

Table of Contents
loading

Related Manuals for IBM E Server i Series

Summary of Contents for IBM E Server i Series

  • Page 1 ERserver iSeries iSeries Access for Windows Operations Console...
  • Page 3 ERserver iSeries iSeries Access for Windows Operations Console...
  • Page 4 © 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.

  • Page 5: Table Of Contents

    System reference code A6005008 and B6005008 Configure Operations Console on the PC . 68 System reference code A9002000 . . 111 System reference code A6005082 . . 111 Chapter 5. Manage Operations Console 71 © Copyright IBM Corp. 2002, 2003...
  • Page 6 Failure to display D1008065 and D1008066 Unable to find correct modem at Add RAS automatically after calling the function . . 111 Device selection . 114 IPL step C6004031 takes longer than expected Troubleshoot other Operations Console problems Troubleshoot remote control panel and virtual Operations Console remains in QCTL .

  • Page 7: Part 1. Operations Console

    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.
  • Page 8 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.

  • Page 9: Chapter 1. What's New For V5R2

    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...
  • Page 10 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. iSeries: iSeries Access for Windows Operations Console...

  • Page 11: Chapter 2. Print This Topic

    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...
  • Page 12 iSeries: iSeries Access for Windows Operations Console...

  • Page 13: Chapter 3. Plan For Operations Console

    Operations 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...

  • Page 14: Plan For Your Backup Console

    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. v If 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.
  • Page 15 – 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.

  • Page 16: Scenarios: Select Your Configuration

    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.
  • Page 17 Table 1. Scenario configuration Advantages and Scenarios Disadvantages A single console A single console Consoles for Directly dial up directly attached directly attached multiple servers a server from a to the server to the server or partitions remote location without remote with remote support support...
  • Page 18 v You 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. v The console can be securely placed behind locked doors in the server room.
  • Page 19 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: v The administrator will not have to be near the server to perform console tasks. v Control panel functions can be performed from a remote location provided they are set up on a local console PC.
  • Page 20 v A 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. v Multiple PCs can be configured as the console to a server or partition, but only one can be active at a time.

  • Page 21: Prepare For Your Network Environment

    LAN adapter for service tools. Network security IBM recommends treating the console over a LAN connection with the same physical security considerations and controls as a local console directly attached to the server or a twinaxial console. For instance, consider configuring a local console on a network in a network separate from the main network (or the company intranet) and strictly control access to the machine acting as the console.
  • Page 22 The iSeries console security consists of service device authentication, user authentication, data privacy, and data integrity: Service device authentication This security assures one physical device is the console. Operations Console local console directly attached to the server is a physical connection similar to a twinaxial console.
  • Page 23 Data encryption Enhanced authentication and data encryption provide network security for console procedures. Operations Console local console on a network uses a version of SSL which supports device and user authentication but without using certificates. Device authentication The device authentication is based on a service tools device ID. Service tools device IDs are administered in Dedicated Service Tools (DST).
  • Page 24 PC fails, if you decide to exchange the PC for a different one or if you upgrade it. Protection tips When using Operations Console local console on a network, IBM recommends the following items: 1. Create another service tools device ID with console attributes.
  • Page 25 to enable connections or console activities across a local area network (LAN), besides enabling directly cabled and dial-in (modem) connections. A single PC can have multiple connections to multiple iSeries servers and can be the console for multiple iSeries servers. An example is having a logically partitioned server using the same PC as the console for all partitions.

  • Page 26: Plan For Your Operations Console Migration

    Figure 2. iSeries Navigator and Operations Console configuration on the same network However, if the network adapter and configured OS/400 LIND and the service network adapter as defined by the service host name are on separate networks, then an additional PC LAN adapter is required. Figure 3.

  • Page 27: Migrate From A Local Console Directly Attached To A Local Console On A Network (Lan)

    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.
  • Page 28 If you get a message stating that the LAN adapter was not found, you have not satisfied the hardware requirements for Operations Console. 6. Press F11 to configure the adapter. 7. Enter the appropriate network data. 8. Press F7 to store the data. 9.
  • Page 29 8. Verify that the IOP containing the adapter for the local console directly attached is tagged as the alternate console. Attention: If the current console IOP is not selected as the alternate console IOP, you may not be able to finish configuration. Also, if the correct IOP to be used for the new console type is not correctly tagged you may have to use the Operations Console to debug any problems you might encounter.

  • Page 30: Migrate From A Twinaxial Console To Operations Console

    2. To configure the new console type, see Set up Operations Console. It is recommended that you perform an initial program load (IPL) to be certain there are no errors. Once you are satisfied that the new console is working correctly you can proceed with any plans to move or remove any adapter or configurations.
  • Page 31 v If you selected an Operations Console local console on a network (LAN), do the following: a. The Verify Operations Console Adapters window appears. This is the resource found by the system to be used for your LAN connection. If you receive a message stating that the LAN adapter was not found, you need to satisfy the hardware requirements for Operations Console.
  • Page 32 v If the adapter to be used for Operations Console is under the same IOP as the twinaxial adapter, the console IOP is already correctly tagged. Go to step 9. v If the adapter to be used for Operations Console is under a different IOP, place a 1 in front of the IOP to select it as the console IOP.

  • Page 33: Migrating From An Operations Console To A Twinaxial Console

    Continue with Configure the PC. Configure the PC to use the new console type from using a twinaxial console to an Operations Console To migrate from a twinaxial console to an Operations Console, you must configure the PC to use the new console type. To configure the new console type, see Set up Operations Console.
  • Page 34 6. Select Twinaxial. 7. Press F3 to return to the DST main menu. 8. Select Start a service tool. 9. Select Operator Panel functions. 10. Select the type of initial program load (IPL) you want to perform when you have finished with cable or adapter work on the server. Then, select F10 to power down the iSeries.
  • Page 35 10. Select Work with DST environment. 11. Select System Devices. 12. Select Console mode. 13. If you are currently using Operations Console local console on a network (LAN), select Operations Console local console on a network (LAN) and follow these steps to deallocate the network adapter: a.

  • Page 36: Plan For Your Operations Console Install Or Upgrade

    3. Perform an initial program load (IPL) to ensure there are no errors. Then, at a later time, remove or move any hardware you planned for. When you are satisfied with your new console delete the current configuration if you will not be using the cabled connection as a backup console. To delete the configuration, do the following: 1.

  • Page 37: Plan For Your Control Panel

    If you are going to be utilizing Operations Console on your new iSeries server (migrating from a different console type), it is important that you configure the new Operations Console PC before the beginning of the server model upgrade. At the point in the upgrade instructions where console functions are required on the new iSeries server, you will be able to perform any required functions without the need for your current console device.
  • Page 38 iSeries: iSeries Access for Windows Operations Console...

  • Page 39: Chapter 4. Set Up Operations Console

    Set up a local console directly attached to the server There are unique setup prerequisites depending on the operating system you are using. Select the operating system on which you are installing Operations Console: © Copyright IBM Corp. 2002, 2003...
  • Page 40 Complete prerequisite checklist for Windows 98/Me Complete the prerequisite checklist for a local console directly attached to the server running Windows 98/Me. Complete prerequisite checklist for Windows NT Complete the prerequisite checklist for a local console directly attached to the server running Windows NT.

  • Page 41: Set Up A Local Console Directly Attached To The Server With Remote Access Allowed

    Complete prerequisite checklist for Windows 2000: Local console directly attached to the server Complete the following checklist to set up a local console directly attached to the server on Windows 2000: __ 1. Run prerequisite checking program on the PC. __ 2.
  • Page 42 Complete prerequisite checklist for Windows NT: Local console directly attached to the server with remote access allowed Complete the following checklist to set up a local console directly attached to the server with remote access allowed on Windows NT: __ 1. Run prerequisite checking program on the PC. __ 2.

  • Page 43: Set Up A Local Console On A Network

    __ 6. Install iSeries Access for Windows. __ 7. Apply iSeries Access for Windows service packs. __ 8. Install AS400 Operations Console Connection Modem. __ 9. Install PC modem. __ 10. Create and configure incoming connections. __ 11. Grant remote access. __ 12.

  • Page 44: Set Up A Local Console Through Dial-Up Support

    __ 4. Install iSeries Access for Windows. __ 5. Apply iSeries Access for Windows service packs. __ 6. Configure a service host name. __ 7. Create service tools device IDs on the server. __ 8. Confirm installation of TCP/IP on the PC. __ 9.
  • Page 45 Complete prerequisite checklist for Windows XP Complete the prerequisite checklist for a local console through dial-up support running Windows XP. Complete prerequisite checklist for Windows 98/Me: Local console through dial-up support Complete the following checklist to set up a local console through dial-up on Windows 98/Me: __ 1.

  • Page 46: Set Up A Remote Console Through Dial-Up Support

    Complete prerequisite checklist for Windows XP: Local console with dial-up support Complete the following checklist to set up a local console through dial-up on Windows XP: __ 1. Run prerequisite checking program on the PC. __ 2. Meet Operations Console hardware requirements. __ 3.

  • Page 47: Complete Required Prerequisite Tasks

    __ 2. Meet Operations Console hardware requirements. __ 3. Meet Operations Console software requirements. __ 4. Install iSeries Access for Windows. __ 5. Apply iSeries Access for Windows service packs. __ 6. Install PC modem. __ 7. Install Remote Access Service. __ 8.
  • Page 48 Meet Operations Console software requirements Meet Operations Console software requirements for the PC and iSeries. Meet Operations Console cable requirements Meet Operations Console cable requirements for the PC and iSeries. Verify available communications port Verify that you have an available communications port for your Operations Console configuration.

  • Page 49: Run Prerequisite Checking Program

    LAN card for Operations Console according to your iSeries model. IBM supports a local console on a network (LAN) only on Models 270, 810, 820, 825, 830, 840, 870, and 890. Table 2 shows the supported cards for LAN connectivity.

  • Page 50: Meet Operations Console Software Requirements

    Important: If an emergency arises where your LAN connection fails, you should configure an Operations Console local console directly attached to the server. See Planning for your backup console. Table 3 also shows the correct location for the directly cabled console. Table 2.

  • Page 51: Meet Operations Console Cable Requirements

    PC5250 or IBM Personal Communications (V5.5 CSD 1 minimum) needs to be installed for the console only. It is not required for remote control panel configurations. Table 1. Resulting encryption level Cryptographic Access Client Encryption on the Resulting data encryption...
  • Page 52 Table 1. Operations Console cards and cables Server Feature code (card) Part number (cable) 9406 640/650/730/740/S30/S40 2699 97H7556 9406 600/620/720/S10/S20 2721 or 2745 97H7557 9401 150 2721, 2742, 2745, 2771, 97H7557 2793 9406 270/830/840 9406 810/820/825/870/890 Table 2. Remote control panel cables Server Part number (cable) 9406 640/650/S30/S40...

  • Page 53: Verify Available Communications Port

    Before you use Operations Console, you must install iSeries Access for Windows. During the installation of iSeries Access for Windows, you are going to install a 5250 emulator (if you do not already have PC5250 or IBM Personal Communications V5.5 CSD 1 minimum) and Operations Console support. See the iSeries Access web site for updated PC requirements.

  • Page 54: Install As400 Operations Console Connection Modem

    1. Insert the iSeries Setup and Operations CD-ROM in the CD-ROM drive. 2. Select the iSeries Access for Windows option to start the installation. 3. Wait until the IBM iSeries Access for Windows window appears. 4. To continue with the setup program, click Next and follow the prompts.
  • Page 55 5. Click Browse... 6. Navigate to drive:\path\Client Access\Aoc\Inf\ cwbopaoc.inf where drive: is the drive where iSeries Access for Windows is installed. Note: The default installation path is C:\Program Files\Ibm\Client Access\Aoc\Inf\cwbopaoc.inf 7. Click Open, then click OK. 8. Select Operations Console Connection, and then click Next.
  • Page 56 5. Click Browse... 6. Navigate to drive:\path\Client Access\Aoc\Inf\ cwbopaoc.inf where drive: is the drive where iSeries Access for Windows is installed. Note: The default installation path C:\Program Files\Ibm\Client Access\Aoc\Inf\cwbopaoc.inf. 7. Click Open, then click OK. 8. Select the communications port where you are going to install the Operations Console cable (for example, COM1).

  • Page 57: Install Pc Modem

    5. Click Have Disk... 6. Click Browse... Navigate to drive:\path\Client Access\Aoc\Inf\ cwbopaoc.inf where drive: is the drive where iSeries Access for Windows is installed. Note: The default install path is: C:\Program Files\Ibm\Client Access\Aoc\Inf\cwbopaoc.inf 7. Click Open, then click OK. 8. Click Next.
  • Page 58 2. If you are currently in the Modems folder, click Add, and then Next. Otherwise, if you are at the Install New Modem window, click Next. The PC should find the new modem and report its location. 3. When the window shows the modem it found, click Next to accept it. The PC will now load the driver code to support it.

  • Page 59: Confirm Installation Of Tcp/Ip On The Pc

    Install PC modem for Windows XP If you are installing a PC modem that requires specific drivers, use the instructions that the modem manufacturer provides. Otherwise, follow these steps to install the PC modem: 1. Click Start —> Settings —> Control Panel —> Phone and Modem Options. 2.

  • Page 60: Install Or Configure Remote Access Service (Nt Only)

    8. Click Apply. If prompted, insert your Windows Setup CD-ROM. 9. Click OK to restart the PC. Install or configure Remote Access Service (NT only) Make sure that you install and set up Remote Access Service according to your intended configuration. You only need to install Remote Access Service if you are using Windows NT.
  • Page 61 Desired configuration Necessary modems Local console directly attached to the server AS400 Operations Console connection¹ and with remote access allowed a PC modem Local console through dial-up support A PC modem Remote console through dial-up support A PC modem Note: 1. The AS400 Operations Console connection modem is not a physical modem but a logical device driver that comes with Operations Console and allows a local console to connect to an iSeries server.
  • Page 62 c. Go to step 13. v To configure a local console to receive calls from a remote console, select the following values: a. For Allow remote clients running, select the TCP/IP check box and clear any others (unless your own operation requires them). b.

  • Page 63: Install Microsoft Service Pack

    Install Microsoft service pack Anytime Remote Access Service is either installed or reinstalled, you need to install Windows NT Service Pack 6 (minimum level) before attempting to use Operations Console. If you need a service pack and have Internet capabilities, download the latest Service Pack from http://www.microsoft.com .
  • Page 64 Select the correct modem for your iSeries server: 1. Access Dedicated Service Tools (DST). 2. Select Work with remote service support. 3. Select Change service attributes. 4. In the Modem Type field, select the modem that you are going to use. If you select option 9 (Other), then the Other modem initialization string field becomes available.
  • Page 65 Note: After the system has fully powered down, you may remove the directly attached console device. Then, you will most likely perform an IPL in normal mode and allow users to access the system. After you complete this task, you need to Configure the modem for your local console through dial-up configuration.
  • Page 66 Modem initialization strings for the iSeries server and PC: Use this section to modify the modem initialization strings for your iSeries server and PC according to your modem type. Strings for modem types supported by IBM (7852, 7855, and 7857) and for OEM modems are listed below.
  • Page 67 AT&FE0M0X2$BA1&W0$MB9600S0=0 AT - ATTENTION &F - LOAD FACTORY SET (SWITCH SET TO SYNC) E0 - DISABLE ECHO M0 - DISABLE SPEAKER X2 - CHECK FOR DIAL TONE BEFORE DIALING $BA1&W0 - TURN OFF SPEED CONVERSION $MB9600 - CONNECT AT 9600 ONLY S0 = 0 SPECIFIES NO AUTO ANSWER Initialization string for 7855: For the 7855-10 modem, the initialization string for the iSeries system is:...
  • Page 68 &D2 - DROP LINE WHEN DTR GOES OFF F8 - USE 9600 BPS ONLY *I8 - USE 9600 BPS ONLY &E2 - USE ERROR CORRECTION Initialization strings for ZOOM: For ZOOM VFXV32BIS, the initialization string for the iSeries system is: AT&FE0M0S0=2&C1&D2&K3&S1 AT - ATTENTION &F - LOAD FACTORY ASYNC SETTINGS...
  • Page 69 4. Press the Up-arrow button until 3 is shown. At this point, 3 begins to alternate with the cursor. 5. Press the Enter button, and IBM 7857 V25BIS aa shows. To reset the 7852 modem for synchronous or asynchronous use, use the switch...

  • Page 70: Grant Remote Access

    4. Press the Up-arrow button until 0 is shown. At this point, 0 begins to alternate with the cursor. 5. Press the Enter button, and IBM 7857 AT CMD aa shows. To reset the 7852 modem only for asynchronous, use the switch settings below: UUDDUUUDDUDDUUUU (Where U=up and D=down.)

  • Page 71: Create And Configure Incoming Connections

    2. Select Settings. 3. Select Control Panel. 4. Select Network and Dial-up Connections. Note: If Incoming Connections does not exist, you have to install it. For more information, see Create and configure incoming connections. 5. Click Incoming Connections. 6. Click the Users tab 7.
  • Page 72 Note: If you have a virtual private network (VPN), leave this check box unchecked. Then, click Next. 8. Select or add any users to dial into the local console. Then, click Next. 9. Select the Internet Protocol (TCP/IP) check box (if needed). Then, click Properties.

  • Page 73: Install An Operations Console Cable

    step. If your network does not use DHCP, click Specify TCP/IP addresses. Then, do the following to specify the addresses: a. In the From field, type the address 192.168.0.5 b. In the To field, type the address 192.168.0.24 c. The Total field shows 20 Select the Allow calling computer to specify its own IP address check box.

  • Page 74: Configure Operations Console On The Pc

    4. Select Operations Console. Note: If Operations Console did not appear, you need to complete an iSeries Access for Windows selective setup. Click Start —> Programs —> IBM iSeries Access for Windows —> Selective Setup. iSeries: iSeries Access for Windows Operations Console...
  • Page 75 The wizard starts the console connection panel for you. The configuration is complete. The connection is now ready to be connected. Click Finish to begin working with Operations Console. The wizard invokes the console connection for you. Highlight the connection name then use one of these methods to start your connection.
  • Page 76 iSeries: iSeries Access for Windows Operations Console...

  • Page 77: Chapter 5. Manage Operations Console

    Start the system using a manual IPL Use these instructions to start the system using a manual IPL. Activate the communications line on the server Use these instructions to activate the communications line on the server. © Copyright IBM Corp. 2002, 2003...

  • Page 78: Change A Console Configuration

    Deactivate the communications line on the server Use these instructions to deactivate the communications line on the server. Dial the server Use these instructions to dial the server from your local console through dial-up support. Change a console configuration You may need to change an existing local console or remote console to meet your specific needs while using Operations Console.

  • Page 79: Delete A Console Configuration

    2. Click Disconnect. Wait until the status shows Not connected to local console at the remote console. 3. Select the configuration name. 4. From the Connection menu, click Configure Connection. 5. Continue through the wizard and make any necessary changes. Delete a console configuration You may need to delete an existing local console or remote console to meet your specific needs while using Operations Console.

  • Page 80: Connect A Local Console To A Server

    1. Open Operations Console to start the connection: a. Click Start and select Programs. b. Select IBM iSeries Access for Windows. c. Click Operations Console. By default, Operations Console does not automatically try to connect a local console on a network to an iSeries server. If you selected Start connection when Operations Console starts in Properties, the local console connects to the iSeries server automatically.
  • Page 81 Operations Console needs a valid access password, service tools user ID, and service tools password to authorize the connection between the local console and server. For more information, see Service Tools. For a visual of this concept, see Operations Console LAN security administration. Note: If the connection is to a logical partition and you have configured a console and remote control panel, you will receive a sign-on window for each function.

  • Page 82: Connect A Remote Console To A Local Console By Modem

    Select IBM iSeries Access for Windows. c. Click Operations Console. By default, Operations Console does not automatically try to connect a local console on a network to an iSeries server. If you selected Start connection when Operations Console starts in Properties, the local console connects to the iSeries server automatically.

  • Page 83: Control Tasks Between Users

    If you selected Start connection when Operations Console starts when you configured the remote console, the remote console starts the connection to the local console automatically. 2. If you did not select Start connection when Operations Console starts, you need to start the connection to the local console as follows: a.
  • Page 84 Transfer control between users Use these instructions to transfer control between users. Identify user in control of a server Identifying the user who has iSeries control at a given time may help you determine how to proceed when you want to obtain control. Perform the following steps to identify the user who has control: 1.
  • Page 85 emulation) that is currently interacting with the server. A functional remote control panel allows you to perform control panel functions from the PC. Thus, the PC in control becomes the console and can perform remote control panel functions. Only one PC can have control at a time. If your local console starts in attended mode (directly attached connections only), you have control immediately after you Connect a local console directly attached to the server.
  • Page 86 a. Select the configuration name. b. From the Connection menu, click Request Control. c. If you installed and configured the remote control panel, confirm that it appears. If it does not appear, see Remote control panel fails to start. After the remote control panel appears, a sign-on window may appear. d.
  • Page 87 Request control at the remote console Requesting iSeries control at the remote console allows you to have an active console and a functional remote control panel at the remote console. An active console is a command interface to a server (5250 emulation) that is currently interacting with the server.
  • Page 88 v End the remote console connection to the local console. To end the connection, follow these steps: 1. Select the configuration name. 2. From the Connection menu, click Disconnect. The connection status shows Disconnecting. 3. Wait until the status shows Not connected to local console. Send a message to a controlling local console or remote console While using Operations Console, you may need to communicate with the user who has iSeries control.

  • Page 89: Change Keyboard Definitions

    These interactions show the expected behavior from the local console and remote console users: v No user has control of a server. Therefore, SERVER appears in the Current User field and incoming control requests will be automatically granted. v When a remote console requests control, control will be granted to the remote console.

  • Page 90: Activate The Communications Line On The Server

    The system takes approximately 10 to 30 minutes to power on and progress through an IPL far enough to continue with these instructions. You should see that the data changes in the Function/Data display. The last step of the IPL may take 5 minutes to complete before the Attention light is turned on.

  • Page 91: Dial The Server

    manual mode and the extended control panel functions should be activated. The extended functions are activated from when the communications line was activated. To deactivate the communications line on the server, do the following: 1. If your system is not in manual mode, if the extended functions are not activated, or both, follow these steps: a.
  • Page 92 user or PC is the active console. Also, leaving the newly connected PC in this state will not allow the console activities to be automatically transferred to this PC. In this case you have two choices. v Disconnect the connection using the Operations Console window. To disconnect the connection, follow these steps: 1.

  • Page 93: Manage Your Local Console On A Network

    existing console type, target console type, system load, and other factors may prevent the system from using the new console type. In these circumstances an IPL is necessary to complete the transition from one to the other. If you are using a shared IOP in an LPAR environment you can deallocate and allocate the resource from one partition to another, if your hardware supports this method.

  • Page 94: Changing The Service Tools Device Id Password On The Pc And Server

    v If you have previously connected successfully using this local console on a network configuration, you need to reset the service tools device ID password on the PC and the server. To do this, see Resynchronize the PC and service tools device ID password.

  • Page 95: Resynchronize The Pc And Service Tools Device Id Password

    Note: Using Properties to change access passwords for the remote control panel in logical partitions is currently not supported. You must use the configuration wizard to change the password. 1. Select the connection name for which you will be changing the access password.
  • Page 96 3. Type 2 in front of the service tools device ID to be reset, and then press Enter. 4. Press Enter again to confirm the reset. Note: When you reset the password in DST, the service tools device ID password becomes the service tools device ID name in uppercase. If you will be using a password other than the device name, you will have to delete the current service tools device ID and create a new ID with your desired password.
  • Page 97 c. Using the Down button, decrement the data to 65, and then press the Enter button. The system will respond with 65 00. After processing the function the system will respond with a D1008065. Repeat this step so that you have entered 7 function 65s. You will have 5 minutes to complete this task.

  • Page 98: Create Service Tools Device Ids On The Server

    Reset the service tools device ID password on the PC Reset the service tools device ID password on the PC by doing one of the following: v To delete the configuration and re-create it, follow these steps: 1. If connected, disconnect as follows: a.

  • Page 99: Configure A Service Host Name

    4. Use option 1 to create a new service tools device ID and enter the new service tools device ID name in the first blank name field. Press Enter. 5. Enter the service tools device ID password. Enter it again for verification. You may enter a description.

  • Page 100: Deactivate Or Move The Lan Card From Use By Operations Console

    Note: You may have to temporarily change the console type to complete this work. For example, you use twinaxial on the primary partition but want the remote control panel function for one or more logical partitions. To create a service host name: 1.

  • Page 101: Changing Network Values For Operations Console (Lan)

    Important: You must change the console type to something other than Operations Console (LAN) or the adapter will get reallocated on the next IPL. Changing network values for Operations Console (LAN) If you need to make a change to the network adapter used for Operations Console (LAN), such as a new IP address or a new adapter card, use these instructions: 1.
  • Page 102 From the Connection menu, select New configuration. b. Continue the configuration and enter the new IP data at the appropriate time. c. Complete the rest of the new configuration. The PC client is now ready to make a connection. If you have already performed an IPL on the system, you are now ready to reconnect using the new network data or adapter.

  • Page 103: Chapter 6. Troubleshoot Operations Console Connections

    If your local console allows remote consoles to connect to it, make sure that you have the same service packs at the local console and remote console. Review the following status messages to diagnosis if you have a connection problem. © Copyright IBM Corp. 2002, 2003...

  • Page 104: Status Messages When Configuration Is Running Normally

    Status messages when configuration is running normally Status messages that indicate you do not have connection problems. Status messages when you have connection problems Status messages that indicate you have connections problems. Status messages when configuration is running normally The following status messages assist you in identifying whether or not you have connection problems.

  • Page 105: Status Messages When You Have Connection Problems

    If the status message you received is not listed, see Status messages when you have connection problems. Status messages when you have connection problems The following status messages assist you in identifying whether or not you have connection problems. These status messages indicate that you do have connection problems: Remote control panel unavailable This appears during an initial connection to an iSeries server.

  • Page 106: Troubleshoot Connection Problems

    disconnected. To find a possible solution, see Local console does not detect cables and Remote control panel fails to start. Note: If the local console is configured to start in unattended mode, the local console will not be in control and will not be able to disconnect normally.
  • Page 107 Error message: The connection to the system is not a secure connection Solutions to problems that occur when a local console fails to make a secure connection. Local or remote console status remains Connecting Solutions to problems that prevent the local console from connecting to the server or prevent the remote console from connecting to a local console due to improper hardware or software configurations.
  • Page 108 To activate the communications line on the server, do the following: 1. Use the Down button to select function 66. 2. Press the Enter button. The system attempts to initialize the line. If it is successful, the Function/Data window displays D1008066. If it could not initialize the line, it displays D1008065. See Failure to display D1008065 and D1008066 automatically after calling the function, if the expected reference code did not appear in a few minutes.
  • Page 109 v If you are using Ethernet for your network, you can use a crossover cable to directly connect the PC to the adapter card temporarily. This will isolate the PC and server from any potential problems on your network that might interfere with proper operations.
  • Page 110 If that does not help and you suspect that there is a possibility that the PC may truly not have the buffered UART, IBM recommends that you slow the connection down between the PC and server. Depending on the operating system, you may have to change the registry, the DUN object, or the phone book entry, or all three.
  • Page 111 2. If it is not found, use these instructions to install it: a. Place the installation media, if CD-ROM, into the CD—ROM drive and wait for the program to begin. Then, close the window. If the program did not automatically start, or the installation media is not a CD-ROM, continue with the next step.

  • Page 112: Remote Console Connection Problems

    v Echo typed characters locally v Append line feeds to incoming line ends v Wrap lines that exceed terminal width 13. Click OK. Click OK. 14. Do a Connect. 15. At the server’s control panel enter a function 65 (you need to take the server to a known state).

  • Page 113: Troubleshoot Authentication Problems

    Remote console through dial-up fails to connect to local console While you are connecting a remote console to a server, you may encounter remote console connection problems. These are solutions to a problem that occurs when a remote console modem fails to establish a connection with a local console: v If your PC modem is listed as a Standard Modem option in the Modems folder, configure it with a different manufacturer and model.

  • Page 114: Internal Authentication Errors When Connecting Windows 98/Me Remote Consoles To Windows 2000

    Internal authentication errors when connecting Windows 98/Me remote consoles to Windows 2000 If you have this error, follow these instructions at the local console: 1. Go into the Incoming Connection Properties. 2. Click the User tab. 3. Check the option Require all users to secure their passwords and data. It should be turned off.

  • Page 115: Troubleshoot System Reference Code (Src) Data

    Troubleshoot system reference code (SRC) data There can be problems with your Operations Console configuration if you receive any of the following system reference codes (SRCs): SRCs A6005001, A6005004, A6005007, B6005001, B6005004, and B6005007 Solutions for SRCs A6005001, A6005004, A6005007, B6005001, B6005004, and B6005007.

  • Page 116: System Reference Code A6005008 And B6005008

    System reference code A6005008 and B6005008 Use this table if you received reference codes A6005008 or B6005008. If an IPL did not find a console and if the console type is set to anything except a 1, the system will display code A6005008 or B6005008. v If you are attempting to use a twinaxial console the only data relevant in this SRC is word 16.

  • Page 117: System Reference Code A9002000

    If Word 17 value is: Failure Word 18 means: Word 19 means: Async card not detected No cables detected Card position Wrong cable detected Card position Cable ID Port in use Card position System reference code A9002000 Possible reasons you received system reference code A90002000: v If the system displays this SRC code, it usually means that a console was not found.

  • Page 118: Remote Control Panel Fails To Start

    Remote control panel fails to start Solutions for remote control panel cables. Unable to use the mode function Solutions for when you are unable to use the mode function on remote control panel or virtual control panel. Remote control panel fails to start If your remote control panel fails to start, verify the following: v Verify that the cables are properly connected.

  • Page 119: Local Console Does Not Detect Cables

    Console options not available in configuration wizard Prior to V4R5, it was required to have a 5250 emulator installed (PC5250 or IBM Personal Communications). Starting with V4R5 the emulator is no longer required when only the remote control panel will be used. As a result, when the wizard gets...

  • Page 120: Unable To Find Correct Modem At Add Ras Device Selection

    Unable to find correct modem at Add RAS Device selection The user can be setting up a remote console or a local console in Windows NT. They have either recently added or replaced a PC modem but are unable to find the item in the list of Add RAS device window.

  • Page 121: Local Console Receives Message: Remote Access Service Server Did Not Start

    Local console receives message: Remote Access Service server did not start If a local console is set up to receive calls and there is no PC modem configured to receive those calls, it will post a Remote Access Service Server did not start message.
  • Page 122 iSeries: iSeries Access for Windows Operations Console...

  • Page 123: Chapter 7. Related Information

    Chapter 7. Related information IBM related information contains technical, know-how, and ″how to″ information. Manuals iSeries Access for Windows Setup Use this manual to install and configure iSeries Access for Windows on both the iSeries server and the PC. Installation and configuration is necessary on both the server and the PC.
  • Page 124 ensures that you have everything you need and meet all prerequisites. The planning information in this topic helps you place the server, plan power needs, print any special cabling or setup instructions, meet any PC requirements, and prepare for unique configurations based on how you will use the server (for example, clustering of servers, Internet connections, and rack mounting).
  • Page 126 Printed in U.S.A.

Table of Contents