Interface Card OL* Support Guide HP-UX 11i v3 HP Part Number: 5992-1723 Published: September 2007 Edition: E 0709
© 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 12.211 and 12.212, 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.
Table of Contents About This Document.......................................................................................................13 Intended Audience................................................................................................................................13 New and Changed Information in This Edition...................................................................................13 Publishing History..........................................................................
Changing Views.........................................................................................................................36 Changing the View by Device Class.....................................................................................36 Changing the View with Search...........................................................................................37 Refreshing the I/O Tree...........................................................................................................
6 Troubleshooting............................................................................................................77 Messages from pdweb Actions.............................................................................................................77 Log Files...........................................................................................................................................77 SAM Log File..................................................................................
List of Figures 2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 2-10 2-11 2-12 2-13 2-14 2-15 2-16 2-17 2-18 2-19 2-20 2-21 2-22 2-23 2-24 2-25 2-26 2-27 2-28 2-29 5-1 5-2 5-3 5-4 The pdweb Interface......................................................................................................................26 pdweb Banner................................................................................................................................30 pdweb Tabs with the OLRAD Cards tab active..................
List of Tables 1 2 1-1 1-2 1-3 2-1 2-2 2-3 2-4 2-5 2-6 2-7 3-1 3-2 3-3 5-1 6-1 6-2 6-3 Publishing History Details............................................................................................................13 HP-UX 11i Releases.......................................................................................................................14 Terms and Meanings.....................................................................................................................
List of Examples 3-1 4-1 4-2 The olrad -q Command Output....................................................................................................60 The olrad -q Command Output....................................................................................................66 CRA Reporting Success.................................................................................................................
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 http://www.docs.hp.com. The document publication date and manufacturing part number indicate the document's current edition.
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) Book Title KeyCap Emphasis Bold Bold ComputerOut UserInput Command Variable [] {} ... | An HP-UX manpage.
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 http://www.docs.hp.
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.
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.
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.
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.
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).
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.
Firmware Patch Information You may need to update system firmware to enable OL*. For more information, see Read Before Installing or Updating to HP-UX 11i. Shared Slots 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.
Table 1-3 Frequency Matching Scenarios for Shared Slots (continued) Slot 1 Slot 2 Description Add Delete 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 Delete Replace and Delete succeed. The slot and card operates at the lowest operating frequency.
2 The pdweb Peripheral Device Tool Web Interface This chapter describes the features and functions of the pdweb Peripheral Device Tool Web interface.
• • 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.
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.
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 You must be logged in as root to perform a hardware scan, reinstall device files, or perform any OL* tasks on slots.
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. 7. Select the system you wish to access with pdweb. Click Apply. A verification screen displays to confirm the target system 8. 9.
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.
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.
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.
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.
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.
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.
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 Reinstall the special device files applicable to the selected device. Run a new hardware scan immediately. Changing Views Changing the View by Device Class A complete list of devices, including all classes, is displayed when you select All. This is the default view.
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.
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.
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.
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 Generate a slot-specific report detailing which system critical resources are affected by changes to the specified slot.
Figure 2-15 pdweb OLRAD Cards Slot and Card Interfaces Tab Examples Navigating pdweb 41
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.
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.
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. 2. Select a slot from the list on the OLRAD Cards tab. Click Add Card Online. The Add Card Online page appears, describing the add procedure. As you follow the steps, each step is checked off.
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 4. CRA Result Available Actions Suggested Course of Action Success Power Off and Cancel Continue to add the new card. Warning Power Off and Cancel Carefully review the results data to determine whether tocontinue to add the new card.
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.
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.
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.
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 4. CRA Result Available Actions Suggested Course of Action Success Power Off and Cancel Continue to replace the card. Warning Power Off and Cancel Carefully review the results data to determine whether to continue to replace the card.
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.
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.
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.
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.
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 54 CRA Result Available Actions Suggested Course of Action Success Power Off and Cancel Continue to delete the card. Warning Power Off and Cancel Review the results data to determine whether to continue to delete the card.
Table 2-6 pdweb Delete a Card CRA Results (continued) 3. CRA Result Available Actions Suggested Course of Action Data Critical Warning Force Power Off and Cancel Terminate the card deletion, resolve the data conflicts, and attempt to delete the card again. System Critical Warning Done Terminate the card deletion. It will be detrimental to the system. Error Done Terminate the card deletion. A problem exists that must be investigated using the information provided in the CRA.
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. 3. Select the Hardware Path of the Cell to which the I/O chassis is being added. 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.
Table 2-7 pdweb LED States LED State Description Steady OFF Normal Normal operating mode. BLINKing Locate Slot is being identified by request. Steady ON Attention Operational hardware problem in this slot. To turn a slot LED to BLINK or OFF, follow these steps: 1. 2. Select a card from the list on the OLRAD Cards tab. Click Turn On/Off Slot LED. The Turn On/Off LED page is displayed, identifying the selected slot. Figure 2-29 pdweb Turn On/Off LED 3.
3 Attention Button - Direct Slot Control This chapter describes methods and procedures to perform OL* operations using the Attention Button.
The Attention LED helps you locate a slot and can indicate an operational hardware problem at the slot. Table 3-2 lists the attention LED states. Table 3-2 Attention LED State LED State Description Steady OFF Normal Normal operating mode. BLINK Locate Slot is identified at a user's request. Steady ON Attention Operational hardware problem at this slot. Location requests take priority over the Attention LED displaying operational problems.
• • • The power LED is steady OFF. If the system has an empty slot in the ON state, use the olrad command or the pdweb tool to power the slot OFF. The Attention LED is steady OFF or is BLINKing (if you located the slot). You are grounded to the chassis of the unit. For more information about card installation, see the Host Bus Adapter (HBA) documentation. To add a card online using the Attention Button, follow these steps: 1. 2. 3. If a latch is present, press the latch into the unlocked position.
NOTE: When you initiate an online replacement using the Attention Button, the system performs a restrictive CRA. The online replacement fails if critical resources may be impacted. If you want to control the CRA, use pdweb or the olrad command. For latch instructions, see the system hardware documentation.
Table 3-3 Results of Pressing the Attention Button (continued) Initial Condition Slot Occupied Press Attention Button Results Slot Suspended Driver Attached Power to slot Yes N/A No ON Nothing happens. Yes Yes Yes ON The slot powers off. No N/A N/A ON The slot powers off. No N/A N/A OFF Nothing happens.
4 The olrad Command This chapter describes how to use the olrad command to perform OL* operations. This chapter addresses the following topics: • Using olrad • Options, Scripts, and Logging Using olrad The olrad command enables you to perform online addition, replacement, and deletion of I/O cards. The olrad command performs a Critical Resource Analysis (CRA) of the system before performing any OL* operations.
Example 4-1 The olrad -q Command Output #olrad -q Slot Path 0-0-0-1 0-0-0-2 0-0-0-3 0-0-0-4 0-0-0-5 0-0-0-6 0-0-0-7 0-0-0-8 0/0/8/1 0/0/10/1 0/0/12/1 0/0/14/1 0/0/6/1 0/0/4/1 0/0/2/1 0/0/1/1 Bus Num 140 169 198 227 112 84 56 28 Max Spd 133 133 133 133 133 133 133 133 Spd Pwr 66 66 66 133 133 133 133 133 On On On Off Off Off Off Off Driver(s) Capable Occu Susp OLAR OLD Max Mode Yes No Yes Yes PCI-X Yes No Yes Yes PCI-X Yes No Yes Yes PCI-X No N/A N/A N/A PCI-X No N/A N/A N/A PCI-X No N/A N/A N/A P
IMPORTANT: Ensure that the latch is closed firmly. For more information, see “IMPORTANT” (page 19). 6. Enter the following command: #/usr/bin/olrad -A slot_ID 7. To verify that the operation succeeded, enter the following command: #/usr/bin/olrad -q slot_ID For more information about physically installing the card, see the Host Bus Adapter (HBA) documentation.
2. Prepare to delete: #/usr/bin/olrad -d slot_ID Driver instances are removed as part of this action. 3. 4. 5. If present, manually unlock the latch. Physically remove the existing card from the slot. Enter the following command: #/usr/bin/olrad -D slot_ID 6.
The Activation and De-activation of a cell as part of Dynamic nPartition operation are performed using the parolrad(1M) command. WARNING! It is possible for an I/O Chassis to be in inactive state, either because the I/O Chassis is connected to an inactive cell or because the I/O Chassis has been de-configured using the olrad chassis delete operation. The only supported procedure for adding/removing/replacing of PCI I/O cards in such an inactive I/O chassis is as follows: 1.
-r slot_id -R slot_id -d slot_id -D slot_id Prepare to replace a card on the system at the specified slot. A CRA is run to ensure that the card replacement will not cause disruption in the functioning of the system. The driver scripts run ( pref_replace and prep_replace) for the affected slots (if any) and the current slot. The drivers associated with the current slot and affected slots are suspended. The target slot is powered off and the Attention LED is set to BLINK. Post Replace phase.
5 Comparing and Combining OL* Methods This chapter compares the three OL* tools to help you decide which tool best meets your needs. Occasionally it may be easier to start with one tool and finish with another. This chapter provides information about using multiple tools to complete an OL* task. This chapter addresses the following topics: • Comparing OL* Methods • Mixing OL* Methods Comparing OL* Methods The following flowcharts compare different methods for performing the same OL* task.
Adding a Card Figure 5-1 illustrates the different methods you can use to add a card. Figure 5-1 Add Card Methods Comparison Flowchart 1. This assumes that all other tasks to add the card have already been performed. 2. The system performs a CRA. If the CRA detects a critical resource associated with the card, the CRA fails, which causes the OL* operation to fail. NOTE: Figure 5-1 illustrates a condensed version of the power LED behavior.
Replacing a Card Figure 5-2 illustrates the different methods you can use to replace a card. Figure 5-2 Replace Card Methods Comparison Flowchart 1. This assumes that all other tasks to replace the card have already been performed. 2. The system performs a CRA. If the CRA detects a critical resource associated with the card, the CRA fails, which causes the OL* operation to fail. NOTE: Figure 5-2 illustrates a condensed version of the Power LED behavior.
Deleting a Card Figure 5-3 illustrates the different methods you can use to delete a card. Figure 5-3 Delete Card Methods Comparison Flowchart 1. This assumes that all other tasks to delete the card have already been performed. 2. The system performs a CRA. If the CRA detects a critical resource associated with the card, the CRA fails, which causes the OL* operation to fail. NOTE: Figure 5-3 illustrates a condensed version of the Power LED behavior.
Attention LED Control Figure 5-4 illustrates the different methods you can use to control the Attention LED. Figure 5-4 Attention LED Control Methods Comparison Flowchart Changing the Attention LED state is a high priority action, and occurs immediately.
Mixing OL* Methods OL* tools enable you to complete an operation using a different method than the one you used to initiate the operation. Table 5-1 describes the consequences of mixing OL* tools in single operation. Table 5-1 Consequences of Mixing OL* Methods Start Replace Process Complete Replace Process pdweb olrad pdweb Attention Button1 olrad pdweb Attention Button pdweb olrad Comments and Actions to Bring the Slot Power ON You are in the middle of a sequence of pdweb screens.
6 Troubleshooting This chapter describes OL* errors and the steps you can take to correct them. This chapter addresses the following topics: • • • • Messages from pdweb Actions Attention Button Actions Messages from olrad Actions hotplugd Daemon Diagnostics Messages from pdweb Actions There are two types of pdweb messages: • • Messages that record OL* activity and errors generated by commands executed by pdweb. These messages are stored in various log files.
#tail /var/opt/hpwebadmin/logs/error_log To view the entire log file, you can use any of the following commands: • • • pg more cat The NetTL Log File The NetTL log file contains all errors generated by olrad except those that are generated when using view options such as -q or -c. This is a log file, not a directory. The NetTL log file is located in /var/adm/nettl.LOG00 To view the NetTL log file, use the netfmt command.
Messages from olrad Actions The olrad command uses the NetTL subsystem to log errors and create an audit trail for all OL* operations. The olrad command uses the SYSADMIN subsystem formatter to format the log messages.
Table 6-3 hotplugd Daemon Log File Messages Message Meaning ioctl(DEV_OLAR_GET_ABEVENT/WAIT) An error occurred on the ioctl() call to get Attention Button events error : errno= errMsg from the kernel in the WAIT mode. The errMsg value gives the reason for the error. ioctl(DEV_OLAR_GET_ABEVENT/NOWAIT) An error occurred on the ioctl()call to get Attention Button events from error : errno = errMsg the kernel in the NOWAIT mode. The errMsg value gives the reason for the error.
Table 6-3 hotplugd Daemon Log File Messages (continued) Message Meaning #oprnNum oprn - slot( slotId hotplugd received an invalid PCI OL* operation on slot slotId. The ) - time( time ) - Invalid PCI oprn value can be one of the following: OL * operation • INVALID • INVALID_INSERTION • INVALID_REMOVAL The time value is the time when the Attention Button was pressed. This error can occur if INSERTION or REMOVAL is received and the slot is not in the right state.
OL* Action Behavior Issue If an online replace or an online delete operation is performed on the PCI-E x8 switched slots, the slot becomes unusable under the following conditions: • • • Operating System: HP-UX 11i v3 HP Integrity servers: rx3600 or rx6600 with express I/O backplane Firmware Version: 2.03 During online replace operation through olrad command, pdweb tool, or Attention button, the card in the PCI-E x8 switched slot (slot 3 or slot 4) becomes unusable.
A OL* Actions, Events, and Scripts Reference This appendix provides reference information about OL* actions, events and scripts. This chapter addresses the following topics: • Attention Button Actions • Attention Button Events • PCI OL* Events • OL* Driver Scripts Attention Button Actions When you press the Attention Button, the system generates a POWER_OFF event in the following cases: • The slot is occupied, no drivers are attached, and the Attention Button event is a NORMAL_REMOVAL event.
OL* Driver Scripts During OL* procedures, olrad can initiate scripts that notify the system of the addition or replacement of an interface card. Because pdweb invokes olrad, these scripts are also run by pdweb. The script name must be the same as the driver name. Scripts are delivered with card drivers and are located in the /usr/sbin/olrad.d/ directory. These scripts do any preparatory work required before an OL* operation. If the driver requires no preparatory action, then no script is executed.
Glossary affected card Interface cards that are in the same power domain as the target slot. See also OL* . affected slots The set of PCI slots, other than the target slot, that have their PCI bus disrupted as a result of a hot-plug operation. This disruption includes anything that would interfere with bus traffic, including events like a bus reset or a loss of bus power. The operating system must quiesce I/O on the affected slots and the target slot before proceeding with the hot plug operation.
Index see also - CRA olrad, 66 pdweb, 42 A accessing pdweb SAM, 25 SCM, 25 SIM, 28 SMH, 25, 28 accessing SMH Command, 27 Web browser, 27 add card attention button, 60 flowchart, 72 olrad example, 66 pdweb, 43, 56 advanced topics, 83 affected card, 20 Apache Web Server Log File, 77 attention button add card, 60 delete card, 62 method, 19 overview, 59 possible results, 62 press more than one, 62 pressed before daemon startup, 62 replace card, 61 attention button actions, 83 attention button events, 83 attent
HP Apache, 77 NetTL, 78 SAM, 77 logging olrad, 70, 79 M messages, 77 mixing OL* methods, 76 MRL meaning, 20 multi-port cards, 22 multiple-function card, 20 N NetTL Log File, 78 O OL*, 20 olrad add card example, 66 attention led, 69 delete card example, 67 method, 19 options, 69 replace card example, 67 syntax, 65 olrad cards tab pdweb, 33 olrad errors, 78 OLX Divider, 20 On-Line Addition, 21 On-Line Deletion, 21 On-Line Replacement, 21 failure, 18 online add pdweb, 43, 56 online delete pdweb, 52 online r
