Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
Interface Card OL* Support Guide: HP-UX 11i v2 > Chapter 4 olrad - Command Line Interface

Using olrad

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

Argument Description and Syntax

The following arguments are used in the command.

slot_id

SLOT ID of an OLA/R capable slot. A slot ID is a list of one or more numbers separated by dashes. Each number represents a component of the physical location of the slot. The user can use the slot ID to locate the slot. The sequence of numbers in the slot ID is platform dependent. On N and L classes, the slot ID contains only the slot number. On all other platforms, including Superdome, the format of the slot ID is: Cabinet#-Bay#-Chassis#-Slot#

hw_path

Hardware path of an OLA/R capable slot.

Preliminary Actions

The following actions should be done prior to adding or replacing a card to provide valuable information about the slots and potential affects of disabling one.

Slot Status

The olrad -q command provides details and the status of all OL* capable slots in the system. In the output, slots with the same bus number are treated as shared slots.

Example 4-1 Example of the olrad -q command output

# olrad -q
Driver(s)
Capable
Slot Path Bus Max Spd Pwr Occu Susp OLAR OLD Max Mode
Num Spd Mode
0-0-3-1 4/0/1/0 21 66 N/A On Yes No Yes N/A PCI N/A
0-0-3-2 4/0/2/0 42 66 N/A On Yes No Yes N/A PCI N/A
0-0-3-3 4/0/3/0 63 66 N/A On Yes No Yes N/A PCI N/A
0-0-3-4 4/0/4/0 84 66 N/A On Yes No Yes N/A PCI N/A
0-0-3-5 4/0/6/0 105 66 N/A On Yes No Yes N/A PCI N/A
0-0-3-6 4/0/14/0 234 66 N/A On Yes No Yes N/A PCI N/A

Critical Resource Analysis

Users are advised to use this option first to check out whether the intended OL* operation is safe and would not cause disruption of the functioning of the system. Perform a CRA against the slot of interest.

Runs critical resource analysis routine on the specified slot_id and display the results. It checks for critical resources on all affected hardware paths associated with the specified slot. It analyzes file systems, volumes, processes, networking, swap, and dump; and generates a report of affected resources.

The CRA severity levels and their meanings. 

CRA_SUCCESS

no affected resources in use.

CRA_WARNINGS

resources in use on affected device(s) but none are deemed critical.

CRA_DATA_CRITICAL

probable data loss, only proceed with the user's permission.

CRA_SYS_CRITICAL

likely to bring down the user's system.

CRA_ERROR

some internal CRA error encountered.

The syntax for this option is olrad -C slot_id.

Example 4-2 CRA Reporting Success.

# olrad -C 0-0-3-2
-------------------------------------------------------------------------------
CRITICAL RESOURCE ANALYSIS REPORT for Slot: 0-0-3-2
-------------------------------------------------------------------------------
Overall Result: SUCCESS
Reason: no affected devices

Date: Thu May 29 11:35:39 2003

Hardware Paths Analyzed:
None

Example 4-3 CRA Reporting a Data Critical Message

# olrad -C 0-0-3-0
-------------------------------------------------------------------------------
CRITICAL RESOURCE ANALYSIS REPORT for Slot: 0-0-3-0
-------------------------------------------------------------------------------
Overall Result: DATA CRITICAL resources will be affected
Reason: resources associated with possible data loss
Date: Thu May 29 11:30:26 2003

Hardware Paths Analyzed:
4/0/0/0/0 - PCI Serial (103c1048)
4/0/0/1/0 - HP PCI 10/100Base-TX Core

SYSTEM CRITICAL RESULTS -------------------------------------------------------

FILE SYSTEM ANALYSIS
Result: no system critical file systems will be affected

SWAP ANALYSIS
Result: no swap will be affected

DATA CRITICAL RESULTS ---------------------------------------------------------

FILE SYSTEM ANALYSIS
Result: no data critical file systems will be affected

NETWORKING ANALYSIS
Result: network ports will be affected
Affected Network Ports:
4/0/0/1/0 IP Address: 15.1.51.57

PROCESS ANALYSIS
Result: no processes will be affected

OTHER RESULTS -----------------------------------------------------------------

VOLUME ANALYSIS
Result: no volumes will be affected

DUMP ANALYSIS
Result: no dump will be affected

FILE SYSTEM ANALYSIS
Result: no CDFS file systems will be affected

NETWORKING ANALYSIS
Result: no other network ports will be affected

-------------------------------------------------------------------------------
End of CRITICAL RESOURCE ANALYSIS REPORT

Adding a New Card

  1. Get the information about all the OLA/R capable slots. Make note of the slot_id field:

    /usr/bin/olrad -q

  2. Prepare to add:

    /usr/bin/olrad -a slot_ID

    A CRA is performed as part of this action.

  3. Manually unlock the latch (if present).[1]
    Physically insert the card into the slot.

  4. Post add:

    /usr/bin/olrad -A slot_ID

  5. Verify the success of the operation, slot power should be ON, driver is OLAR capable, and so on.

    /usr/bin/olrad -q slot_ID

Replacing a Card

  1. Get information about all the OLA/R capable slots. Make note of the slot_id field:

    /usr/bin/olrad -q

  2. Prepare to replace:

    /usr/bin/olrad -r slot_ID

    A CRA is performed as part of this action.

  3. Manually unlock the latch (if present). [1]
    Replace the existing card in the slot with another card.
    Press latch to the locked position (if present).[1]
    The new card must use the same drivers as the replaced card.

  4. Post Replace:

    /usr/bin/olrad -R slot_ID

  5. Verify the success of the operation, slot power should be ON, driver is OLAR capable, and so on.

    /usr/bin/olrad -q slot_ID

Turning the Attention LED to BLINK or OFF

To turn the Attention LED to BLINK

/usr/bin/olrad -I ATTN slot_ID

To turn the Attention LED to OFF

/usr/bin/olrad -I OFF slot_ID



[1] Refer to the Host Bus Adapter (HBA) documentation for details on card installation.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2004 Hewlett-Packard Development Company, L.P.