Interface Card OL* Support Guide

Transcription

1 Interface Card OL* Support Guide HP-UX 11i v3 HP Part Number: Published: September 2007 Edition: E 0709

2 Copyright 2007 Hewlett-Packard Development Company L.P Legal Notices The information contained herein is subject to change without notice. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Microsoft, Windows, and Windows NT are U.S. registered trademarks of Microsoft Corporation. Printed in the US Trademark Notices UNIX is a registered trademark in the United States and other countries, licensed exclusively through The Open Group. Intel Itanium Processor Family is a trademark of Intel Corporation in the US and other countries and is used under license. Microsoft is a U.S. registered trademark of Microsoft Corporation. Netscape is a registered trademark of Netscape Communications Corporation. X Window System is a trademark of the Massachusetts Institute of Technology.

3 Table of Contents About This Document...13 Intended Audience...13 New and Changed Information in This Edition...13 Publishing History...13 Document Organization...13 Typographic Conventions...14 HP-UX Release Name and Release Identifier...14 Related Documents...15 HP Encourages Your Comments PCI Card OL* Overview...17 Important Terms and Concepts...20 Planning and Preparation...20 Card Compatibility...20 Online Addition...21 Online Replacement...21 Online Deletion...21 Critical Resources...22 Other Situations to Consider...22 Power Domains...22 Multiport Cards...22 Virtual Ports...22 Firmware Patch Information...23 Shared Slots...23 Frequency Mismatch...23 PCI Error Recovery The pdweb Peripheral Device Tool Web Interface...25 Peripheral Device Tool...25 Features and Benefits...25 How the pdweb Tool Works...26 Security...27 Accessing pdweb...27 Using SMH...27 Accessing SMH...27 Using a Web Browser...27 Using the pdweb Command...27 Accessing the pdweb tool...28 Using SIM...28 Using pdweb With Bastille...29 Navigating pdweb...30 Components of the GUI...30 Banner...30 Tabs...30 Lists...30 Action Menu...32 Command Preview...32 OLRAD Cards Tab...33 I/O Tree Tab...34 Table of Contents 3

4 Changing Views...36 Changing the View by Device Class...36 Changing the View with Search...37 Refreshing the I/O Tree...38 Reinstalling Device Files...39 Viewing Slot Information...39 Available pdweb Actions...40 Slot Detail View...40 Using Search...42 Critical Resource Analysis...42 Adding a Card Online...43 Replacing a Card Online...47 Bringing a Card Online...51 Deleting a Card Online...52 Configuring an I/O Chassis During Dynamic npartition Operations...56 Turning the Attention LED to BLINK or OFF Attention Button - Direct Slot Control...59 Introduction to the Attention Button, Power LED, and Attention LED...59 Using the Attention Button...60 Adding a Card Online...60 Replacing a Card Online...61 Deleting a Card On-Line...62 Locating a Slot With the Attention LED...62 The hotplugd Daemon and Log file...62 Results of Pressing the Attention Button The olrad Command...65 Using olrad...65 Syntax and Arguments...65 Preliminary Actions...65 Determining Slot Status...65 Performing a CRA...66 Adding a New Card...66 Replacing a Card...67 Deleting a Card...67 Configuring an I/O Chassis During Dynamic npartition Operations...68 De-configuring an I/O Chassis During Dynamic npartition Operations...68 Turning the Attention LED to BLINK or OFF...69 Options, Scripts, and Logging...69 Options...69 Scripts...70 Logging Comparing and Combining OL* Methods...71 Comparing OL* Methods...71 Adding a Card...72 Replacing a Card...73 Deleting a Card...74 Attention LED Control...75 Mixing OL* Methods Table of Contents

5 6 Troubleshooting...77 Messages from pdweb Actions...77 Log Files...77 SAM Log File...77 HP Apache-Based Web Server Log File...77 The NetTL Log File...78 Command Errors...78 olrad Errors...78 Other Command Errors...78 Attention Button Actions...78 Messages from olrad Actions...79 hotplugd Daemon Diagnostics...79 Messages in the System Log File...79 Messages in the hotplugd Daemon Log File...79 OL* Action Behavior Issue...82 A OL* Actions, Events, and Scripts Reference...83 Attention Button Actions...83 Attention Button Events...83 PCI OL* Events...83 OL* Driver Scripts...84 Preface Operations Actions...84 Prepare Operations Scripts...84 Post Operations Scripts...84 Glossary...85 Index...87 Table of Contents 5

6 6

7 List of Figures 2-1 The pdweb Interface pdweb Banner pdweb Tabs with the OLRAD Cards tab active List size selection menu pdweb List Example pdweb Action Menu pdweb Command Preview Example Detail Slot View on pdweb I/O Tree Tab in pdweb Image pdweb I/O Tab Detail View pdweb Class and Search Options pdweb I/O Tree Search Results pdweb Reinstall Device Files Screen OL* Cards in pdweb Image pdweb OLRAD Cards Slot and Card Interfaces Tab Examples pdweb OLRAD Cards Attached Devices and Device Files Tab Examples pdweb CRA Critical Example pdweb Adding a Card Example pdweb Adding a Card CRA Example pdweb Adding a card CRA Step 2 Example pdweb Choose a Card to Replace pdweb Replace Card Example pdweb Replace Card CRA Example pdweb Bring Card Online pdweb Bring Card Online pdweb Bring Card Online Success pdweb Choose a Card to Delete pdweb Adding I/O Chassis Card Example pdweb Turn On/Off LED Add Card Methods Comparison Flowchart Replace Card Methods Comparison Flowchart Delete Card Methods Comparison Flowchart Attention LED Control Methods Comparison Flowchart

8 8

9 List of Tables 1 Publishing History Details HP-UX 11i Releases Terms and Meanings Installing Card into a Slot with a Different Frequency Frequency Matching Scenarios for Shared Slots pdweb List Navigation Buttons pdweb Slot State Graphic Symbols pdweb Slot Detail Information Tabs pdweb Adding a Card CRA Results pdweb Replace a Card CRA Results pdweb Delete a Card CRA Results pdweb LED States Power LED State Attention LED State Results of Pressing the Attention Button Consequences of Mixing OL* Methods Log Files System Log File Messages hotplugd Daemon Log File Messages

10 10

11 List of Examples 3-1 The olrad -q Command Output The olrad -q Command Output CRA Reporting Success

12 12

13 About This Document This document describes how to manage slots and cards using OnLine Add, Replace, and Delete (OL*) functionality on systems running HP-UX 11i v2 or HP-UX 11i v3. For more information about the I/O card online addition and replacement procedure for systems running HP-UX 11i v1 see Chapter 2 (Managing PCI Cards with OLAR) of Configuring HP-UX for Peripherals at The document publication date and manufacturing part number indicate the document's current edition. The publication date and manufacturing part number will change when a new edition is published. To ensure that you receive new editions, subscribe to the appropriate product support service. See your HP sales representative for details. The latest version of this document can also be found online at: Intended Audience This document is intended for system and network administrators responsible for installing, configuring, and managing slots and cards. Administrators are expected to have knowledge of operating system concepts, commands, and configuration. This document is not a tutorial. New and Changed Information in This Edition This edition includes new content on Online Deletion and Critical Resource Analysis (CRA) output for HP-UX 11i v3. Publishing History This is the third edition of this document. Table 1 Publishing History Details Document Manufacturing Part Number B Operating Systems Supported HP-UX 11i v3 HP-UX 11i v3 Publication Date February 2007 September 2007 Document Organization Chapter 1 PCI Card OL* Overview Chapter 2 The pdweb Peripheral Device Tool Web Interface Chapter 3 Attention Button - Direct Slot Control Chapter 4 The olrad Command Chapter 5 Comparing and Combining OL* Methods Use this chapter to learn about OL* technology and a brief overview of the various OL* methods. Use this chapter to learn how to perform OL* operations using a web-based GUI. Use this chapter to learn how to perform OL* operations using the Attention Button. Use this chapter to learn how to perform OL* operations from the command line. Use this chapter to contrast and compare the various methods of performing OL* operations, and the consequences of mixing methods. Intended Audience 13

14 Chapter 6: Troubleshooting Appendix A OL* Actions, Events, and Scripts Reference Use this chapter to learn about troubleshooting, error messages, and information on error logs. Use this appendix to learn about advanced OL* actions, events and scripts. Typographic Conventions This document uses the following conventions. audit(5) An HP-UX manpage. In this example, audit is the name and 5 is the section in the HP-UX Reference. On the Web and on the Instant Information CD, it may be a hot link to the manpage itself. From the HP-UX command line, enter man audit or man 5 audit to view the manpage. See man(1). Book Title The title of a book. On the Web and on the Instant Information CD, it may be a hot link to the book itself. KeyCap The name of a keyboard key. Return and Enter both refer to the same key. The name of an onscreen button to click. Emphasis Text that is emphasized. Bold Text that is strongly emphasized or text that refers to a specific feature in an online GUI. Bold The defined use of an important word or phrase. ComputerOut Text displayed by the computer. UserInput Commands and other text that you type, or text that acts as a link in a GUI. Command A command name or qualified command phrase. Variable The name of a variable that you can replace in a command or function, or information in a display that represents several possible values. [ ] The contents are optional in formats and command descriptions. If the contents are a list separated by, you must choose one of the items. { } The contents are required in formats and command descriptions. If the contents are a list separated by, you must choose one of the items.... The preceding element can be repeated an arbitrary number of times. Separates items in a list of choices. HP-UX Release Name and Release Identifier Each HP-UX 11i release has an associated release name and release identifier. The uname -r command returns the release identifier. This table shows the releases available for HP-UX 11i. Table 2 HP-UX 11i Releases Release Identifier B B B B B B Release Name HP-UX 11i v1 HP-UX 11i v1.5 HP-UX 11i v1.6 HP-UX 11i v2 HP-UX 11i v2 September 2004 HP-UX 11i v3 Supported Processor Architecture PA-RISC Intel Itanium Intel Itanium Intel Itanium PA-RISC Intel Itanium PA-RISC Intel Itanium 14 About This Document

15 Related Documents Additional documentation for the pdweb (pdweb) is available in the online help system. Click on Help Overview from the main pdweb screen. For information on the olrad command, see the olrad(1m) manpage and Chapter 4 The olrad Command. For more information on the pdweb command, see the pdweb(1m) manpage and Chapter 2 The pdweb Peripheral Device Tool Web Interface. The following documents available on are related to OL* actions and may provide additional information. HP System Partitions Guide: Administration for npartitions OL* and Error Recovery Support in PCI Drivers chapter in the 11i v3 Driver Development Guide. Managing Systems and Workgroups: A Guide for HP-UX System Administrators. A document in the System Administration section for the specific OS release version you are using. PCI Error Recover Product Note Installing and Managing HP-UX Virtual Partitions (vpars) Software Distributor Administration Guide for HP-UX 11i HP Servicecontrol Manager Documentation For additional information about HP servers that support the pdweb tool, see the following links. hp servers HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send comments to: netinfo_feedback@cup.hp.com Include the document title, manufacturing part number, and any comments, errors found, or suggestions for improvement for this document. Related Documents 15

16 16

17 1 PCI Card OL* Overview Most PCI cards and HP Integrity servers support OL* functionality. For those that do not, see the specific card and server documentation. OL* enables the following actions: Adding a new PCI card without affecting other components of the system and without requiring a system reboot. Replacing an existing PCI card without affecting other components of the system and without requiring a system reboot. Deleting an existing PCI Card without affecting other components of the system and without requiring a system reboot. 17

18 WARNING! Observe all safety precautions to avoid being injured while accessing systems to add, replace, or delete cards. CAUTION: Observe all safety precautions prior to physically accessing the system to prevent static discharge from damaging the system. IMPORTANT: Online replacement (OLR) of a LAN card in a Serviceguard cluster fails because the Critical Resource Analysis (CRA) performed as part of the OLR operation returns CRA_SYS_CRITICAL. You will encounter this problem whether you use the Peripheral Device Tool (pdweb) or the HP-UX olrad command. To fix this problem, apply patch PHNE_ NOTE: You can apply patch PHNE_35894 without a reboot. On a system to which patch PHNE_35894 has been applied, you will be able to perform online replacement of hot-swappable cards (without bringing down the cluster). For detailed information, see Replacing LAN or Fibre Channel Cards in chapter 8 of Managing Serviceguard, available at NOTE: If for some reason you need to proceed without patch PHNE_35894, you must follow the Off-Line Replacement procedure under Replacing LAN or Fibre Channel Cards in chapter 8 of Managing Serviceguard. For more information about this issue, see SR # (JAGag27186). 18 PCI Card OL* Overview

19 IMPORTANT: If a system is booted, or an Online Addition operation is completed, with the latch on a PCI slot in the open position, the slot may become unusable, requiring a boot to return the slot to a usable state. The three scenarios where this may happen are: Booting with the latch of an occupied PCI slot in the open position results in the card in that slot being unusable. The ioscan command will show the software state for the card in that slot as UNUSABLE. Also, a PCIError Reported at <H/W path> message will appear on the console. Booting with the latch of an unoccupied slot in the open position, then adding a card to that slot and executing an ioscan command, will result in the card being in the UNUSABLE state (provided the -k option is not used and the ioscan is not restricted from covering the path to that slot). In this scenario, the card will become UNUSABLE, regardless of whether the latch is closed or left open, after the card is added to the slot. Performing a PCI card online addition (OLA) operation using the olrad command or the pdweb GUI, and leaving the latch of the slot opened while bringing the card online, results in the card being in the UNUSABLE state. This behavior is due to a firmware issue. Until a firmware fix is available, you can use the following procedure to recover: 1. Close the latch on the PCI slot that is in the UNUSABLE state. 2. Reboot the system; the slot will become usable again. Scope: This problem occurs under the following conditions: Operating System: HP-UX 11i v3 HP 9000 servers: rp8420 or rp7420 Firmware Version: PDC firmware version: 24.1 To verify the PDC firmware version, you can run STM, or you can run the sysrev command from the management processor Command Menu (CM) prompt as follows: MP:CM> sysrev NOTE: Certain classes of hardware are not intended for access by users. At this time this includes V class and Superdome systems. HP recommends that these systems only be opened by a qualified HP Engineer. Failure to observe this requirement can invalidate any support agreement or warranty to which you may otherwise be entitled. Each of the three OL* methods has similarities and differences and a chapter is devoted to each method, as well as an additional chapter with flowcharts showing all of the methods together for comparison and to act as a quick reference. pdweb Attention Button olrad The pdweb (pdweb) Web based method of OL*. For more information, see Chapter 2 (page 25). The hardware system slot based method of using OL*. For more information, see Chapter 3 (page 59). The availability of this method depends on the specific hardware involved. See your hardware documentation for specifics. The command-line method of using OL*. For more information, see Chapter 4 (page 65). You can use these three tools to perform similar tasks using different techniques. For a direct comparison of the methods to help you decide which method to use in a particular situation, see Chapter 5 (page 71). 19

20 HP recommends that you complete one operation using one method. Mixing OL* Methods (page 76) includes a table, which details the consequences of mixing OL* methods. With many cards placed close together in a system, it can be difficult to locate a particular slot. You can turn the Attention LED to a blinking state for easy slot location. Information for blinking the Attention LED is included with each OL* method. Important Terms and Concepts Table 1-1 Terms and Meanings Term OL* Power Domain target card target card slot affected card affected card slot MRL OLX Divider CRA hotplugd Meaning All aspects of Online Addition (OLA), Online Replacement (OLR), and Online Deletion (OLD) of PCI and PCI-X interface cards. A grouping of one or more interface card slots that are powered on or off as a unit. HP Integrity systems have each slot in a separate power domain. The interface card which will be added, replaced or deleted using OL* and the card slot it resides in. Interface cards and the card slots they reside in which are in the same power domain as the target slot. Multi-slot power domains are not implemented. Manual Retention Latch. A physical latch that locks a card into position in a slot and influences power to the slot. Also referred to as a latch. A physical divider situated between slots and features a power LED, an attention LED, the Attention Button, and an MRL. The OLX Divider may not contain the Attention Button. See your platform documentation for specifics on LED and Attention Button positioning. Critical Resource Analysis. A system check for critical resources on all affected hardware paths associated with the specified slot, analyzing file systems, volumes, processes, networking, swap, and dump. Generates a report of affected resources. A daemon that handles events generated by pressing a PCI I/O slot Attention Button. Planning and Preparation In many cases, other interface cards and slots within the system are dependent upon the target card If the target card is a multiple-function card (MFC), suspending drivers for the target card slot also suspends individual drivers for the multiple hardware paths on that card. If the target card has multiple ports, then all individual ports are suspended and then resumed when the card is replaced. If you temporarily stop power to a multi-card power domain, you will also stop power to any other card slots (affected card slots) in that same power domain. During card replacement and deletion, pdweb and olrad perform a CRA, which checks all ports on the target card for critical resources that are temporarily unavailable while the card is shut down. These tools prevent you from performing OL* procedures that can adversely affect other areas of the server. This section provides information that minimizes errors or problems when performing OL* procedures. Card Compatibility When you perform an OL* operation, you must consider the compatibility of the cards used. Each of the three operations have different requirements, as outlined here. 20 PCI Card OL* Overview

21 Online Addition When you add an interface card online, first determine whether the new card is compatible with the system. Each OL* capable PCI slot provides a set amount of power. The card to be added cannot require more power than is available. Some systems may have only one slot per bus with sufficient power. The card must also operate at the slot's bus frequency. For more information, see Frequency Mismatch (page 23). Before you add a card to the system, the appropriate driver for that card must be configured in the kernel. In most cases, the added card is the same type as a card already in the system, and the driver is already in the kernel. Kernel configuration is accessible through kcweb. If the required driver is not present, a reboot is required to load the driver. You can then ass the card while the system is down, or add it online after rebooting. A reboot may not be needed if the OS version supports Dynamic Loadable Kernel Modules (DLKM). If the necessary driver is not present you can load it manually. If the driver is static and not configured in the kernel, then the card cannot be added online. Online Replacement IMPORTANT: Online replacement (OLR) of a LAN card in a Serviceguard cluster fails because the Critical Resource Analysis (CRA) performed as part of the OLR operation returns CRA_SYS_CRITICAL. You will encounter this problem whether you use the Peripheral Device Tool (pdweb) or the HP-UX olrad command. Online Deletion To fix this problem, apply patch PHNE_ NOTE: You can apply patch PHNE_35894 without a reboot. On a system to which patch PHNE_35894 has been applied, you will be able to perform online replacement of hot-swappable cards (without bringing down the cluster). For detailed information, see Replacing LAN or Fibre Channel Cards in chapter 8 of Managing Serviceguard, available at NOTE: If for some reason you need to proceed without patch PHNE_35894, you must follow the Off-Line Replacement procedure under Replacing LAN or Fibre Channel Cards in chapter 8 of Managing Serviceguard. For more information about this issue, see SR # (JAGag27186). When replacing an interface card online, you must use an identical replacement card. This is referred to as like-for-like replacement. Using a similar but not identical card can cause unpredictable results. For example, a newer version of the target card with identical hardware can use an updated firmware version that may conflict with the current driver. If a new card is not acceptable, pdweb will report that the card cannot be resumed, the Attention Button method will result in the slot not being powered up, and olrad will return an error. During the replacement process, the driver instance for each port on the target card runs in a suspended state. I/O to the ports is either queued or failed while the drivers are suspended. When the replacement card comes online, the driver instances resume normal operation. Each driver instance must be capable of resuming and controlling the corresponding port on the replacement card. The PCI specification enables a single physical card to contain more than one port. Attempting to replace a card with another card that has more ports can result in the additional ports being claimed by other drivers if an ioscan occurs when slot power is on. When deleting an interface card online, you do not need to consider card compatibility. Planning and Preparation 21

22 During the deletion process, the driver instance for each port on the target card is suspended. I/O to the ports are either queued or failed while the drivers are suspended. When the card is removed, the driver instances deleted. Critical Resources Replacing a running card can seriously affect the system. Since slot power must be off when you remove the old card and insert the new card, first consider the effects of shutting down the card's functions, especially if there is no online failover or backup card to pick up those functions. For example: Which mass storage devices will be temporarily disconnected when the card is shut down? Will a critical networking connection be lost? A critical resource can cause a system crash or loss of data if the slot is suspended or disconnected. For example, if the SCSI adapter to be replaced connects to the unmirrored root disk or swap space, the system crashes when the card is shut down. During an OL* procedure, it is essential to check the targeted card for critical resources. Also check the effects on existing disk mirrors and other situations in which a card functions can be taken over by another card that is affected by the OL* procedures. Other Situations to Consider This section presents situations you can encounter when performing OL* operations, and how to handle them. These include the following: Power Domains Multiport Cards Virtual Ports Firmware Patch Information Shared Slots Frequency Mismatch Power Domains You cannot perform an OL* action for a card if any member of its power domain is a critical resource. Multiport Cards Virtual Ports Multiport PCI cards provide more than one function. Multiport cards have separate hardware paths for each port, and separate drivers bound at each hardware path. You cannot perform an OL* action for a card if any port is a critical resource. Some driver designs create virtual ports that do not directly correspond to any physical hardware. Virtual ports are identified by the driver that controls them. For example, HP Fibre Channel mass storage card drivers create virtual ports with drivers named fcp, fcpdev, fcparray, and fcpmux to control different aspects of the Fibre Channel mass storage network to which they are attached. The pdweb GUI does not explicitly list virtual ports on screens that affect physical ports, however both types of ports are suspended and resumed as appropriate. Since virtual ports are reported by ioscan, they appear with the same slot ID as their corresponding physical port. 22 PCI Card OL* Overview

23 Firmware Patch Information Shared Slots You may need to update system firmware to enable OL*. For more information, see Read Before Installing or Updating to HP-UX 11i. Slots that share the same PCI or PCI-X bus are called shared slots. The behavior of an OL* operation on a shared slot depends on the state of the bus, which depends on whether cards are already on the other shared slots of the bus. CAUTION: If a card on a shared slot is added, replaced, or deleted, a frequency or bus mode mismatch can cause the OL* operation to fail. Frequency Mismatch All cards must operate at their slot's bus frequency. A PCI card can run at a frequency lower than its maximum capability. A card added that has a higher frequency capability than the slot runs at the slower slot speed. Cards with a slower frequency may not be able to be installed in a slot with a higher frequency. Table 1-2 describes the consequences of installing a card into a slot with a different frequency. Table 1-2 Installing Card into a Slot with a Different Frequency Card Frequency Slot Frequency Consequences Exceptions Lower Higher Bus drops to match the lower frequency. If this is a shared frequency domain, the installation is rejected to prevent slowing down an already running card. Higher Lower Card speed drops to match the bus speed. No exceptions. Table 1-3 describes the consequences on frequency compatibility on shared slots. Table 1-3 Frequency Matching Scenarios for Shared Slots Slot 1 Add Empty Replace Empty Delete Empty Add Replace Add Slot 2 Empty Add Empty Replace Empty Delete Add Replace Replace Description No frequency issue. The slot and card operate at an optimum frequency. No frequency issue. The slot and card operate at an optimum frequency. No frequency issue. The slot and card operate at an optimum frequency. No frequency issue. The slot and card operate at an optimum frequency. No frequency issue. No frequency issue. The first card to be added in sets the slots operating frequency. If the second card can match that frequency, the second Add succeeds. Otherwise, the Add operation fails. The first card to be replaced sets the slots operating frequency. If the second card can match that frequency, the second Replace succeeds. Otherwise the Replace operation fails. The first card to be Added or Replaced sets the slots operating frequency. If the second card Added or Replaced can match that frequency, the operation succeeds. Otherwise, the second operation fails. Other Situations to Consider 23

24 Table 1-3 Frequency Matching Scenarios for Shared Slots (continued) Slot 1 Add Replace Slot 2 Delete Delete Description If Add is performed first and the added card can perform at the second slots operating frequency Add succeeds. Otherwise Add fails. If Delete is performed first, there is no frequency issue. An Add in the other slot succeeds and the Added card operates at an optimum frequency Replace and Delete succeed. The slot and card operates at the lowest operating frequency. When Adding a card to the slot where delete is performed, Add succeeds if the added card can perform at the other slots operating frequency. Otherwise Add fails PCI Error Recovery The PCI Error Recovery feature enables you to detect, isolate, and automatically recover from a PCI error, avoiding a Machine Check Abort (MCA) or a High Priority Machine Check (HPMC). PCI Error Recovery is enabled by default on the HP-UX 11i v3 operating system. With the PCI Error Recovery feature enabled, if a PCI error occurs on an I/O bus adapter containing an I/O card that supports PCI Error Recovery: The PCI bus is isolated from further I/O The I/O devices are quiesced The error is cleared The bus is reset The devices are resumed If the devices encounter further errors upon resumption, they will remain stopped. If the devices are in hotpluggable slots, the olrad command or the attention button can be used to manually recover. If PCI Error Recovery is disabled and a PCI error occurs, an MCA or HPMC will occur, then the system will crash. For detailed information about PCI Error Recovery, see the PCI Error Recovery Product Note, and the PCI Error Recovery Support Matrix. Both documents can be accessed in the High Availability category at: 24 PCI Card OL* Overview

25 2 The pdweb Peripheral Device Tool Web Interface This chapter describes the features and functions of the pdweb Peripheral Device Tool Web interface. This chapter addresses the following topics: Peripheral Device Tool How the pdweb Tool Works Security Accessing pdweb Using pdweb with Bastille Navigating pdweb Critical Resource Analysis Adding a Card Online Replacing a Card Online Bringing a Card Online Deleting a Card Online Turning the Attention LED to BLINK or OFF Peripheral Device Tool The Peripheral Device Tool (pdweb) is an easy-to-use, powerful peripheral device management solution that uses a Web-enabled graphical user interface (GUI). This tool enables you to view all devices on a host system and configure the slots and cards for that system. The GUI steps you through the entire process of card addition, replacement or deletion. pdweb operates in a single-system environment. You can launch pdweb from the System Management Homepage (SMH), or from the Systems Insight Manager (SIM). IMPORTANT: System Administration Manager (SAM) is deprecated in HP-UX 11i v3. It is replaced by SMH. For more information, see Using SMH (page 27). When you start SAM, the SMH command is automatically called. Servicecontrol Manager (SCM) is replaced by SIM in HP-UX 11i v3. For more information, see Using SIM (page 28). Additional information about pdweb is available from the various help links within the tool, including the online help system, related documentation, product support services, and other online resources. To review the product version number, copyright, and other legal notices, see the about help topic. Features and Benefits The pdweb GUI provides the following key features: Viewing detailed information about cards, devices, and slots, including all available PCI/OL* slots in an easy-to-read format. Adding, replacing, and deleting a card without shutting down the host system. Creating special device files dynamically. Generating a CRA report that lists the resources lost if a slot is powered off. These resources are grouped by their impact on the system. Bringing cards online without shutting down the host system. Peripheral Device Tool 25

26 Blinking or extinguishing the Attention Button LED of any slot that supports online actions. Previewing commands that support the GUI actions prior to execution. The pdweb tool also provides the following benefits: Performance improvements over previous pdweb implementations; actions that took a minute or more now take only a few seconds. Smart OL* technology takes advantage of the feature that only allows a matching replacement card to be brought online. The Fast Web interface is light on the network and can be used in places where an X Windows interface is not available or does not provide equivalent speed. Additional Web security provides a secure, encrypted connection between the Web browser and the host system. How the pdweb Tool Works The pdweb GUI is powered by the pdweb command introduced in HP-UX 11i v2. This command invokes the necessary pdweb Web tools and the GUI. The pdweb tool uses the olrad command and other existing commands including ioscan, insf, and diskinfo to gather data and perform actions on the system. You can access the pdweb GUI using SMH or SIM. Figure 2-1 The pdweb Interface 26 The pdweb Peripheral Device Tool Web Interface

27 Security When you access pdweb from a Web browser, you log in using the secure HTML log in screen. Your log in information is securely transmitted using the SSL protocol. SSL provides data encryption and server authentication using public and private key technology. The Web server uses a certificate for server authentication. By default, this certificate is self-signed, but you can replace it with a certificate that is signed by a trusted certificate authority. If the Web browser is displayed on a different system than it is running on, X Window events are sent over the network as clear text. Intruders can intercept information, including passwords, as it moves between the system the browser is running on and the system it is displayed on. The pdweb command does not automatically use a Web browser unless it is running on the same host as the X Windows server. To override this security feature, use the -F option of the pdweb command. Accessing pdweb Using SMH Accessing SMH You can access pdweb in the following ways: Using the System Management Homepage (SMH) Using HP Systems Insight Manager (SIM) You are required to log in to SMH before you can access the pdweb tool. You can access the SMH log in page in the following ways: Using a Web browser Using the pdweb Command Using a Web Browser To launch SMH from a Web browser, follow these steps: 1. Open a Web browser on any network client that is connected to your company intranet. 2. Enter where hostname is the fully qualified host name of the target host system. 3. The SMH log in screen displays. Using the pdweb Command To launch SMH from the command line, follow these steps: 1. Set the DISPLAY environment variable to the system where you want to see the GUI. Enter the following command: # export DISPLAY=hostname:0.0 where hostname is the fully qualified host name of the system where you want to see the GUI. 2. Enter the following command: # pdweb -F Security 27

28 3. A browser starts and displays the SMH log in screen. TIP: If a supported Web browser has been installed somewhere other than the default location, set the BROWSER environment variable to the path of the browser. For a detailed description of the pdweb command, see the pdweb(1m) manpage and the 11i v3 System Administration Guide Configuration Volume. Accessing the pdweb tool Using SIM You must be logged in as root to perform a hardware scan, reinstall device files, or perform any OL* tasks on slots. To view peripheral devices, you can log in as an unprivileged user. NOTE: Ensure that the cookies are enabled in your Web to run pdweb. If cookies are not enabled in your browser, an error message is displayed. To access the pdweb tool from SMH, follow these steps: 1. Log in to SMH with User Name and password. 2. On the SMH home page, select Tools from the menu bar. 3. On the Tools page, select Manage Peripheral Devices from the Peripheral Devices submenu. The pdweb tool displays, with a banner showing Tools Peripheral devices Manage Peripheral Devices. Alternatively, on the SMH home page, select Peripheral Devices from the System Configuration submenu. The pdweb banner displays Home System Configuration Peripheral Devices. NOTE: If pdweb does not display, then it is not installed or you do not have the necessary permissions to access it. Log out of SMH when your work is complete. This prevents anyone from accessing your active session and avoids a potential breach in security. NOTE: The SMH session times out if you do not keep it active. You cannot configure the timeout using pdweb. A message appears to alert you that you are about to be logged out. To return to SMH, click OK. Be sure to keep the session active by using the controls within SMH or the Refresh button in your browser. You are required to access SIM before you can access the pdweb tool. To log in to SIM and access the pdweb tool, follow these steps: 1. Open a Web browser on any system that is connected to your company intranet. 2. Access the log in screen at: Where hostname is the fully qualified host name of the SIM central management server (CMS). 3. Log in to SIM with name and password. 28 The pdweb Peripheral Device Tool Web Interface

29 4. On the SIM home page, select Tools System Information System Management Homepage... from the menu bar. A browser starts and displays a System Management Homepage target selection screen. 5. Select HP-UX in the subgroup Systems by Operating System as the target system from the drop down menu. A list of systems display. 6. Select the system you wish to access with pdweb. 7. Click Apply. A verification screen displays to confirm the target system 8. To verify the target system, select the system. 9. Click Run Now. The SMH log in screen displays. 10. Log in to SMH with User Name and password. 11. On the SMH home page, select Tools from the menu bar. 12. On the Tools page, select Manage Peripheral Devices from the Peripheral Devices submenu. The pdweb tool displays, with a banner showing Tools Peripheral devices Manage Peripheral Devices. Alternatively, on the SMH home page, select Peripheral Devices from the System Configuration submenu. The pdweb banner displays Home System Configuration Peripheral Devices. NOTE: If pdweb does not display, then it is not installed or you do not have the necessary permissions to access it. Log out of SMH when your work is complete. This prevents anyone from accessing your active session and avoids a potential breach in security. NOTE: The SMH session times out if you do not keep it active. You cannot configure the timeout using pdweb. A message appears to alert you that you are about to be logged out. To return to SMH, click OK. Be sure to keep the session active by using the controls within SMH or the Refresh button in your browser. For more information about the SIM product, see the HP Systems Insight Manager documentation, available at: Using pdweb With Bastille HP Bastille is an OS hardening and lockdown tool that enhances the security of an HP-UX system. It configures daemons, system settings, and firewalls to be more secure. It turns off unnecessary services such as pwgrd and printing, and it configures client software such as rcp and rlogin to be more secure. HP Bastille also helps create chroot jails that limit the vulnerability of common Internet services such as Web servers and Domain Name Servers (DNS). To use pdweb in conjunction with HP Bastille, you must configure the system as follows: 1. Log in as root. 2. Enter the following command: #cp /etc/opt/sec_mgmt/bastille/mandmz.config /etc/opt/sec_mgmt/bastille/config. Using pdweb With Bastille 29

30 This copies the configuration file, preconfigured to work with pdweb, to the correct directory. NOTE: The HOST.config configuration file can also be used but it is less secure. Do not use the DMZ.config configuration file as pdweb because it does not allow the Web server to autostart. 3. Enter the following command: #bastille -b to activate the new configuration. For more information, see the bastille(1m) manpage. Navigating pdweb The basic features of the pdweb GUI are described in the following sections. Components of the GUI The pdweb GUI has the following components: Banner Tabs Lists Action Menu Command Preview Banner The pdweb banner located at the top of the page contains the tool name and your user name. The Sign out button is located on the right hand side of the banner. Figure 2-2 pdweb Banner Tabs Tabs divide information into several sections, making it easy to locate and manage devices and slots. The active tab is highlighted with a different color, making it easy to identify. The default tab presented after logging in depends on whether you log in as root and the capabilities of the system slots. If you log in as root and the system slots are OL* capable, the OLRAD Cards tab displays. Otherwise the I/O Tree tab is displayed. Figure 2-3 pdweb Tabs with the OLRAD Cards tab active Lists Lists organize, group, and summarize information. Use lists as the starting point for managing the devices and slots on the system. Each list of items is relevant to the active tab. 30 The pdweb Peripheral Device Tool Web Interface

31 NOTE: Only one list item can be selected at a time. You cannot select multiple devices or slots from a list. Long lists can use more than one page to display all listed items. The number of items on display are altered by selecting from the drop down menu. Figure 2-4 List size selection menu Lists with sizes which exceed the amount selected are navigated through by the arrow buttons. The following table describes the abilities of the buttons. Table 2-1 pdweb List Navigation Buttons Sets the list to the beginning. Sets the list forward by n items, where n is the selected number of items to display. Sets the list backward by n items, where n is the selected number of items to display. Sets the list to the end. Figure 2-5 pdweb List Example Navigating pdweb 31

32 Action Menu The Action menu to the right of a list is context-sensitive and changes each time a tab is selected. The actions in this menu activate based on the selected item and its capabilities. The Action menu is always available and enables you to execute the actions listed. For example, the first time the OLRAD Cards tab is activated, only help actions are active in the Actions menu. When you select an OL* capable slot, other actions in the menu activate. Figure 2-6 pdweb Action Menu Command Preview When you select an action that invokes a process (these actions end with an ellipsis), you are presented with a process page for the action. This page contains a Command Preview that displays the command to be executed by the pdweb. You can decide whether you want to proceed with the action or cancel it. TIP: The Command Preview relates the GUI action to the underlying command syntax and execution. Figure 2-7 pdweb Command Preview Example 32 The pdweb Peripheral Device Tool Web Interface

33 OLRAD Cards Tab The OLRAD Cards tab columns that comprise the list of slots provide basic information about each slot. N/A in the Suspended column means that either there is no card in the slot or that the card is not OL* capable. Graphic indicators appear in the list of slots and on the minitabs to enable you to quickly identify the state of each slot. These graphics display according to the state of the slot and are described in table 2-2. Table 2-2 pdweb Slot State Graphic Symbols Symbol Description Power is applied to the slot. A card is present in the slot. The card is in a suspended state and can be brought online. To view details of a slot, click anywhere in the row where the slot appears in the list. Once you select a row, the detailed view of the slot displays below the tabular list, presenting all available information about the selected slot. Navigating pdweb 33

34 Figure 2-8 Detail Slot View on pdweb I/O Tree Tab To enable you to quickly view all of the I/O devices (I/O Tree) on your system, pdweb uses information from the last hardware scan and displays the results in a table. The Hardware (H/W) Path, Class (type), and a Description of each device found on the host system are listed. The last hardware scan date and time appear to the left of Refresh. 34 The pdweb Peripheral Device Tool Web Interface

35 Figure 2-9 I/O Tree Tab in pdweb Image The information presented in this tab is derived from the last execution of ioscan cached on the host system. It is read-only and can only be refreshed by running a new hardware scan, see Refreshing the I/O Tree (page 38). NOTE: Devices are determined and displayed by ports responding to the hardware scan. You cannot determine which devices exist on multifunction (combination) cards. To view device details, both internal and leaf nodes, click anywhere in the row where the device appears in the list. The detailed view of the device displays, below the list, presenting all available information about the selected device. The information displayed varies for each device because this data is dependent on the information retrieved during the hardware scan. See Figure 2-10 (page 36). Navigating pdweb 35

36 Figure 2-10 pdweb I/O Tab Detail View You can filter the list of devices by changing the view. See "Changing Views." The actions available to root on this tab are as follows: Reinstalling Device Files Refresh Changing Views Changing the View by Device Class Reinstall the special device files applicable to the selected device. Run a new hardware scan immediately. A complete list of devices, including all classes, is displayed when you select All. This is the default view. 36 The pdweb Peripheral Device Tool Web Interface

37 Changing the devices list view enables you to isolate a device category from the entire list, shorten long lists by filtering, or locate a particular device. Change the view using the Class list control, which filters the devices list based on your selection. The filter choices are the major device classes: disk tape autochanger (autoch) lan lunpath fc All the filters rely on the device category (returned as part of the hardware scan), which is listed in the Class column of the device list. For example, if you select tape from the Class list, only tape devices appear in the new list. To return to the complete list of devices, select All. Choose another filter from the Class control to reset the selection of a device. Changing the View with Search You can filter the list of devices by searching with criteria you define, such as device class, hardware path, word or phrase. This is useful for isolating device classes that are not included in the standard Class filter control. You can use the Class filter and text search controls independently or together. Figure 2-11 pdweb Class and Search Options To search in pdweb, follow these steps: Navigating pdweb 37

38 1. To search within a particular device class only, select a filter from the Class list or use the all devices default. The filtered list displays. NOTE: Make filtering selections first because all search and filtering criteria are reset when you select a filter. 2. Enter the information you want to find in the Search text box. Spell your search criteria correctly; the search function is case sensitive. 3. Click to view a list of devices that match your search criteria. If no devices are displayed, modify your search text and selection in the Class list and search again. For example, select the default class All. Enter the search text ba to view only bus adapter devices. Figure 2-12 pdweb I/O Tree Search Results To reset all search criteria and return to the default view, click. Refreshing the I/O Tree Updating the information presented on the I/O Tree tab uses an on-demand hardware scan facility that executes ioscan and updates the cached data the system stores in the kernel. Executing ioscan can result in the addition or deletion of devices from the devices list or a change in state. For more information, see the ioscan(1m) manpage. Click Refresh in the upper right corner of the tab to begin a hardware scan. The hardware scan is executed as a background task on the host to enable you to continue to use pdweb. The Refresh button changes to Finished? with a message alerting you that the hardware scan has been launched in the background. To monitor the progress of the hardware scan, click Finished? which remains until the hardware scan finishes. 38 The pdweb Peripheral Device Tool Web Interface

39 The processing time for the hardware scan is dependent on the number of devices connected to the host system. If you have a large number of devices connected to your host system, hardware scans can be time consuming, use them with care. Reinstalling Device Files You can reinstall special files for a particular device if the files are missing, corrupt, or out of date. NOTE: You must log in as root to reinstall device files. Reinstalling device files executes in the background because it can take several minutes to run the insf command, depending on the type of node selected (internal or leaf). To reinstall files for a device follow these steps: 1. Select a device from the I/O Tree tab. 2. Click Reinstall Device Files. NOTE: This menu selection is not active unless a device is selected. A confirmation window displays to enable you to review the command to be executed and decide whether to continue the action. Figure 2-13 pdweb Reinstall Device Files Screen 3. Click Reinstall to reinstall the device files for the selected device or Cancel to discontinue the action. The command executes and the I/O Tree tab displays. Viewing Slot Information To enable you to view all the slots on your system with OL* capability, pdweb uses the olrad command and presents the results in an easy-to-read tabular format in a Web browser. Navigating pdweb 39

40 Figure 2-14 OL* Cards in pdweb Image Available pdweb Actions These actions are available in a list on the right hand side of the tool. Those actions which can be applied to a selected slot are activated for selection. Run Critical Resource Analysis Add Card Online Replace Card Online Delete Card Online Bring Card Online Turn On/Off Slot LED Slot Detail View Generate a slot-specific report detailing which system critical resources are affected by changes to the specified slot. Add a new card to a selected slot and bring it online Replace an existing card in a selected slot and bring it online. Delete an existing card in a selected slot. Bring a card online after postponement during an add or replace action. Turn the Attention LED to BLINK or OFF for the selected slot. Once you select a slot, it's details appear below the list of slots in the four minitabs described in the table below: Table 2-3 pdweb Slot Detail Information Tabs Tab Slot Card Interfaces Attached Devices Device Files Description Slot-specific information, including whether or not the slot is OL* capable All interfaces (or every port on the card) found in the slot All devices connected to the selected slot All special devices files associated with the selected slot The details presented can vary for each slot and are dependent on the information gathered by the olrad command. For data object specifics, see the olrad(1m) manpage. 40 The pdweb Peripheral Device Tool Web Interface

41 Figure 2-15 pdweb OLRAD Cards Slot and Card Interfaces Tab Examples Navigating pdweb 41

42 Figure 2-16 pdweb OLRAD Cards Attached Devices and Device Files Tab Examples Using Search You can filter the list of slots by searching for a particular slot, path, word, or phrase. TIP: Use search to isolate Suspended slots from a long list. To search for a slot, follow these steps: 1. Enter the information you want to search for in the text Search box. Spell your search criteria correctly; the search function is case sensitive. 2. Click to view a list of slots that match your search criteria. If no slots are displayed, modify your search text. For example, search on the text yes to view only slots that are Occupied or Suspended. Alternatively, if you use the search text off, only those slots that are currently powered off are displayed. To reset all search criteria and return to the default view, click. Critical Resource Analysis A critical resource can cause a system crash or loss of data if the slot is suspended or disconnected. For example, if a SCSI adapter to be replaced connects to unmirrored root disk or swap space, the system will crash when the card is replaced. During an OL* procedure, it is essential to check the targeted card for critical resources, and for the effects of existing disk mirrors and other situations where a card's functions can be taken over by another card that will not be affected. A Critical Resource Analysis (CRA) is a usage report of a set of interface resources. A brief summary is provided when the usage analysis is performed. Detailed analysis logs for each subsystem exist in the /var/adm/cra.log logfile. NOTE: The CRA in HP-UX 11i v3 provides a briefer report and more comprehensive logs than previous systems. The following areas are analyzed: System Critical Resources with a high probability of crashing or degrading the performance of the system, including /(root), /stand, /usr, /etc and all directly mounted swap file systems. 42 The pdweb Peripheral Device Tool Web Interface

43 Data Critical Warnings Resources with a high probability of data loss, including locally mounted file systems, (excluding system critical, NFS, CD-ROM File System [CDFS], and any multipath logical volume,) all open files including device files, and any networking card that is not suspended. Other resources in use on affected devices and are not deemed critical to the system, including volume groups, logical volumes not being used or with alternate paths, dump, affected CDFS file systems, networking cards protected by high availability resources, and networking cards that are suspended. TIP: HP recommends that you generate and carefully review a CRA for your target card and slot prior to executing any OL* actions. To run a CRA, follow these steps: 1. Select a card from those listed on the OLRAD Cards tab. 2. Click Run Critical Resource Analysis. The CRA report for that slot appears in a scrollable window. See pdweb CRA Critical Example (page 43). To print the report, use your Web browser's print features. 3. Click Done at the end of the report when you are finished reading it. The OLRAD Cards tab displays. Figure 2-17 pdweb CRA Critical Example Adding a Card Online This action is active only when the selected slot can add a card. Before beginning, familiarize yourself with the OL* concepts in Important Terms and Concepts (page 20). Adding a Card Online 43

44 IMPORTANT: Do not attempt to physically add a card before beginning the process properly using pdweb, olrad, or the Attention Button. You are prompted to add the card to the target slot at the appropriate point in the pdweb process. To add a card, follow these steps: 1. Select a slot from the list on the OLRAD Cards tab. 2. Click Add Card Online. The Add Card Online page appears, describing the add procedure. As you follow the steps, each step is checked off. You can choose to end the procedure at any time, leaving the system unchanged, by clicking Cancel. Figure 2-18 pdweb Adding a Card Example 3. To start adding the card, click Run CRA. A CRA runs on the system and the results are displayed in Step 1 of the Add Card process. 44 The pdweb Peripheral Device Tool Web Interface

45 Figure 2-19 pdweb Adding a Card CRA Example The results of the CRA determine the action you take in Step 2. You are presented with the following choices. Table 2-4 pdweb Adding a Card CRA Results CRA Result Success Warning Data Critical Warning System Critical Warning Error Available Actions Power Off and Cancel Power Off and Cancel Force Power Off and Cancel Done Done Suggested Course of Action Continue to add the new card. Carefully review the results data to determine whether tocontinue to add the new card. Terminate the card addition, resolve the data conflicts, and attempt to add the card again. Terminate the card addition, because it will be detrimental to the system. Terminate the card addition. A problem exists that you must investigate using the information provided in the CRA. 4. Click Power Off or Force Power Off. The following actions start: The amber Attention LED is set to BLINK. The target slot is powered off if necessary. The target slot green power LED is set to steady OFF. Adding a Card Online 45

46 Click any button to return to the OLRAD Cards tab and leave the state of the target slot unchanged. Figure 2-20 pdweb Adding a card CRA Step 2 Example CAUTION: Do not push the Attention Button on the slot, if one exists. The slot powers on and the system attempts to bring the card online prematurely. IMPORTANT: Only add a card to a slot when the power LED is OFF. At the system, locate the target slot and confirm that the green power LED is off and the amber Attention LED is flashing. If either LED is not in the correct state, see the Messages from pdweb Actions (page 77). 5. Physically install the new card in the target slot. IMPORTANT: Ensure that the latch is closed firmly. For more information, see IMPORTANT (page 19). For information about card installation, see the Host Bus Adapter (HBA) documentation. 46 The pdweb Peripheral Device Tool Web Interface

47 6. Choose one of the following options: To bring the card online now, click Bring Card Online. The following actions start: The target slot is powered on. The target slot green power LED is set to steady ON. The card and device drivers are bound to the target slot. The amber attention LED is set to steady OFF. These events activate the target card and bring it online in the target slot. When the system finishes bringing the card online, a confirmation page displays. Click Done to return to the OLRAD Cards tab. The card you added is listed in the target slot with the updated information. For more information, see Bringing a Card Online (page 51) for screen image. If an error occurs, see Messages from pdweb Actions (page 77) for additional information. To bring the card online later, click Defer. You return to the OLRAD Cards tab. The target slot is updated to reflect that it is suspended. To bring a deferred card online, see Bringing a Card Online (page 51) procedure to complete this process. Replacing a Card Online You can replace an existing card in a slot that is capable of OL* card replacement. IMPORTANT: Online replacement (OLR) of a LAN card in a Serviceguard cluster fails because the Critical Resource Analysis (CRA) performed as part of the OLR operation returns CRA_SYS_CRITICAL. You will encounter this problem whether you use the Peripheral Device Tool (pdweb) or the HP-UX olrad command. To fix this problem, apply patch PHNE_ NOTE: You can apply patch PHNE_35894 without a reboot. On a system to which patch PHNE_35894 has been applied, you will be able to perform online replacement of hot-swappable cards (without bringing down the cluster). For detailed information, see Replacing LAN or Fibre Channel Cards in chapter 8 of Managing Serviceguard, available at NOTE: If for some reason you need to proceed without patch PHNE_35894, you must follow the Off-Line Replacement procedure under Replacing LAN or Fibre Channel Cards in chapter 8 of Managing Serviceguard. For more information about this issue, see SR # (JAGag27186). IMPORTANT: A replacement card must use the same drivers as the existing card. For example, you cannot replace a LAN card with a SCSI card. Before beginning, familiarize yourself with the OL* concepts in How the pdweb Tool Works (page 26). IMPORTANT: Do not attempt to physically replace a card before beginning the replace process in pdweb. You will be prompted to replace the card in the target slot at the appropriate point in the process. To replace a card, follow these steps: Replacing a Card Online 47

48 1. Select a card from the list on the OLRAD Cards tab. Figure 2-21 pdweb Choose a Card to Replace 2. Click Replace Card Online. The Replace Card Online page displays. As you progress through the defined steps, each step is checked off. At any time, you can choose to end the process and leave the system unchanged by clicking Cancel. Figure 2-22 pdweb Replace Card Example 3. To start the card replacement, click Run CRA. A CRA runs on the system and the results are displayed in Step 1 of the card replacement process. 48 The pdweb Peripheral Device Tool Web Interface

49 Figure 2-23 pdweb Replace Card CRA Example The results of the CRA determine what you can do in the next step. The following table lists these result driven choices. Table 2-5 pdweb Replace a Card CRA Results CRA Result Success Warning Data Critical Warning System Critical Warning Error Available Actions Power Off and Cancel Power Off and Cancel Force Power Off and Cancel Done Done Suggested Course of Action Continue to replace the card. Carefully review the results data to determine whether to continue to replace the card. Terminate the card replacement, resolve the data conflicts, and attempt to replace the card again. Terminate the card replacement. It will be detrimental to the system. Terminate the card replacement. A problem exists that must be investigated using the information provided in the CRA. 4. Click Power Off or Force Power Off. The following actions start: The amber Attention LED is set to BLINK. The target slot is powered off if necessary. The target slot green power LED is set to steady OFF. Replacing a Card Online 49

50 Click any other button to return to the OLRAD Cards tab and leave the state of the target slot unchanged. CAUTION: Do not push the Attention Button on the slot, if one exists. The slot powers on and the system attempts to bring the card online prematurely. IMPORTANT: Only replace a card in a slot when the power LED is OFF. At the system, locate the target slot and confirm that the green power LED is off and the amber Attention LED is flashing. If either LED is not in the correct state, see Messages from pdweb Actions (page 77). 5. Physically remove the existing card, then install the new card in the target slot. IMPORTANT: Ensure that the latch is closed firmly. For more information, see IMPORTANT (page 19). For more information about card installation, see the Host Bus Adapter (HBA) documentation. Figure 2-24 pdweb Bring Card Online 50 The pdweb Peripheral Device Tool Web Interface

51 6. Choose one of the following actions: To bring the card online now, click Bring Card Online. The following actions start: The target slot is powered on. The target slot green power LED is set to steady ON. The card and device drivers are bound to the target slot. The amber Attention LED is set to steady OFF. These events activate the target card and bring it online in the target slot. When the system finishes bringing the card online, a confirmation page displays. Click Done to return to the OLRAD Cards tab and see that the replaced card is listed in the target slot with the updated information. If an error occurs, see Messages from pdweb Actions (page 77) for additional information. To bring the card online later, click Defer. Bringing a Card Online If you deferred bringing the card online, you return to the OLRAD Cards tab and the target slot is updated to reflect that it is suspended. To bring a deferred card online, see Bringing a Card Online to complete this process. Click Done to return to the main screen. If you postponed the completion of adding or replacing a card in a slot or experienced an error in the last step of a card replacement, you can complete the process and bring the card online as a separate task. All slots containing cards that can be brought online are identified in the Suspended column of list of cards on the OLRAD Cards tab with yes and the following icon:. To bring a card online, follow these steps: 1. Select a card from the list on the OLRAD Cards tab. 2. Click Bring Card Online. The Bring Card Online page appears identifying the slot selected. Bringing a Card Online 51

52 Figure 2-25 pdweb Bring Card Online 3. To bring the card online, click Bring Card Online. The following actions start: The target slot is powered on. The target slot green power LED is set to steady ON. The card and device drivers are bound to the target slot. The amber attention LED is set to steady OFF. These events activate the target card and bring it online in the target slot. When the system finishes, a confirmation page appears identifying the results. 4. Click Done to return to the OLRAD Cards tab. The card that was brought online is listed in the target slot with the updated information. If an error occurs, see Messages from pdweb Actions (page 77) for additional information. Figure 2-26 pdweb Bring Card Online Success Deleting a Card Online You can delete a card online only when the selected slot is OL* capable. Before beginning, familiarize yourself with the OL* concepts in How the pdweb Tool Works (page 26). 52 The pdweb Peripheral Device Tool Web Interface

53 IMPORTANT: Do not attempt to physically remove a card before beginning the delete process in pdweb. You will be prompted to remove the card from the target slot at the appropriate point in the process. To delete a card from a slot, follow these steps: 1. Select a card from the list on the OLRAD Cards tab. Figure 2-27 pdweb Choose a Card to Delete 2. Click Delete Card Online. The Delete Card Online page appears. As you progress through the defined steps, each step is checked off. You can choose to end this process at any time, leaving the system unchanged, by clicking Cancel. To start deleting the card, click Run CRA in the following screen: Deleting a Card Online 53

54 The results of the CRA determine Step 2. The following table lists the result driven choices. Table 2-6 pdweb Delete a Card CRA Results CRA Result Success Warning Available Actions Power Off and Cancel Power Off and Cancel Suggested Course of Action Continue to delete the card. Review the results data to determine whether to continue to delete the card. 54 The pdweb Peripheral Device Tool Web Interface

55 Table 2-6 pdweb Delete a Card CRA Results (continued) CRA Result Data Critical Warning System Critical Warning Error Available Actions Force Power Off and Cancel Done Done Suggested Course of Action Terminate the card deletion, resolve the data conflicts, and attempt to delete the card again. Terminate the card deletion. It will be detrimental to the system. Terminate the card deletion. A problem exists that must be investigated using the information provided in the CRA. 3. Select Power Off to stop the power supply for the target slot from which the card must be removed. After completing this step, the target slot LED starts blinking. Remove the card manually from the slot. 4. Select Post Delete to switch off the slot LED. 5. The following final screen is displayed: Deleting a Card Online 55

56 6. Click Done to return to the main pdweb screen. Configuring an I/O Chassis During Dynamic npartition Operations To add an I/O chassis to a cell, follow these steps: 1. Click Add Chassis Online. The Add Chassis Online page appears. Figure 2-28 pdweb Adding I/O Chassis Card Example 2. Select the Hardware Path of the Cell to which the I/O chassis is being added. 3. Click the Add Chassis button. The I/O Chassis will be added to the selected cell hardware path and the pdweb main screen is displayed. Turning the Attention LED to BLINK or OFF You can control the amber Attention LED of a slot by setting it to BLINKing or OFF, to help physically locate a slot. The slot does not need to be occupied to use this feature. In addition to the amber Attention LED, each slot has a green power LED that indicates the power state of the slot. It is important to recognize the functional differences of these two LEDs. The following table lists the states of the amber Attention LED. 56 The pdweb Peripheral Device Tool Web Interface