Reference Operations Console and Other i5/os (OS/400) Consoles

Transcription

1 Reference Operations Console and Other i5/os (OS/400) Consoles

2 2

3 Reference Operations Console and Other i5/os (OS/400) Consoles 3

4 This document has been formatted to be viewed. Internal links will be in light blue and external links are dark blue. You can obtain a free reader for this document at Send comments or suggestions to: egerwill@us.ibm.com or gerentz@us.ibm.com First Edition (July 2008) This edition contains information pertaining to V5R3M0 and later of OS/400, i5/os, and IBM I OS. Copyright International Business Machines Corporation 2007, All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. 4

5 Safety and environmental notices Safety notices may be printed throughout this guide: DANGER notices call attention to a situation that is potentially lethal or extremely hazardous to people. CAUTION notices call attention to a situation that is potentially hazardous to people because of some existing condition. Attention notices call attention to the possibility of damage to a program, device, system, or data. World Trade safety information Several countries require the safety information contained in product publications to be presented in their national languages. If this requirement applies to your country, a safety information booklet is included in the publications package shipped with the product. The booklet contains the safety information in your national language with references to the U.S. English source. Before using a U.S. English publication to install, operate, or service this product, you must first become familiar with the related safety information in the booklet. You should also refer to the booklet any time you do not clearly understand any safety information in the U.S. English publications. German safety information Das Produkt ist nicht für den Einsatz an Bildschirmarbeitsplätzen im Sinne 2 der Bildschirmarbeitsverordnung geeignet. Laser safety information IBM servers can use I/O cards or features that are fiber-optic based and that utilize lasers or LEDs. Laser compliance All lasers are certified in the U.S. To conform to the requirements of DHHS 21 CFR Subchapter J for class 1 laser products. Outside the U.S., they are certified to be in compliance with IEC as a class 1 laser product. Consult the label on each part for laser certification numbers and approval information. CAUTION: This product might contain one or more of the following devices: CD-ROM drive, DVD-ROM drive, DVD-RAM drive, or laser module, which are Class 1 laser products. Note the following information: Do not remove the covers. Removing the covers of the laser product could result in exposure to hazardous laser radiation. There are no serviceable parts inside the device. Use of the controls or adjustments or performance of procedures other than those specified herein might result in hazardous radiation exposure. (C026) 5

6 CAUTION: Data processing environments can contain equipment transmitting on system links with laser modules that operate at greater than Class 1 power levels. For this reason, never look into the end of an optical fiber cable or open receptacle. (C027) CAUTION: This product contains a Class 1M laser. Do not view directly with optical instruments. (C028) CAUTION: Some laser products contain an embedded Class 3A or Class 3B laser diode. Note the following information: laser radiation when open. Do not stare into the beam, do not view directly with optical instruments, and avoid direct exposure to the beam. (C030) Power and cabling information for NEBS (Network Equipment-Building System) GR-1089CORE The following comments apply to the IBM servers that have been designated as conforming to NEBS (Network Equipment-Building System) GR-1089-CORE: The equipment is suitable for installation in the following: Network telecommunications facilities Locations where the NEC (National Electrical Code) applies The intrabuilding ports of this equipment are suitable for connection to intrabuilding or unexposed wiring or cabling only. The intrabuilding ports of this equipment must not be metallically connected to the interfaces that connect to the OSP (outside plant) or its wiring. These interfaces are designed for use as intrabuilding interfaces only (Type 2 or Type 4 ports as described in GR-1089-CORE) and require isolation from the exposed OSP cabling. The addition of primary protectors is not sufficient protection to connect these interfaces metallically to OSP wiring. Note: All Ethernet cables must be shielded and grounded at both ends. The ac-powered system does not require the use of an external surge protection device (SPD). The dc-powered system employs an isolated DC return (DC-I) design. The DC battery return terminal shall not be connected to the chassis or frame ground. Product recycling and disposal This unit must be recycled or discarded according to applicable local and national regulations. IBM encourages owners of information technology (IT) equipment to responsibly recycle their equipment when it is no longer needed. IBM offers a variety of product return programs and services in several countries to assist equipment owners in recycling their IT products. Information on IBM product recycling offerings can be found on IBM s Internet site at Esta unidad debe reciclarse o desecharse de acuerdo con lo establecido en la normativa nacional 6

7 o local aplicable. IBM recomienda a los propietarios de equipos de tecnología de la información (TI) que reciclen responsablemente sus equipos cuando éstos ya no les sean útiles. IBM dispone de una serie de programas y servicios de devolución de productos en varios países, a fin de ayudar a los propietarios de equipos a reciclar sus productos de TI. Se puede encontrar información sobre las ofertas de reciclado de productos de IBM en el sitio web de IBM Note: This mark applies only to countries within the European Union (EU) and Norway. Appliances are labeled in accordance with European Directive 2002/96/EC concerning waste electrical and electronic equipment (WEEE). The Directive determines the framework for the return and recycling of used appliances as applicable throughout the European Union. This label is applied to various products to indicate that the product is not to be thrown away, but rather reclaimed upon end of life per this Directive. In accordance with the European WEEE Directive, electrical and electronic equipment (EEE) is to be collected separately and to be reused, recycled, or recovered at end of life. Users of EEE with the WEEE marking per Annex IV of the WEEE Directive, as shown above, must not dispose of end of life EEE as unsorted municipal waste, but use the collection framework available to customers for the return, recycling, and recovery of WEEE. Customer participation is important to minimize any potential effects of EEE on the environment and human health due to the potential presence of hazardous substances in EEE. For proper collection and treatment, contact your local IBM representative. Battery return program This product may contain sealed lead acid, nickel cadmium, nickel metal hydride, lithium, or lithium ion battery. Consult your user manual or service manual for specific battery information. The battery must be recycled or disposed of properly. Recycling facilities may not be available in your area. For information on disposal of batteries outside the United States, go to or contact your local waste disposal facility. IBM sealed lead acid, nickel cadmium, nickel metal hydride, and other battery packs from IBM Equipment. For information on proper disposal of these batteries, contact IBM at Please have the IBM part number listed on the battery available prior to your call. 7

8 For Taiwan: Please recycle batteries. For the European Union: Note: This mark applies only to countries within the European Union (EU). Batteries or packaging for batteries are labeled in accordance with European Directive 2006/66/ EC concerning batteries and accumulators and waste batteries and accumulators. The Directive determines the framework for the return and recycling of used batteries and accumulators as applicable throughout the European Union. This label is applied to various batteries to indicate that the battery is not to be thrown away, but rather reclaimed upon end of life per this Directive. In accordance with the European Directive 2006/66/EC, batteries and accumulators are labeled to indicate that they are to be collected separately and recycled at end of life. The label on the battery may also include a chemical symbol for the metal concerned in the battery (Pb for lead, Hg for mercury and Cd for cadmium). Users of batteries and accumulators must not dispose of batteries and accumulators as unsorted municipal waste, but use the collection framework available to customers for the return, recycling, and treatment of batteries and accumulators. Customer participation is important to minimize any potential effects of batteries and accumulators on the environment and human health due to the potential presence of hazardous substances. For proper collection and treatment, contact your local IBM representative. For California: Perchlorate Material special handling may apply. See The foregoing notice is provided in accordance with California Code of Regulations Title 22, Division 4.5 Chapter 33. Best Management Practices for Perchlorate Materials. This product/part may include a lithium manganese dioxide battery which contains a perchlorate substance. 8

9 Table of Contents Safety and environmental notices...5 Start here - Welcome to Operations Console and other i5/os consoles...12 Chapter 1: Reference...13 Common Terminology...13 Console types covered in this document...13 Platform and environment information...14 Operating system console designations...15 Operations Console connectivities...16 Supported Adapters...17 Supported adapter locations...20 Supported models by release...23 Default addresses for the HMC1 and HMC2 ports...24 Power6 processor-based Blade and Power6 processor-based System running VIOS/IVM...25 PC requirements for Operations Console...26 What Functions, When?...26 Local console on a network (LAN) specific information...38 Supported resources for a local console on a network (LAN)...38 Supported adapter locations in a non-hmc managed system...39 What if my non-hmc managed system has an embedded Ethernet port?...41 What are the network requirements for a local console on a network (LAN)?...42 Local console directly attached...43 Supported asynchronous communication adapters for a local console directly attached configuration...43 Supported adapter locations in primary partitions or non-partitioned systems...44 Supported cables...46 What communications port(s) are required for Operations Console?...47 Other references...48 What are the software requirements for Operations Console?...48 What is the meaning of the field Current state of console tag on the Select Console window?...49 Operations Console simplification (V6R1)...50 Autocreate service tools device IDs...50 Automatic management of the access password...51 Automatic discovery of systems...51 Troubleshooting system reference code (SRC) data...53 SRCs A6nn500x...53 SRCs A , A , and A SRC A Step-by-step analysis

10 D after attempting to activate the asynchronous communications adapter...66 SRC A SRC A Failure to display D and D automatically after calling the function...73 Startup step C takes longer than expected in D-mode IPL...73 Chapter 2: Considerations for planning...74 All systems - General Operations Console considerations...74 What if I need more than one adapter of the type currently used as the console?...74 What is Allow console recovery and console can be taken over by another console?...75 Can more than one console be made available for use as necessary?...75 Can I have more than one connection active at a time?...77 How many 5250 sessions can I have active at a time?...77 Do I have to be concerned about encryption?...77 What do I need to be aware of when planning to install a new release of OS/400 or i5/os?...78 What do I need to be aware of when planning to upgrade my system to another model?...78 How does the system determine what the console or console's resource should be?...79 Do I have to dedicate a resource to the console?...80 If I use a local console on a network (LAN) what should I take into consideration if I have to recover my system?...81 What if I use a local console on a network (LAN) and have more than one device connecting at the same time?...82 What do I consider if I have multiple console devices with multiple systems?...82 Do I have to be aware of IOA/IOP placement?...83 How does the system handle adapter activation when multiple console types are available?...83 Pre-Power5 processor-based systems...84 Pre-Power5 processor-based - All systems...84 What considerations do I take into account for IOPs?...84 What considerations do I need to know about a backup console in a recovery action?. 85 What should I consider for a backup console?...85 Pre-Power5 processor-based systems using a local console directly attached...86 Pre-Power5 processor-based - Non-partitioned systems...86 Can I place a console resource anywhere in my system?...86 What do I need to know regarding any recovery actions?...87 Pre-Power5 processor-based - Partitioned systems...87 What tags do I have to use for console?...87 What do I need to know about multiple adapters for consoles?...87 Power-processor-based Systems - Common information...88 Power-processor-based Systems - All systems /5768 and 5706/5707 adapters and 2742 asynchronous communications adapters

11 Power Systems - Not HMC managed...89 What considerations do I take into account if I want to use a 5706/5707 or 5767/5768 (Power6 processor-based only) adapter instead of the embedded port?...89 How does the system know which resource to use for the console when there isn't an HMC?...89 What if the system has two or more adapters of the same connectivity?...91 How do I specify which adapter to use for console when more than one is available?..92 Can more than one console supporting resource be activated at the same time?...94 What do I tag for console using the HMC?...94 Which tags do I have to be aware of with Operations Console?...95 Power5 processor-based Systems Specific...96 Power5 processor-based - Non-partitioned systems - Not managed by a Hardware Management Console (HMC)...96 What is the default local console on a network (LAN) resource?...96 Power6 processor-based Systems Specific...97 Power6 processor-based - All systems...97 What is the default local console on a network (LAN) resource?...97 What is the Virtual Ethernet (IVE) - Host Ethernet Adapter (HEA)?...97 Power6 processor-based - Non-partitioned systems...98 What is the default for a local console on a network (LAN) resource?...98 Power6 processor-based - Partitioned systems...99 What do I have to know about servers with an HMC?...99 What do I have to know about tagging a Host Ethernet Adapter logical port or IOA for the console?...99 Power6 processor-based Blade and Power6 processor-based systems running VIOS/IVM What do I have to know about Power6 processor-based blades and systems running VIOS/IVM? RCP & VCP What is a RCP or VCP? What type of restrictions am I likely to encounter? Why did I lose the RCP when I previously had it working? What considerations are specific to the virtual control panel? How to determine what model or serial number a system is? Chapter 3: System Locations for Cards & Cables Appendix A. Notices Trademarks Electronic emission notices Class A Notices Terms and conditions

12 Start here - Welcome to Operations Console and other i5/os consoles Operations Console is an installable component of iseries Access for Windows, System i Access for Windows, or other formal names depending on release, which will be referred to as Client Access for the rest of this document. It allows you to use one or more PCs to access and control, either remotely or locally, console and control panel functions. You can use Operations Console to manage IBM i (formerly i5/os), i5/os, or OS/400 operating system in a partitioned or non-partitioned environment. In a partitioned environment, you might want to use the Hardware Management Console (HMC) or the Advanced System Management Interface (ASMI) to access your hardware. Operations Console uses 5250 emulation provided by either Client Access or IBM Personal Communications to emulate a console. To emulate a server control panel, Operations Console provides a graphical remote control panel or virtual control panel. Operations Console can use a local area network (LAN) or direct cable attachment to enable communications between a server and a PC. It supports dial-in connections from remote PCs to PCs that are directly attached to servers. These remote PCs can then function as a console. This remote capability is only available in i5/os or OS/400 prior to V6R1. This document should answer nearly all questions in the planning for Operations Console and other i5/os consoles. Chapter 1 Reference, page 13, contains information for quickly looking up data pertaining to consoles. Chapter 2 Considerations for planning, page 74, for details regarding consoles and their resources on your system. Be sure you know all the considerations for a particular console and the hosting system before you start any work. Chapter 3: System Locations for Cards & Cables, page 106, contains graphics of most of the supported type/model systems to help determine a card location. Important: You must know what hardware will be used to support a console and any hardware work to add, remove, or replace to accomplish the console goal. 12

13 Chapter 1: Reference This chapter provides you with quick lookup data. It assumes you already know what console you will be working with and factors that might influence it. Common Terminology The use of the term embedded Ethernet port throughout this document is meant to mean the Ethernet port available where an adapter slot is not used. For pre-power5 processor-based systems, the only system with an embedded Ethernet port is the On Power5 processor-based systems there are two ports designated as the embedded Ethernet ports. For Power6 processor-based systems this refers to the Integrated Virtual Ethernet (IVE), or Host Ethernet Adapter (HEA) in some documents, which comes as a 2-port or 4-port adapter. IBM AS/400, AS/400e, iseries, eserver, System i, Systemi5, eserver i5, Power processor-based, Power5 processor-based, Power6 processor-based are all designations for systems supported from before V5R3 to the present. You will see a mix of these terms in this document and unless specified, the data can be applied to any supported system for the release or releases. Operations Console relies on the level of Licensed Internal Code (LIC) and not necessarily the level of i5/os,operating System/400, OS/400 or IBM i. The client code does not use mid-release designations, only service packs. The use of the term system and server are interchangeable in this document. Also, when referring to a system, in most cases, you can also apply the data to a partition. modem was renamed as the Operations Console Connection modem in V5R4. All references to this modem driver will use the newer name. AS/400 Operations Console Connection iseries Navigator, System i Navigator, and other names may pertain to the Navigator product of Client Access and will be referred to Navigator in this document. Console types covered in this document The following console types are represented in this document. Although the main objective of this document is to provide information for Operations Console, you will find that you can use this document to install or change from and to other console types. These include twinaxial, Thin Console, and the Hardware Management Console (HMC), plus the Advanced System Management Interface. These other consoles and interfaces are not covered in detail but there should be enough information available here or from the provided links for you to install a system with your desired console or change from one console type to another. 13

14 Platform and environment information The term platform refers to the type of hardware you will be using. Use the following table to help determine your platform: Platform System types and models as an example Pre-Power Processor-based xx series Power5 Processor-based , 520, 525 Power6 Processor-based 9407-M15 520, 9408-M25 520, 9409-M Power6 Processor-based using VIOS/IVM JS22 and JS12 Type 7998 blade servers The term environment is used to further define the platform: - A standalone system has a single partition running a single copy of i5/os, and no Hardware Management Console (HMC). You can have a standalone environment with any platform except the blade server. - An HMC-managed system is a Power5 or Power6 processor-based system managed by an HMC. - A partitioned Pre-Power Processor-based system has a primary partition plus one or more secondary partitions, and no HMC. The first partition is numbered 0 (zero). - All Power Processor-based models consist of one or more logical partitions. The first, or only partition, is numbered 1 (one). - The Power6 Processor-based blade is a IBM BladeCenter JS22 and JS12 Type 7998 blade server based on IBM Performance Optimization with Enhanced RISC (POWER ) Architecture technologies. The BladeCenter JS22 Type 7998 blade server runs in BladeCenter units to provide a high-density, high-performance blade server environment using advanced processing technology. All Power6 processor-based blades are restricted to use a local console on a network (LAN) only. 14

15 Operating system console designations Note: The following terminology will help you communicate with service providers and follow procedures for changing consoles. DST console The console in control of the system when the system is IPLed to Dedicated Service Tools (DST) or, function 21 has been performed. alternate console The term alternate console is referring to a twinaxial console that has control of the system in the following environments: A twinaxial workstation on the primary twinaxial workstation controller with port 0 (address 1) or port 1 (address 0 or 1) can become an alternate console device if twinaxial console is selected. Only the use of port 0, address 0 will allow for a system console. Port 0, address 1 or port 1, address 0 or 1 work at DST to allow debugging issues of the system console. If you attempt to install using one of the alternate consoles the system will warn you that you are not on the system console. A twinaxial workstation on the controller where the alternate console tag is referencing. The use of Port 0, address 0 or 1 or port 1, address 0 or 1 work as an alternate console. The alternate console can only become a DST console so you can not install the system's operating system from this console. If you attempt to IPL the system into i5/os (OS/400 or IBM i) the system will post SRC A and you will not have a system console. This terminal then becomes just another workstation. However, you can do a function 21 to access DST. Operations Console and HMC type consoles do not use resources tagged as the alternate console. Note: Tagging the same IOP as both the primary console and the alternate console may result in the inability to select a console. system console The console that is in control of the operating system when the ENDSYS command has completed and the system is in a restricted state. Only one device can be the system console. backup console A backup console is what you would use in the event that your current console becomes inoperable for any reason. Having another set of resources that can be implemented quickly is the goal. All the same considerations apply to the backup console. 15

16 Operations Console connectivities Local console directly attached to the server If your needs are to use a console type similar to the requirements of twinaxial console then this is the connectivity for you. It uses a special serial cable between the PC and the system so the requirement of locating the console close to the system is met. You rely on physical security if you need to restrict access to the console. Local console directly attached to the server with remote access allowed (V5R3/V5R4 only) In addition to the properties of the directly attached console, this configuration choice also allows a remote console to dial into the local console and become the console. Currently, there are other third-party solutions that may be more flexible. Local console on a network (LAN) Use this configuration when you need more than one PC to become the console, one at a time of course. This connectivity requires a network resource on the system and PCs. This network, however, may only consist of the system and those PCs that might connect, or could include a large network infrastructure allowing access from off-site locations. See What are the network requirements for a local console on a network (LAN)? on page 42 for specific information. Remote console through dial-up support (V5R3/V5R4 only) This is the configuration that would be paired with a Local console directly attached with remote access allowed to provide console capability at a remote site in environments where there may not be any network capability. 16

17 Supported Adapters Supported adapter locations on page 20. Supported models by release on page 23. If you don't know what model system you are working with see determine what model or serial number a system is on page 105. Supported resources for a local console on a network (LAN) Adapter type PCI 100Mbps Tokenring Adapter PCI 100/10 Mbps Ethernet IOA 2849 PCI 100/10 Mbps Ethernet IOA 5706/5707 PCI 1000/100/10 Mbps Ethernet IOA or embedded port 5767/5768 PCIe 1000/100/10 Mbps Ethernet IOA IVE (HEA) embedded port The IVE (HEA) is the default resource. Use the top, or right-most port. Restrictions Requires IOP V5R3 - V5R4 Power5 processor-based and earlier systems Requires IOP V5R3M5 IOP-less Power5 processorbased V5R4M5 (or later) Power6 processorbased V5R4M5 (or later) Power6 processorbased only V5R4M5 (or later) Power6 processorbased only 17

18 Supported asynchronous communication adapters for a local console directly attached configuration Supported asynchronous adapters, depending on platform: Adapter type 2699/9699 Two-Line WAN IOA 2721/9721 PCI Two-Line WAN IOA 2745/9745 PCI Two-Line WAN IOA 2771/9771 PCI Two-Line WAN IOA w/modem 2742/6805 PCI Two-Line WAN IOA 2793/2794 PCI Two-Line WAN IOA w/modem (See table below) 576C/2893/2894 PCIe Two-Line WAN IOA w/modem (See table below) Restrictions V5R3 & V5R3M5 SPD hardware only V5R3 & V5R3M5 SPD to PCI migration tower hardware only V5R3 thru V5R4M5 Pre-Power and Power5 processor-based - Requires IOP V5R3 and later Pre-Power5 processorbased V5R4M5 IOP-less Power-processor-based V5R3 and later Pre-Power5 processorbased V5R4M5 IOP-less Power-processor-based V5R4M5 (or later) Power6 processorbased only 18

19 Supported asynchronous adapters, Power6 processor-based and later Sales Feature (Order #) 2793/ / / / / / /2894 Feature Code (WRKHDWRSC *CMN) 2793 (0614/2793/9793) C Power6 processor-based console card slot types and supported adapters for each slot type The IVE (HEA) is the default resource. Use the top, or right-most port. Slots C1, C2, C3 Type PCIe C4, C5 PCI- Adapters 5767/ Ethernet 2893/2894 (576C) Asynchronous 5706/ Ethernet 2793/ Asynchronous Asynchronous 19

20 Supported adapter locations If you don't know what model system you are working with see determine what model or serial number a system is on page 105. Supported adapter locations in a non-hmc managed system Note: Systems managed by a Hardware Management Console (HMC) or pre-power5 processorbased systems that have logical partitions use tagging to designate the console resource. For graphics of most supported systems see System Locations for Cards & Cables on page 106. Pre-Power5 processor-based primary partitions and non-partitioned systems Type Model ECS/Async C07 C07 C06 C C02 C02 C C SB2 SB3 C02 C02 C08 C08 C07 C09 Graphic page 109 Graphic page 110 Local console on a network (LAN) & Twinaxial Twinaxial only Twinaxial only C06, C05 Twinaxial only Twinaxial only Twinaxial only C06, C05 C06, C05 C04, C03, C11 Embedded port C03, C02, C01 C04, C06, C10 C04, C06, C10 C04, C06, C07, C08, C09 C04, C06, C07, C08, C09 C04, C06, C10 C04, C06, C10 20

21 Power5 processor-based (not HMC managed) The embedded support was not supported for Operations Console at V5R3M0. Support started with V5R3M5 along with the new plus models. This allowed the use of a local console on a network (LAN) on systems with an IS adapter. Full IOP-less function for add-in adapters was supported starting in V5R4M5. Type Model ECS/Async C3 C4 C2 (2, 3) C3 C4 C2 (2, 3) C3 C4 C2 (2, 3) C3 C4 C2 (2, 3) C2 (1, 3) C2 (3) C2 (3) Local console on a network (LAN) & Twinaxial Embedded port (5, 6) C5, C2 Embedded port (5, 6) C5, C2 Embedded port (5, 6) C5, C2 Embedded port (5, 6) C5, C2 Embedded port (5, 6) C4 (4) Embedded port (5, 6) C4, C6 C4 (5, 6) 21

22 Power6 processor-based (not HMC managed) Type 9406 Model ECS/Async Local console on a network (LAN) & twinaxial HEA, C4, C2 (5, 6, 7) MMA C1, C4 (3) MMA C1, C4 (3) HEA, C4, C2 (5, 6, 7) M15 C1, C2, C5 (3) HEA, C4, C2 (5, 6, 7) M25 C1, C2, C5 (3) HEA, C4, C2 (5, 6, 7) M50 C1, C2, C3, C5, C4 C1, C2, C3, C5, C4 550 (3) (5, 6, 7) (1) If an IS is installed then use C5 (V5R3M0 only) (2) OPSCONSOLE macro or console service function (65+21) +Fn for card selection (V5R3M5 with PTF MF39303) (V5R4M0 with PTF MF39304) (3) OPSCONSOLE macro or console service function (65+21) +Fn for card selection (V5R4M5 or later) (4) If an IS is installed then no LAN card or WS card (V5R3M0 only) (5) The embedded Ethernet port is the default location. You must disable this support in order to use an external 1 Gbps Adapter such as a 5706/ /5768 (Power5 processor-based/6 only & V5R3M5 or later) (6) OPSCONSOLE macro or console service function (65+21) +Bn for card selection (V5R4M5 or later) (7)The IVE (HEA) is the default resource. Use the top, or right-most port. 22

23 Supported models by release If you don't know what model system you are working with see determine what model or serial number a system is. This group of models will be referred to as pre-power5 processor-based. When referring to logical partitions that belong to this group start counting from zero (0) as the first partition. This table indicates which releases of i5/os or OS/400 are supported by each of the System RISC models. System Model to OS Level Mapping Type Model V5R3 V5R4 V6R SB SB3 23

24 When referring to logical partitions that belong to this group start counting from one (1). This table indicates which releases of Licensed Internal Code (LIC) are supported by each of the Power5 processor-based models System Model to LIC Level Mapping Type Model V5R3 V5R3M5 V5R4 V6R When referring to logical partitions that belong to this group start counting from one (1). This table indicates which releases of LIC are supported by each of the Power6 processor-based models System Model to LIC Level Mapping Type Model V5R4M5 V6R MMA MMA FHA M M M Default addresses for the HMC1 and HMC2 ports The following table lists the manufacturing default Ethernet port addresses for connecting an HMC, Thin Console, or Advanced System Management Interface (ASMI). Platform FSP A Subnet Mask HMC1 HMC2 Power processorbased Power processorbased 24

25 Platform FSP B (if installed) HMC1 HMC Subnet Mask Power5 processorbased Power processorbased Power6 processor-based Blade and Power6 processorbased System running VIOS/IVM The IBM BladeCenter JS22 and JS12 Type 7998 blade server is based on IBM Performance Optimization with Enhanced RISC (POWER ) Architecture technologies. The BladeCenter JS22 Type 7998 blade server runs in BladeCenter units to provide a high-density, highperformance blade server environment using advanced processing technology. All Power6 processor-based blades are restricted to use a local console on a network (LAN) only. The physical/logical route to the network determined when configuring the Blade Center and partition. The port assigned to the partition must be bridged in order to access the network. Also, since VIOS/IVM are required, the VIOS will always be partition 1 so the first user partition for a console will always be 2. You would configure a local console on a network (LAN) to use partition 2 if you have to manually configure it. The first usable partition for data would be partition 2. Partition 1 is where VIOS is installed. 25

26 PC requirements for Operations Console Note: Operations Console does NOT support the use of more than one network adapter in the PC. Operating System (1,2) Operations Console PC PC requirements - processor and memory Windows NT 4.0 (V5R3 only) Pentium 300 MHz recommended 64 MB memory minimum (128 MB recommended) Windows 2000 Pentium 500 MHz recommended 128 MB memory minimum (256 MB recommended) Windows P Professional Pentium 500 MHz (P6 or equivalent compatible microprocessor) 256 MB memory minimum Windows Vista Pentium 800 MHz (Use Windows P instructions) 512 MB memory minimum Notes: 1. See the Client Access Web site for any updated PC requirements Windows Vista only supports a local console on a network. What Functions, When? Supported Windows Operating Systems Operating System Win 9x Win NT Win 2000 Win P Win Vista (1) Began V4R3 V4R4 V4R4 V5R2 V5R4 Thru V5R2 V5R3M5 Current Current Current Originally, Windows Vista was supported at SI25949 (SP4) A problem in PC5250 requires SI27741 (SP6) for any function requiring PC5250, including Operations Console. 26

27 Configurations Function Direct cable Direct cable w/remotes Remote console Dial-up Local console LAN console Began V4R3 V4R3 Thru Current V5R4 V4R3 V4R4 V5R4 V5R2 V5R1 Current System side function Function CSFs / macros All 5250 consoles provide green-onblack QCONSOLE device ID grants RCP access Partition remote panel granted by default Allow system value security changes by default Allow new digital certificates by default default and expired password to change its own password off by default Manual kick at C Autocreate DevIDs VSDISCOVER Device ID option in SST locked by default Unlock service tool device IDs option in DST security data V5R3 V5R3 Update V5R3M5 V5R4M0 V5R4M5 V6R1? 27

28 Takeover / Recover Function Takeover/recover Need to force option to use it Takeover/recover Takes effect immediately now Behavior changed with new macros: V5R3 V5R3 Update V5R3M5 V5R4M0 V5R4M5 V6R1 SHOWSTATUS SKIPSTATUS TAKEON TAKEOFF RCP/VCP (Power5 processor-based/6 hardware does not support ANY directly-cabled RCP) Function RCP - cabled ser. RCP - cabled par. Begin Thru Notes V4R3 V5R3 1 V4R5 V5R3 2 NT only V5R1 Current RCP (LAN) Logical partitions VCP V5R2 Current Note 1: No serial-based RCP models are supported Note 2: Parallel-based RCP exist and may work but not supported Info Center changes Function Separate InfoCntrs for iseries/power5 processor-based Add Power6 processor-based doc Separate Changing console doc V5R3 V5R3 Update V5R3M5 28 V5R4M0 V5R4M5 V6R1

29 Client - Wizard Function V4R3 Client rewritten Client rewrite w/new panels w/graphics All panels have the same graphics All panels have context graphics DevID/Access PW Same panel DevID/Access PW Separate panels Conditional DevID panel / No access PW DevID no longer requires a userentered PW PC or system Simplified some wizard work USB/PCMCIA support for serial COM1-9 AS/400 Operations Console Connection modem Rebrand Operations Console Connection modem V4R4 V4R5 V5R1 V5R2 V5R3 V5R4 V6R1 29

30 Client - GUI Function V4R3 V4R4 V4R5 V5R1 V5R2 V5R3 V5R4 Properties page Device ID tab gone Display device ID on general tab Answer BOOTP has subnet mask and gateway address fields for edit Access PW tab pre-filled with old PW Use console on configuration tab has field for IP address Hot keys (Settings) Alt+w or Alt+shift+w Turn off Autodiscover Answer BOOTP to config tab Expand connection to display functions Ability to change config by using the wizard A more Windows like interface Single sign-on Suppress msgs Drag-n-drop Sngl/dbl clicks 30 V6R1

31 Client - Function Function V5R4 Auto reset of device ID for PC Access PW managed by client, not user, by default Client - Misc Function PC-prerequisite program EZ-Setup Navigator support Navigator localhost Crypto support V6R1 V4R3 V4R4 V4R5 V5R1 V5R2 V5R3? V5R4 V6R1 Implied Implied Implied In Base In Base Pre-Power5 processor-based - Serial - Direct cable Models & Adapters 150/ = /S10 620/720/S20 640/730/S30 650/740/S40 4xx/5xx V4R3 V4R4 V4R5 V5R1 V5R2 V5R3 V5R3 V5R3M5 Update

32 Pre-Power5 processor-based (iseries) - Serial - Direct cable Models & Adapters 270 V4R5 V5R1 V5R ( ) (2) 820/830/ ( ) (2) 800/ (2) 825/870/ (2) V5R (2) (3) (2) (3) (2) (3) (2) (3) V5R3 V5R3M5 V5R4M0 V5R4M5 V6R1 Update (2) 2771 (2) 2771 (5) 2771 (5) (3) (3) (2) 2771 (2) 2771 (5) 2771 (5) (3) (3) (2) 2771 (2) 2771 (5) 2771 (5) 2771 (3) (3) (5) (2) 2771 (2) 2771 (5) 2771 (5) 2771 (3) (3) (5) (1) will be searched for and takes over for the 2745 if both installed (2) - New parallel RCP cable (3) - Another new parallel RCP cable (4) - IOPless for RSSF only (5) - Parallel RCP - Not supported Power5 processor-based - Asynchronous - Direct cable Models V5R3 Power5 processorbased 520/550/ Power5 processorbased 550/ (1) - IOPless for RSSF only (2) - IOPless supported V5R3 Update V5R3M5 V5R4M0 V5R4M5 V6R (1) (1) (1) (1) 2742 (2) (2) 2742 (2) (2) 2742 (2) (2) 2742 (2) (2) 32

33 Power6 processor-based - Asynchronous - Direct cable (all HW runs IOP-less) Models Power6 processorbased 9117-MMA FHA MMA M M M New PCI-E slots V5R4M C V6R C Pre-Power5 processor-based - Network (LAN) Models V5R1 V5R2 V5R3 V5R3 V5R3M5 V5R4M0 Update 150/ /S10-620/720/S20-640/730/S30-650/740/S40-4xx/5xx Not supported /830/ / Embed. Embed. Embed. Embed. Embed. 870/ V5R4M5 V6R Embed Embed

34 Power5 processor-based - Network (LAN) Models V5R3 Power5 processorbased 520/ V5R3 Update Power5 processorbased 550/ Power5 processorbased Any model that supports IOP-less HW V5R3M5 V5R4M0 V5R4M5 V6R1 Embed. 5706/ Embed. 5706/ Embed. 5706/ Power6 processor-based - LAN Models Power6 processorbased 9117-MMA FHA MMA M M M New PCI-E slots V5R4M5 V6R1 IVE(HEA) IVE(HEA) 5706/7 5706/ Power6 processorbased Blade LAN console only IVE(HEA) Only VIOS/IVM managed LAN console only IVE(HEA) Only 5767/8 5767/8 34 Embed. 5706/ Embed. 5706/ Embed. 5706/ Embed. 5706/ Embed. 5706/ Embed. 5706/ Embed. 5706/ Embed. 5706/ Embed. 5706/

35 Console Service Functions (65+21) - Equivalent macros Functions C3 / A3 / DD E1 / E2 / D1 / D2 Fn Bn V5R3 V5R3M5 (1) V5R4M0 (1) V5R4M5 Timeout secs V6R1 (1) PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0) SRC data in SRC A , D , AND D Word / Data Basic word Expanded word 13 w/encn Expanded word 13 w/lan flag/card Expanded word 16 V5R2 V5R3 V5R3M5 V5R4M0 V6R1? 35 V5R4M5

36 System models by supported release (no longer supported) System Model to OS Level Mapping Type Model V3R6 V3R7 V4R1 V4R2 V4R3 V4R4 V4R5 V5R1 V5R2 V5R3 V5R4 V6R S S S S S S S SB1 36

37 System models by supported release (currently supported) System Model to OS Level Mapping Type Model V3R6 V3R7 V4R1 V4R2 V4R3 V4R4 V4R5 V5R1 V5R2 V5R3 V5R4 V6R JS12 Blade JS22 Blade 9117 MMA FHA MMA SB SB M M M Requires V5R4M5 of Licensed Internal Code

38 Local console on a network (LAN) specific information Supported resources for a local console on a network (LAN) Adapter type Restrictions PCI 100Mbps Tokenring Adapter Requires IOP PCI 100/10 Mbps Ethernet IOA V5R3 - V5R4 Power5 processor-based and earlier systems 2849 PCI 100/10 Mbps Ethernet IOA Requires IOP 5706/5707 PCI 1000/100/10 Mbps V5R3M5 IOP-less Power5 processorethernet IOA or embedded port based V5R4M5 (or later) Power6 processorbased 5767/5768 PCI-E 1000/100/10 Mbps V5R4M5 (or later) Power6 processorethernet IOA based only IVE (HEA) embedded port V5R4M5 (or later) Power6 processorthe IVE (HEA) is the default resource. based only Use the top, or right-most port

39 Supported adapter locations in a non-hmc managed system Note: Systems managed by a Hardware Management Console (HMC) or pre-power5 processorbased systems that have logical partitions use tagging to designate the console resource. Graphics of system locations for Operations Console on page 106. Pre-Power5 processor-based primary partitions and non-partitioned systems Type Model Local console on a network (LAN) & twinaxial Twinaxial only Twinaxial only C06, C C06, C C06, C C04, C03, C Embedded port C03, C02, C C04, C06, C C04, C06, C C04, C06, C07, C08, C C04, C06, C07, C08, C SB2 C04, C06, C SB3 C04, C06, C10 39

40 Power5 processor-based (not HMC managed) The embedded support was not supported for Operations Console at V5R3M0. Support started with V5R3M5 along with the new plus models. This allowed the use of a local console on a network (LAN) on systems with an IS adapter. Full IOP-less function for add-in adapters was supported starting in V5R4M5. Type Model Local console on a network (LAN) & twinaxial 515 Embedded port (2, 3) C5, C2 520 Embedded port (2, 3) C5, C Embedded port (2, 3) C5, C2 525 Embedded port (2, 3) C5, C2 550 Embedded port (2, 3) C4 (1) 570 Embedded port (2, 3) C4, C6 595 C4 (2, 3) 40

41 Power6 processor-based (not HMC managed) Type Model Local console on a network (LAN) & twinaxial 9406 MMA HEA, C4, C2 (2, 3, 4) M15 HEA, C4, C2 (2, 3, 4) M25 HEA, C4, C2 (2, 3, 4) M50 C1, C2, C3, C5, C4 550 (2, 3) (1) If an IS is installed then no LAN card or WS card (V5R3M0 only) (2) The embedded Ethernet port is the default location. You must disable this support in order to use an external 1 Gbps Adapter such as a 5706/ /5768 (Power5 processor-based/6 only & V5R3M5 or later) (3) OPSCONSOLE macro or console service function (65+21) +Bn for card selection (V5R4M5 or later) (4) The IVE (HEA) is the default resource. Use the top, or right-most port. What if my non-hmc managed system has an embedded Ethernet port? The following information only pertains to systems that are not partitioned and therefore aren't Hardware Management Console (HMC) managed. If your system is HMC managed then you should tag the specific adapter resource you wish to use for the partition. Pre-Power5 processor-based The only model with a supported embedded Ethernet port is the By default, this is the only supported resource when using a local console on a network (LAN). However, if this port reports as failed the system will look at the following locations for an acceptable adapter resource in the order given: C03, C02, C01 Power5 processor-based The first embedded Ethernet port is now the default for a local console on a network (LAN) starting with V5R3M5 of Licensed Internal Code. Prior to this code level the embedded Ethernet port could not be used for Operations Console (LAN). If you want to use a different adapter for console you have to disable support for the embedded port. 41

42 Power6 processor-based By default, a non-hmc managed system will use the first embedded Ethernet port, top or right-most. The system automatically reserves a logical port for each physical port available on the IVE. If you want to use a different adapter for console you have to disable support for the embedded port. What are the network requirements for a local console on a network (LAN)? Basically, the network requirements are pretty simple. The PC client needs to be able to connect to the target system or partition using whatever means is best in your working environment. However, in order to set up a new system and perform some changes to the console there may additional requirements. To set up a new system, for example, the system relies on the BOOTP process in which the system sends out broadcast information which is answered by the PC client. The network infrastructure needs to be capable of passing this broadcast data through the network to the PC client. With the increasing sensitivity to security on networks, some users have elected to isolate the console from their normal network. You can connect a Ethernet cross-over cable directly between the PC and the pre-power5 processor-based system. On Power-processor-based models, if you use a 1 Gbps adapter, such as a 5706/5707 or 5767/5768 you don't even have to use a cross-over cable. A standard Ethernet cable would work just fine since all adapters built after the 2849 have sensing hardware function that automatically uses either cable type. A crossover cable is a standard network cable that has the transmit and receive signal wires reversed. This virtually allows each end to act as if a hub, switch, or router were between them. The use of a crossover cable might also require a nonstandard network configuration at the system and PC. V6R1 introduces the ability of the PC client to detect new V6R1 systems using a proprietary method called VSDISCOVER. It uses the same requirements as BOOTP except the broadcast packets are initiated at the PC client instead of the system. 42

43 Local console directly attached Supported asynchronous communication adapters for a local console directly attached configuration Supported asynchronous adapters, depending on platform: Adapter type Restrictions 2699/9699 Two-Line WAN IOA V5R3 & V5R3M5 SPD hardware only 2721/9721 PCI Two-Line WAN IOA V5R3 & V5R3M5 SPD to PCI migration tower hardware only 2745/9745 PCI Two-Line WAN IOA V5R3 thru V5R4M5 Pre-Power5 2771/9771 PCI Two-Line WAN IOA processor-based and Power5 processorw/modem based - Requires IOP 2742/6805 PCI Two-Line WAN IOA V5R3 and later Pre-Power5 processorbased V5R4M5 IOP-less Power-processorbased 2793/2794 PCI Two-Line WAN IOA V5R3 and later Pre-Power5 processorw/modem (See table below) based V5R4M5 IOP-less Power-processorbased 576C/2893/2894 PCIe Two-Line V5R4M5 (or later) Power6 processorwan IOA w/modem (See table below) based only 43

44 Power6 processor-based and later Sales Feature Feature Code (Order #) (WRKHDWRSC *CMN) 2793/ (0614/2793/9793) 6803/ / / / / / C Supported adapter locations in primary partitions or nonpartitioned systems Systems managed by a Hardware Management Console (HMC) or pre-power5 processorbased systems that have logical partitions use tagging to designate the console resource. Operations Console does not use any embedded serial ports located on the system. Graphics of system locations for Operations Console on page 106. Pre-Power5 processor-based primary partitions and non-partitioned systems Type Model ECS/Async C C C C Graphics page Graphics page C C C C C C C C SB2 C SB3 C02 44

45 Power5 processor-based (not HMC managed) The series typically had a 2793/2794 adapter in C03 for systems ordered with Operations Console (Direct) driven by an IOP at V5R3M0. In V5R3M5 the 2793/2794 was supported as IOP-less in C04 but only for remote service or other point-to-point communications, not for Operations Console. Operations Console didn't fully support IOP-less function until V5R4M5. Type Model ECS/Async C3 C4 C2 (2, 3) C3 C4 C2 (2, 3) C3 C4 C2 (2, 3) C3 C4 C2 (2, 3) C2 (1, 3) C2 (3) C2 (3) Power6 processor-based (not HMC managed) Type Model ECS/Async 9406 MMA C1, C4 (3) M15 C1, C2, C5 (3) M25 C1, C2, C5 (3) M50 C1, C2, C3, C5, C4 550 (3) (1) If an IS is installed then use C5 (V5R3M0 only) (2) OPSCONSOLE macro or console service function (65+21) + Fn for card selection (V5R3M5 with PTF MF39303) (V5R4M0 with PTF MF39304) (3) OPSCONSOLE macro or console service function (65+21) + Fn for card selection (V5R4M5 or later) 45

46 Supported cables Console cable Model / /170 Feature Code (card) , 2742, 2745, 2771, , 2745, 2771, /810/820/825/830/840/ M C, 2742, M C, 2742, M C, 2742, MMA C, 2742, 2793 Part Number (cable) 97H7556 (0328) 97H7557 (0367), 39J H7557 (0367), 39J H7557 (0367), 39J H7557 (0367), 39J H7557 (0367), 39J H7557 (0367), 39J5835 RCP cable - Support dropped for parallel in V5R4M0 / Serial RCP went away with no supported HW in V5R4M0 Server Part Number (cable) /820/830/840 (1) 04N5592 (2) 53P5704 All other systems 97H7591 (0381) Note 1. Currently, these servers support the remote control panel only under Windows NT Workstations 4.0, Windows 2000, and Windows P. Note 2. There is a missing pin in the connector at one end of this cable. This end connects to the system. The new cable is labeled don t trust missing pin Parallel cabled RCP not supported in V5R4 and later 46

47 What communications port(s) are required for Operations Console? For the configuration wizard to configure Operations Console successfully, you need to verify that you have an available communications port. If you have a pre-power5 processor-based system with V5R3 or V5R3M5 and it uses a serial remote control panel cable the PC requires a serial port, also. If your system supports a serial remote control panel and you plan to use it along with the console, the PC must have two serial ports. You need a connector for a communications interface such as a serial port. Operations Console supports serial COM ports 1-9. One COM port is required for system console support. Note: Operations Console does not use any embedded serial ports located on the system. To check that you have an available communication port, check the documentation for your PC or with the PC manufacturer to verify you have the necessary communications port or ports. When you configure Operations Console, the wizard will search for a port for the console. The use of a Universal Serial Bus (USB) to serial port adapter support has been added to Operations Console. The adapter will be placed at the PC end of the console serial cable and connect to the PC's USB port. When installing the USB adapter, follow the manufacturer's instructions, the operating system will assign a serial port to that adapter, COM 4, for example. This adapter will be used exclusively for the console. As above, Operations Console supports serial COM ports 1-9. Any adapter should work but IBM can not guarantee every adapter to work correctly in every PC environment. Should a failure occur, you can contact the manufacturer of the adapter, the manufacturer of the PC, your hardware service provider, or you can try another adapter. Also, the use of a serial PCMCIA adapter on a notebook is also supported as long as the communications port provided is within the range supported by Operations Console. However, IBM does not guarantee that all adapters will work in all situations. Restrictions on use The adapter must plug directly into a USB connector on the PC. Neither the use of a USB hub to share connections nor the use of USB extension cables is supported, however these devices may function correctly in some situations. Parallel directly attached remote control panel (V5R3 only) Operations console uses LPT port 1. A directly attached remote control panel is not supported on any system starting with V5R4. 47

48 Other references What are the software requirements for Operations Console? Operations Console is supported on Windows NT workstation (V5R3 only), Windows 2000 Professional, Windows P Professional, and Windows Vista. Note: Windows Vista can only be used for a local console on a network configuration. You cannot use Windows Vista for a local console directly attached. Use the instructions for Windows P for any instructions. PC5250 or IBM Personal Communications V5.9 (V5.7 with CICS system definition data set (CSD) 1 minimum) needs to be installed for the console only. It is not required for configurations that are used only for remote control panel. Note: If you run any software that enables SOCKS on your PC (the PC accesses the Internet through a firewall, such as Microsoft Proxy Client, Hummingbird SOCKS Client, NEC SOCKS 5, or others), you cannot route the subnet for to the firewall. Operations Console uses addresses in the range of to Incorrect routing causes Operations Console to fail. Check your SOCKS configuration and make sure that the entry is: Direct

49 What is the meaning of the field Current state of console tag on the Select Console window? For a partitioned system or partition the state supplies debug data for console failures by showing the data. This data is available to any device capable of accessing SST. In addition to this data, there is expanded data available in SRC A in word 16. Select Console System: Allow console recovery and console can be taken over by another console Select one of the following: Console type Twinaxial 2. Operations console(direct) 3. Operations console(lan) 4. Hardware management console(hmc) Current state of console tag IOCS0 1=Yes, 2=No 3 0 Taken from the help text: Current state of console tag This field indicates the current state of the console tag if this is a logical system partition. The device (IOA) or resource (IOP) tag value can be 0 = No device or IOP found or tagged 1 = Twinaxial device tagged 2 = Async direct attached device tagged 3 = LAN attached device tagged 4 = HMC device tagged. 5 = IOP resource tagged, device could be async or LAN or twinaxial device. 6 = Invalid IOA device tagged. It is normal for a value of 0 (zero) when the system is not partitioned. 49

50 Operations Console simplification (V6R1) Operations Console can automatically create service tools device IDs, manage access passwords, and discover systems. Operations Console automates working with service tools device IDs. The system, by default, is set to maintain up to ten service tools device IDs of a maximum value of 49 in addition to QCONSOLE. You no longer have to manually create a new device ID when adding a PC to connect into a system or partition. See Autocreate service tools device IDs below for more details. Also, Operations Console takes control of the access password activity for you. The authentication process remains the same, but when this function is active, you are not asked to enter the access password during a connection. However, you must provide a DST user ID and password to successfully connect. This function does not affect a local console that is directly attached or any other console type. See Automatic management of the access password below for more details. Auto-discovery of systems running V6R1 of Licensed Internal Code takes place each time Operations Console is started or on-demand by pressing Alt+w (or Alt+W). See Automatic discovery of systems below for more details. Autocreate service tools device IDs By default, the operating system sets the value of the Autocreate service tools device IDs option to 10. This default value gives you 11 connections to be automatically managed. You have QCONSOLE as a default ID and then 10 additional service tools device IDs. These display as QCONSOLE00, QCONSOLE 01, through whatever value is set. It is recommended that you have at least one spare so you need not remember to increase the value if you try to add an additional connection. These service tools device IDs are listed in the Work with Service Tools Device IDs window so you can keep track of how many are created. However, the device ID QCONSOLE is listed and can be used normally. For example, if you create a service tools device ID with a name of QCONSOLE02, when the third connection is established to use the auto created device IDs, the ID is given out as if it were created automatically. You can change the default value of the Autocreate service tools device IDs option. This function is used for any new configured connections you create. This means that if you upgraded from a prior release of Operations Console on the PC, your current configurations are retained and continue to work just as they did before. However, if the PC and system do get out of synchronization, instead of issuing an error message to resynchronize them, this function automatically recovers the issue. 50

51 When you create a local console on a network configured connection, you need to enter the name of the service interface (service host name.) The name you use depends on the circumstances for the connection. For example, if this is a new system and this is the first console to connect, then the name might be whatever you want to call it or it might be what a DHCP server gave it. There may be times in which you configure a connection with an auto-created service tools device ID, grant access to the remote control panel, then at a later time you connect and find that you no longer have a remote control panel. This is the result of a change in the assigned service tools device ID. Something occurred, possibly not connecting this device in a few days for instance, so the service tools device ID got reset. A reset of the device ID includes revoking permission to the RCP, so you, again, have to manually grant permission to the RCP. Currently, the only way to prevent this would be for you to create a specific service tools device ID for this configured connection and delete the previous one. Automatic management of the access password By default, you cannot set an access password when you create an Operations Console configuration. An access password is automatically generated and supplied to the connection process at the appropriate time. You do not need to know this password as it is automatically managed by the system. However, if you do want to change the access password, you can do this on the Properties page. Changing this password causes the automatic process of supplying the password to be disabled. You need to enter your access password for any connection that requires an access password. The sign-on process requires a valid DST user ID and password to be entered to authenticate the user. Automatic discovery of systems When Operations Console starts, a search for qualified systems begins. A "qualified system" is any system running V6R1 with an active service host name (service interface). It does not need to have Operations Console as the console type. If the PC gets a response from the network for any qualified systems, Operations Console creates a configuration for that system. It also preserves any pre-existing configured connections. A qualified system must have a value set for the Autocreate service tools device IDs option, which has a default value of 10. If this value is zero, the system might not report correctly and therefore might not show up in this auto-generated list of systems. This auto-discovery function occurs any time Operations Console begins or when performed on-demand by holding down the alt key, the shift key, and then pressing w, or alternately, by holding down the Alt key and pressing the w key. This causes Operations Console to begin a new search for eligible systems. 51

52 Important: If a system shows up in the list of configured connections, it does not guarantee that the system can be connected to. In rare cases, there are conditions in which the system is able to satisfy the requirements to report but not meet all requirements for a connection. This function can be turned off by entering the Settings window by holding the Alt key and pressing the shift key and then the s key (Alt+S). You can then turn off the Auto-discover function. 52

53 Troubleshooting system reference code (SRC) data The following SRCs are available here for look-up and analysis: A6nn500x, A , A , A , A , D , A , A , D , C SRCs A6nn500x These system reference codes (SRC) are used to access console types and console tasks associated with the console service functions (65+21). These SRCs are associated with the operation of the control panel method to change the console type or accomplish a console task when the console or other workstation is not available. For more information on how to use this function, see Using the console service functions (65+21). Note: nn can be any alphanumeric designation. A6nn 500A - You are displaying the current console value setting. A6nn 500B - You did a second so you are in edit mode. A6nn 500C - You executed a second 21 to cause an action, such as setting the console to another value. A6nn 500D - Too much time elapsed after entering edit mode to cause an action so you must enter edit mode again if you intend to make a change. A function 21 at this time forces the console to DST, not causing an action. 53

54 SRCs A , A , and A These system reference codes (SRCs) are used for a console that fails during initial program load (IPL) (not Operations Console). The following SRCs might be displayed for twinaxial consoles. A A console resource (controller) was not found when the server was started. A A console device was not found when the server was started. A twinaxial controller was found but cannot be used. This indicates only the presence of a controller. It does not indicate that the controller can be defective. A A console device was not found when the server was started. The controller (6A59) was found but the connection is starting. This can be a problem with the device or emulator, or the data flow path is not being established or maintained. These SRCs, as well as the attention light, are reset when a console is detected and becomes active. It is possible that you might have to restart the server to find a console device again if one of these SRCs exists for a long period of time, depending on many factors, including model, hardware present, etc. You can force the server to try to find the console again by doing a function 21 from the control panel, remote control panel, or virtual control panel. You can also use the console service functions (65+21) to gather data or attempt recovery. 54

55 SRC A This system reference code (SRC) is used for a console that fails during a manual IPL (Operations Console or D-mode IPL). The data present in this SRC has evolved from V5R3 to the latest code. Some of these changes were introduced using PTFs and later used in the next release's base code. Not all words within the SRC are used for all problems. Use the following tables if you received SRC A If restarting the server did not find a console and if the console type is set to anything except a 1, the system displays code A If you are attempting to use a twinaxial console, the only data relevant in this SRC is word 16. Use the following table to determine the twinaxial failure. The first four characters of this word contains the last four characters of the original failure type. For example, if word 16 contains , the twinaxial-related SRC is A and the console type is set to use a twinaxial console. If you are attempting to use Operations Console, select the appropriate section in the table below as follows: Local console on a network (LAN) uses words 13, 14, and 15. Local console that is directly attached uses words 17, 18, and 19. Note: If you just replaced the LAN adapter associated with a local console on a network (LAN), you need to wait at least 35 minutes for the server to find and use the new LAN adapter. In this case, after the server is satisfied, it starts using the new adapter, the console starts, and the SRC disappears. This topic will provide a step-by-step analysis, on page 63 of an example A SRC and provide the meaning of the data along with applicable usage and reference what needs to be performed in order to make a change. Keep in mind that you do not have to follow this step-bystep method to get to the meaning of the various parts of the data. The words of data are represented differently depending on how you accessed the data. In our example you see words 1 thru 9 which would correspond to functions 11 thru 19 on older physical control panels or the RCP/VCP. Here's a very common SRC we'll work with: Word 1: A Word 2: 03D00061 Word 3: 06C00004 Word 4: Word 5: C Word 6: 50070A03 Word 7: FA Word 8: Word 9:

56 Here the data is broken down into the significant pieces: Click the link in the data areas to go to the appropriate table of details. Word Data Significant Data A Base SRC Not used Significant Data Significant Data 11 A D C AA LAN flag C0 BB Assigned direct connect location 0004 CCCC LAN console reason code for the failure C A03 0A GG Tag information 03 HH Console type FA DDDDDDDD Depends on reason code in word 13 C EEEEEEEE Depends on reason code in word FFFF If the console is twinaxial this is the SRC that would have been displayed FA JJJJJJJJ Direct cable reason code KKKKKKKK Depends on reason code in word LLLLLLLL Depends on reason code in word 17 56

57 Word 13 (AA BB) of AA BB CCCC The following table contains the Word 13 values for the AABB status indicators, which display differently depending on the system's code level and whether or not you have installed PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0). The AABB values only display on systems that are not managed by a Hardware Management Console (HMC). V5R3/V5R4 Without PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0) AA means: E1 - Allows the internal embedded adapter No support for the internal embedded adapter. Example BB means: E2 - Allows the external adapter No support for the external adapter. E1E20005 (AA BB CCCC) = Allows both the internal embedded adapter and external adapter (typical values for new systems). The system is on the network, but is not communicating with the PC. V5R3/V5R4 With PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0) AA means: E0 - System is upgraded from V5R3 and support for the 1 GB Ethernet adapter is not set. E1 - Disabled. Both the internal embedded adapter and external adapters are not being searched for. E2 - Allows the internal embedded adapter. E4 - Allows the external adapter. E6 - Allows both internal embedded adapter and external adapter. BB means: C2, C3, or C4 - Location of selected asynchronous adapter used for console, ECS, and remote service. Note: C4 cannot be selected for use with the console when using the 2793 asynchronous adapter, but it can be selected for use with ECS and remote service. Example E6C30005 (AA BB CCCC) = Allows both the internal embedded adapter and external adapter (typical values for new systems), and the asynchronous adapter can be used for console, ECS, and remote service. The system is on the network, but it is not communicating with the PC. 57

58 V5R4M5 and later Word 13 reason codes as AA BB in the 5008 SRC code AABBCCCC: A E E F A Embedded or External flag state (0 or E) Embedded flag is on 0 D-mode with no flags 1 no LAN flags are on - This is the disable flag. 2 Embedded is enabled 4 External is enabled 6 Both internal and external enabled Only the external flag is on 0-5 Selected LAN card location BB Selected Async card location C1 - C5 F FF HMC managed, Thin Console or Primary / standalone on Pre-Power5 processor-based Examples for AABB 06C0 Both internal and external enabled and no async card has been selected. E1C2 Only the external flag is on and the LAN adapter in C1 has been selected. The async adapter in C2 has been selected. 58

59 Word 13 (CCCC) of AA BB CCCC Word 14 (DDDDDDDD) Word 15 (EEEEEEEE) The following table defines the Words 13, 14, and 15 values. Word 13 (AA BB CCCC) for a local console on a network (LAN). (AA BB CCCC) If Word 13 value (CCCC) is: 0000 Failure Unexpected condition 0001 No supported hardware detected or hardware detected is not expected. For example, you replaced the LAN IOA so the serial number is different LAN IOA failed to report Hardware error LAN Word 14 DDDDDDDD means: Could report any word 14 data for any of the other reason codes (cccc) Common error codes: 53001A80, 53002AC0 Network, cable or the LAN adapter might not be operational. Word 15 EEEEEEEE means: Could report any data for any word 15 of the other reason codes (cccc) In some cases the serial number of the expected adapter might be displayed. If a serial number is displayed, an adapter was previously configured. If you are installing a new server or partition that you will rely on BOOTP to complete the configuration, you might have to clear this data using the console service functions (65+21). Adapter position or serial number of adapter : This error code indicates the adapter reported, but is not initialized yet. This is not considered an error at this time. The adapter should be activated shortly (AA BB BOOTP status: If attempts are zero, then BOOTP is ready when called. If attempts have a value, then the PC did not respond. Failure For other error codes, contact your service provider. Attempts Word Adapter position or serial number of adapter Word 15

60 CCCC) If Word 13 value (CCCC) is: 0005 FFFF DDDDDDDD means: Server's LAN connection IP address is active, but the PC failed to connect. Are the PC and server on the same network? Are they using the same protocol? Can the PC ping the server? (ping serverhostname) The system has a problem with the alternate stack. EEEEEEEE means: Adapter position or serial number of adapter Word 16 (FFFF) of FFFF GG HH The following SRCs might be displayed for twinaxial consoles. twinaxial equivalent SRC Description code A A console resource (controller) was not found when the server was started. A A console device was not found when the server was started. A twinaxial controller was found but cannot be used. This indicates only the presence of a controller. It does not indicate that the controller can be defective. A A console device was not found when the server was started. The controller (6A59) was found but the connection is starting. This can be a problem with the device or emulator, or the data flow path is not being established or maintained. 60

61 Word 16 (GG) of FFFF GG HH Value Description (HE) 1 Supported, reporting workstation IOA in the tagged IOA location. 2 Reporting communications IOA in the tagged IOA location with at least one reporting port that supports the async protocol and needed physical interface 3 Supported, reporting LAN IOA in the tagged IOA location, or a LAN port with the tagged port DRC (used for HEA). 4 HMC console has been configured. 0A No console IOA tag, no console IOP tag, and no console port DRC tag found, and HMC console has not been configured. Note: This is normal for standalone systems since they don't involve tagging. 0B A physical slot number cannot be determined from the IOA tag. 0C No reporting IOA in the tagged IOA location. 0D More than one valid, reporting console IOA in the tagged IOA location. This is an unexpected error. 0E A reporting IOA was found at the location specified by the console IOA tag, but it was NOT a communications IOA, and was not valid for any other kind of console (i.e. not twinaxial). The following codes are new at V6R1 0F An IOP has been tagged for the console, and not an IOA nor an HEA port. 10 Reporting LAN ports were found at the location specified by the console IOA tag, but the specific LAN port type (CCIN) is not supported for LAN console. 11 A reporting communications IOA is in the tagged IOA location, but it has no reporting ports. 12 A reporting communications IOA is in the tagged IOA location, but it has no reporting LAN ports, and no reporting ports that support direct connect Operations Console (support the async protocol and have the correct physical interface). 13 No reporting port resource was found with the DRC tag for the console port resource. 14 A reporting port was found with the DRC tag for the console, but it did not qualify for use with operations console. 61

62 Word 16 (HH) of FFFF GG HH HH = Console type The console type value is represented by the last two characters in the form xxxx yy zz. 00 = Not defined by user (old default value) 01 = Twinaxial 02 = Operations console(direct) 03 = Operations Console (LAN ) 04 = Hardware Management Console (HMC) or Thin Console Note: It is expected that a D-mode IPL with a new load source hard disk drive displays the console type value of 00. An example of when this can occur is if the copy of data from a failing hard disk drive does not copy all data or you are installing a new logical partition. Also, there are times when the hard disk drive is late reporting and the console type value is not retrieved in time. In these cases, you can use the console service functions (65+21) to set a console type value or attempt to contact the console again. Words 17, 18, and 19 The following table defines the Words 17, 18 and 19 values for a local console that is directly attached. (JJJJJJJJ) If Word 17 value is: FA Direct cable Failure (KKKKKKKK) (LLLLLLLL) Word 18 means: Word 19 means: Asynchronous adapter not detected No cables detected Adapter position Adapter type Wrong cable detected Adapter position Cable ID Port in use Adapter position Adapter type Not configured for direct cable 62

63 Step-by-step analysis We'll start with the same example data from the beginning of this topic. Here's a very common SRC we'll work with: Word 1: A Word 2: 03D00061 Word 3: 06C00004 Word 4: Word 5: C Word 6: 50070A03 Word 7: FA Word 8: Word 9: You normally know the console type you are trying to connect. Let's start with that. The console type is located in word 16 (FFFF GG HH) so the data Word 6: 50070A03 means that our example system's problem is with LAN console. Of course if you got this value and you were trying to use another console type you know this is the problem. If that's true, assuming you don't have another device to use, you would use the console service functions (65+21) to set the correct console type. For this example a value of 03 (Operations Console (LAN)) is correct. The next piece of data of concern is the tag information, also in word 16 (FFFF GG HH), shows a value of Word 6: 50070A03. From the appropriate table you can see that it means: 0A No console IOA tag, no console IOP tag, and no console port DRC tag found, and HMC console has not been configured. Note: This is normal for standalone systems since they don't involve tagging. So if this was representing a single partitioned then this isn't the problem. However, if this represented a different value, such as 0A you see the console is incorrectly tagged. 0C No reporting IOA in the tagged IOA location. For this example, the data is correct so we'll move on. Note: We already know that this is a local console on a network (LAN) so the only data left that is relevant is in words 13, 14 and 15. Words 17, 18 and 19 have no bearing, which is further represented with: Word 7: FA FA Not configured for direct cable 63

64 Another possible problem affecting a Power-processor-based system not managed by an HMC is, as in our example system, whether the LAN flags are correct. If we are trying to use the embedded port for the console the embedded port flag must be turned on. The data: Word 3: 06C00004 V5R4M5 and later (our example system) Reason codes as AA BB in the 5008 SRC code AABBCCCC: A E E F A Embedded or External flag state (0 or E) Embedded flag is on 0 D-mode with no flags 1 no LAN flags are on - This is the disable flag. 2 Embedded is enabled 4 External is enabled 6 Both internal and external enabled Only the external flag is on 0-5 Selected LAN card location BB Selected Async card location C1 - C5 F FF HMC managed, Thin Console or Primary / standalone on Pre-Power5 processor-based The only part of the table we're concerned with is AA. The value in BB isn't used for a network attached console. If you look under AA you see that both the embedded port and the external port flags are on. This is the default value from manufacturing. Since the embedded port is on, the external flag isn't considered. So this is good also. If the data had indicated a 00 or 01 then the system wouldn't be able to use the embedded port. In this case you'd have to use the console service functions (65+21) to set the correct flags. Another scenario might be that AA had a value of E0 which would indicate an intent to use an external 1 GB Ethernet adapter such as the 5706 but the adapter location has not been selected yet. 64

65 That only leaves the reason code in word 13. Word 3: 06C00004 Word 4: Word 5: C (AA BB CCCC) If Word 13 value (n) is: 0004 Failure BOOTP status: If attempts are zero, then BOOTP is ready when called. If attempts have a value, then the PC did not respond. Word 14 DDDDDDDD means: Attempts Word 15 EEEEEEEE means: Adapter position or serial number of adapter Word 14 has a value so the data is indicating BOOTP was taking place at the time the SRC was issued. There are numerous reasons for this condition: The system serial number might be in error when you created the configured connection. Delete and recreate the configured connection. The partition number might be in error when you created the configured connection. Delete and recreate the configured connection. The system and PC aren't connected to the system in a way that broadcast packets sent by the system can be detected by the PC. Either connect the PC or system to the same hub, router or switch, or configure the network device to pass broadcast packets. If you are setting up a Power6 processor-based blade check that you have bridging properly enabled in VIOS/IVM. Word 15 is rarely used when the system is using V5R4M5 or later of Licensed Internal Code since the system uses the UID (Universal Identifier) of the adapter to find the resource and for the embedded there is no card slot so this data often contains just the C to indicate no slot number. Also, there are conditions in which a location or adapter serial (or UID) cannot be determined so you may see just

66 D after attempting to activate the asynchronous communications adapter This system reference code is used primarily to debug a failure to activate the asynchronous adapter for a console directly attached or remote service. However, it can be useful in getting information, such as the LAN flags/adapter without the need to see a SRC of A Note: The same data is also represented when the system posts an SRC D The words of data are represented differently depending on how you accessed the data. In our example you see words 1 thru 9 which would correspond to functions 11 thru 19 on older physical control panels or the RCP/VCP. Here is an example: Word 1: D Word 2: 0D Word 3: 06C41015 Word 4: Word 5: Word 6: F Word 7: Word 8: Word 9: Not returned or used for this function 66

67 Data broken out into significant pieces: Click the link in the data areas to go to the appropriate table of details. Word Data Significant Data D Base SRC Not used Significant Data Significant Data 11 D D C AA LAN flag C4 BB Assigned direct connect location CC DD CC = IOP state DD=Reason code for failure on activation F EEEEEEEE initialization return code FFFFFFFF activation return code F GGGGGGGG cable ID Not used Not used Not returned or used 67

68 Word 13 Word 13 values for the AABBCCDD status indicators display differently depending on the system's code level and whether or not you have installed PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0). Values AABB only display on systems that are not managed by a Hardware Management Console (HMC) so the expected values are 0000 or FFFF. Note: References to the RV port means the port in which you would attach the console cable or an external modem. V5R3/V5R4 Without PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0) If Word 13 value is: Without PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0) AA means: E1 - Allows the internal embedded adapter No support for the internal embedded adapter. BB means: CC means: DD means: E2 - Allows the external adapter No support for the external adapter IOP RV port 20 - IOP internal modem 30 - IOPless RV port 40 - IOPless internal modem FF - No supported resource or port was found 00 - Received OK status from modem 01 - CTS time out 02 - Received Connect status from PC client 03 - Stop request 07 - Received function 66 while active 08 - Failed to find port 16 - Port not found 68

69 V5R3/V5R4 With PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0) If Word 13 value is: With PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0) AA means: BB means: CC means: DD means: E0 - System is upgraded from V5R3 and support for the 1 GB Ethernet adapter is not set. E1 - Disabled. Both the internal embedded adapter and external adapters are not being searched for. E2 - Allows the internal embedded adapter. E4 - Allows the external adapter. E6 - Allows both internal embedded adapter and external adapter. C2, C3, or C4 Location of selected asynchronous adapter used for console, ECS, and remote service. Important: If you have a system that was shipped with Licensed Internal Code (LIC) prior to V5R4M5, you cannot select slot C4 for use with the console when using the 2793, but you can select slot C4 for use with ECS and remote service IOP RV port 20 - IOP internal modem 30 - IOPless RV port 40 - IOPless internal modem FF - No supported resource was found 00 - Received OK status from modem 01 - CTS time out 02 - Received Connect status from PC client 03 - Stop request 07 - Received function 66 while active 08 - Failed to find port 16 - Port not found Example: With PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0) E6C (AABBCCDD) = Allows for the internal embedded adapter and the asynchronous adapter. The asynchronous adapter is located in slot C2, which is running with IOP support, can be used for console, ECS, and remote service. The system is directly connected and is communicating with the PC. 69

70 V5R4M5 and later Reason codes as AA BB in the D SRC code AABBCCDD: A E E F A Embedded or External flag state (0 or E) Embedded flag is on 0 D-mode with no flags 1 no LAN flags are on - This is the disable flag. 2 Embedded is enabled 4 External is enabled 6 Both internal and external enabled Only the external flag is on 0-5 Selected LAN card location BB Selected Async card location C1 - C5 F FF HMC managed, Thin Console or Primary / standalone on Pre-Power5 processor-based If Word 13 value is: CC means: Word 13 values for the AABBCCDD status indicators With PTF MF IOP RV port (V5R3M5) or PTF 20 - IOP internal modem MF39304 (V5R4M0) 30 - IOPless RV port 40 - IOPless internal modem FF - No supported resource was found DD means: 00 - Received OK status from modem 01 - CTS time out 02 - Received Connect status from PC client 03 - Stop request 07 - Received function 66 while active 08 - Failed to find port 16 - Port not found Note: Only the most common values for DD are documented here. If you have a value other than what is provided, contact your service provider. 70

71 Words 14 (EEEEEEEE) and 15 (FFFFFFFF) Word 14 contains the reason an SRC of D is returned. A successful activation usually occurs when the console type value is set to Operations console(direct), value of 02. All zeros for word 14 indicate the server was able to activate the asynchronous communications adapter but the resulting failure SRC was issued because the system was unable to detect the correct condition on the cable. The most common reason for this is that the serial port on the PC is in an unexpected state. Powering off the PC and then powering it back on might clear this condition. An unstable Client Access installation might also cause this condition. Try uninstalling and then reinstalling Client Access, and removing the Operations Console connection modem, and reinstalling it might correct this condition. (EEEEEEEE) If Word 14 value is: (FFFFFFFF) If Word 15 value is: CC CC10031A Word 14 means: Successful activation Port not found No cable attached Activation failed (see word 15) Word 15 means: Resource might be in use Cable mismatch or country code not set (Use CHGNETA to set country code, if needed.) Note: Only the most common values are documented here. If you have a value other than what is provided, contact your service provider. Word 16 Word 16 contains the cable ID which is expected to be Another value or might indicate a wrong cable or no cable at all. Don't assume that a value of is no cable since some asynchronous communications adapters can provide a value here even when no cable is attached. 71

72 SRC A The console creation fails in i5/os. These are some possible reasons you might receive system reference code (SRC) A : The console was not found by i5/os. The server value QAUTOCFG must be set to ON. Use one of the following to verify or set this system value on the server: Use the WRKSYSVAL QAUTOCFG command. During a manual IPL, in the IPL Options window, for Set major system options, select Y. Then for Enable automatic configuration, select Y. If you just migrated the console from one type to another and the new console fails to work in i5/os, you might need to use another workstation to manually delete the controller and device description associated with the old console device. Note: You might be able to use the console service functions (65+21), on page to assist in a recovery or gathering resolution data. SRC A This system reference code (SRC) occurs during a manual initial program load (IPL) when the system obtains a console, but the console closes. Note: The console type does not affect this SRC. These are some possible reasons why you might receive SRC A : 1. If you IPL the server to DST and then close the emulator, disconnect the console, or close Operations Console after the console is found. 2. If a console is found, but then the server loses the console connection. This SRC disappears if the console is reassigned and the server can locate a console. 72

73 Failure to display D and D automatically after calling the function When working with servers that have a double row for the Function/Data window, after calling the function 65 or 66, the control panel might not automatically display the resulting system reference code. In these cases, you must do a function 11 to determine whether the function 65 or 66 completed successfully. If you were doing an activation (66) and the function did not complete successfully, see D Note: This pertains only to those servers without a Hardware Management Console. 1. Using the control panel or the remote control panel, press the Up or Down buttons until 11 is displayed. 2. Press Enter. For more information, see Reference codes list for customers. Startup step C takes longer than expected in Dmode IPL This can be the result of a problem or configuration change. If you are troubleshooting a connection issue, you can force the system to end the search for the console by performing a function 21 (enable DST) from the control panel, remote control panel, or Hardware Management Console. This speeds the process of posting a failing system reference code (SRC) without waiting the entire search time, which can be 45 minutes or longer. Allow the system to attempt to find the console for five or 10 minutes before circumventing the step unless you expect a failure to occur and only need to retrieve the SRC data. Important: Use care when considering this bypass function. Bypassing the remaining time in the process of the search might prevent a correctly working console from being activated in some cases. 73

74 Chapter 2: Considerations for planning Use this chapter to determine what might influence your intended console or backup console. All systems - General Operations Console considerations What if I need more than one adapter of the type currently used as the console? If you need additional network or asynchronous communications adapters in your system special consideration should be given to where you place or designate for console and backup console. Consider the following: Pre-Power5 processor-based systems Non-partitioned Since the adapter used for console is selected by location try to locate the additional adapter(s) in locations not eligible for console use. Partitioned Since you tag at an IOP level for console you can place additional cards so they are associated with a different IOP. If you cannot do this you run the risk that the system will be unable, in all cases, to determine which adapter to use when activation occurs. This is even true if the second adapter is intended to be used in an emergency as the backup console. Using a backup console of a different connectivity, a Local console directly attached as a backup to a local console on a network (LAN) instead of a second network adapter is recommended. Power5 processor-based and Power6 processor-based systems Non-partitioned The system still determines the console resource by location but some models and releases allow an individual adapter to be designated for the console. V5R3M5 uses PTF MF39303 to add this capability for a model V5R4M0 uses PTF MF39304 to add this capability for a model Starting with V5R4M5 support for additional models to be able to designate a particular location was implemented. See Chapter 1: Reference on page 13 to find out if your model has this capability. Partitioned Power5 processor-based and Power6 processor-based systems typically tag the console at an IOA level so you can specify the individual adapter to be used. The Console tag determines the console for all consoles and the Operations Console tag is also set if you plan to use a Local console directly attached. 74

75 What is Allow console recovery and console can be taken over by another console? There is also a special set of console options called Allow console recovery and console can be taken over by another console. This set of functions allows Operations Console to take control from another console device. The default value of this console option is disabled. Twinaxial devices use a special 5250 emulation and do not qualify for this takeover and recovery function. When the option is enabled: The first Operations Console device connected becomes the console. Additional LANconnected Operations Console devices will have a special DST signon. All other 5250-based connections will display the new Console Information Status window. Console recovery without the loss of the job is available. When the option is disabled: The first Operations Console device connected becomes the console. All other 5250-based connections will be presented the new Console Information Status window. Console recovery without the loss of the job is not available. Can more than one console be made available for use as necessary? Operations Console, both local console directly attached to the server and a local console on a network (LAN), HMC, and twinaxial workstations, can coexist as console-capable devices if you remember the following rules: Only the configured console type is supported. If no console type is specified, such as when a new partition is being created, the supporting hardware tagged by the HMC is used. If there is no HMC, then the console is determined by any eligible adapters by location. If more than one eligible adapter is found, then the first connected device determines the console. 75

76 In the case of a server without an HMC, for example, if you use Operations Console (Direct) as the console type and you have a LAN adapter that is available to support a console, and has a valid configuration, then the console is the directly attached PC. However, the LAN adapter is started at IPL time and the connecting PC, one or multiple, displays the Console Information Status window. The field Take over the console displays NO and the message at the bottom of the window indicates that this device is not the supported console type. Back in V5R1 and V5R2 if you had adapters present where they could be used to support a console you could actually switch from one console to another very simply. For example, if the console type was set to Operations console(lan) you could disconnect your console and start a twinaxial workstation or even Operations Console (Direct). However, it was also found that the system didn't always select the correct console during an IPL. Starting with V5R3, the code was changed to only allow a console using the configured console type. Other connectivities might be able to connect but not become the console. However, there are temporary solutions for the use of a different console. Only one device can be active at a time. A twinaxial workstation on port 0 address 0 can become a console device if twinaxial console is selected. If twinaxial console is selected as the console type, then Operations Console devices might not be started. If there is a configured service host name, for example, to support iseries Navigator, then the system activates the supporting adapter in addition to the twinaxial adapter. If you use Operations Console (LAN) for the console, but you have an eligible asynchronous communications adapter available as a backup, then the LAN adapter is activated to support the console. The asynchronous communications adapter does not automatically get started since the console type value is not set for its use at this time. However, because it is eligible to support the console, assuming the Operations Console tag is set, then the operating system cannot use this resource. Depending on your hardware environment you may have to change just the console type or the console tag. This assumes that the hardware is already installed. 76

77 Can I have more than one connection active at a time? Operations Console allows multiple LAN connections to a single system or logical partition, but only one 5250 session can have control of a system at a time. An active console is the command interface to a system through 5250 emulation or IBM Personal Communications that is currently interacting with the system. More than one Operations Console device might have data on the window but only one is actually active. The client PC also allows multiple local console connections but allows only one Local console directly attached to the system configuration for a single PC. How many 5250 sessions can I have active at a time? There is a maximum of 26 active emulator sessions available per PC. Active emulator sessions are identified by a single letter of the English alphabet (A through Z). You can have more than 26 configured connections, but only 26 of those sessions can be active. If you use 5250 emulation provided by IBM Personal Communications or the PC5250 emulation provided by Client Access for other than Operations Console then those sessions, telnet for example, count as one each of the maximum 26 sessions. If you had 20 active consoles and 6 active telnet sessions you have used the maximum number of emulator sessions. During the course of using these connections, you can close the emulator for a connected configuration to free up an emulator identifier. The next emulation session started can then use that identifier. Another limitation for having multiple connected emulators on the same PC is the amount of available PC resources, memory and video capability, to support a large number of connections. Since each connection and associated functions (console, control panel, or both) will use PC resources, you might need to add more memory to support more connected sessions. Each PC s hardware, operating system, and active programs vary so that there is no clear way to identify in advance how many sessions your particular usage supports. Do I have to be concerned about encryption? Operations Console network connections use a version of Secure Sockets Layer (SSL), which supports device and user authentication without using certificates. By default, Operations Console uses the strongest encryption possible for authentication and data. 77

78 What do I need to be aware of when planning to install a new release of OS/400 or i5/os? Pre-Power5 processor-based systems using a local console directly attached Pre-Power5 processor-based systems have a small risk that a release upgrade may fail when upgrading to V5R3 or later from an earlier release. See Pre-Power5 processorbased systems using a local console directly attached on page 86 for details. All systems: When you receive the i5/os release upgrade, all of the user IDs included with the operating system are expired, except for (eight 1's). For all upgrades and installations, you need to establish a connection between the system and Operations Console using the service tools user ID of This prevents any failed reauthentication of the client connection to the system caused by expired user IDs. This is especially important for automated installations and upgrades. It is recommended that you update Client Access to V6R1 before you upgrade the i5/os operating system. Note: Failure to comply with the above actions may prevent the console from working correctly during the upgrade or installation. Important: During a manual IPL of the system and if no console has been specified before, you receive two additional displays to confirm the setting of the console type. The first requires that you accept your current console type, and the second shows that a value did not previously exist (a zero is present for the old value) and the new value is shown. Press Enter to exit and set the console type automatically. The IPL then continues to the IPL or Install the System display. This condition is most likely to occur during the installation of a new partition, but it can happen on your first manual IPL, for example, during the A-mode IPL following the restore of Licensed Internal Code, or during the upgrade or installation when a console value of zero is found. What do I need to be aware of when planning to upgrade my system to another model? If you are migrating from a different console type to Operations Console on your new system, it is important that you configure your new Operations Console PC before beginning the upgrade. The Operations Console features that match the connectivity you plan to use should be specified as part of the order for your new system. In this way, at the point in the upgrade instructions where console functions are required on the new system, you can perform them on your new Operations Console device. 78

79 Also, when migrating a former load source device that was used with Operations Console local console on a network (LAN) configuration, and this load source device is to become a load source device in a new partition, the LAN adapter must be deallocated before removing the device from the old partition and installing it in the new partition. When you upgrade your system, a change in system serial numbers could prevent the client from answering the BOOTP request if you are relying on this method to configure the service host name on the new system. If the result of your system upgrade includes a Hardware Management Console (HMC), make sure to use this as the system console until your upgrade is complete. Because some upgrades are staged, your intended console might lack the necessary resources for a period of time. Because the HMC uses virtual resources, you will not have problems with a lack of resources for another console type. How does the system determine what the console or console's resource should be? Only the configured console type is supported. If no console type is specified, such as when a new partition is being created, the supporting hardware tagged by the HMC is used. If there is no HMC, then the console is determined by any eligible adapters by location. If more than one eligible adapter is found, then the first connected device determines the console. In the case of a server without an HMC, for example, if you use Operations Console (Direct) and you have a LAN adapter that is available to support a console, and has a valid configuration, then the console is the directly attached PC. However, the LAN adapter is started at IPL time and the connecting PC, one or multiple, displays the Console Information Status window. The field Take over the console displays NO and the message at the bottom of the window indicates that this device is not the supported console type. Every time the system has to determine what to activate for a console, either during an IPL or on demand using the console service functions (65+21) or OPSCONSOLE macro, the system checks for a tag. If the system is partitioned there has to be a tag. The tag would point to a console resource and is converted to a console type value. This value is then saved for use later, if needed. If there is no tag involved, when the system is not partitioned, a check is made to determine if the system has a console type defined. If so, a check is made to determine if the user has designated a particular slot location for the supporting resource. If there is one then it is activated. If not, then a search is performed to determine the resource and activate it. 79

80 If there isn't a console type defined, such as a D-mode to install a new partition, then the system will activate all eligible console resources and use the first connected device for the console. An attempt to save this data is made but in the case where a recovery is in progress and the load source wasn't able to be copied, a new load source doesn't yet have structure (provided by the initialize function) so the save will be aborted. Then, after the Licensed Internal Code has been restored and the system IPLs again you will receive windows in which you will be forced to accept the current console type and the data is saved. Do I have to dedicate a resource to the console? The service interface is typically a single adapter used for service tools. For a local console that is directly attached, if there is no network adapter selected, either by location or partition tagging, then this is the service interface. More commonly it is a network adapter to support either a local console on a network or the service tools server. In the case where there is a valid network adapter available, even if another console is selected and there is a valid service host name associated with the adapter, then this is the service interface. It can support a console, the service tools server, or both. Occasionally the console is not connected using this network adapter, but the service tools server is configured to support the Navigator interface for hard disk drive configuration or similar functions. With Version 6 Release 1, the service interface can be shared with a line description, thus sharing the same interface. This works only when the Host Ethernet Adapter, 5706/5707, or 5767/5768 is supporting the service interface. It is possible to have a local console that is directly attached using a 2793 adapter, for example, and a 2849 network adapter configured for the service tools server. Each adapter is dedicated to support its respective function and is not available in the operating system. If you were to use the Host Ethernet Adapter in the previous example, the 2793 is dedicated but the service tools server running on the Host Ethernet Adapter can be shared with the operating system. 80

81 If I use a local console on a network (LAN) what should I take into consideration if I have to recover my system? New servers and partitions are most likely using distribution media from IBM and therefore, the only service tools device ID available is QCONSOLE. If you need to perform a recovery installation of a server or partition with the initialize option (scratch installation) and are using IBM distribution media, you only have QCONSOLE available. If you elect not to use QCONSOLE, or the configured connection (at the PC) is using a different service tools device ID, then you might need to delete and re-create the configuration so that QCONSOLE can be used. If the system and PC client both run V6R1 then, by default, the autocreate service tools device ID function is enabled and the connection will automatically negotiate a usable service tools device ID if the configured connection is already configured to use QCONSOLE. Consider the following based on your server's configuration: Servers without an HMC or pre-power5 processor-based primary partitions The only scenario where the value is not set is after a load-source hard-disk-drive replacement without a good copy from old to new. If this is the case, then all eligible adapters, by location, can support a console, except LAN. If LAN is the only available connectivity and the restoration media is not a SAVSYS, then you might need to use the control panel to perform the console service functions (65+21) to change the console type value. Logical partitions When a logical partition is initially set up, you have to specify the Console tag, an IOA or IOP (IOP in the case of pre-power5 processor-based systems) for console and, in the case of local consoles that are directly attached, the Operations Console tag. The system uses this information to search for a console. Only this resource is activated and the system uses the first connected device as the console to restore the Licensed Internal Code (LIC). The data used to restore the LIC determines if you need to set the console type value following the restoration of the code. You can also get a display asking for confirmation for selecting the console type value. If needed, you can use this console to change to another console. If the console fails to connect, you can use the HMC command window, if an HMC is present, to tag another resource and then use the console service functions (65+21) to specify a different console type value, if needed. 81

82 What is the service tools server and what should I know about it? If you use Operations Console (LAN), you must create a service host name (interface). After this is created, the server is also ready to use the service tools server to support, for example, iseries Navigator functions. However, you can have a network adapter for the service tools server when the console is something other than Operations Console (LAN). To do this, you need to configure the service host name (interface) so that the service tools server uses that connection. With a configured network adapter available at IPL, the system activates the adapter that supports the console, but also activates the adapter used for the service host name, if different. In this scenario, you now have two resources in your system that might not be used by the operating system, depending on your hardware. Conversely, if you previously had a service host name for iseries Navigator and are now using Operations Console (LAN), you do not have to make any IP configuration changes because the same resource is used. In other words if you use a local console on a network (LAN) you automatically have access to the service tools server. Note: If you do not use Operations Console (LAN) as your console, you might have to temporarily change the console type value and Console tag to configure a LAN adapter for use as the service tools server. After the configuration is complete, you are able to revert the console type value and any tagging back to the original values. What if I use a local console on a network (LAN) and have more than one device connecting at the same time? If you use Operations Console (LAN) with multiple PCs configured to become the console, all of these PCs are actively connected at IPL time. There is no way to know which PC will become the console because the first one connected will be the active console. If you enabled the console option, Allow console recovery and console can be taken over by another console, then you are able to take over the console at the PC you want to use. What do I consider if I have multiple console devices with multiple systems? Consider the following when considering multiple consoles and multiple servers: Local console on a network (LAN) Operations Console allows multiple LAN connections to a single server, but only one 5250 session can have control of the server at a time. An active console is a command interface to a server (5250 emulation) that is currently interacting with the server. More than one Operations Console device can have data on the window, but only one is truly active. A single PC can have multiple active connections to one or more servers or partitions. 82

83 or local console directly attached with remote access allowed The client (PC) only supports one local console that is directly attached or one local console that is directly attached with remote access allowed for a single PC. Also, if the PC being used as a local console that is directly attached with remote access allowed is also a remote console to another server, only one outgoing asynchronous connection is allowed at a time. You have to disconnect the local console that is directly attached to connect as a remote console. The server only supports a single incoming directly attached connection. Local console directly attached You can mix both connectivities, directly attached and LAN, at the same time on the same PC if you follow the preceding guidelines. Operations Console, twinaxial console and even an HMC can coexist. It might be best if you use the HMC as the emergency console since switching to an HMC is a very simple process and can even be performed without an IPL in nearly all cases. Do I have to be aware of IOA/IOP placement? Do not place your console adapter on the same IOP as storage devices. Having a dedicated IOP for the console adapter and one for the storage devices reduces possible connectivity problems. For example, during very heavy usage of storage devices, the console might appear to stop working temporarily. If this happens, it should resume operation shortly. If you must place the console adapter on shared resources, keep the other usages to a minimum for better console reliability. Also, enable the console option Allow console recovery and console can be taken over by another console. How does the system handle adapter activation when multiple console types are available? When a server is not managed by an HMC, it is possible to have more than one console adapter available for activation. For example, the console type is set to Operations console(lan) and has a device connected that is the system console. If an Operations Console (Direct) adapter is also activated, the corresponding device can also connect at the same time. However, this device cannot become the console and only displays the Console Information Status window. Each of the adapters are dedicated to their designated function and are not available for use in the operating system. The console service functions (65+21) and the OPSCONSOLE macro have support to designate a particular adapter which solves these issues. 83

84 Pre-Power5 processor-based systems Pre-Power5 processor-based - All systems What considerations do I take into account for IOPs? Try to avoid putting your Operations Console on the same IOP as storage devices. There might be configurations when this cannot be avoided. During very heavy usage of storage devices, the console might appear to stop working temporarily, but it should resume operation shortly. If the console is placed on the same IOP as the storage devices, enable the console option Allow console recovery and console can be taken over by another console. Multiple IOPs capable of supporting a console workstation can interfere with the selection of the desired LAN adapter. Consider the following: Having a second IOP on the bus before your intended console adapter card, when the first IOP contains a twinaxial adapter card, may fail to provide a LAN-connected console. For example, a model 890 uses eligible card locations C04, and C06 through C10 and if an IOP were placed in C08 and a twinaxial adapter preceded this IOP on the bus then the LAN adapter card located at C09 or C10 will fail to provide a LANconnected console. The LAN adapter card must be in a location preceding the second IOP, such as C06 or C07. Typically, the card location used for Operations Console directly attached configurations, commonly referred to as the Electronic Customer Support (ECS) slot, is located close to the beginning of the bus. When the card location is a low number, for example C02, then C03 is further from the beginning of the bus than C02. When the card location is a high number, for example C07, then C06 is further from the beginning of the bus than C07. There may be exceptions to this numbering scheme based on specific models and expansion units. Contact your service representative if you have questions about the placement of the ECS. 84

85 What considerations do I need to know about a backup console in a recovery action? When planning the configuration of the backup console or consoles remember that recovering from the loss of the console depends on many factors. Some of these factors include, the model and series, the hardware resources available, the previous console type, and the intended console type. Recovery might consist of repairing the currently failed console or temporarily replacing it with another console type. Most changes of a console type can be performed without the need for an IPL but there may be circumstances in which an IPL will still be necessary. When using the console service functions (65+21), consolesupporting hardware must be installed and available prior to performing the function. Any partition tagging of resources must also have been done already. Important: If you plan to use Operations Console local console on a network (LAN) as a backup to another console type, the network adapter must be located in a console designated slot or in a properly tagged IOP. If not previously configured, the BOOTP process is used to configure the system. What should I consider for a backup console? If you access your system remotely, consider off-site console capability or another type of connectivity for the console. A local console on a network can be backed up with an additional local console on a network PC. If the network adapter were to fail, consider a Local console directly attached to the system as a backup. In a logical partition or multiple-system environment, you will most likely be using multiple local consoles on a network (LAN) configuration on a single PC as your primary consoles. Consider additional PCs using this same type configuration. Avoid supporting too many consoles on the same PC if possible. The PC resources can be easily overwhelmed when supporting multiple consoles and remote control panels. Consider multiple local console on a network configurations in large environments so that each PC has a core set of console responsibilities and the 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. Another consideration is a dedicated PC to be the backup of a certain number of consoles, but not connected until necessary. 85

86 When you mostly use consoles on a network, consider setting up a Local console directly attached to the system on a PC and place it on a rollaway cart with a console cable. If you have supporting adapters, you can quickly roll the cart with the PC near the system or partition in need of the console. After connecting the cable and changing the console type value, you have a console to replace the currently failed console. This same concept also applies to twinaxial workstations. If more than one local console on a network is planned, be certain to create additional service tools device IDs on the system before you start configuring the Operations Console PC. Each PC connecting to the same target system or logical partition must have a unique service tools device ID. In summary, consider incorporating as much redundancy as possible into your console configuration. You can reduce your exposure to a catastrophic console failure by using another method to provide a console in place, or by making compromises and adjustments for the various hardware requirements necessary to overcome the various levels of failures. Pre-Power5 processor-based systems using a local console directly attached If your system has a 2771 adapter card in the processing unit and you plan to use Operations Console as either your primary console or as a backup console, it must be installed in the location designated by model for cable connections based on the following table, prior to the upgrade or installation. Each model has a different preferred location: Pre-Power5 processor-based - Non-partitioned systems Can I place a console resource anywhere in my system? Console supporting hardware may be required to be located in specific slot locations, based on model. Refer to Chapter 1: Reference on page 13 for locations based on your system's model. 86

87 What do I need to know regarding any recovery actions? If the load source storage device fails and the system recovery includes the use of the IBM distribution Licensed Internal Code media instead of a customer backup, and the system is using Operations Console (LAN), you might have to use another console type for the initial portion of the system recovery. Pre-Power5 processor-based - Partitioned systems What tags do I have to use for console? Models 8xx are tagged for a console type only at the IOP level. Tagging an IOP that has two similar console adapters reporting to it (for example, two 2849s or two 2771s) for the same IOP can sometimes make it difficult to determine, in advance, which adapter will be used for the console. When tagging the IOP, make sure that it only has one console-capable adapter per connectivity (for example, only one 2849 and one 2771). Each adapter can support a different console type but only one adapter type should be present. The lowest addressed adapter on the bus is attempted first. But if that adapter is slow in reporting to the system, another adapter might get selected instead, when two adapters of the same connectivity are present. Another example of this might be that the IOP has both a 2838 and a 2849 Ethernet adapter reporting to it. They are different adapters but have the same connectivity for the console. If you plan to use Operations Console as your primary console or as a backup console, you must tag the IOP to support the primary console and Electronic Customer Support (slot), even if you do not plan to use Electronic Customer Support. For example, if you are planning to use Operations Console on a direct connection, you must tag an IOP with the Console tag and the ECS tag. These steps are also necessary if you are planning to use Operations Console with a LAN connection. What do I need to know about multiple adapters for consoles? When more than one console adapter is available for a single IOP, the adapter with the lowest bus address will be chosen for use by Operations Console. For example, you tag an IOP that has two LAN adapters installed. The system will use the first adapter found on the bus. However, during an IPL the first adapter may not be ready in time and the system could select the second adapter. This could prevent the console from starting immediately or you might not be able to use that resource for your intended purposes. It is recommended that you install only one console-capable adapter that matches your configurations for a single IOP. This situation also will affect asynchronous adapters used by a Local console directly attached to the system. 87

88 Power-processor-based Systems - Common information Power-processor-based Systems - All systems 5767/5768 and 5706/5707 adapters The 2-Port 10/100/1000 Base-T Ethernet PCI Express Adapter (5767), 2-Port Gigabit Ethernet-S PCI Express Adapter (5768), PCI 1 Gbps Ethernet T IOA (5706), and PCI 1 Gbps Ethernet S IOA (5707) do not require an IOP and are available for use with the Operations Console. When using these adapters, you can locate the LAN adapters in any of the remaining slots, specific to the adapter, on your server if your server supports this type of operation and is managed by an HMC. If the system is not managed by an HMC, the LAN adapter must be located in one of the designated card locations that supports a local console on a network (LAN). Only the first port of this adapter can be used for the console. The first port is the top port or the right-most port. If you elect to use this adapter instead of the default embedded Ethernet port, you must disable the embedded port before the system can use the adapter and 2742 asynchronous communications adapters The 2793 and 2742 asynchronous communications adapters no longer require an IOP when the system is running V5R4M5 or later of Licensed Internal Code. 88

89 Power Systems - Not HMC managed What considerations do I take into account if I want to use a 5706/5707 or 5767/5768 (Power6 processor-based only) adapter instead of the embedded port? When a server is not managed by an HMC, by default, the embedded port and external adapter support are both enabled. In order to use the external adapter you first have to disable support for the embedded port. When the embedded Ethernet port is disabled, the console-supporting hardware is required to be located in specific slot locations based on the server model. For Operations Console (LAN), there might be more than one location that can support a console. When more than one location is available for a server model, the locations are listed from highest priority to lowest priority when the console searches for consolecapable hardware resources. The console service functions (65+21) and the OPSCONSOLE macro have support to designate a particular adapter. You can also use the OPSCONSOLE macro or the console service functions (65+21) to disable this support. Also, the 5706/5707, 5767/5768, 2793, or 2742 adapters are able to run without an IOP. If you do not want to use the embedded Ethernet port, a 5706/5707, or a 5767/5768 adapter for the console, you can disable this option. How does the system know which resource to use for the console when there isn't an HMC? When a server is not managed by an HMC the system relies on a specific set of "rules" to determine what resource will be used. By default, the embedded Ethernet port would be used. However, you can disable this port so you can use a different adapter. Just disabling the embedded Ethernet port forces the system to look at one or more specific locations for a console-supporting resource. In the tables above, based on platform and model, the locations are listed in the order the system searches for an appropriate resource. The first supporting resource is then selected. 89

90 Depending on your model and level of Licensed Internal Code you may be able to designate a specific resource which allows a little more flexibility in case you need a second or third adapter of the same connectivity for non-console use. The embedded Ethernet port support is one flag and the use of a 1 Gbps adapter (5706/5707, 5767/5768) is another. For example, if you disabled both flags and still wanted to use a local console on a network (LAN) you would need to supply an adapter like the 2849 driven by an IOP. You could then use an external 5706/5707, which is a higher speed adapter, for another purpose and the slower 2849 would be dedicated to the console. The console service functions (65+21) and the OPSCONSOLE macro have support to also designate a particular adapter and enable or disable the flags. If you use V5R4M5 (or later) of Licensed Internal Code you can access this support using the Select Console window, as shown here: Select Console System: Allow console recovery and console can be taken over by another console Select one of the following: Console type Twinaxial 2. Operations console(direct) 3. Operations console(lan) 4. Hardware management console(hmc) Current state of console tag Allow be Allow be 90 1=Yes, 2=No 3 0 supported internal LAN adapter to the console supported Gigabit LAN adapter to the console Press enter to continue. F3=Exit F12=Cancel S10BACFC 1=Yes, 2=No 1=Yes, 2=No

91 What if the system has two or more adapters of the same connectivity? Multiple console-supporting adapters on servers without an HMC, and without an enabled embedded Ethernet port if a local console on a network (LAN) is to be used, might interfere with console selection. Consider the following: The server attempts to use the first, or only, console IOA based on the current console type value. If your server model supports a second adapter location for LAN and has a LAN adapter installed, a problem with the first adapter might cause the server to use the second LAN adapter for the console, making it unavailable for use by the operating system. Selection of a specific adapter location is possible on select models prior to V5R4M5. (V5R3M5 with PTF MF39303) (V5R4M0 with PTF MF39304) These PTFs allows you to specify the asynchronous communications adapter used for a local console directly attached. Starting in V5R4M5 most models have the ability to designate the adapter associated with a local console directly attached and local console on a network (LAN). If designating a network adapter, selecting a card slot, then support for the embedded Ethernet port has to be disabled before the external adapter can be used. When a server is not managed by an HMC, it is possible to have more than one console adapter available for activation. For example, the console type is set to Operations console(lan) and has a device connected that is the system console. If an Operations Console (Direct) adapter is also activated, the corresponding device can also connect at the same time. However, this device cannot become the console and only displays the Console Information Status window. Each of the adapters are dedicated to their designated function and are not available for use in the operating system. 91

92 How do I specify which adapter to use for console when more than one is available? If you have an IBM System i5 or eserver i5 520, 525, or 515 model, your system (running V5R3M5 or V5R4M0 of Licensed Internal Code) can have asynchronous adapters located in multiple slots simultaneously, including locating the 2793 asynchronous adapter in slot C4. Slot C4 allows an IOA that does not require an IOP. This is possible only for systems that are not managed by an HMC and have an input/output adapter (IOA) that does not require an input/output processor (IOP). To allow for this greater flexibility on the 520, you must install PTF MF39303 (V5R3M5) or PTF MF39304 (V5R4M0). These PTFs should already be installed on the 525 and 515. With these PTFs, you are able to select an individual asynchronous adapter for use with the console and remote service by using either the OPSCONSOLE macro or the console service functions (65+21). The console and remote service functions must all remain on a single asynchronous adapter. If you have a system that was shipped with Licensed Internal Code (LIC) prior to V5R4M5, you cannot select slot C4 for use with the console when using the 2793, but you can select slot C4 for use with remote service. Example: If you have an asynchronous adapter located in both C2 and C3 for use by Operations Console (Direct), you can choose to use either slot for console and remote service, without having to remove the asynchronous adapter from the other slot. Starting in V5R4M5 all models have the ability to designate the adapter associated with a local console directly attached and local console on a network (LAN). For a local console directly attached you can use the macro: OPSCONSOLE ENBSLOT <1-5> depending on model Also available using the console service function Fn For a local console on a network (LAN) you can use the macro: OPSCONSOLE ENBLSLOT <1-5> depending on model Also available using the console service function Bn If designating a network adapter, selecting a card slot, then support for the embedded Ethernet port has to be disabled before the external adapter can be used. 92

93 To disable either the embedded Ethernet port or add-on 5706/5707 adapters using V5R4M5 (or later) of Licensed Internal Code, complete the following steps: 1. Access service tools using DST or SST. 1. If you are using DST, select Work with DST environment, and then System devices. 2. If you are using SST, select Work with service tools user IDs and devices. 2. Select Select Console. 3. Type a 2 in either the Allow supported internal LAN adapter to be the console or Allow supported Gigabit LAN adapter to be the console field, depending on what you want to disable. 4. Press Enter. The example below shows how to set up a Power5 processor-based or Power6 processor-based system to use an external adapter instead of the embedded or HEA/IVE port. Select Console System: Allow console recovery and console can be taken over by another console Select one of the following: Console type Twinaxial 2. Operations console(direct) 3. Operations console(lan) 4. Hardware management console(hmc) Current state of console tag Allow be Allow be 93 1=Yes, 2=No 3 0 supported internal LAN adapter to the console supported Gigabit LAN adapter to the console Press enter to continue. F3=Exit F12=Cancel S10BACFC 1=Yes, 2=No 1=Yes, 2=No

94 If you do not have a working console device, but you have another workstation that can access System Service Tools (SST), then you can use the preceding DST/SST procedure or use the OPSCONSOLE macro to disable your intended resource. If you do not have any working devices, then you must use the console service functions (65+21). You can also use either of these methods to re-activate support for these resources. Can more than one console supporting resource be activated at the same time? When a server is not managed by an HMC, it is possible to have more than one console adapter available for activation. For example, the console type is set to Operations console(lan) and has a device connected that is the system console. If an Operations Console (Direct) adapter is also activated, the corresponding device can also connect at the same time. However, this device cannot become the console and only displays the Console Information Status window. Each of the adapters are dedicated to their designated function and are not available for use in the operating system. Power-processor-based Systems - HMC managed What do I tag for console using the HMC? IBM System i5 and eserver i5 models with an HMC support tagging at an IOP or IOA level. There are advantages and disadvantages to tagging either the IOP or the IOA. First, some background on how the system determines what console to use when the system is HMC managed. The system starts this process by first looking at the tag and blindly setting the console type to match the supported adapter. If you try to change the console type and have an IOA tagged you get back an error that there isn't any supporting hardware. The system only knows to use the resource tagged. Determining the console happens during an IPL, obviously, but this process also takes place when other console-related activity is performed such as a If the tag is to an IOA this is a predictable function. If you tagged an IOP and had both a console-supporting network adapter, in addition to an asynchronous communication adapter, the system selects the first detected and eligible adapter to determine the console. If for some reason the adapter reporting first were to be delayed the system would select the other adapter and would set the console type to the wrong value. The result is no console and a very puzzled user. 94

95 Another fact you should know is that tagging at an IOP level may reserve one or more console-supporting adapters. For example, you use a network resource for the console but have an asynchronous communication adapter associated with that same IOP. As part of the console detection function the system may reserve the asynchronous adapter for use by a console in case you want to make a quick change in the console device. When the operating system tries to use this resource you might find that it won't vary on because it's in-use. But tagging at the IOP level is still desirable if you only associate one network adapter and one asynchronous communication adapter to it. To fall back from one console type to another only requires a change of the console type. This works fine except that you may end up dedicating the other adapter to possible console functions. If you need to change the console type, you can make the change without an IPL in most cases. You can use the HMC command window to specify the tag. This allows the change to be used immediately, although you might have to force the system to determine the new console in some instances. This can be performed using the same command window, using the OPSCONSOLE macro, or use the console service functions (65+21). Which tags do I have to be aware of with Operations Console? Consider the following when determining what to tag for Operations Console: Operations Console (LAN) If you use a LAN-based PC for your console, the only tag you need to set is for console. Operations Console (Direct) If you use a direct cable attached PC for your console, you need to specify the tag for Console and Operations Console. The Operations Console tag is the equivalent of the former Electronic Customer Support (ECS) tag. The Operations Console tag is required if you are using a directly connected console, if you are configuring for a directly connected backup console, or if you are using an asynchronous communications adapter for remote service. Tagging the IOA allows you to select the specific adapter used for the Operations Console. Therefore, if multiple console-capable adapters exist in the IOP, only the selected console-capable adapter is used for the console. The tag automatically sets the console type during the next activation following the partition profile update. An IPL will not read the changed partition profile. 95

96 You can use the HMC command window to specify the tag. This allows the change to be used immediately, although you might have to force the system to determine the new console in some instances. This can be performed using the same command window, with the OPSCONSOLE macro, or using the console service functions (65+21). Power5 processor-based Systems Specific Power5 processor-based - Non-partitioned systems - Not managed by a Hardware Management Console (HMC) What is the default local console on a network (LAN) resource? Operations Console now defaults the first embedded Ethernet port as the default console port in systems not using an HMC. This includes the 5706/5707 adapters. However, the server will not check for the 5706/5707 adapter unless support for the default embedded Ethernet port has been disabled. Support for the default embedded Ethernet port is disabled in manufacturing for systems where the embedded ports do not exist, for example, the

97 Power6 processor-based Systems Specific Power6 processor-based - All systems What is the default local console on a network (LAN) resource? What is the Virtual Ethernet (IVE) - Host Ethernet Adapter (HEA)? Operations Console now defaults the first Integrated Virtual Ethernet (IVE) port as the default console port in systems not using an HMC. The IVE can also be referred to as the Host Ethernet Adapter (HEA) in some documentation and these terms can be used interchangeably. This document may just use the term embedded Ethernet port. In this context it means the first port on the first physical port or the logical port reserved for the console when the IVE was configured for the partition. When working with IVE (HEA) on a system without an HMC, the top, or right-most, port is the default port for console. Consider the following regarding the IVE: The IVE is available in two versions: 2-port and 4-port Each Host Ethernet Adapter physical port supports a maximum of 16 logical ports. A 2-port Host Ethernet Adapter supports a maximum of 16 logical ports, because both ports share a single cable group. If there are four ports, then two ports share the 16 logical ports for each port group for a total of 32 logical ports. Each logical partition can have one logical port for each physical port, and you cannot assign a logical port number to a physical port or logical partition. You can assign the logical port ID to the physical port, but the system assigns the actual port number. Some systems can have up to four Host Ethernet Adapter ports, one for each drawer. Partitions using Host Ethernet Adapter resources cannot be migrated. See What is the default for a local console on a network (LAN) resource below for using the IVE in a non-partitioned environment. 97

98 Power6 processor-based - Non-partitioned systems What is the default for a local console on a network (LAN) resource? Operations Console now defaults the first Integrated Virtual Ethernet (IVE) port, also known as the Host Ethernet Adapter (HEA), as the default console port in systems not using an HMC. The IVE can also be referred to as the Host Ethernet Adapter (HEA) in some documentation and can be used interchangeably. In this document it may be referred to as the embedded Ethernet port. When working with IVE (HEA) on a system without an HMC, the top, or right-most, port is the default port for console. Consider the following regarding the IVE: 1. The IVE is available in two versions: 2-port and 4-port 2. Each Host Ethernet Adapter physical port supports a maximum of 16 logical ports. 3. A 2-port Host Ethernet Adapter supports a maximum of 16 logical ports, because both ports share a single cable group. 4. If there are four ports, then two ports share the 16 logical ports for each port group for a total of 32 logical ports. Each logical partition can have one logical port for each physical port, and you cannot assign a logical port number to a physical port or logical partition. You can assign the logical port ID to the physical port, but the system assigns the actual port number. 5. Some systems can have up to four Host Ethernet Adapter ports, one for each drawer. Partitions using Host Ethernet Adapter resources cannot be migrated. If you do not want to use this resource for your console and would rather use an adapter located in a card slot you must disable the embedded support. 98

99 Power6 processor-based - Partitioned systems What do I have to know about servers with an HMC? A Host Ethernet Adapter logical port or an input/output adapter (IOA) must be tagged for console with a Hardware Management Console (HMC) if you will be using a console other than the HMC. For more information, see What do I have to know about tagging a Host Ethernet Adapter logical port or IOA for the console below. What do I have to know about tagging a Host Ethernet Adapter logical port or IOA for the console? Consider the following when determining what to tag for Operations Console: Operations console(lan) If you use a local console on a network (LAN), the only tag you need to set is for console. Operations console(direct) If you use a direct cable attached PC for your console, you need to specify the tag for Console and the Operations Console tag. The Console tag requires that you specify a Host Ethernet Adapter logical port or an IOA. The Operations Console tag is required if you are using a local console directly attached for your console, if you are configuring for a directly connected backup console, or if you are using an asynchronous communications adapter for remote service. You can tag a Host Ethernet Adapter logical port for the console in the partition profile. When doing this, you are actually tagging a physical port of the Host Ethernet Adapter and using the assigned logical port. Tagging the IOA allows you to select the specific adapter used for the Operations Console. Therefore, if multiple console-capable adapters exist in the IOP, only the selected consolecapable adapter is used for the console. Tagging the IOA in the partition profile automatically sets the console type during the next activation following the partition profile update. An IPL will not read the changed partition profile. You can also use the HMC command window to specify the tag. This allows the change to be used without the need to power off the server or perform an IPL, in most cases. 99

100 Power6 processor-based Blade and Power6 processor-based systems running VIOS/IVM What do I have to know about Power6 processor-based blades and systems running VIOS/IVM? Power6 processor-based blade servers that have partitions only support a local console on a network (LAN). Depending on how the IBM BladeCenter is configured, when you create the partition, you may not have as many choices regarding the logical network ports. It is critical that the Host Ethernet Adapter has been set to be bridged, as shown here: >> Select the resource (usually the resource showing zero in Available Connections) >> Properties View/Modify Host Ethernet Failure to have this bridged will prevent the client PC to configure the partition during the Dmode IPL to restore Licensed Internal Code. 100

101 View/Modify Virtual Ethernet >> Click the Virtual Ethernet Bridge tab A resource must be defined here, as well, or the system will be unable to connect to the network. Operations Console is configured and managed the same as any other system with a local console on a network (LAN). for information regarding the installation and setup of the blade server see the on-line Information Center under Systems hardware >> BladeCenter information >> Blade servers >> select your blade server. For information regarding Operations Console information not covered in this document should be in the on-line Information Center under Systems hardware >> System i information >> Managing consoles, interfaces, and terminals >> Managing i5/os consoles >> Managing Operations Console

102 RCP & VCP What is a RCP or VCP? Both remote control panel and virtual control panel are graphical interfaces to the control panel. The remote control panel allows you to perform most of the control panel functions from a local console when directly attached or by way of a network connection. The virtual control panel allows you to perform most of the control panel functions from a local location but connects using the console's serial cable to remove the need for a network adapter. If you are using a pre-power5 processor-based system and the remote control panel connection is with a separate serial or parallel cable (V5R3 only on pre-power5 processorbased systems) then you have access to the system to include powering it on from the client. A network connected RCP or VCP cannot power on a system or partition. Use the configured connection's Properties > Configuration to add, remove, or validate the RCP. What type of restrictions am I likely to encounter? The user must be granted access to a partition's remote control panel and functions to use the remote control panel or virtual control panel. If a local console on a network is being used, then the service tools device ID must also be granted access to that partition's remote control panel to use this feature. By default, usercreated user IDs will have these permissions. By default, service tools device IDs may not be automatically granted access to the remote control panel for the partition. But access can be granted by an administrator for the user ID, device ID, or both. The user that authenticates a connection must also have authority to the respective partition's keylock to change the mode. This varies by release so check the service tools device ID that will be used to verify it has access to this function. Note: Starting with V6R1, the system is set to automatically create service tools device IDs by default. However, these auto-created service tools device IDs do not automatically have access to the remote control panel functions so you may be required to manually grant this access. Also, if the service tools device ID gets reset, either manually or automatically by the system access to the remote control panel functions will be reset back to revoked. 102

103 Any configured connection that includes the remote control panel option and the device ID is not authorized is temporarily disabled (grayed out) or missing. 1. The remote control panel option is disabled (grayed out) after the first connection if it was selected but not authorized. 2. The remote control panel option is missing after the first connection if it was not selected and was not authorized. After the device ID is authorized, it becomes active or reappears in Properties, on the next connection. If you have a server model that uses the keystick, the mode button will work with the same functions as the physical control panel when the keystick is inserted. Note: Systems with a keystick require the keystick to be inserted before the user is eligible to use the mode button. For example, the user has the remote panel key privilege but will not have the mode function available until the keystick is present. For systems without the keystick, the user ID being used would only require the remote panel key privilege. The service tools user ID used to authenticate the connection must have the partition remote panel key privilege to use the mode function provided by the RCP or VCP. Service tools user IDs QSECOFR, QSRV, , or already have this permission by default. As always, check the online Information Center for more details. Why did I lose the RCP when I previously had it working? There may be times in which you configure a connection with an auto-created service tools device ID, grant access to the remote control panel, then at a later time you connect and find that you no longer have a remote control panel. This is the result of a change in the assigned service tools device ID. Something occurred, possibly not connecting this device in a few days for instance, so the service tools device ID got reset. A reset of the device ID includes revoking permission to the RCP, so you, again, have to manually grant permission to the RCP. Currently, the only way to prevent this would be for you to create a specific service tools device ID for this configured connection and delete the previous one. 103

104 What considerations are specific to the virtual control panel? There is no requirement for a network adapter even though the configuration process uses the local console on a network (LAN) option. The VCP requires a unique service tools device ID. You may be required to manually create the service tools device ID depending on your version of the operating system. For example, if the system and PC client are both using V6R1 then auto-created service tools device IDs should automatically create the necessary ID but it won't automatically grant access to the system or partition. Earlier releases granted this function by default when you manually created the ID. The VCP is only available while the console is connected. You must remove the parallel remote control panel cable, if installed, before configuring the VCP connection. You cannot use or reuse an existing network name when you create the additional VCP configuration. For example, if you have a configuration named SERVER1, you cannot name the VCP SERVER1. Also, if the intended VCP-capable PC is on a network, you cannot use any name that already exists on that network. All VCP and remote control panels are active at the same time. If you have multiple PCs (LAN connected) that can become the console, one at a time, and those configurations also use the remote control panel functions, all active RCPs can control the system. Use care when working with control panel functions when multiple PCs have access to the functions. 104

105 How to determine what model or serial number a system is? If your system uses a Hardware Management Console (HMC) you can display the properties of the managed system to determine the model and serial number. If your system is not managed by an HMC then you can perform a function 20 at the physical control panel to find out the model. For example, if you receive 6520nnnn it would mean: 6 = = model of the system nnnn = Processor group ID If you have a Power5 processor-based or Power6 processor-based system you can also get the model and serial number from Advanced System Management. The serial number of most systems is usually located on a label attached to the physical control panel or somewhere on the front of the system in the first frame. The 9407-M and 9408-M serial number is no longer on the front cover. It is now on a sticker near the HMC1 and HMC2 ports. 105

106 Chapter 3: System Locations for Cards & Cables See the figure that applies to your server. Model 170(250) Operations Console ports - A=C08 port 106

107 Server 270 Operations Console ports. 107

108 Model 720 Operations Console ports 108

109 Model 730 Operations Console ports 109

110 Model 740 Operations Console ports 110

111 Model 800/

112 Model

113 Model

114 Model 830/SB2 114

115 Model 840/SB3 115

116 Model 870/

117 Models , , , or with the integrated HSL/RIO ports (T3/T4) 117

118 118

119 Back views of a model , , , or without the integrated HSL ports (T3/T4) 119

120 120

121

122 9407-M and 9408-M

123 9409-M

124 9406-MMA

125 Appendix A. Notices This information was developed for products and services offered in the U.S.A. The manufacturer may not offer the products, services, or features discussed in this document in other countries. Consult the manufacturer s representative for information on the products and services currently available in your area. Any reference to the manufacturer s product, program, or service is not intended to state or imply that only that product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any intellectual property right of the manufacturer may be used instead. However, it is the user s responsibility to evaluate and verify the operation of any product, program, or service. The manufacturer may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the manufacturer. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: THIS INFORMATION IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. The manufacturer may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to Web sites not owned by the manufacturer are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this product and use of those Web sites is at your own risk. The manufacturer may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. 125

126 Information concerning products not produced by this manufacturer was obtained from the suppliers of those products, their published announcements or other publicly available sources. This manufacturer has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to products not produced by this manufacturer. Questions on the capabilities of products not produced by this manufacturer should be addressed to the suppliers of those products. All statements regarding the manufacturer s future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. The manufacturer s prices shown are the manufacturer s suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information in softcopy, the photographs and color illustrations may not appear. The drawings and specifications contained herein shall not be reproduced in whole or in part without the written permission of the manufacturer. The manufacturer has prepared this information for use with the specific machines indicated. The manufacturer makes no representations that it is suitable for any other purpose. The manufacturer s computer systems contain mechanisms designed to reduce the possibility of undetected data corruption or loss. This risk, however, cannot be eliminated. Users who experience unplanned outages, system failures, power fluctuations or outages, or component failures must verify the accuracy of operations performed and data saved or transmitted by the system at or near the time of the outage or failure. In addition, users must establish procedures to ensure that there is independent data verification before relying on such data in sensitive or critical operations. Users should periodically check the manufacturer s support websites for updated information and fixes applicable to the system and related software. 126

127 Trademarks The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM AS/400, AS/400e, iseries, eserver, System i, Systemi5, eserver i5, Power, Power5, Power6 AS/400 AS/400e BladeCenter e(logo)server eserver eserver i5 Hummingbird i5/os i5/os(logo) IBM IBM (logo) Operating System/400 iseries OS/400 Power Power5 Power6 System i5 System i xseries MM, Pentium, and are trademarks or registered trademarks of Intel Corporation in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product or service names may be trademarks or service marks of others. 127

128 Electronic emission notices Class A Notices The following Class A statements apply to the IBM System i models that contain the POWER6 processor. Federal Communications Commission (FCC) statement Note: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his own expense. Properly shielded and grounded cables and connectors must be used in order to meet FCC emission limits. IBM is not responsible for any radio or television interference caused by using other than recommended cables and connectors or by unauthorized changes or modifications to this equipment. Unauthorized changes or modifications could void the user s authority to operate the equipment. This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Industry Canada Compliance Statement This Class A digital apparatus complies with Canadian ICES-003. Avis de conformité à la réglementation d Industrie Canada Cet appareil numérique de la classe A respecte est conforme à la norme NMB-003 du Canada. European Community Compliance Statement This product is in conformity with the protection requirements of EU Council Directive 2004/108/EC on the approximation of the laws of the Member States relating to electromagnetic compatibility. IBM cannot accept responsibility for any failure to satisfy the protection requirements resulting from a non-recommended modification of the product, including the fitting of non-ibm option cards. This product has been tested and found to comply with the limits for Class A Information Technology Equipment according to European Standard EN The limits for Class A equipment were derived for commercial and industrial environments to provide reasonable protection against interference with licensed communication equipment. 128

129 European Community contact: IBM Technical Regulations Pascalstr. 100, Stuttgart, Germany Tele: 0049 (0) Fax: 0049 (0) Warning: This is a Class A product. In a domestic environment, this product may cause radio interference, in which case the user may be required to take adequate measures. VCCI Statement - Japan The following is a summary of the VCCI Japanese statement in the box above. This product is a Class A Information Technology Equipment and conforms to the standards set by the Voluntary Control Council for Interference by Information Technology Equipment (VCCI). In a domestic environment, this product may cause radio interference, in which case the user may be required to take adequate measures. Electromagnetic Interference (EMI) Statement - People s Republic of China Declaration: This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may need to perform practical action. Electromagnetic Interference (EMI) Statement - Taiwan The following is a summary of the EMI Taiwan statement above. Warning: This is a Class A product. In a domestic environment this product may cause radio interference in which case the user will be required to take adequate measures. IBM Taiwan Contact Information: 129