IBM Support

LAN Console Connection for Power6 and Power7 Quick Start

Technote (troubleshooting)


This document includes instructions on setting up LAN console on the initial installation of the server. This document only pertains to a non-HMC managed server.

Resolving the problem

This document includes instructions on setting up LAN console on the initial installation of a new server. This document only pertains to a non-HMC managed server. The procedure described in this document works with V6R1M1 and earlier POWER6 and POWER7 (ExB and E8C only) servers. It can be used with a POWER5 server running V5R3M5 and later LIC, substituting port T5 in place of T1.

  • - Preparation

    1. Do not power on the server.
    2. Obtain a static IP address that will be assigned to the server's LAN console adapter for use by the console.


    Subnet mask:

    Default Gateway:

    Optional: Select a unique host name and register the host name and the IP address in your site's Domain Name Server (DNS).

    Host name:

    Note: This IP address is for use by operations console and different than the IP address used to connect a normal telnet session ("green screen"). The IP address must not be in use by another server. Ping the IP address to verify no reply is received (no other device is using the IP address).
    Step 1. Install System i Access for Windows (iSeries Access for Windows) and latest Service Pack.

    Note: The list of Microsoft Windows operating systems supported Operations Console LAN supported on the Microsoft Windows operating systems as documented at:

    a. You will need to be signed on to the PC as the local Administrator account.

    b. Make sure you have installed a full version of iSeries Access with the latest Service Pack.
    The Web site to download the latest SP for iSeries Access follows:
    Step 2.
    Cable the PC direct to Server

    Plug a Cat-5e or Cat-6 (recommended) ethernet cable from the PC directly into T1 port on the back of the server. A crossover is not needed. Note: IBM highly recommends the initial connection be done with the PC direct cabled to the server. The PC and server can be re-cabled to the network once the initial connection is made.
    Back view of a rack mount
    back view of a destop

    Note: Plug the cable into P1-C7-T1 in the diagram above.

    View of a model 550 or 720

    rear view of a model720

    rear view of a model 720

    Note: Plug the cable into P1-T9 in the diagram above.

    Step 3 Configure the PC Networking.
    Access the Windows Control panel, Network Connections.

    a. Disable any additional adapters.
    Disable any additional adapters listed, leaving only the "Local area connection".

    b. Record current TCP/IP settings.
    1) Access the adapter properties, Internet Protocol (TCP/IP), then click properties.
    2) Record the current settings including IP Address, subnet mask and gateway if applicable.
    3) Tape this information on the console PC as a reminder to reset it before reconnecting to the network.

    c. Change the TCP/IP Settings.
    Note: Some versions of i5 OS require that the gateway address respond to pings before the console LAN adapter will activate. IBM support recommends configuring the PC with the default gateway IP address.
    1) Set the IP address to the opcon LAN adapter gateway (See preparation)
    2) Set the subnet mask to the opcon LAN adapter subnet.
    3) Set the Default gateway to the opcon LAN adapter "primary router"/gateway address (same as the IP address).
    Step 4 Disable the PC firewall.

    Note: All PC firewalls must be disabled for the initial connection.

    a. In Windows control panel, click firewall settings and disable the firewall.
    b. In Windows control panel, click security center. Check for any firewall and disable.
    c. Scan all tasks running on the PC for any other software firewall and disable the firewall.
    Step 5 Configure Operations Console.

    Configure the session on your PC.
    Note: All screen shots below are from Version 6.1

    a. Start operations console
    Select Start, All Programs, IBM iSeries Access, Operations Console.

    This is the OPCON screen.

    b. Launch the Configuration Wizard.
    If this is the first time operations console has started, the connection wizard will start automatically. If it does not start automatically, click Connection, New Connection to manually start the wizard. Read the notifications and click Next:

    This is the Welcome screen.

    c. Select Local console on a network. Click Next.

    This is the configuration screen.

    d. Specify a service host name and IP address.
    1) Give your session a name. The name should be one of the following:
    - A valid host name that was registered in the site DNS for the console IP address in the "preparation" step above.
    - A unique name you make up that is not currently registered in the DNS for any other IP address.
    - V5R4 and earlier only: The service tool console IP address can be specified as the name.
    In the screen shown below, CONSOLE_SESSION is used.

    2a) V5R4: Set the target partition to 1
    2b) V6R1 and later: Press the Tab key.
    When you tab away from the Service Host name field, the Service TCP/IP address field will enable.

    3) V6R1 and later: Specify the service TCP/IP Address
    Enter the LAN console adapter IP address from the "preparation" step above.

    4) Click Next.

    This is the Service host screen.

    e. Specify the LAN Console Interface information.
    Service TCP/IP Address: Use the IP address you picked in "preparation"
    Service Subnet Mask: Use the subnet mask you picked in "preparation"
    Service gateway address 1: Use the default gateway you picked in "preparation"
    System serial Number: The System serial number must match the tag on the server. It should be 7 characters long, no dash.
    Target partition: The target partition must be set to 1.
    Click Next.

    This is the Interface input screen.

    f. Specify the device ID.
    If prompted to specify a service tools device ID enter QCONSOLE. Click Next.

    This is the device ID screen.

    g. Create an Access Password.
    V6R1 and later will not prompt for an access password. Note: Be sure to record this case-sensitive password as it must be entered each time the console connection is opened. Click Next.

    h. Click Finish.
    Your session is now ready to connect.

    This is the Config complete screen.

    i. Connect the console
    Double click on the session name to start the connection.
    The connection should show a status of "connecting"
    Step 6 Power on the server
    a. Set the for a manual IPL.

    1. Locate the Server's control panel. Look for the little blue tab on the front of the box; push it to the side, and pull out slowly.
    2. Press the Up arrow until you see 02, and press Enter.
    3. Press Enter again, and you will see a < move to the N.
    4. Press the up arrow and your N will change to an M.
    5. Press Enter.
    6. Press Enter again. This will bring you back to just 02.

    b. Once you have the server set to a manual IPL, push the white power button to power on the server.
    Step 7 Connect the console
    a. Monitor the console status
    Watch for the status of "Pending Authorization". Once the status changes, the service tools signon window is displayed however it may be behind the Operations Console window. Resize/move the window to locate the sign-on.

    This is the System i Ops Console screen.

    b. Sign on to service tools. Use the ID "11111111" with password of eight 1's ("11111111")

    This is the Service Tools Sign-on screen.

    c. IPL and configure the system
    For helpful tips on configuring the new server, refer to Rochester Support Center knowledgebase document N1018613 New System Setup - Beyond the Basic Console Connection: (click to link)

    d. Monitor the control panel for failure
    If your session does not connect wait for the power on to halt on an attention or IPL failure system reference code (SRC) such as A6005008 or B2xxxx. If the power on halts at A6005008, leave the server in this state and call your IBM service provider for assistance. In the United States, call 1-800-IBM-SERV (1-800-426-7378) and use fastpath code 3400.
    Step 8 Reset the PC and Re-cable

    Note: IBM Support recommends that you configure and start an i5 TCP interface on a second port (T2, T3, T4) prior to moving the console. This ensures there is an alternate method to access the server.

    a. Reset the PC TCP Configuration
    Use the information from Step 3b to reset the PC to its original TCP/IP settings.
    Important Note: The PC IP configuration must be reset prior to cabling the PC back to the network because the PC is configured with the gateway IP address,

    b. Recable the PC and server
    The PC and and server console port (T1) can now be re-cabled to the network.
    • - LAN Console activation and IPL scenarios

      The following information is included to assist in determining specific console related topics you may run into.

        • - Switching to LAN Console

          It is always preferable to configure LAN Console while still attached to HMC. This minimizes the problems if LAN Console is not working in first attempt. LAN Console configuration is stored on the Load Source.

          o HMC-managed systems
          The search for a console will be satisfied by the console tag in the partition profile. You would uncheck HMC and click Select then select the intended LAN resource. It will take an Activate of the partition to make use of the LAN resource for the console.

          o Non-HMC managed systems (standalone single partition)
          The search for a console is also dependent on the Console type set in DST/SST (Work with DST Environment - Work with System Device - Select console). It is important that the Console type is set to “3” before trying to IPL in manual mode with LAN Console 

          • - D-IPL without Load Source configuration (and LAN Console connected to HEA)

            When making D-IPL without Load Source, the problem using LAN Console is more complicated. The IPL has no configuration to use, no Network adapter serial number, and no console type set. Therefore, the system will show C6004031 (searching for console) for 20-30 minutes. Then A6005008 is displayed, meaning no available console. The reason for this is console type=0 and HEA adapter may be disabled.
            First step is to select console  (refer to the procedure below):

            Steps 1 – 6
            Display will respond A600500A (meaning that no console bit is set).

            Steps 7 – 9
            Display will show A60x500B (meaning edit mode and x=selection).

            Continue Steps 4 – 6 until display shows A603500B (expect 3 times).
            Confirm A603500B with Step 10 – 11
            Select FC11.

            After 1 minute, display will show C6004508; then change it to A603 500C (meaning action was successfully submitted).

            If at any time A60x500D is displayed, function has timed out because the function has been entered too slow).

            Second step is to activate HEA adapter (function E1 – Enable embedded adapter) (refer to the procedure below):

            Steps 1 – 6
            Display will respond A603500A (meaning that console bit is set to 3).

            Steps 7 – 9
            Display will show A603500B (meaning edit mode and x=selection).

            Continue Steps 4 – 6 until display shows A6E1500B (expect 5 times).
            Confirm A6E1500B with Step 10 – 11
            Select FC11.

            After 1 minute, display will show C6004508; then change it to A6E1 500C (meaning action was successfully submitted)
            If at any time A60x500D is displayed, function has timed out because the function has been entered too slow).

            Now the Operation Console should pop up with password screen. Because this is a new connection, without any password, enter default - which is 8 times 1, in all three fields. Now a 5250 screen opens and, after 2 minutes, the SLIC screen is shown.

            • - Procedure to set Console bit and enable HEA

              Problem: SRCA6005008 or SRCA9002000

              Resolution: Verify console mode and debug

              1. Control panel in manual mode. Note: You can check if the upper functions are already available by pressing the down arrow button once. If it did not go to 70 or 69, you need to do Steps 2 and 3. Otherwise, proceed to Step 4.
              2. FC25 enter.
              3. FC26 enter. Note: The following steps must be done within 60 seconds or a time-out occurs. SRC A6XX500D = time-out setting console bit, start over.
              4. FC65 enter.
              5. FC21 enter.
              6. FC11 expected return with current console type:
              A604 500A = HMC console
              A603 500A = LAN console
              A602 500A = Direct cable console
              A601 500A = Twinax console
              7. FC65 enter.
              8. FC21 enter.
              9. FC11 expected return: A6XX500B (Is this the function you want? Refer to table below).
              No:  Go to Step 7
              Yes: Continue with Step 10.
              10. FC21 enter to perform the selected function.
              11. FC11 enter expected return of A6XX500C.
              XX) Console bit function
              Console Type
              No console defined
              Twinax console
              Direct-attached Operations Console
              LAN Operations Console
              Hardware Management Console (HMC)
              Clearing the resource and configuration for the Operations Console LAN adapter
              Deactivating and activating the Operations Console LAN adapter
              Dumping Operations Console-related flight recorders to vlogs
              Enable embedded port (OPSCONSOLE ENBINTLAN)
              Enable add-on adapter (OPSCONSOLE ENBEXTLAN)
              Disable embedded port (OPSCONSOLE DISINTLAN)
              Disable add-on adapter (OPSCONSOLE DISEXTLAN)
              Enable LAN adapter in slot Cn (OPSCONSOLE ENBLSLOT n)
              Note: This requires that the embedded (internal) LAN flag be off and the external flag be on or you will not see this series.
              Enable asynchronous adapter in slot Cn (OPSCONSOLE ENBSLOT n)

              Note: The Bn and Fn may advance from search order rather then numerically. For example, if the search order is C4,C3,C1, the Bn and Fn numbers may show you the 4 before another lower number. This is determined by model, and not all models will be affected.
              • - Service Tools Device ID password issue when switching between with/without Load Source

                There may be a service tools device ID password issue, and the connection will remain in “Pending authorization" after receiving an error regarding the service tools device ID password. The reason for this is that a new connection for LAN Console defaults the profile QCONSOLE. If you use this service tools device ID, which is recommended, if you migrated a load source to the new system without first resetting the password, the new client PC configuration will not match the password assigned for the connection used prior to the change. However, if the same PC and configuration is used with the same load source in the new system, you should not receive an error.

                On a D-mode IPL, there is no security other than DST user ID and password. If presented a sign-on with an access password, the entitlement does not involve the service tools device ID password. You may get an informational message that the connection is not secure for some releases. However, if you restore code, with or without an initialization of the load source, the system will perform an A-mode IPL after the restore completes. This IPL will perform a full authentication and may post the message that the service tools device ID password is out of synchronization or in-use. If you receive this message, you will be required to reset the password on the system.

                To reset the service tools device ID password using the control panel or remote control panel, you should do the following:

                1. Systems without a keystick show 01 B in the Function/Data window. Note: You may not need to perform Steps 2 and 3 if you already have access to the upper functions.
                2. From the control panel, use the Up or Down buttons so that the Function/Data window shows 25. Then, press Enter. The Function/Data window should show 25 00.
                3. Press the Up button once to increment the data to show 26. Then, press Enter. The system most likely responds with 01 B in the Function/Data window. Note: If the system responds with 65 FF, repeat Steps 2 and 3 again. Use the following information to help determine your progress and success of the reset:

                The double-row display control panel presents data like this:

                Each word is 8 characters; however, four words are displayed at a time for words 12 through 19. For example:

                Requesting word 12 (Function 12) provides you:

                Requesting word 13 (function 13) provides you:

                The remote control panel presents data like this:


                Each word is 8 characters only and displayed individually. If you want word 17, request Function 17. Important Note: To know where you are in the process, the following information is provided:

                o Word 17 of the SRC D1008065 contains the number of function 65s you have completed. When it reaches a count of seven, the reset of the service tools device ID password takes place. Word 18 is then set to 00000000.

                o Word 18 displays 00000001 until you have entered the seventh function 65. When the reset is complete, this word is set to 00000000 unless more than five minutes have elapsed. Note: If you enter function 65 more than seven times, the count starts over.
                4. Using the Down button, decrement the data to show 65. Then, press Enter. The system responds with 65 00. Note: You might need to perform a Function 11 to display the results (D1008065). Allow at least 10 seconds for the initial Function 65 to complete before doing a Function 11 if the display is not responding with D1008065.
                5. Using the Down button, increment the data to show 13, assuming a double-row display on the physical control panel. If using the remote control panel you will select function 17. Then, press Enter. The system responds with ...0001 and will continue to increment as you perform each Function 65.
                6. Repeat Steps 4 and 5 so that you have entered seven Function 65s. You have five minutes to complete this task. When the seventh 65 is entered and, if it is found that greater than five minutes have elapsed, the reset is not processed and the count returns to zero. Note: You must see word 17 as a 7 and word 18 as a 0, or the reset did not occur.
                • - Retry connection

                  If display is showing A6005008, a retry can be issued by pressing the following sequence:

                  65 + 21 + 21+ 11

                  The control panel will then show C6004508. Then, it may change to A6xx500C to show the successful completion of the last command (xx=last command). After about a minute, the panel may display 01 B x (x=last IPL mode).
                  Now a 21 will try to force DST, if the system is not already IPLed only to DST.

                  • - Network and Bootp

                    See Operation Console Networking for more details.
                    The system will start sending BOOTP at any time a search for the console finds that a LAN resource will be used and no IP address has been assigned. This includes all IPLs and even a 65+21+21 reset.
                    V6R1 has improved discovery functionality. V5R4M5 and earlier relies only on BOOTP to discover console. V6R1 also uses autoconfigure with VSDISCOVER. When starting Operations Console with V6R1, the PC sends a broadcast packet to signal qualifying systems to respond. If a system receives this packet and is using V6R1, it responds back to the requesting PC. The PC will see if the system passed back network data and, if it did, will create a configuration for the user. If the system is not configured, the system and PC attempt to negotiate this information and, if successful, you get a configuration. If the negotiation fails to reach a trusted agreement, no configuration takes place and the system continues to perform BOOTP.

                    • - Bootstrap Protocol

                      A local Operations Console on a network uses the Bootstrap Protocol (BOOTP) to configure the server service IP communications stack. The IP stack configuration, plus server serial number and partition ID, is requested in the Operations Console configuration wizard. The server broadcasts a BOOTP request. The Operations Console PC replies with the information submitted during the configuration wizard. The server then stores and uses the configuration information for the service IP communications stack.
                      The Operations Console PC must be placed on a network that is accessible by the server. This can be the same physical network or a network that permits broadcast packets to flow. This is an initial setup requirement; typical Operations Console operation does not require this. This setup should occur on the same physical network.
                      The BOOTP request carries the server serial number and partition ID. The server serial number and partition ID are used to assign the IP configuration information. If you are having problems configuring the service IP communications stack, check that the Operations Console PC is on the same physical network and the server serial number and partition ID are correct in the configuration.
                      Important Note: IBM System i5 and eServer i5 models start counting logical partitions with the number 1 (even if it is the only partition), instead of a 0. For the console to connect correctly, your logical partitions must also begin numbering at 1 instead of 0. This is especially true if you rely on the BOOTP process to configure the server with its network data. A local console on a network (LAN) uses ports 2323, 3001, and 3002. To use Operations Console in a different physical network, the router and firewall must allow IP traffic on these ports. BOOTP uses UDP ports 67 and 68 per RFC 951.

                      The success of BOOTP is dependent on the network hardware used to connect the server and the PC . In some cases, you may need a different console device to configure the connection in DST. To use BOOTP, the network hardware used must be capable of AutoNegotiation of Speed and Duplex if using the 2838 Ethernet adapter for the Operations Console connection

                      • - Migration Notes

                        The following information needs to be taken into account if you are migrating from one model to another.
                        If the current load source will be used on the new target system, you need to perform the following tasks before powering down the existing system:

                        Deallocating or moving the Operations Console LAN adapter

                        You might need to deallocate the LAN adapter from use by Operations Console. A migration is one example of why you might need to do this. Plan to deallocate the LAN adapter if you are not using a local console on a network (LAN) configuration even as a backup, or use the service tools server. After the LAN adapter is deallocated, you can move it or use it for another purpose. You must also be using a workstation other than a local console on a network (LAN) because the following steps might cause the console to disconnect. Deallocating the LAN adapter currently associated with a local console on a network (LAN) is accomplished by using either the dedicated service tools (DST) or the system service tools (SST). However, you must unlock the SST option before you can use it. For additional information on SST, see Unlocking service tools device IDs in SST.

                        1. Access service tools using DST or SST.
                        o If you are using DST, select Work with DST environment, and then System devices.
                        o If you are using SST, select Work with service tools user IDs and devices, and then select Configure service tools LAN adapter.
                        2. Press F6 to perform a clear, and then press F7 to store the new values.

                        Resetting the service tools device ID password using another device

                        Resetting the service tools device ID password using another device is accomplished by using either the dedicated service tools (DST) or the SST. However, you must unlock the SST option before you can use it. For additional information about SST, see Unlocking service tools device IDs in SST. Steps for resetting the service tools device ID password using another device:

                        1. Access service tools using DST or SST.
                        o If you are using DST, select Work with DST environment.
                        o If you are using SST, select Work with service tools user IDs and devices.

                        2. Select Service tools device ID QCONSOLE.

                        3. Type 2 in front of the service tools device ID to be reset, and press Enter.

                        4. Press Enter again to confirm the reset.

                        Important Notes
                        1. Failure to deallocate the LAN adapter before moving the load source may require extensive control panel only recovery procedures. If the current load source will be used as a load source on the target system and the resource currently used for the console is moved into the target system, the partition with this load source will find the resource and use it even if is intended to be in another partition!

                        2. Failure to reset the QCONSOLE service tools device ID password will require you to perform the resynchronization above if you do not use the same PC and configured connection on that PC. It is always safer to reset it, because the PC client will automatically resynchronize on the next connection.

                        3. If the target model has an HMC, it is recommended that you use that for the console to complete the migration process and install any partitions. After the system is stable, you can migrate to LAN console. See Changing consoles for more details.

                      Cross reference information
                      Segment Product Component Platform Version Edition
                      Operating System IBM i 7.1
                      Operating System IBM i 6.1

                      Historical Number


                      Document information

                      More support for: IBM i
                      System Console

                      Software version: 5.4.5, 6.1, 6.1.0, 6.1.1, 7.1, 7.1.0

                      Operating system(s): IBM i

                      Reference #: N1018663

                      Modified date: 07 February 2013

                      Translate this page: