Service Manual hp StorageWorks Director 2/140 Product Version: FW v06.xx/HAFM SW v08.02.00 Third Edition (July 2004) Part Number: AA–RTDTC–TE This guide provides procedures for servicing the HP StorageWorks Director 2/140.
© Copyright 2002–2004 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Contents Contents About this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 2 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 Maintenance Analysis Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Factory Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Clean Fiber Optic Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power-On Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power-Off Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IML, IPL, or Reset the Director . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Tools Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing the UPM Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing the UPM Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RRP: SFP Optical Transceiver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tools Required . . . . . . . . . . . . . . .
Contents Miscellaneous Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 A Information and Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 HAFM Application Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Element Manager Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 8 LCD panel (LAN 2 IP address) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discover Setup dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing Domain Information dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 New Firmware Description dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modify Firmware Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send Firmware dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send Firmware Complete dialog box. . . . . . . . . . . . . . . . . . . . . . .
Contents 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 10 MAP 0500: Event Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP 0600: Event Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP 0600: Port Operational and LED States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP 0600: Invalid Attachment Reasons and Actions . . . . . . . . . . . . . . . . . . . .
About this Guide About this Guide This guide describes the service procedures for the HP StorageWorks Director 2/140.
About this Guide Overview This section covers the following topics: ■ Intended Audience ■ Related Documentation Intended Audience This publication is intended for service personnel, and any individuals who monitor, configure, and repair the Director 2/140. Related Documentation For a list of corresponding documentation included with this product, see the Related Documents section of the HP StorageWorks Director Release Notes.
About this Guide Conventions Conventions consist of the following: ■ Document Conventions ■ Text Symbols ■ Equipment Symbols Document Conventions This document follows the conventions in Table 1.
About this Guide Caution: Text set off in this manner indicates that failure to follow directions could result in damage to equipment or data. Tip: Text in a tip provides additional help to readers by providing nonessential or optional techniques, procedures, or shortcuts. Note: Text set off in this manner presents commentary, sidelights, or interesting points of information. Equipment Symbols The following equipment symbols may be found on hardware for which this guide pertains.
About this Guide Any surface or area of the equipment marked with these symbols indicates the presence of a hot surface or hot component. Contact with this surface could result in injury. WARNING: To reduce the risk of personal injury from a hot component, allow the surface to cool before touching. Power supplies or systems marked with these symbols indicate the presence of multiple sources of power.
About this Guide Rack Stability Rack stability protects personnel and equipment. WARNING: To reduce the risk of personal injury or damage to the equipment, be sure that: ■ The leveling jacks are extended to the floor. ■ The full weight of the rack rests on the leveling jacks. ■ In single rack installations, the stabilizing feet are attached to the rack. ■ In multiple rack installations, the racks are coupled. ■ Only one rack component is extended at any time.
About this Guide Getting Help If you still have a question after reading this guide, contact an HP authorized service provider or access our web site: http://www.hp.com. HP Technical Support Telephone numbers for worldwide technical support are listed on the following HP web site: http://www.hp.com/support/. From this web site, select the country of origin. Note: For continuous quality improvement, calls may be recorded or monitored.
About this Guide 18 Director 2/140 Service Manual
General Information 1 The HP StorageWorks Director 2/140 provides dynamic switched connections between Fibre Channel servers and devices in a storage area network (SAN) environment. SANs introduce the concept of server-to-device networking and multi-switch fabrics, eliminate requirements for dedicated connections, and enable the enterprise to become data-centric. A SAN provides speed, high capacity, and flexibility for the enterprise, and is primarily based upon Fibre Channel architecture.
General Information Director Description The Director 2/140 is a second-generation, 140-port product that provides dynamic switched connections between Fibre Channel servers and devices in a SAN environment. Directors (from one to three) can be configured to order in an HP-supplied equipment rack, which can provide up to 420 ports in a single cabinet. Directors are managed and controlled through an HAFM appliance supplied by HP with HAFM and Director 2/140 Element Manager installed.
General Information Maintenance Approach Whenever possible, the director maintenance approach instructs service personnel to perform fault isolation and repair procedures without degrading or interrupting operation of the director, attached devices, or associated applications.
General Information Front View Figure 1 displays FRUs accessible from the front of the director. 4 1 2 3 1 2 Power and system error LEDs Up to 32 universal port module (UPM) cards 3 4 Redundant control processor (CTP) cards Power module assembly Figure 1: Director FRUs (front access) Rear View Figure 2 displays FRUs accessible from the rear of the director.
General Information 1 2 3 4 5 6 1 2 3 Redundant fan modules 4 Up to 3 universal port module (UPM) cards 5 Maintenance port 6 Redundant serial crossbar (SBAR) assemblies AC module Power supplies Figure 2: Director FRUs (rear access) Director 2/140 Service Manual 23
General Information Software Diagnostic Features The director provides the following diagnostic software features that aid in fault isolation and repair of problems: ■ On-board diagnostic and monitoring circuits that continuously report FRU status to HAFM and the Element Manager. These applications provide system alerts and logs that display failure and diagnostic information at the HAFM appliance or a remote workstation communicating with the HAFM appliance.
General Information Double-click a director icon to open the Element Manager. The Element Manager provides a Java-based GUI to manage, monitor, and isolate problems for a specific director. The application operates locally on the HAFM appliance, or through an Ethernet LAN connection from a remote user workstation. When the Element Manager opens, the default display is the Hardware View. A Director 2/140 Status table and a graphical representation of the director hardware (front and rear) display.
General Information Event Table The event table displays the last ten events that occurred since the HAFM application was started. Events that occurred during a prior instance of the application do not display. If a new event occurs while ten events display, the oldest event is discarded. A deeper event history is maintained in the form of a log file viewed through the HAFM application.
General Information Table 2: HAFM Services Status Symbols Alert Symbol Meaning Blank The status indicator is blank during HAFM application initialization. Green circle All events are viewed (acknowledged with appropriate action taken). Yellow triangle One or more nonfatal events have not been viewed. Red diamond (with yellow background) A fatal error occurred.
General Information — Fibre Channel ports and port performance statistics. — The active zone set. — Event log entries, and clear the system error LED at the director front bezel. — Information about attached devices (nodes). ■ Operations panel—Perform the following operations and maintenance tasks: — Enable port beaconing and perform port diagnostics (internal and external loopback tests). — Reset Fibre Channel ports. — Set the director online state. — Upgrade director firmware.
General Information ■ coldStart—Reports that the SNMP agent is reinitializing due to a director reset. ■ warmStart—Reports that the SNMP agent is reinitializing due to a director IPL. ■ authorizationFailure—Reports attempted director access by an unauthorized SNMP manager. This trap is configurable and is disabled by default. Director-specific SNMP traps specified in the custom MIB include Fibre Channel port operational state changes and FRU operational state changes.
General Information ■ Torque tool with hexagonal adapter—The torque tool with 5/32” hexagonal adapter (Figure 4) is required to remove and replace director logic cards. Caution: The torque tool supplied with the director is designed to tighten director logic cards and is set to release at a torque value of six inch-pounds. Do not use an Allen wrench or torque tool designed for use with another HP product. Use of the wrong tool may overtighten and damage logic cards.
General Information Figure 6: Fiber optic protective plug ■ Null modem cable—An asynchronous RS-232 null modem cable (Figure 7) is required to configure director network addresses and acquire Event Log information through the maintenance port. The cable has nine conductors and has DB-9 male and female connectors. Figure 7: Null modem cable Tools Supplied by Service Personnel The following tools are expected to be supplied by service personnel performing director maintenance actions.
General Information ■ T10 Torts® tool—The tool is required to rack-mount the director or to remove, replace, adjust, or tighten various chassis or cabinet components. ■ Electrostatic discharge (ESD) grounding cable with attached wrist strap—Use of the ESD wrist strap is required when working in and around the director card cage. ■ Maintenance terminal (desktop or notebook PC)—The PC is required to configure director network addresses and acquire Event Log information through the maintenance port.
Diagnostics 2 This chapter describes diagnostic procedures used by service representatives to fault isolate the Director 2/140 problems or failures to the field-replaceable unit (FRU) level. The chapter describes how to perform the maintenance analysis procedures (MAPs).
Diagnostics Maintenance Analysis Procedures Note: HAFM and Element Manager screens in this manual may not match the screens on your server and workstation. The title bars have been removed, and the fields may contain data that does not match the data seen on your system. Fault isolation and related service procedures are provided through MAPs. The procedures vary depending on the diagnostic information provided.
Diagnostics MAP Page MAP 0300: HAFM Appliance Software Problem Determination 83 MAP 0400: Loss of HAFM Appliance or Web Browser PC Communication 92 MAP 0500: FRU Failure Analysis 107 MAP 0600: UPM Card Failure and Link Incident Analysis 115 MAP 0700: Fabric, ISL, and Segmented Port Problem Determination 138 MAP 0800: HAFM Appliance or Web Browser PC Hardware Problem Determination 153 Table 5 lists the event codes and the corresponding MAPs.
Diagnostics Table 5: Event Codes and Corresponding Maintenance Action (Continued) Event Code 36 Explanation Action 051 HAFM appliance database invalid. Go to MAP 0700: Fabric, ISL, and Segmented Port Problem Determination. 052 HAFM appliance internal error. Go to MAP 0700: Fabric, ISL, and Segmented Port Problem Determination. 060 Fabric controller unable to synchronize databases. Go to MAP 0700: Fabric, ISL, and Segmented Port Problem Determination. 061 Fabric controller database invalid.
Diagnostics Table 5: Event Codes and Corresponding Maintenance Action (Continued) Event Code Explanation Action 074 ILS frame delivery error threshold exceeded. Event data intended for engineering evaluation. Perform data collection procedure (“Collecting Maintenance Data” on page 192) and return CD to HP support personnel. 080 Unauthorized World-Wide Name. Go to MAP 0600: UPM Card Failure and Link Incident Analysis. 081 Invalid attachment.
Diagnostics Table 5: Event Codes and Corresponding Maintenance Action (Continued) Event Code 38 Explanation Action 142 Low BB_Credit detected on an ISL. Go to MAP 0700: Fabric, ISL, and Segmented Port Problem Determination. 143 Low BB_Credit relieved on an ISL. No action required. 150 Zone merge failure. Go to MAP 0700: Fabric, ISL, and Segmented Port Problem Determination. 151 Fabric configuration failure.
Diagnostics Table 5: Event Codes and Corresponding Maintenance Action (Continued) Event Code Explanation Action 303 Cooling fan propeller failed. Go to MAP 0500: FRU Failure Analysis. 304 Cooling fan propeller failed. Go to MAP 0500: FRU Failure Analysis. 305 Cooling fan propeller failed. Go to MAP 0500: FRU Failure Analysis. 310 Cooling fan propeller recovered. No action required. 311 Cooling fan propeller recovered. No action required. 312 Cooling fan propeller recovered.
Diagnostics Table 5: Event Codes and Corresponding Maintenance Action (Continued) Event Code 40 Explanation Action 415 Backup CTP card removed. Replace FRU. 416 Backup CTP card installed. No action required. 417 CTP card firmware synchronization initiated. No action required. 418 User-initiated CTP card switchover. No action required. 420 Backup CTP card NV-RAM failure. Go to MAP 0500: FRU Failure Analysis. 421 Firmware download complete. No action required.
Diagnostics Table 5: Event Codes and Corresponding Maintenance Action (Continued) Event Code Explanation Action 450 Serial Number mismatch detected. No action required—Any configured Feature Keys will be cleared, configuration information will be synched with the backplane VPD, and the CTP will automatically be IPLed. 451 Switch speed incompatibility detected.
Diagnostics Table 5: Event Codes and Corresponding Maintenance Action (Continued) Event Code 42 Explanation Action 500 UPM card hot-insertion initiated. No action required. 501 UPM card recognized. No action required. 502 UPM card anomaly detected. No action required. 503 UPM card hot-removal completed. No action required. 504 UPM card failure. Go to MAP 0600: UPM Card Failure and Link Incident Analysis. 505 UPM card revision not supported.
Diagnostics Table 5: Event Codes and Corresponding Maintenance Action (Continued) Event Code Explanation Action 582 Bit error threshold exceeded. Go to MAP 0600: UPM Card Failure and Link Incident Analysis. 583 Loss of signal or loss of synchronization. Go to MAP 0600: UPM Card Failure and Link Incident Analysis. 584 Not operational primitive sequence received. Go to MAP 0600: UPM Card Failure and Link Incident Analysis. 585 Primitive sequence timeout.
Diagnostics Table 5: Event Codes and Corresponding Maintenance Action (Continued) Event Code 44 Explanation Action 801 Critically hot temperature warning (UPM card thermal sensor). Go to MAP 0600: UPM Card Failure and Link Incident Analysis. 802 UPM card shutdown due to thermal violation. Go to MAP 0600: UPM Card Failure and Link Incident Analysis. 805 High temperature warning (SBAR assembly thermal sensor). Go to MAP 0500: FRU Failure Analysis.
Diagnostics MAP 0000: Start MAP This MAP describes initial fault isolation for the Director 2/140. Fault isolation begins at the HAFM appliance, failed director, or Internet-connected personal computer (PC) running the Embedded Web Server interface or attached host. 1 Prior to fault isolation, acquire the following information from the customer: ■ A system configuration drawing or planning worksheet that includes the HAFM appliance, directors, other HP products, and device connections.
Diagnostics ■ Display a Dr. Watson for Windows 2000 dialog box? NO YES ↓ An HAFM appliance application problem is indicated. Event codes are not recorded. Go to “MAP 0300: HAFM Appliance Software Problem Determination” on page 83. Exit MAP. 4 Did the HAFM appliance crash and display a blue screen with the system dump file in hexadecimal format (blue screen of death)? NO YES ↓ An HAFM appliance application problem is indicated. Event codes are not recorded.
Diagnostics Boot from LAN? Press Figure 8: LCD panel during boot sequence d. Ignore the message. After ten seconds, the appliance performs the boot sequence from the basic input/output system (BIOS). During the boot sequence, the appliance performs additional POST tests and displays the following operational information at the LCD panel: — Host name. — System date and time. — LAN 1 and LAN 2 IP addresses. — Fan 1, fan 2, fan 3, and fan 4 rotational speed.
Diagnostics 6. Enter the HAFM appliance IP address in the Network Address field. If you are logging in to the local HAFM appliance, the network address is localhost. The default address that displays in the Network Address field is the address of the last appliance accessed. Click the Network Address drop down list to see the network addresses of all HAFM appliances that were accessed from the computer you are logged in to.
Diagnostics Did the View All - HAFM 8 window display and is the HAFM application operational? YES NO ↓ An HAFM appliance hardware problem is indicated. Event codes are not recorded. Go to “MAP 0800: HAFM Appliance or Web Browser PC Hardware Problem Determination” on page 153. Exit MAP. 7 Inspect the alert indicators of each managed director at the main window physical map or product list.
Diagnostics ■ An illuminated green LED on the active CTP card, and illuminated green PWR OK LEDs on both power supplies. ■ Audio emanations and airflow from cooling fans. Is the director powered on? YES NO ↓ A power distribution problem is indicated. Go to step 23 to obtain event codes. If no event codes are found, go to “MAP 0100: Power Distribution Analysis” on page 69. Exit MAP. 9 At the director, inspect the amber LED at the top of each CTP card.
Diagnostics Do blinking red and yellow diamonds overlay all UPM card graphics? NO YES ↓ Failure of all installed UPM cards is indicated. Go to step 23 to obtain event codes. If no event codes are found, go to “MAP 0600: UPM Card Failure and Link Incident Analysis” on page 115. Exit MAP. 13 Blinking red and yellow diamonds overlay both serial crossbar (SBAR) assembly graphics or both fan module graphics. Redundant FRU failures are indicated. Go to step 23 to obtain event codes.
Diagnostics 16 Does a blinking red and yellow diamond overlay a UPM card graphic? NO YES ↓ A UPM card failure is indicated. Go to step 23 to obtain event codes. If no event codes are found, go to “MAP 0600: UPM Card Failure and Link Incident Analysis” on page 115. Exit MAP. 17 A blinking red and yellow diamond overlays a control processor (CTP) card, SBAR assembly, or fan module graphic. A FRU failure is indicated. Go to step 23 to obtain event codes.
Diagnostics 2. Disable FRU beaconing. a. At the Hardware View, right-click the FRU graphic. A menu displays. b. Click Enable Beaconing. The check mark disappears from the box adjacent to the option, and FRU beaconing is disabled. Was FRU beaconing enabled because a FRU failure or degradation was suspected? YES NO ↓ The director is operational. Exit MAP. Go to step 22. 20 Does a yellow triangle (attention indicator) overlay a UPM card graphic? YES NO ↓ Go to step 22.
Diagnostics Figure 11: Port Properties dialog box 3. Inspect the Operational State field. Does the Operational State field display a Segmented E_Port message? NO YES ↓ Expansion port (E_Port) segmentation is indicated. Go to step 23 to obtain event codes. If no event codes are found, go to “MAP 0700: Fabric, ISL, and Segmented Port Problem Determination” on page 138. Exit MAP. A message displays indicating a link incident problem. Go to step 23 to obtain event codes.
Diagnostics If a link incident occurred, the affected port number is listed with one of the following messages. Link interface incident-implicit incident. Link interface incident-bit-error threshold exceeded. Link failure-loss of signal or loss of synchronization. Link failure-not-operational primitive sequence (NOS) received. Link failure-primitive sequence timeout. Link failure-invalid primitive sequence received for the current link state.
Diagnostics Figure 13: Event Log Were one or more event codes found? NO YES ↓ Go to Table 5 on page 35. Return to the MAP step that sent you here. 24 Are you at the director reporting the problem? YES NO ↓ Go to step 36. 25 Is the power LED (green) at the director front bezel illuminated? NO YES ↓ Go to step 30. 26 Is the director connected to facility AC power and powered on? NO YES ↓ Go to step 29.
Diagnostics ■ At the front bezel, an illuminated power LED (green) or system error LED (amber). ■ An illuminated green LED on the active CTP card, and illuminated green PWR OK LEDs on both power supplies. ■ Audio emanations and airflow from cooling fans. Is the director powered on? YES NO ↓ A power distribution problem is indicated. Go to step 23 to obtain event codes. If no event codes are found, go to “MAP 0100: Power Distribution Analysis” on page 69. Exit MAP.
Diagnostics A faulty power LED is indicated, but director and Fibre Channel port operation is not disrupted. The LED is connected to the circuitry in a fan module, and the module must be removed and replaced (“RRP: Redundant Fan Module” on page 250). Exit MAP. 30 Is the system error LED (amber) at the director front bezel blinking? YES NO ↓ Go to step 32. 31 Unit beaconing is enabled for the director. 1. Consult the customer and next level of support to determine the reason unit beaconing is enabled.
Diagnostics Is the amber LED at the top of a UPM card illuminated or are any amber LEDs associated with Fibre Channel ports illuminated? NO YES ↓ A UPM card or Fibre Channel port failure is indicated. Go to step 23 to obtain event codes. If no event codes are found, go to “MAP 0600: UPM Card Failure and Link Incident Analysis” on page 115. Exit MAP. 34 Is the amber LED on a CTP card, SBAR assembly, or fan module illuminated? NO YES ↓ A FRU failure is indicated. Go to step 23 to obtain event codes.
Diagnostics 38 Boot the Web browser PC. 1. Power on the PC in accordance with the instructions delivered with the PC. The Windows desktop displays. 2. Launch the PC browser application by double-clicking the appropriate icon at the Windows desktop. 3. At the Netsite field (Netscape Navigator) or Address field (Internet Explorer), type http://xxx.xxx.xxx.xxx, where xxx.xxx.xxx.xxx is the IP address of the director (obtained in step 1 on page 45). The Username And Password Required dialog box displays. 4.
Diagnostics 39 Is the Embedded Web Server interface operational with the View panel displayed? NO YES ↓ Go to step 44. 40 A Page cannot be found, Unable to locate the server, HTTP 404-file not found, or other similar message displays. The message indicates the Web browser PC cannot communicate with the director because: ■ The director-to-PC Internet link could not be established. ■ AC power distribution in the director failed, or AC power was disconnected.
Diagnostics 42 At the director, inspect the amber LED at the top of each CTP card. Is the amber LED illuminated on both CTP cards? NO YES ↓ Failure of both CTP cards is indicated. Event codes are not recorded. Go to “MAP 0500: FRU Failure Analysis” on page 107. Exit MAP. 43 A director-to-PC Internet link problem (Internet too busy or IP address typed incorrectly) is indicated. 1. Wait approximately five minutes, then attempt to log in to the director again. 2.
Diagnostics Figure 15: View Port Properties panel Does the Beaconing field display an On message? YES NO ↓ Go to step 47. 46 Port beaconing is enabled. 1. Consult the customer and next level of support to determine the reason port beaconing is enabled. 2. Disable port beaconing: a. At the View panel, choose the Operations option at the left side of the panel. The Operations panel opens with the Port Beaconing page displayed. b. Click the Beaconing State check box for the port.
Diagnostics c. Return to the View panel (Port Properties tab). Continue to the next step. 47 At the View panel, does the Operational State field display a Segmented message? NO YES ↓ Port segmentation is indicated. Go to step 52 to obtain event codes. If no event codes are found, go to “MAP 0700: Fabric, ISL, and Segmented Port Problem Determination” on page 138. Exit MAP.
Diagnostics Figure 16: View FRU Properties panel 2. Inspect the Status fields for both power supplies. Does the Status field display a Failed message for either power supply? NO YES ↓ A power supply failure is indicated. Go to step 52 to obtain event codes. If no event codes are found, go to “MAP 0100: Power Distribution Analysis” on page 69. Exit MAP. 51 Inspect the Status fields for director FRUs, including CTP cards, SBAR assemblies, fan modules, and the backplane.
Diagnostics 52 Obtain event codes from the Embedded Web Server Event Log. Note: If multiple event codes are found, note all codes and associated severity levels. Record the date, time, and listed sequence, and determine if the codes are related to the reported problem. Begin fault isolation with the most recent event code with the highest severity level. Other codes may accompany this event code, or may indicate a normal indication after a problem is recovered. 1.
Diagnostics Figure 17: Monitor Log panel Were one or more event codes found? NO YES ↓ Go to Table 5 on page 35. Return to the MAP step that sent you here. 53 You are at the console of an OSI or FICON server attached to the director reporting the problem. If an incident occurs on the Fibre Channel link between the director and server, a link incident record is generated and sent to the server using the reporting procedure defined in T11/99-017v0 (OSI) or the FICON architecture document (FICON).
Diagnostics Was a link incident record generated and sent to the director-attached OSI or FICON server? YES NO ↓ Perform director fault isolation at the HAFM appliance (or customer-supplied server). Go to step 3. 54 The link incident record provides the attached director port number(s) and one or more of the following event codes and messages. Record all event codes that may relate to the reported problem. 581—Link interface incident—implicit incident.
Diagnostics MAP 0100: Power Distribution Analysis This MAP describes fault isolation for the director power distribution system, including defective AC power cords, redundant power supplies, or the power module assembly. 1 Was an event code 200, 201, 202, or 208 observed at the Director 2/140 Event Log (HAFM appliance) or at the Embedded Web Server Event Log? YES NO ↓ Go to step 10.
Diagnostics Was a corrective action performed? YES NO ↓ Go to step 5. 4 Verify redundant power supply operation. 1. Inspect the power supply and ensure the green PWR OK LED illuminates and all amber LEDs extinguish. 2. At the Hardware View, observe the graphic representing the power supply and ensure a failure symbol (blinking red and yellow diamond) does not display. Is a failure indicated? YES NO ↓ The director is operational. Exit MAP.
Diagnostics 7 A redundant power supply failed and must be removed and replaced (“RRP: Redundant Power Supply” on page 241). ■ This procedure is concurrent and can be performed while director power is on. ■ Perform the data collection procedure as part of FRU removal and replacement. Note: Do not remove a power supply unless a replacement is immediately available. To avoid director overheating, a power supply must be replaced within five minutes.
Diagnostics 9 Verify director operation: 1. Inspect the director front bezel and ensure the green power LED illuminates. Inspect the active CTP card and ensure the green LED illuminates. 2. Inspect both power supplies. Ensure both green PWR OK LEDs illuminate and all amber LEDs extinguish. 3. At the Hardware View, observe all graphics representing FRUs and power supplies, and ensure emulated green LEDs illuminate. Is a failure indicated? YES NO ↓ The director is operational. Exit MAP.
Diagnostics 12 Inspect the director for indications of being powered on, such as: ■ At the front bezel, an illuminated power LED (green) or system error LED (amber). ■ An illuminated green LED on the active CTP card. ■ At least one green PWR OK LED illuminated on a power supply. ■ Audio emanations and airflow from cooling fans. Is the director powered on? YES NO ↓ Go to step 14.
Diagnostics 15 Ensure both power supplies are correctly installed and seated in the director. If required, partially remove and reseat the power supplies. Was a corrective action performed? YES NO ↓ Go to step 17. 16 Verify operation of both power supplies. 1. Inspect the power supplies and ensure the green PWR OK LEDs illuminate and all amber LEDs extinguish. 2.
Diagnostics Did power module assembly replacement solve the problem? NO YES ↓ The director is operational. Exit MAP. A power module assembly failure is not confirmed. Replace the original power module assembly to avoid the cost of expending a replacement FRU. Continue to the next step. 19 One or both power supplies are operational, but logic cards are not receiving DC power. In-card circuit breakers for all logic cards may have tripped due to a power surge, or the backplane failed.
Diagnostics 22 At the Hardware View, does a yellow triangle display at the alert panel and a blinking red and yellow diamond (failed FRU indicator) display over a power supply graphic? NO YES ↓ A redundant power supply failed. Go to step 7. 23 At the Hardware View, does a grey square display at the alert panel, a No Link status displays at the director Status table, and graphical FRUs are uninstalled? YES NO ↓ A green circle displays at the alert panel and the director is operational. Exit MAP.
Diagnostics Analysis for an Ethernet link or dual CTP card failure is not described in this MAP. Go to “MAP 0000: Start MAP” on page 45. If this is the second time at this step, contact the next level of support. Exit MAP. 25 Is the Embedded Web Server interface operational? NO YES ↓ Go to step 28. 26 A Page cannot be found, Unable to locate the server, HTTP 404-file not found, or other similar message displays.
Diagnostics 28 Inspect power supply operational states at the Embedded Web Server interface. 1. At the View panel, click the FRU Properties tab. The View panel (FRU Properties tab) displays. 2. Inspect the Status fields for both power supplies. Does the Status field display a Failed message for either power supply? NO YES ↓ A redundant power supply failed. Go to step 7. The director is operational. Exit MAP.
Diagnostics 2 Was an event code 400, or 411, or 413 observed at the director Event Log (HAFM appliance) or at the Embedded Web Server Event Log? YES NO ↓ Analysis for the failure is not described in this MAP. Go to “MAP 0000: Start MAP” on page 45. Exit MAP. 3 Table 7 lists event codes, brief explanations of the codes, and the associated steps that describe fault isolation procedures. Table 7: MAP 0200: Event Codes Event Code Explanation Action 400 Power-up diagnostic failure.
Diagnostics Table 8: Byte 0 FRU Codes Byte 0 Failed FRU Action 01 Backplane. Go to step 5 02 CTP card. Go to step 6 03 SBAR assembly. Go to step 7 05 Fan module. Go to step 8 06 Power supply. Go to step 9 UPM card. Go to step 10 08-0F 5 The backplane failed POSTs (indicated by a 01 FRU code) and must be removed and replaced (“RRP: Backplane” on page 256). ■ This procedure is non-concurrent and must be performed while director power is off.
Diagnostics Did CTP card replacement solve the problem? NO YES ↓ The director is operational. Exit MAP. Contact the next level of support. Exit MAP. 7 An SBAR assembly failed POSTs (indicated by a 03 FRU code) and must be removed and replaced (“RRP: Redundant SBAR Assembly” on page 247). ■ This procedure is concurrent and can be performed while director power is on. ■ Perform the data collection procedure as part of FRU removal and replacement.
Diagnostics 9 A power supply failed POSTs (indicated by a 06 FRU code) and must be removed and replaced (“RRP: Redundant Power Supply” on page 241). ■ This procedure is concurrent and can be performed while director power is on. ■ Perform the data collection procedure as part of FRU removal and replacement. Note: Do not remove a power supply unless a replacement is immediately available. To avoid director overheating, a power supply must be replaced within five minutes.
Diagnostics 12 The backup CTP card failed POST/IPL diagnostics (as indicated by an event code 413) and must be removed and replaced (“RRP: Redundant CTP Card” on page 226). ■ This procedure is concurrent and can be performed while director power is on. ■ Perform the data collection procedure as part of FRU removal and replacement. Note: Do not remove and replace a redundant CTP card if the backup CTP card is not fully operational and director power is on.
Diagnostics 2 An application or operating system problem is indicated. Close the HAFM application (at the browser-capable PC connected through an Ethernet LAN segment to the HAFM appliance). 1. At the HAFM appliance Windows 2000 desktop, click the Send Ctrl-Alt-Del button at the top of the window. The Windows Security dialog box displays, as shown in Figure 18. Note: Do not simultaneously press Ctrl, Alt, and Delete. This action controls the browser-capable PC, not the rack-mount management appliance.
Diagnostics Figure 19: Task Manager dialog box, Applications tab 3. Choose the View All - HAFM 8 entry and click End Task. The HAFM application closes. 4. Close the Task Manager dialog box. Continue to the next step. 3 Attempt to clear the problem by rebooting the HAFM appliance. 1. Choose Start > Shut Down. The Shut Down Windows dialog box displays. 2. At the Shut Down Windows dialog box, choose Shut Down The Computer and click Yes to power off the appliance. 3.
Diagnostics d. Ignore the message. After ten seconds, the appliance performs the boot sequence from the basic input/output system (BIOS). During the boot sequence, the appliance performs additional POST tests and displays the following operational information at the LCD panel: — Host name. — System date and time. — LAN 1 and LAN 2 IP addresses. — Fan 1, fan 2, fan 3, and fan 4 rotational speed. — Central processing unit (CPU) temperature. — Hard disk capacity. — Virtual and physical memory capacity. 4.
Diagnostics Did the View All - HAFM 8 window display and is the HAFM application operational? NO YES ↓ The problem is transient and the HAFM appliance is operational. Contact the next level of support. Exit MAP. 4 Did the HAFM application display a dialog box with the message Connection to HAFM appliance lost-click OK to exit application or HAFM application error n (where n is an error message number 1 through 8 inclusive)? NO YES ↓ An HAFM application error occurred.
Diagnostics 7 Upgrade the downlevel HAFM application (“Install or Upgrade Software” on page 218). Did the software upgrade solve the problem? NO YES ↓ The HAFM appliance is operational. Exit MAP. Contact the next level of support. Exit MAP. 8 Did the Element Manager display a dialog box with the message Element Manager error 5001 or Element Manager error 5002? NO YES ↓ An Element Manager error occurred. Click OK to close the dialog box, and close HAFM and the Element Manager. Go to step 4.
Diagnostics YES NO ↓ Go to step 13. 12 The data collection process failed. Retry the process using a new CD (“Collecting Maintenance Data” on page 192). Did the data collection process complete? NO YES ↓ Return the CD to HP for analysis by third-level support. Exit MAP. Contact the next level of support. Exit MAP. 13 Did the HAFM appliance lock up or crash and display a Dr. Watson for Windows 2000 dialog box, as shown in Figure 20? Figure 20: Dr.
Diagnostics YES NO ↓ Go to step 14. A Windows 2000 operating system or HAFM application error occurred and transmitted a handling exception event to the operating system. 1. Click Cancel to close the Dr. Watson for Windows 2000 dialog box and HAFM application. 2. Using the My Computer function at the Windows 2000 desktop, copy the crash dump file (user.dmp) from the local disk (C:) to the CD-RW drive (D:). 3.
Diagnostics d. Ignore the message. After ten seconds, the appliance performs the boot sequence from the basic input/output system (BIOS). During the boot sequence, the appliance performs additional POST tests and displays the following operational information at the LCD panel: — Host name. — System date and time. — LAN 1 and LAN 2 IP addresses. — Fan 1, fan 2, fan 3, and fan 4 rotational speed. — Central processing unit (CPU) temperature. — Hard disk capacity. — Virtual and physical memory capacity. 3.
Diagnostics Did the View All - HAFM 8 window display and is the HAFM application operational? NO YES ↓ The problem is transient and the HAFM appliance is operational. Exit MAP. Contact the next level of support. Exit MAP. MAP 0400: Loss of HAFM Appliance or Web Browser PC Communication This MAP describes fault isolation of the Ethernet communication link between a director and the HAFM appliance, or between a director and a Web browser PC running the Embedded Web Server interface.
Diagnostics ↓ Go to step 3. 2 Table 9 lists event codes, brief explanations of the codes, and associated steps that describe fault isolation procedures. Table 9: MAP 0400: Event Codes Event Code Explanation Action 430 Excessive Ethernet transmit errors. Go to step 8 431 Excessive Ethernet receive errors. Go to step 8 432 Ethernet adapter reset.
Diagnostics 5 Ensure the director reporting the problem is connected to facility AC power and the power switch (circuit breaker) at the rear of the director is set to the ON (up) position. Inspect the director for indications of being powered on, such as: ■ At the front bezel, an illuminated power LED (green) or system error LED (amber). ■ An illuminated green LED on the active CTP card, and illuminated green PWR OK LEDs on both power supplies. ■ Audio emanations and airflow from cooling fans.
Diagnostics Table 10 lists the error messages and associated steps that describe fault isolation procedures. Table 10: MAP 0400: Error Messages and Actions Error Message Action Never connected. Go to step 8 Link timeout. Go to step 8 Protocol mismatch. Go to step 15 Duplicate session. Go to step 18 Unknown network address. Go to step 21 Incorrect product type.
Diagnostics 10 If appropriate, verify that the hubs are correctly daisy-chained, as shown in Figure 21. Figure 21: Ethernet Hubs, Daisy-Chained Note: To check two hubs, use step 1 and step 2 (top and middle hub instructions only). 1. At the first (top) Ethernet hub, ensure an RJ-45 Ethernet patch cable connects to port 24 and the medium-dependent interface (MDI) switch is set to MDI (in). 2.
Diagnostics Was a corrective action performed? NO YES ↓ Go to step 1. 11 Verify operation of the Ethernet hub or hubs. Inspect each hub for indications of being powered on, such as: ■ Green Power LED illuminated. ■ Green Status LEDs illuminated. Is a hub failure indicated? YES NO ↓ Go to step 13. 12 Remove and replace the Ethernet hub. Refer to the supporting documentation shipped with the hub for instructions.
Diagnostics Did repair of an unrelated LAN-attached device solve the problem? NO YES ↓ The director-to-HAFM appliance connection is restored and is operational. Exit MAP. Contact the next level of support. Exit MAP. 14 The Ethernet adapter on the director’s active CTP card reset in response to an error. The connection to the HAFM appliance terminated briefly, then recovered upon reset. Perform the data collection procedure and return the CD to HP for analysis by third-level support personnel.
Diagnostics 17 A director firmware upgrade is required (“Download a Firmware Version to a Director” on page 210). Perform the data collection procedure after the download. Did the director-to-HAFM appliance Ethernet connection recover? NO YES ↓ The director-to-HAFM appliance connection is restored and is operational. Exit MAP. Contact the next level of support. Exit MAP. 18 An instance of the HAFM application is open at another HAFM appliance and communicating with the director (duplicate session).
Diagnostics ■ Hard disk capacity. ■ Virtual and physical memory capacity. 2. After a few seconds, the LCD panel displays the following, as shown in Figure 22. LAN 2: 010.001.001.001 Figure 22: LCD panel (LAN 2 IP address) 3. Depending on switch-to-server LAN connectivity, record the appropriate IP address (LAN 1 or LAN 2). Continue to the next step. 20 Configure the HAFM appliance reporting the Duplicate Session communication problem as a client. 1. At the HAFM main window, choose SAN > Logout.
Diagnostics Did the HAFM appliance reconfigure as a client and did the Ethernet connection recover? NO YES ↓ The director-to-HAFM appliance connection is restored and the second HAFM appliance is operational as a client. Exit MAP. Contact the next level of support. Exit MAP. 21 The IP address defining the director to the HAFM application is incorrect or unknown and must be verified. A maintenance terminal (PC) and asynchronous RS-232 null modem cable are required to verify the director’s IP address.
Diagnostics 7. Configure the Port Settings parameters as follows: ■ Bits per second—57600. ■ Data bits—8. ■ Parity—None. ■ Stop bits—1. ■ Flow control—Hardware. When the parameters are set, click OK. The Director 2/140 HyperTerminal window displays. 8. At the > prompt, type the user-level password (the default is password) and press the Enter key. The password is case sensitive. The Director 2/140 HyperTerminal window displays with a C> prompt at the bottom of the window. 9.
Diagnostics Figure 23: Discover Setup dialog box 2. Highlight the director to be reconfigured from the Available Addresses list, and click Change. The Editing Domain Information dialog box displays, as shown in Figure 24. Figure 24: Editing Domain Information dialog box 3. Click Yes. The Domain Information dialog box displays with the IP Address page open, as shown in Figure 25. Figure 25: Domain Information dialog box (IP Address page) 4. Enter the correct IP address in the IP Address field. 5.
Diagnostics At the HAFM master log, did the IP address below the director icon change to the new entry and did the Ethernet connection recover? NO YES ↓ The director-to-HAFM appliance connection is restored and is operational. Exit MAP. Contact the next level of support. Exit MAP. 23 An incorrect product type is defined to the HAFM appliance. 1.
Diagnostics 24 The product at the configured IP address is not an HP managed product. Notify the customer of the problem. 1. At the HAFM main window, right-click the icon with the grey square representing the product reporting the problem. A menu displays. 2. Choose Delete. A Warning dialog box displays, asking if the product is to be deleted. 3. Click Yes to delete the product. Exit MAP.
Diagnostics ■ Audio emanations and airflow from cooling fans. Is the director powered on? YES NO ↓ A power distribution problem is indicated. Go to “MAP 0100: Power Distribution Analysis” on page 69. Exit MAP. 28 At the director, inspect the amber LED at the top of each CTP card. Is the amber LED illuminated on both CTP cards? NO YES ↓ Failure of both CTP cards is indicated. Go to “MAP 0500: FRU Failure Analysis” on page 107. Exit MAP.
Diagnostics MAP 0500: FRU Failure Analysis This MAP describes fault isolation for the CTP card, SBAR assembly, and fan module. Failure indicators include: ■ The amber LED on the FRU illuminates. ■ The amber emulated LED on a fan graphic at the Hardware View illuminates.
Diagnostics Table 11: MAP 0500: Event Codes (Continued) Event Code 108 Explanation Action 420 Backup CTP card NV-RAM failure. Go to step 7 426 Multiple ECC single-bit errors occurred. Go to step 7 433 Non-recoverable Ethernet fault. Go to step 7 440 Embedded port hardware failed. Go to step 7 604 SBAR assembly failure. Go to step 9 605 SBAR assembly revision not supported. Go to step 16 607 Director contains no operational SBAR assemblies.
Diagnostics 3 Is fault isolation being performed at the director? YES NO ↓ Fault isolation is being performed at the HAFM appliance or Embedded Web Server interface. Go to step 10. 4 Inspect both fan modules at the rear of the director. Fan module LEDs can be inspected through the hexagonal cooling vents of the radio frequency interference (RFI) shield.
Diagnostics 6 Inspect the faceplates of both CTP cards at the front of the director. Is the amber LED at the top of a CTP card illuminated but not blinking (beaconing)? YES NO ↓ Go to step 8. 7 A CTP card failed and must be removed and replaced (“RRP: Redundant CTP Card” on page 226). ■ This procedure is concurrent and can be performed while director power is on. ■ Perform the data collection procedure as part of FRU removal and replacement.
Diagnostics 9 An SBAR assembly failed and must be removed and replaced (“RRP: Redundant SBAR Assembly” on page 247). ■ This procedure is concurrent and can be performed while director power is on. ■ Perform the data collection procedure as part of FRU removal and replacement. Did SBAR assembly replacement solve the problem? NO YES ↓ The director is operational. Exit MAP. Contact the next level of support. Exit MAP.
Diagnostics 13 Is a blinking red and yellow diamond (failed FRU indicator) overlaying an SBAR assembly graphic at the Hardware View? NO YES ↓ An SBAR assembly failure is indicated. Go to step 9. 14 At the Hardware View, is a grey square displayed at the alert panel, a No Link status displays at the Director 2/140 Status table, and graphical FRUs are uninstalled? YES NO ↓ A green circle displays at the alert panel and the director is operational. Exit MAP.
Diagnostics 16 An SBAR assembly is not recognized by director firmware because the firmware version is not supported or the SBAR assembly failed. Advise the customer of the problem and determine the correct firmware version to download from the HAFM appliance. Download the firmware (“Download a Firmware Version to a Director” on page 210). Perform the data collection procedure after the download. Continue to the next step.
Diagnostics 20 Ensure the director reporting the problem is connected to facility AC power and the power switch (circuit breaker) at the rear of the director is set to the ON (up) position. Inspect the director for indications of being powered on, such as: ■ At the front bezel, an illuminated power LED (green) or system error LED (amber). ■ An illuminated green LED on the active CTP card. ■ At least one green PWR OK LED illuminated on a power supply. ■ Audio emanations and airflow from cooling fans.
Diagnostics 23 Inspect CTP card operational states at the Embedded Web Server interface. Inspect the Status fields for both CTP cards. Does the Status field display a Failed message for either CTP card? NO YES ↓ A CTP card failure is indicated. Go to step 7. 24 Inspect SBAR assembly operational states at the Embedded Web Server interface. Inspect the Status fields for both assemblies.
Diagnostics 1 Was an event code 080, 081, 504, 505, 506, 507, 512, 514, 800, 801, or 802 observed at the director Event Log (HAFM appliance) or at the Embedded Web Server Event Log? YES NO ↓ Go to step 3. 2 Was an event code 581, 582, 583, 584, 585, or 586 observed at the console of an OSI or FICON server attached to the director reporting the problem? YES NO ↓ Go to step 4. 3 Table 12 lists event codes, brief explanations of the codes, and associated steps that describe fault isolation procedures.
Diagnostics Table 12: MAP 0600: Event Codes (Continued) Event Code Explanation Action 586 Invalid primitive sequence received for current link state. Go to step 24 800 High temperature warning (UPM card thermal sensor). Go to step 7 801 Critically hot temperature warning (UPM card thermal sensor). Go to step 7 802 UPM card shutdown due to thermal violation.
Diagnostics Verify location of the failed port. For an OSI environment, Figure 27 and Figure 28 show UPM card numbers (0 through15) and port numbers (0-127 and 132-143). For a FICON environment, Figure 27 and Figure 28 show UPM card numbers (0 through 15), port numbers (0-127 and 132-143), and bolded logical port addresses (hexadecimal 04 through 8F).
Diagnostics ■ Perform an external loopback test for the port as part of FRU removal and replacement. Did optical transceiver replacement solve the problem? NO YES ↓ The director is operational. Exit MAP. 7 A UPM card failed, and the card must be removed and replaced (“RRP: UPM Card” on page 231). ■ This procedure is concurrent and can be performed while director power is on. ■ Verify location of the failed port.
Diagnostics 9 Does a blinking red and yellow diamond (failed FRU indicator) display over a UPM card graphic at the Hardware View or display adjacent to a Fibre Channel port graphic at the Port Card View? NO YES ↓ A port or UPM card failure is indicated. Go to step 6. 10 Did a Fibre Channel port or UPM card (all ports) fail a loopback test? NO YES ↓ Go to step 14.
Diagnostics Table 13: MAP 0600: Port Operational and LED States Operational State Green LED Amber LED Action Offline Off Off Go to step 16 Not Operational Off Off Go to step 16 Testing Off Blinking Internal loopback test in process. Exit MAP. Testing On Blinking External loopback test in process. Exit MAP.
Diagnostics Did one of the listed messages display in the Link Incident Log? YES NO ↓ The director is operational. Exit MAP. Go to step 33. 14 A Fibre Channel port or UPM card (all ports) failed an internal or external loopback test. 1. Reset each port that failed the loopback test. a. At the Hardware View, right-click the port. A menu displays. b. Choose Reset Port. A Reset Port n message box displays, where n is the port number. c. Click OK. The port resets. 2.
Diagnostics 16 A director port is unblocked and receiving the offline sequence (OLS) or not operational sequence (NOS) from an attached device. Inform the customer that the attached device failed or is set offline. Exit MAP. 17 Beaconing is enabled for the port. 1. Consult the customer and next level of support to determine the reason port beaconing is enabled. 2. Disable port beaconing. a. At the Port Card View, right-click the port graphic. A menu displays. b. Click Enable Beaconing.
Diagnostics Did configuring the WWN or nickname solve the problem? NO YES ↓ The director is operational. Exit MAP. Contact the next level of support. Exit MAP. 19 The port has an invalid attachment. The information in the Port Properties dialog box specifies the reason (Table 14). Table 14: MAP 0600: Invalid Attachment Reasons and Actions Reasons 124 Action Unknown Contact the next level of support. ISL connection not allowed on this port. Go to step 20 Incompatible switch at other end of ISL.
Diagnostics 20 The port connection conflicts with the configured port type. Either an expansion port (E_Port) is incorrectly cabled to a Fibre Channel device or a fabric port (F_Port) is incorrectly cabled to a fabric element (director or switch). 1. At the Hardware View for the selected director, choose Configure > Ports. The Configure Ports dialog box displays. 2. Use the vertical scroll bar as necessary to display the information row for the port indicating an invalid attachment. 3.
Diagnostics 2. At the Hardware View, choose Configure > Operating Parameters > Fabric Parameters. The Configure Fabric Parameters dialog box displays, as shown in Figure 29. Figure 29: Configure Fabric Parameters dialog box 3. Choose the operating mode as follows: ■ Choose Open Fabric 1.0 from the Interop Mode list box. ■ Choose Homogeneous from the Interop Mode list box. 4. Click Activate to save the selection and close the window.
Diagnostics ■ If the port is operational and a device is attached, the green LED illuminates, the amber LED extinguishes, and the port state is Online. Did removing the loopback plug solve the problem? NO YES ↓ The director is operational. Exit MAP. Contact the next level of support. Exit MAP. 24 A port connection timed out because of an unresponsive device (node) or an ISL connection was not allowed because of a security violation (authorization failure reject).
Diagnostics 26 An SBAR assembly failed and must be removed and replaced (“RRP: Redundant SBAR Assembly” on page 247). ■ This procedure is concurrent and can be performed while director power is on. ■ Perform the data collection procedure as part of FRU removal and replacement. Did SBAR assembly replacement solve the problem? NO YES ↓ The director is operational. Exit MAP. Contact the next level of support. Exit MAP. 27 Inspect and service the host bus adapters (HBAs), as necessary.
Diagnostics 2. Ensure the Enable Switch Binding checkbox is enabled (checked) for both directors. 3. Ensure the Connection Policy radio buttons are compatible for both directors. 4. Click Activate for each director or switch. The switch binding feature is consistently enabled for both directors or switches. Did configuring the switch binding parameters solve the problem? NO YES ↓ The director is operational. Exit MAP. Contact the next level of support. Exit MAP.
Diagnostics 3. At the Membership List of section, update the membership list for both elements to ensure interswitch compatibility, then click OK. The fabric binding feature is consistently enabled for both directors or switches. Did updating the fabric membership lists solve the problem? NO YES ↓ The director is operational. Exit MAP. Contact the next level of support. Exit MAP. 30 A port connection is not allowed because of a switch binding mismatch.
Diagnostics Did updating the switch membership lists solve the problem? NO YES ↓ The director is operational. Exit MAP. Contact the next level of support. Exit MAP. 31 A port connection is not allowed because of a Computer Network Technologies (CNT) wide area network (WAN) extension mode mismatch. Based on switch-to-switch differences between the ELP maximum frame sizes allowed, a connection was not allowed to a director set to CNT WAN extension mode. Contact Computer Network Technologies for support.
Diagnostics 3. Choose the This port (n) only option (where n is the port number) and click OK. The link incident clears. 4. Monitor port operation for approximately five minutes. Did the link incident recur? YES NO ↓ The problem is transient and the Fibre Channel link and director are operational. Exit MAP. 34 Inspect the fiber optic jumper cable attached to the port and ensure the cable is not bent and connectors are not damaged. If the cable is bent or connectors are damaged: 1.
Diagnostics 3. Disconnect both ends of the fiber optic jumper cable. 4. Clean the fiber optic connectors (“Clean Fiber Optic Components” on page 194). 5. Reconnect the fiber optic jumper cable. 6. Unblock the port (“Unblock a Port” on page 203). 7. Monitor port operation for approximately five minutes. Did the link incident recur? YES NO ↓ The Fibre Channel link and director are operational. Exit MAP.
Diagnostics Did the link incident recur? YES NO ↓ The attached device, Fibre Channel link, and director are operational. Exit MAP. 39 The director port reporting the problem is causing the recurrent link incident. The recurring link incident indicates port or UPM card degradation and a possible pending failure. Go to step 6. 40 A UPM card is not recognized by director firmware because the firmware version is not supported or the UPM card failed.
Diagnostics ■ AC power distribution in the director failed, or AC power was disconnected. ■ Both of the director’s CTP cards failed. Continue to the next step. 44 Ensure the director reporting the problem is connected to facility AC power and the power switch (circuit breaker) at the rear of the director is set to the ON (up) position. Inspect the director for indications of being powered on, such as: ■ At the front bezel, an illuminated power LED (green) or system error LED (amber).
Diagnostics 46 Inspect Fibre Channel port operational states at the Embedded Web Server interface. 1. At the View panel, click the Port Properties tab. The View panel (Port Properties tab) displays with port 0 highlighted in red. 2. Click the port number (0-127 and 132-143) for which a failure is suspected to display properties for that port. 3. Inspect the Operational State field. Scroll down the View panel as necessary. 4.
Diagnostics 3. Perform an external loopback test for the port as part of FRU removal and replacement. Exit MAP.
Diagnostics MAP 0700: Fabric, ISL, and Segmented Port Problem Determination This MAP describes isolation of fabric logout, interswitch link (ISL), and E_Port segmentation problems. Failure indicators include: ■ An event code recorded at the Director 2/140 Event Log or the Embedded Web Server Event Log. ■ A segmentation reason associated with a Fibre Channel port at the Embedded Web Server interface.
Diagnostics Table 16: MAP 0700: Event Codes (Continued) Event Code Explanation Action 052 HAFM appliance internal error. Go to step 8 060 Fabric controller unable to synchronize databases. Go to step 9 061 Fabric controller database invalid. Go to step 9 062 Maximum interswitch hop count exceeded. Go to step 10 063 Received link state record too large. Go to step 11 070 E_Port is segmented. Go to step 12 071 Director is isolated.
Diagnostics Does the Operational State field indicate Segmented E_Port? YES NO ↓ Analysis for a UPM card failure or other link incident is not described in this MAP. Go to “MAP 0600: UPM Card Failure and Link Incident Analysis” on page 115. Exit MAP. 6 Inspect the Segmentation Reason field at the Port Properties dialog box. Table 17 lists port segmentation reasons and associated steps that describe fault isolation procedures.
Diagnostics All attached devices resume operation after fabric login. Perform the data collection procedure and return the CD to HP for analysis by third-level support personnel. Exit MAP. 8 A minor error occurred that caused HAFM appliance databases to be reinitialized to an empty state. As a result, a disruptive server logout and login occurred for all attached devices. The following list explains the errors.
Diagnostics Advise the customer of the problem and work with the system administrator to reconfigure the fabric so the path between any two fabric elements does not traverse more than three hops. Did fabric reconfiguration solve the problem? NO YES ↓ The director and multi-switch fabric are operational. Exit MAP. Contact the next level of support. Exit MAP.
Diagnostics Table 18: MAP 0700: Byte 4, Segmentation Reasons Byte 4 Segmentation Reason Action 01 Incompatible operating parameters. Go to step 14 02 Duplicate domain IDs. Go to step 15 03 Incompatible zoning configurations. Go to step 16 04 Build fabric protocol error. Go to step 17 05 No principal switch. Go to step 19 06 No response from attached switch. Go to step 20 07 ELP retransmission failure timeout.
Diagnostics 7. Set both directors online (“Set Online State” on page 200). Did the operating parameter change solve the problem and did both directors join through the ISL to form a fabric? NO YES ↓ The directors, associated ISL, and multi-switch fabric are operational. Exit MAP. Contact the next level of support. Exit MAP. 15 A director E_Port segmented because two fabric elements had duplicate domain IDs. 1.
Diagnostics Did the domain ID change solve the problem and did both directors join through the ISL to form a fabric? NO YES ↓ The directors, associated ISL, and multi-switch fabric are operational. Exit MAP. Contact the next level of support. Exit MAP. 16 A director E_Port segmented because two directors had incompatible zoning configurations. An identical zone name is recognized in the active zone set for both directors, but the zones contain different members. 1.
Diagnostics Figure 37: Zoning dialog box (Zone Library tab) 5. Click the Active Zone Set tab. The Zoning dialog box displays with the Active Zone Set page open, as shown in Figure 38. Figure 38: Zoning dialog box (Active Zone Set tab) 6. Inspect zone names in the active zone set to determine the incompatible name.
Diagnostics 7. Modify the incompatible zone name as directed by the customer: a. At the Zoning dialog box, click the Zone Library tab. The dialog box returns to the Zone Library page, as shown in Figure 37. b. Right-click the zone name to be changed from the Zones field. A pop-up menu displays. c. Choose the Rename option from the menu. The selected zone name remains highlighted in blue. d. Enter the new zone name (specified by the customer). e.
Diagnostics Did the IPL solve the problem and did both directors join through the ISL to form a fabric? NO YES ↓ The directors, associated ISL, and multi-switch fabric are operational. Exit MAP. Perform the data collection procedure and contact the next level of support. Exit MAP. 19 A director E_Port segmented because no director in the fabric is capable of becoming the principal switch. 1. Notify the customer the director will set offline.
Diagnostics Did the switch priority change solve the problem and did both directors join through the ISL to form a fabric? NO YES ↓ The directors, associated ISL, and multi-switch fabric are operational. Exit MAP. Contact the next level of support. Exit MAP. 20 A director E_Port segmented (at an operational director) because a response to a verification check indicates an attached director is not operational. 1.
Diagnostics 22 A 142 event code occurs only if the optional OpenTrunking feature is enabled. The event code indicates OpenTrunking firmware detected an ISL with no transmission BB_Credit for a period of time that exceeded the configured low BB_Credit threshold. This results in downstream fabric congestion. No action is required for an isolated event or if the reporting ISL approaches 100% throughput.
Diagnostics Table 19: Bytes 8 through 11 Failure Reasons and Actions Bytes 8 - 11 Failure Reason Action 01 Invalid data length. Go to step 24 08 Invalid zone set format. Go to step 24 09 Invalid data. Go to step 25 0A Cannot merge. Go to step 25 F0 Retry limit reached. Go to step 24 F1 Invalid response length. Go to step 24 F2 Invalid response code. Go to step 24 24 A zone merge failed during ISL initialization.
Diagnostics 25 A zone merge failed during ISL initialization. The following list explains the reason: ■ Failure reason 09—Invalid data caused a zone merge failure. ■ Failure reason 0A—A Cannot Merge condition caused a zone merge failure. Obtain supplementary error code data for the 150 event code. 1. At the Hardware View, choose Logs > Event Log. The Event Log displays. 2. Examine bytes 12 through 15 of event data that specify the error code. Record the error code.
Diagnostics Table 20: MAP 0700: Segmentation Reasons and Actions Segmentation Reason Action Incompatible operating parameters. Go to step 14 Duplicate domain IDs. Go to step 15 Incompatible zoning configurations. Go to step 16 Build fabric protocol error. Go to step 17 No principal switch. Go to step 19 No response from attached switch. Go to step 20 ELP retransmission failure timeout.
Diagnostics 3 Are you performing fault isolation at one of the following servers? ■ The management appliance running the Windows 2000 Professional operating system. ■ A customer-supplied server running the client HAFM application and a Windows operating system (Windows 95, Windows 98, Windows 2000, Windows XP, or Windows NT 4.0). YES NO ↓ Analysis for the server failure is not described in this MAP. Contact the next level of support. Exit MAP. 4 At the HAFM appliance, close the HAFM application. 1.
Diagnostics 6 Reboot the HAFM appliance and perform system diagnostics. 1. Choose Start > Shut Down. The Shut Down Windows dialog box displays. 2. Choose Shut down from the drop-down list and click OK to power off the appliance. 3. Wait approximately 30 seconds and press the power ( ) button on the liquid crystal display (LCD) panel to power on the appliance and perform power-on self-test (POST). During POST: a. The green LCD panel illuminates. b.
Diagnostics Did POSTs detect a problem? NO YES ↓ A computer hardware problem exists. Refer to the supporting documentation shipped with the appliance for instructions on resolving the problem. Exit MAP. 7 After rebooting the appliance, the HAFM Services and HAFM applications start, and the HAFM 8 Log In dialog box displays. Did the HAFM 8 Log In dialog box display? YES NO ↓ Go to step 9. 8 Log in to the HAFM appliance using the HAFM 8 Log In dialog box. 1.
Diagnostics 9 Perform one of the following: ■ If the appliance has standalone diagnostic test programs resident on the hard drive, perform the diagnostics. Refer to supporting documentation shipped with the appliance for instructions. ■ If the appliance does not have standalone diagnostic test programs resident on fixed disk, go to step 10. Did diagnostic test programs detect a problem? NO YES ↓ Refer to the supporting documentation shipped with the appliance for instructions to resolve the problem.
Diagnostics — Central processing unit (CPU) temperature. — Hard disk capacity. — Virtual and physical memory capacity. 4. After successful POST completion, the LCD panel displays a Welcome!! message, then continuously cycles through and displays appliance operational information. 5. After rebooting the appliance at the LCD panel, log on to the HAFM appliance Windows 2000 desktop through a LAN connection to a browser-capable PC.
Diagnostics 12 Advise the customer and next level of support that the appliance hard drive should be restored to its original factory configuration. If the customer and support personnel do not concur, go to step 13. 1. Format the appliance hard drive. Refer to supporting documentation shipped with the appliance for instructions. 2. Restore the appliance hard drive using the HAFM appliance Restore/Boot CD shipped with the appliance. Refer to the readme.txt file on the CD for instructions. 3.
Diagnostics 160 Director 2/140 Service Manual
Repair Information 3 This chapter describes repair and repair-related procedures used by service representatives for the Director 2/140 and associated field-replaceable units (FRUs).
Repair Information Factory Defaults Table 21 lists the defaults for the passwords and IP, subnet, and gateway addresses. Table 21: Factory-set Defaults Item Default Customer password password Maintenance password level-2 IP address 10.1.1.10 Subnet mask 255.0.0.0 Gateway address 0.0.0.0 Procedural Notes Note: HAFM and Element Manager screens in this manual may not match the screens on your server and workstation.
Repair Information Using Log Information The HAFM, Element Manager, and EWS applications provide access to logs that provide information for administration, operation, and maintenance personnel. Each log stores up to 1,000 entries. The most recent entry displays at the top of a log. If a log is full, a new entry overwrites the oldest entry. Five logs are accessed through the HAFM application: ■ Audit Log—Displays a history of user actions performed through the HAFM application.
Repair Information ■ Director 2/140 Event Log—Displays a history of events for the director, such as system events, degraded operation, FRU failures, FRU removals and replacements, port problems, Fibre Channel link incidents, and HAFM appliance-to-director communication problems. All detected software and hardware failures are recorded in the Director 2/140 Event Log. The information is useful to maintenance personnel for fault isolation and repair verification.
Repair Information For a description of the EWS Logs and an explanation of the button functions at the bottom of the log window, refer to the hp StorageWorks Embedded Web Server User Guide. Viewing Logs You can view log data through the Master Log on the main window. However, if you want to see only certain types of events, for example only login/logout events (session events), open a specific log through the View Logs dialog box. To view a log, perform the following: 1.
Repair Information 2. Click Export. The Save dialog box displays. 3. Browse to the folder where you want to save the file. Type a file name in the File Name field. 4. Click Save. The file is exported in tab-delimited format. To view it in table format, open the file in Microsoft Excel. Obtaining Port Diagnostic Information Port and UPM card diagnostics are performed at the director or HAFM appliance (Element Manager). These diagnostics include: 166 ■ Inspecting port and UPM card LEDs at the director.
Repair Information UPM Card LEDs To obtain port operational information, inspect port LEDs at the director UPM card faceplate or the emulated port LEDs at the HAFM Hardware View. These port operational states are defined in Table 22. Table 22: Port Operational States Port State Green LED Amber LED Alert Symbol Description Online On Off None An attached device is connected to the director and ready to communicate, or is communicating with other attached devices.
Repair Information Table 22: Port Operational States (Continued) Port State 168 Green LED Amber LED Alert Symbol Description Invalid Attachment On Off Yellow Triangle The director port has an invalid attachment state if: (1) a loopback plug is connected to the port with no diagnostic test running, or (2) the port is cabled to another port on the same director, or (3) the port connection conflicts with the configured port type.
Repair Information Table 22: Port Operational States (Continued) Port State Green LED Amber LED Alert Symbol Description Segmented E_Port On Off Yellow Triangle The E_Port is segmented, preventing two connected directors from joining and forming a multi-switch fabric. Testing Off Blinking Yellow Triangle The port is performing an internal loopback test. On Blinking Yellow Triangle The port is performing an external loopback test.
Repair Information Figure 40: Port List View The Port List View provides status information in the following columns: ■ #—The director port number (0 through 139 inclusive). ■ Addr—The director logical port address in hexadecimal format (FICON management style only). ■ Name—The port name configured through the Configure Ports dialog box. ■ Block Config—The port status (Blocked or Unblocked). ■ State—The operating state of the port.
Repair Information ■ Operating Speed—The operating speed of the port (Not Established, 1, or 2 Gb/sec.). ■ Alert—If Link Incident (LIN) alerts are configured for the port through the Configure Ports dialog box, a yellow triangle displays in the column when a link incident occurs. A yellow triangle also displays if beaconing is enabled for the port. A red and yellow diamond displays if the port fails. Double-click anywhere in a row for an installed port to open the Port Properties dialog box.
Repair Information Figure 41: Performance View Each port bar graph in the upper portion of the view displays the instantaneous transmit or receive activity level for the port, and is updated every five seconds. The relative value displayed is the greater of either the transmit or receive activity (whichever value is greatest when sampled). Each port graph has 20 green-bar level indicators corresponding to 5% of the maximum throughput for the port (either transmit or receive).
Repair Information ■ Enable or disable port channel wrapping (when the director is configured for FICON management style). ■ Swap one Fibre Channel port address with another (when the director is configured for FICON management style). ■ Clear link incident alerts. ■ Reset the port. ■ Enable or disable port binding. ■ Clear threshold alerts.
Repair Information — Primitive sequence errors—Incorrect primitive sequences are received from an attached device, indicating Fibre Channel link-level protocol violations. At the Hardware View, a yellow triangle displays to indicate a link incident. — Discarded frames—Received frames could not be routed and were discarded because the frame timed out (insufficient buffer-to-buffer credit) or the destination device was not logged in to the director.
Repair Information — Flows rerouted to and from ISLs. Viewing Port Properties To open the Port Properties dialog box, perform the following: 1. Double-click a port graphic at the Hardware View or a port row at the Port List View. The Port Properties dialog box displays, as shown in Figure 42.
Repair Information ■ Block Configuration—A user-configured state for the port (Blocked or Unblocked). ■ LIN Alerts Configuration—A user-specified state for the port (On or Off), configured through the Configure Ports dialog box. ■ FAN Configuration—A user-configured state for FAN configuration (Enabled or Disabled). ■ Beaconing—User-specified for the port (On or Off). When beaconing is enabled, a yellow triangle appears adjacent to the status field.
Repair Information Table 23: Invalid Attachment Messages and Explanations (Continued) Message Explanation 03 ELP rejected by the attached switch. This director or switch transmitted an exchange link protocol (ELP) frame that was rejected by the switch at the other end of the ISL (Invalid Attachment only). 04 Incompatible switch at the other end of the ISL.
Repair Information Viewing the Port Technology To open the Port Technology dialog box, perform the following: 1. Right-click a port graphic at the Hardware View or a port row at the Port List View. A menu displays, 2. Choose Port Technology. The Port Technology dialog box displays, as shown in Figure 43. Figure 43: Port Technology dialog box The Port Technology dialog box provides the following information: ■ Port Number—The director port number (0-127 and 132-143 inclusive).
Repair Information Viewing the Port List Page When the EWS interface opens, the View panel displays as the default. To view the Port List page, perform the following: 1. At the View panel, choose the Monitor option at the left side of the panel. The Monitor panel displays with the Port List page open, as shown in Figure 44. Figure 44: Monitor panel (Port List page) A row of information for each port (0 through 139 inclusive) appears.
Repair Information Viewing the Port Stats Page When the EWS interface opens, the View panel displays as the default panel. To view the Port Stats page, perform the following: 1. At the View panel, choose the Monitor option at the left side of the panel. The Monitor panel displays with the Port List page open, as shown in Figure 44. 2. Click the Port Stats tab. The Monitor panel displays with the Port Stats page open, as shown in Figure 45.
Repair Information ■ Traffic statistics—These entries provide information about port traffic, including: — Fibre Channel frames received and transmitted. — Four-byte words received and transmitted. — Offline sequences received and transmitted. — Link resets received and transmitted. — Loop initialization primitives (LIPs) generated and detected. — Percent link utilization (receive and transmit).
Repair Information — Address ID errors—Received frames had unavailable or invalid Fibre Channel destination addresses, or invalid Fibre Channel source addresses. This typically indicates the destination device is unavailable. — Frames too short—Received frames were less than the Fibre Channel minimum size, indicating the frame arrived at the director port corrupted.
Repair Information Figure 46: View panel (Port Properties page) The Port Properties page displays information for one port. Values update only when the page opens for a selected port or the user chooses Get Port Properties. The page defaults to port 0. Increment or decrement the port number displayed (0 through 139 inclusive) by clicking Fwd>> or <
Repair Information ■ Beaconing—The user-specified state for the port (On or Off). ■ FAN Configuration—The user-configured state for fabric address notification (FAN) configuration (Enabled or Disabled). ■ Operational State—The port state ((Online, Offline, Not Installed, Inactive, Invalid Attachment, Link Reset, No Light, Not Operational, Port Failure, Segmented E_Port, or Testing).
Repair Information 2. Open the HAFM application. The View All - HAFM 8 main window displays. 3. Double-click the icon representing the director for which the loopback test will be performed. The Hardware View for the selected director displays. 4. At the Hardware View, verify the location of the port or UPM card to be tested.
Repair Information — To select an individual port for test, type the port number in the Port Number field. — To select a UPM card for test, type the port number of any of the four ports on the card in the Port Number field, then choose All Ports On Card option. 8. Choose Internal Loop from the Diagnostics Test drop-down list. 9. Click Next. Beaconing initiates for the port or UPM card selected for test. At the Hardware View, a yellow triangle displays at the top of the UPM card.
Repair Information b. At the Port Card View, right-click the tested port. A menu displays. c. Choose Reset Port. A reset warning box displays. d. Click OK. The port resets. External Loopback Test To perform an external loopback test for a single port or a UPM card (four ports): 1. Notify the customer a disruptive external loopback test will be performed on a port or UPM card, and the fiber optic cable or cables will be disconnected.
Repair Information 6. Disconnect the fiber optic jumper cable from the port to be tested. If a UPM card will be tested, disconnect all four fiber optic jumper cables. Caution: If name server zoning is implemented by port number, ensure the fiber optic cables that are disconnected to perform the loopback test are reconnected properly. A cable configuration change disrupts zone operation and may incorrectly include or exclude a device from a zone. 7.
Repair Information — A red progress bar (indicating percent completion) travels from left to right across the Completion Status field. As an individual port is tested, the amber LED flashes (beacons) and the green LED illuminates (indicating loopback traffic through the port). Note: Click Stop Test at any time to abort the loopback test. 15. When the test completes, test results display (for each port tested) as Port xx: Passed! or Port xx: Failed! in the message area of the dialog box.
Repair Information 2. Open the HAFM application. The View All - HAFM 8 main window displays. a. Double-click the icon representing the director for which the channel wrap test will be configured. The Hardware View for the selected director displays. b. At the Hardware View, verify the location of the port to be configured for the channel wrap test.
Repair Information 4. Click Maintenance and choose Swap Ports. The Swap Ports dialog box displays. 5. Enter the logical port addresses (in hexadecimal format) of the pair of ports to be swapped at the First address and Second address fields. The ports are automatically blocked during the procedure. 6. Choose the Unblock after swap check boxes to unblock the ports when the procedure completes. 7. Click Next.
Repair Information Collecting Maintenance Data When the director operational firmware detects a critical error or FRU failure, the director automatically copies the contents of dynamic random access memory (DRAM) to a dump area in FLASH memory on the active CTP card, then initiates a failover to the operational FRU. The director then transfers (through the Ethernet connection) the captured dump file from FLASH memory to the HAFM appliance hard drive.
Repair Information 4. Remove the backup cd from the HAFM appliance backup drive and insert a blank backup cd. 5. At the Save Data Collection dialog box, select the backup drive from the Look in: drop-down menu, then type a descriptive name for the collected maintenance data in the File name field. Ensure the file name has a .zip extension, then click Save. 6. A dialog box displays, as shown in Figure 49, with a progress bar that shows percent completion of the data collection process.
Repair Information Clean Fiber Optic Components Perform this procedure as directed in this publication and when connecting or disconnecting fiber optic cables from director UPM card connectors (if necessary). To clean fiber optic components: 1. Obtain the appropriate tools (portable can of oil-free compressed air and alcohol pads) from the fiber optic cleaning kit. 2. Disconnect the fiber optic cable from the port. Use compressed air to blow any contaminants from the connector, as shown in 1 on Figure 50.
Repair Information Power-On Procedure To power on the director: 1. One alternating current (AC) power cord is required for each power supply installed. Ensure power cords connect facility power to the input power module at the bottom rear of the director. If two power cords are installed for high availability, plug the cords into separate facility power circuits. WARNING: An HP-supplied power cord is provided for each director power supply.
Repair Information Power-Off Procedure Powering the director off and on (performing a power cycle) resets all logic cards and executes POSTs. When performing a power cycle, wait approximately 30 seconds before switching power on. Note: When the director is powered off, the operation of attached Fibre Channel devices is disrupted. Do not power off the director unless directed to do so by a procedural step or the next level of support. To power off the director: 1.
Repair Information IML, IPL, or Reset the Director This section describes procedures to IML, IPL, or reset the Director 2/140. An IML or reset is performed at the CTP front panel using the IML or the RESET button. An IPL is performed from the HAFM appliance (Director 2/140 Element Manager). Do not IPL the director unless directed to do so by a procedural step or the next level of support. An IML and IPL are functionally equivalent.
Repair Information — As the network connection drops, the Director 2/140 Status table turns yellow, the Status field displays No Link, and the State field displays Link Timeout. — The status bar at the bottom of the window displays a grey square, indicating director status is unknown. — Illustrated FRUs disappear, and appear again as the connection is re-established. IPL the Director from the HAFM Appliance To IPL the director from the HAFM appliance, perform the following: 1. Open the HAFM application.
Repair Information 2. During the reset: — The green power (PWR) LED on the director front panel illuminates. — The amber system error (ERR) LED on the director front panel blinks momentarily while the director is tested. — The green LEDs associated with the Ethernet port blink momentarily while the port is tested. — The amber LEDs associated with the ports blink momentarily while the ports are tested.
Repair Information Set the Director Online or Offline This section describes procedures to set the director online or offline. These operating states are described as follows: ■ Online—When the director is set online, an attached device can log in to the director if the port is not blocked. Attached devices can communicate with each other if they are configured in the same zone. ■ Offline—When the director is set offline, all ports are set offline.
Repair Information Set Offline State To set the director offline: 1. Notify the customer the director will be set offline. Ensure the customer’s system administrator quiesces Fibre Channel frame traffic through the director and sets attached devices offline. 2. Open the HAFM application. The View All - HAFM 8 main window displays. 3. Double-click the icon representing the director to be set offline. The Hardware View for the selected director displays. 4. Choose Maintenance > Set Online State.
Repair Information Block and Unblock Ports This section describes procedures to block or unblock director ports. An entire UPM card (four ports) can be blocked or unblocked, or ports can be blocked or unblocked on an individual basis. When a port is blocked, the port is automatically set offline. When a port is unblocked, the port is automatically set online. Note: When a director port is blocked, the operation of an attached Fibre Channel device is disrupted.
Repair Information — A check mark displays in the check box adjacent to the Block Port menu option. 8. Click Back to Full View to return to the Hardware View. Block a UPM Card To block all four ports on a director UPM card: 1. Notify the customer the UPM card will be blocked. Ensure the customer’s system administrator quiesces Fibre Channel frame traffic through the ports and sets attached devices offline. 2. Open the HAFM application. The View All - HAFM 8 main window displays. 3.
Repair Information 2. Double-click the icon representing the director for which a port will be unblocked. The Hardware View for the selected director displays. 3. Double-click the UPM card for which a port will be unblocked. The Port Card View for the selected card displays. 4. Move the mouse pointer over the port to be unblocked and right-click the mouse to open a list of menu options. 5. Choose Block Port. Note the check mark in the box adjacent to the menu item, indicating the port is blocked.
Repair Information Figure 57: Unblock All Ports dialog box 6. Click Yes. The following occur to indicate the UPM card is unblocked (and online): — Emulated green LEDs associated with all four ports illuminate at the Port Card View. — Green LEDs associated with all four ports illuminate at the director. 7. Click Back to Full View to return to the Hardware View.
Repair Information Manage Firmware Versions Firmware is the director’s internal operating code that is downloaded from the HAFM appliance and stored on a CTP card. Up to eight versions can be stored on the HAFM appliance hard drive and made available for download to a director. Service personnel can perform the following firmware management tasks: ■ Determine the firmware version active on a director. ■ Add to and maintain a library of up to eight firmware versions on the HAFM appliance hard drive.
Repair Information 4. The firmware version displays at the lower left corner of the dialog box in XX.YY.ZZ format, where XX is the version level, YY is the release level, and ZZ is the patch level. 5. Click Close to return to the Hardware View. Add a Firmware Version The firmware version shipped with the director is provided on the HP StorageWorks Director Documentation Kit CD. Subsequent firmware versions to upgrade the director are provided to customers through the HP website.
Repair Information d. Ensure the correct directory path is specified at the Save in field and the correct file is specified in the File name field. Click Save. The new firmware version is downloaded and saved to the HAFM appliance or PC hard drive. e. If the new firmware version was downloaded to a PC (not the HAFM appliance), transfer the firmware version file to the HAFM appliance by backup disk, CD-ROM, or other electronic means. 2. Open the HAFM application. The View All - HAFM 8 main window displays.
Repair Information 8. A Transfer Complete message box displays, indicating the new firmware version is stored on the HAFM appliance hard drive. Click Close to close the message box. The new firmware version and associated description display in the Director 2/140 Firmware Library dialog box. 9. Click Close. 10. To send the firmware version to a director, see “Download a Firmware Version to a Director” on page 210.
Repair Information Delete a Firmware Version To delete a director firmware version from the library stored on the HAFM appliance hard drive: 1. Open the HAFM application. The View All - HAFM 8 main window displays. 2. Double-click the icon representing the director from which the firmware version will be deleted. The Hardware View for the selected director displays. 3. Choose Maintenance > Firmware Library. The Director 2/140 Firmware Library dialog box displays, as shown in Figure 58. 4.
Repair Information 2. Before downloading firmware version XX.YY.ZZ to a director, ensure that the required version of the HAFM application, as described in the firmware release notes, is running on the HAFM appliance. a. Choose Help > About. The About dialog box displays and lists the HAFM application version. Click OK to close the dialog box. b. If required, install the correct version of the HAFM application (“Install or Upgrade Software” on page 218). 3.
Repair Information percent completion of the download. The bar progresses to 50% when the last file is transmitted to the first CTP card. The bar remains at the 50% point until the director performs an IPL (indicated by an IPLing message).
Repair Information Manage Configuration Data The Element Manager provides maintenance options to back up, restore, or reset the configuration files stored in nonvolatile random-access memory (NV-RAM) on both director CTP cards. Configuration data in the file includes: ■ Identification data (director name, description, and location). ■ Port configuration data (port names, blocked states, extended distance settings).
Repair Information Figure 65: Backup Complete dialog box 5. Click OK to close the dialog box and return to the Hardware View. Restore the Configuration To restore the director configuration file from the HAFM appliance: 1. Notify the customer the director will be set offline. Ensure the customer’s system administrator quiesces Fibre Channel frame traffic through the director and sets attached devices offline. 2. Set the director offline (“Set Offline State” on page 201). 3. Open the HAFM application.
Repair Information To reset director data to the factory default settings: 1. Notify the customer the director will be set offline. Ensure the customer’s system administrator quiesces Fibre Channel frame traffic through the director and sets attached devices offline. 2. Set the director offline (“Set Offline State” on page 201). 3. Open the HAFM application. The View All - HAFM 8 main window displays. 4.
Repair Information c. At the HAFM application, choose Discover > Setup. The Discover Setup dialog box displays, as shown in Figure 68. Figure 68: Discover Setup dialog box d. Highlight the entry representing the reset director in the Available Addresses window and click Change. The Domain Information dialog box displays, as shown in Figure 69. Figure 69: Domain Information dialog box e. Enter 10.1.1.10 in the IP Address field and click OK.
Repair Information c. Highlight the entry representing the reset director in the Available Addresses window and click Remove. d. At the Discover Setup dialog box, click OK. The director is no longer defined to the HAFM appliance. e. Change a director IP address through the maintenance port, refer to hp StorageWorks Director 2/140 Installation Guide for more information. f. Identify the switch to the HAFM application, refer to hp StorageWorks Director 2/140 Installation Guide for more information. g.
Repair Information Install or Upgrade Software This section describes the procedure to install or upgrade the HAFM application to the HAFM appliance. The HAFM application includes the Director 2/140 Element Manager and HAFM Services applications. The HAFM application shipped with the director is provided on the HAFM Applications CD-ROM. Subsequent software versions for upgrading the director are provided to customers through the HAFM Applications CD-ROM or through the HP website.
Repair Information d. Ensure the correct directory path is specified at the Save in field and the correct file is specified in the File name field. Click Save. The new HAFM version is downloaded and saved to the HAFM appliance or PC hard drive. e. If the new HAFM version was downloaded to a PC (not the HAFM appliance), transfer the HAFM software version file to the HAFM appliance by CD-ROM or other electronic means. 3. Choose Start > Run. The Run dialog box displays, as shown in Figure 70.
Repair Information 6. Follow the online instructions for the InstallAnywhere program. Click Next, Install, or Done as appropriate. 7. Power off and reboot the HAFM appliance. a. Simultaneously press Ctrl + Alt + Delete to display the Windows 2000 Logon Information dialog box. b. Type the username and password and click OK. The Windows 2000 desktop displays. Note: If required, obtain the username and password from the customer or next level of support. 8.
FRU Removal and Replacement 4 This chapter describes removal and replacement procedures (RRPs) used by authorized service representatives for all director field-replaceable units (FRUs). Do not perform a procedure in this chapter until a failure is isolated to a FRU. If fault isolation was not performed, go to “MAP 0000: Start MAP” on page 45.
FRU Removal and Replacement Factory Defaults Table 24 lists the defaults for the passwords and IP, subnet, and gateway addresses. Table 24: Factory-set Defaults Item Default Customer password password Maintenance password level-2 IP address 10.1.1.10 Subnet mask 255.0.0.0 Gateway address 0.0.0.0 Procedural Notes Note: HAFM and Element Manager screens in this manual may not match the screens on your server and workstation.
FRU Removal and Replacement Removing and Replacing FRUs This section describes procedures to remove and replace director FRUs, along with a list of tools required to perform each procedure. In addition, the section provides: ■ ESD information. ■ A list of concurrent FRUs. ■ A list of non-concurrent FRUs. See Chapter 5, ““Illustrated Parts Breakdown” on page 263” for FRU locations and part numbers.
FRU Removal and Replacement 1 Figure 72: ESD grounding points 224 Director 2/140 Service Manual
FRU Removal and Replacement Concurrent FRUs Table 25 lists concurrent FRUs. Concurrent FRUs can be removed and replaced while the director is powered on and operational. The table also lists ESD precaution requirements (yes or no) for each FRU and provides hyperlinks to the removal and replacement procedure.
FRU Removal and Replacement non-concurrent FRUs Table 26 lists non-concurrent FRUs. non-concurrent FRUs are removed and replaced after the director is powered off. The table also lists ESD precaution requirements (yes or no) for each FRU, and references the page number of the removal and replacement procedure.
FRU Removal and Replacement 2. Follow ESD procedures by attaching a wrist strap to the director chassis and your wrist, as shown in Figure 72. Caution: To avoid causing machine errors or damage while working on the director, follow ESD procedures by connecting a grounding cable to the director chassis and wearing an ESD wrist strap. 3. Identify the defective CTP card from the amber LED on the card or failure information at the Hardware View. 4.
FRU Removal and Replacement 2 1 1 Torque tool 2 CTP card Figure 73: CTP card removal and replacement 6. Pull the CTP card from its card track and remove it from the director chassis. Place the card in an antistatic bag to provide ESD protection. Replacing the CTP Card To replace a redundant CTP card: 1. Wait approximately 20 seconds after removal of the failed CTP card to begin this replacement procedure. 2. Remove the replacement card from its protective antistatic bag. 3.
FRU Removal and Replacement 4. Secure the CTP card: a. Insert the torque tool into the cam Allen screw at the top of the card. Turn the torque tool clockwise until you feel it release and hear a clicking sound. As the screw turns clockwise, the card cams into the backplane connector. b. Insert the torque tool into the locking Allen screw at the bottom of the card. Turn the torque tool clockwise until you feel it release and hear a clicking sound. As the screw turns clockwise, the card locks into place. c.
FRU Removal and Replacement 9. Inspect the CTP card to ensure the amber LED is extinguished. If the amber LED is illuminated, go to “MAP 0000: Start MAP” on page 45 to isolate the problem. 10. At the Hardware View, choose Logs > Event Log. The Event Log displays. Ensure the following event codes display in the log: — 410—CTP card reset. — 416—Backup CTP installed. — 422—CTP firmware synchronization complete (only if the firmware versions on the two CTP cards are different).
FRU Removal and Replacement — If at an EWS interface: a. Click the Switch tab at the Operations panel. The Operations panel displays with the Switch page open. b. Click the Sys Err Light tab. The Switch page displays with the Sys Err Light tab selected. A System Error Light is ON message displays on the page. c. Click Clear Light. 16. If necessary, close and lock the equipment cabinet door. RRP: UPM Card Use the following procedures to remove or replace a UPM card.
FRU Removal and Replacement Caution: To avoid causing machine errors or damage while working on the director, follow ESD procedures by connecting a grounding cable to the director chassis and wearing an ESD wrist strap. 4. Identify the defective UPM card from the amber LED on the card or failure information at the Hardware View. 5. Block communication to the defective UPM card (“Block a UPM Card” on page 203). 6. Disconnect the fiber optic jumper cable from each port on the defective card.
FRU Removal and Replacement Caution: The torque tool supplied with the Director 2/140 is designed to tighten director logic cards and is set to release at a torque value of six inch-pounds. Do not use an Allen wrench or torque tool designed for use with another HP product. Use of the wrong tool may overtighten and damage logic cards. a. Insert the torque tool into the locking Allen screw (yellow). Turn the screw counter-clockwise until the spring releases and the tool turns freely. b.
FRU Removal and Replacement Replacing the UPM Card To replace a UPM card: 1. Remove the replacement card from its protective antistatic bag. 2. Hold the card by its stiffener and insert it in the chassis card track, as shown in Figure 74. The label identifying the card should be at the top. Verify the card is aligned in the card tracks, then slide it forward until it makes contact with the backplane. 3. Secure the UPM card: a. Insert the torque tool into the cam Allen screw (uncolored).
FRU Removal and Replacement — 501—Port card has been recognized. If an event code 501 does not display in the log, go to “MAP 0000: Start MAP” on page 45 to isolate the problem. 9. At the Hardware View, double-click the graphic representing the replacement card to open the Port Card View. At the Port Card View: a. Ensure no alert symbols display that indicate a failure (yellow triangle or red diamond). b. Verify that UPM card information (FRU name, position, and state) is correct.
FRU Removal and Replacement RRP: SFP Optical Transceiver Use the following procedures to remove or replace an SFP optical transceiver from a UPM card. A list of tools required is provided. Tools Required The following tools are required to perform these procedures. ■ fiber optic protective plug (provided with the director). ■ Protective cap (provided with the fiber optic jumper cable). ■ fiber optic cleaning kit. Removing the SFP Optical Transceiver To remove an SFP optical transceiver: 1.
FRU Removal and Replacement UPM 1 SHR-2287 Figure 75: SFP optical transceiver removal and replacement Replacing the SFP Optical Transceiver To replace an SFP optical transceiver: 1. Remove the transceiver from its packaging. 2. Insert the transceiver into the port receptacle, as shown in Figure 75. 3. Perform an external loopback test for the port (“External Loopback Test” on page 187). If the test fails, go to “MAP 0000: Start MAP” on page 45 to isolate the problem. 4.
FRU Removal and Replacement 5. Inspect the UPM card with the replacement port transceiver to ensure all amber LEDs are extinguished. If any amber LEDs are illuminated, go to “MAP 0000: Start MAP” on page 45 to isolate the problem. 6. At the Hardware View, choose Logs > Event Log. The Event Log displays. Ensure an event code 510 (SFP optics card hot-insertion initiated) displays in the log. If an event code 510 does not display in the log, go to “MAP 0000: Start MAP” on page 45 to isolate the problem. 7.
FRU Removal and Replacement RRP: UPM Filler Blank Use the following procedures to remove or replace a UPM filler blank. Filler blanks cover and protect unused UPM card slots in the director chassis. A list of tools required is provided. Tools Required The torque tool and hex adapter (provided with the director) is required to perform these procedures. Removing the Filler Blank To remove a filler blank: 1. If the director is installed in a stand-alone configuration, go to step 2.
FRU Removal and Replacement 2 1 1 Torque tool 2 UPM filler blank Figure 76: UPM filler blank removal and replacement Replacing the Filler Blank To replace a filler blank: 1. Remove the filler blank from its packaging. 2. Hold the filler blank by its stiffener and insert it in the chassis card track, as shown in Figure 76. 3. To secure the filler blank, sequentially insert the torque tool into each locking Allen screw.
FRU Removal and Replacement RRP: Redundant Power Supply Use the following procedures to remove or replace a redundant power supply. A list of tools required is provided. Tools Required The ESD grounding cable and wrist strap are required to perform these procedures. Removing the Power Supply To remove a redundant power supply: 1. If the director is installed in a stand-alone configuration, go to step 2.
FRU Removal and Replacement 2 1 1 Power supply 2 AC module Figure 77: Redundant power supply removal and replacement Replacing the Power Supply To replace a redundant power supply: 1. Remove the replacement power supply from its protective antistatic bag. 2. Inspect the rear of the power supply for bent or broken connector pins that may have been damaged during shipping. If any pins are damaged, obtain a new power supply. 3.
FRU Removal and Replacement 6. At the Hardware View, choose Logs > Event Log. The Event Log displays. Ensure an event code 207 (power supply installed) displays in the log. If an event code 207 does not display in the log, go to “MAP 0000: Start MAP” on page 45 to isolate the problem. 7.
FRU Removal and Replacement RRP: AC Module Use the following procedures to remove or replace the AC module. A list of tools required is provided. Tools Required The following tools are required to perform these procedures. ■ Standard cross-tip (Phillips) screwdriver. ■ ESD grounding cable and wrist strap. Removing the AC Module To remove the AC module: 1. If the director is installed in a stand-alone configuration, go to step 2.
FRU Removal and Replacement 2 1 1 Power supply 2 AC module Figure 78: AC module removal and replacement Replacing the AC Module To replace an AC module: 1. Remove the replacement AC module from its protective antistatic bag. 2. Inspect the printed wiring assembly (PWA) side of the AC module for bent or broken connector pins that may have been damaged during shipping. If any pins are damaged, obtain a new assembly. 3. Position the AC module at the rear of the director chassis, as shown in Figure 78.
FRU Removal and Replacement 8. Perform one of the following to verify AC module operation: — At the Hardware View, observe the graphic representing the replacement card and ensure no alert symbols display that indicate a failure (yellow triangle or red diamond). If a problem is indicated, go to “MAP 0000: Start MAP” on page 45 to isolate the problem. — At the EWS interface, open the Switch tab at the View panel and ensure no amber LEDs illuminate that indicate an AC module failure.
FRU Removal and Replacement RRP: Redundant SBAR Assembly Use the following procedures to remove or replace a redundant SBAR assembly (two assemblies in the director) with the backup SBAR assembly operational. A list of tools required is provided. Tools Required The following tools are required to perform these procedures. ■ Standard flat-tip screwdriver. ■ ESD grounding cable and wrist strap. ■ Torque tool and hex adapter (provided with the director).
FRU Removal and Replacement 1 1 SBAR assembly Figure 79: SBAR assembly removal and replacement 6. Using the handles, pull the SBAR assembly out of the director chassis. Support the assembly with one hand when performing this step. 7. Place the SBAR assembly in an antistatic bag to provide ESD protection. Replacing the SBAR Assembly To replace a redundant SBAR assembly: 1. Remove the replacement SBAR assembly from its protective antistatic bag. 2.
FRU Removal and Replacement 8. At the Hardware View, choose Logs > Event Log. The Event Log displays. Ensure the following event codes display in the log: — 600—SBAR card hot-insertion initiated. — 601—SBAR card hot-insertion completed. If an event code 601 does not display in the log, go to “MAP 0000: Start MAP” on page 45 to isolate the problem. 9.
FRU Removal and Replacement b. Click the Sys Err Light tab. The Switch page displays with the Sys Err Light tab selected. A System Error Light is ON message displays on the page. c. Click Clear Light. 14. If necessary, close and lock the equipment cabinet door. RRP: Redundant Fan Module Use the following procedures to remove or replace a redundant cooling fan module. A list of tools required is provided. Tools Required The following tools are required to perform these procedures.
FRU Removal and Replacement 1 1 Fan module Figure 80: Fan module removal and replacement Caution: Do not remove a fan module unless the replacement module is available. Operation of the director with only one fan module for an extended period may cause one or more thermal sensors to post event codes. 6. Using the rear of the fan module as a handle, pull the module from the director. Support the fan module with one hand when performing this step. 7.
FRU Removal and Replacement 3. Position the fan module at the rear of the director chassis, as shown in Figure 80. Using the rear of the fan module as a handle, push the module toward the backplane to engage the connector pins. Support the fan module with one hand when performing this step. 4. Using a standard flat-tip screwdriver, tighten the two captive screws that secure the fan module to the director chassis. 5. Disconnect the ESD wrist strap from the director chassis and your wrist. 6.
FRU Removal and Replacement — If at an EWS interface: a. Click the Switch tab at the Operations panel. The Operations panel displays with the Switch page open. b. Click the Sys Err Light tab. The Switch page displays with the Sys Err Light tab selected. A System Error Light is ON message displays on the page. c. Click Clear Light. 13. If necessary, close and lock the equipment cabinet door. RRP: Power Module Assembly Use the following procedures to remove or replace the power module assembly.
FRU Removal and Replacement 4. Follow ESD procedures by attaching a wrist strap to an approved bench grounding point and your wrist. Caution: To avoid causing machine errors or damage while working on the director, follow ESD procedures by connecting a grounding cable to an approved bench grounding point and wearing an ESD wrist strap. 5. Unseat and disconnect (but do not remove) both power supplies (“RRP: Redundant Power Supply” on page 241). 6. Remove the RFI shield. 7.
FRU Removal and Replacement Replacing the Power Module Assembly To replace the power module assembly: 1. Remove the replacement power module assembly from its protective anti-static bag. 2. Replace the power module assembly. 3. Plug the power module assembly cable into the backplane. 4. Replace the center and upper left fan modules (viewed from the rear) (“RRP: Redundant Fan Module” on page 250). 5. Disconnect the ESD wrist strap from the director chassis and your wrist. 6. Replace the RFI shield. 7.
FRU Removal and Replacement b. Click the Sys Err Light tab. The Switch page displays with the Sys Err Light tab selected. A System Error Light is ON message displays on the page. c. Click Clear Light. 13. If necessary, close and lock the equipment cabinet door. RRP: Backplane Use the following procedures to remove or replace the backplane. A list of tools required is provided. Tools Required The following tools are required to perform these procedures.
FRU Removal and Replacement 2. Notify the customer the director will be powered off. Ensure the customer’s system administrator quiesces Fibre Channel frame traffic through the director and sets attached devices offline. 3. If the director is installed in a stand-alone configuration, go to step 4. If the director is rack-mounted, unlock and open the cabinet front and rear doors as directed by the HP authorized service provider. 4. Power off and unplug the director (“Power-Off Procedure” on page 196).
FRU Removal and Replacement 2 1 1 Card cage 2 Backplane assembly Figure 82: Backplane removal and replacement 16. Remove the card cage (1) and backplane assembly (2), as shown in Figure 82. 17. Disconnect the maintenance port cable from the backplane. 18. The backplane is secured to the card cage with 7 panhead Phillips screws. Use a standard Phillips screwdriver to remove these screws. 19. Remove the backplane (PWA and frame as one FRU) from the card cage.
FRU Removal and Replacement 5. Using a standard Phillips screwdriver, tighten the 7 panhead screws that secure the backplane to the card cage. Tighten the screws alternately from bottom to top and from side to side. 6. Connect the maintenance port cable. 7. Replace the card cage and backplane in the director chassis. with 6 panhead Phillips screws. Use a standard Phillips screwdriver to replace the 6 panhead Phillips screws. 8. Plug the Power/System LED assembly cable into the backplane. 9.
FRU Removal and Replacement — Data bits—8 — Parity—None — Stop bits—1 — Flow control—Hardware When the parameters are set, click OK. The HyperTerminal window displays. d. At the C> prompt, type the maintenance-level password (the default is level-2) and press Enter. The password is case sensitive. The HyperTerminal window displays with a C> prompt at the top of the window. e.
FRU Removal and Replacement — If at an EWS interface: a. Click the Switch tab at the Operations panel. The Operations panel displays with the Switch page open. b. Click the Sys Err Light tab. The Switch page displays with the Sys Err Light tab selected. A System Error Light is ON message displays on the page. c. Click Clear Light. 24. If necessary, close and lock the equipment cabinet door.
FRU Removal and Replacement 262 Director 2/140 Service Manual
Illustrated Parts Breakdown 5 This chapter provides an illustrated parts breakdown for all Director 2/140 field-replaceable units (FRUs). Exploded-view assembly drawings are provided for: ■ Front-accessible FRUs ■ Rear-accessible FRUs ■ Miscellaneous parts ■ Power plugs and receptacles Exploded-view illustrations portray the director disassembly sequence for clarity. Illustrated FRUs are numerically keyed to associated parts lists.
Illustrated Parts Breakdown Front-Accessible FRUs Figure 83 illustrates front-accessible FRUs, and Table 27 is the parts list. The table includes reference numbers to Figure 83, part numbers, descriptions, and quantities. 1 7 8 6 5 2 4 3 7 9 Figure 83: Front-accessible FRUs Table 27: Front-Accessible FRU Parts List Ref . 264 Part Number Description Qty.
Illustrated Parts Breakdown Table 27: Front-Accessible FRU Parts List (Continued) Ref . Part Number Description Qty.
Illustrated Parts Breakdown Rear-Accessible FRUs Figure 84 and Figure 85 illustrate rear-accessible FRUs, and Table 28 and Table 29 are the rear-accessible parts lists. The tables include reference numbers to Figure 84 and Figure 85, part numbers, descriptions, and quantities. 1 2 3 3 4 5 8 7 6 Figure 84: Rear-accessible FRUs (part 1) Table 28: Rear-Accessible FRU Parts List (Part 1) Ref . 266 Part Number Description Qty.
Illustrated Parts Breakdown Table 28: Rear-Accessible FRU Parts List (Part 1) (Continued) Ref . Part Number Description Qty.
Illustrated Parts Breakdown 1 2 3 4 Figure 85: Rear-accessible FRUs (part 2) Table 29: Rear-Accessible FRU Parts List (Part 2) Ref. 268 Part Number Description Qty.
Illustrated Parts Breakdown Miscellaneous Parts Table 30 is the parts list for miscellaneous parts. Table 30: Miscellaneous Parts Part Number Description 254138-001 Power cord, 120 VAC, United States 258754-001 Power cord, AC, 5-15R 254139-001 Power cord, AC Adapter/Jumper, 2.5 m 258753-001 Adapter, ac, 100-240 VAC, autosense 254135-001 Torque driver with 5/32 in.
Illustrated Parts Breakdown 270 Director 2/140 Service Manual
Information and Error Messages A This appendix lists information and error messages that display in pop-up message boxes from the HP StorageWorks HA-Fabric Manager (HAFM) application and the associated Element Managers. The first section of the appendix lists HAFM application messages. The second section lists Element Manager messages. The text of each message is followed by a description and recommended course of action.
Information and Error Messages HAFM Application Messages This section lists HAFM application information and error messages in alphabetical order. Table 31: HAFM Messages Message 272 Description Action A zone must have at least one zone member. When creating a new zone, one or more zone members must be added. Add one or more zone members to the new zone using the Modify Zone dialog box. A zone set must have at least one zone. When creating a new zone set, one or more zones must be added.
Information and Error Messages Table 31: HAFM Messages (Continued) Message Description Action Are you sure you want to delete this zone? The selected zone will be deleted from the zone library. Click Yes to delete the zone or No to cancel the operation. Are you sure you want to delete this zone set? The selected zone set will be deleted from the zone library. Click Yes to delete the zone set or No to cancel the operation.
Information and Error Messages Table 31: HAFM Messages (Continued) 274 Message Description Action Cannot display route. All switches in route must be managed by the same server. You cannot show the route between devices that are attached to switches or directors managed by a different HAFM appliance. Make sure devices named in Show Routes dialog box are attached to products managed by this HAFM appliance. Cannot display route. All switches in route must support routing.
Information and Error Messages Table 31: HAFM Messages (Continued) Message Description Action Cannot modify a zone with an invalid name. Rename zone and try again. A zone must have a valid name to be modified. Assign a valid name to the zone, then modify the name through the Modify Zone Set dialog box. Cannot modify product. The selected product cannot be modified. Verify the HAFM appliance-to-product link is up. If the link is up: ■ The HAFM appliance may be busy.
Information and Error Messages Table 31: HAFM Messages (Continued) Message 276 Description Action Cannot show zoning library. No fabric exists. You cannot show the zoning library if no fabric exists. You must have identified a switch or director to the HAFM application for a fabric to exist. Identify an existing switch or director to the HAFM application using the New Product dialog box. Click OK to remove all contents from log. This action deletes all contents from the selected log.
Information and Error Messages Table 31: HAFM Messages (Continued) Message Description Download complete. Click OK and start the HAFM. Download of HAFM and the Element Manager is complete. Start the HAFM application to continue. Duplicate community names require identical write authorizations. If configuring two communities with identical names, they must also have identical write authorizations. Verify that both communities with the same name have the same write authorizations.
Information and Error Messages Table 31: HAFM Messages (Continued) Message 278 Description Action Error connecting to switch. While viewing routes, the HAFM appliance was unable to connect to the switch. The switch failed or the switch-to-HAFM appliance Ethernet link failed. Try the operation again. If the problem persists, contact the next level of support. Error creating zone. The HAFM application encountered an internal error. Try the operation again.
Information and Error Messages Table 31: HAFM Messages (Continued) Message Description Action Fabric member could not be found. A fabric member does not exist when the application prepared to find a route, find a route node, or gather route information on that fabric member. Ensure the product is incorporated into the fabric and retry the operation. If the problem persists, contact the next level of support. Fabric not persisted.
Information and Error Messages Table 31: HAFM Messages (Continued) Message 280 Description Action Invalid name. One of the following invalid names was used: CON, AUX, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9, NUL, or PRN. Choose a valid name and retry the operation. Invalid network address. The IP address specified for the product is unknown to the domain name server (invalid). Verify and enter a valid product IP address.
Information and Error Messages Table 31: HAFM Messages (Continued) Message Description Action Invalid request. Three conditions result in this message: ■ You tried to add or modify a product from Product View and the network address is already in use. (Network addresses must be unique.) ■ You tried to create a new user with a username that already exists. (A username must be unique.) ■ You tried to delete the default Administrator user. (The default Administrator user cannot be deleted.
Information and Error Messages Table 31: HAFM Messages (Continued) Message 282 Description Action Invalid World Wide Name or nickname. The World Wide Name or nickname that you have specified is invalid. The valid format for the World Wide Name is eight two-digit hexadecimal numbers separated by colons (xx:xx:xx:xx:xx: xx:xx:xx). The valid format for a nickname is non blank characters, up to 32 characters. Try the operation again using a valid World Wide Name or nickname. Invalid World Wide Name.
Information and Error Messages Table 31: HAFM Messages (Continued) Message Description Action No management server specified. An HAFM appliance is not defined to the HAFM application. At the HAFM 8 Log In dialog box, type an appliance name in the Server Name field and click Login. No nickname selected. No nickname was selected when the command was attempted. Choose a nickname and try again. No Element Managers installed. No director or switch Element Manager is installed on this workstation.
Information and Error Messages Table 31: HAFM Messages (Continued) Message 284 Description Action No zone set selected or zone set no longer exists. A zoning operation was attempted without a zone set selected, or the zone set you selected no longer exists in the fabric. Choose a zone set and try the operation again. Only attached nodes can be displayed in this mode. You cannot display unused ports when adding ports by World Wide Name. Change the add criteria to Add by Port.
Information and Error Messages Table 31: HAFM Messages (Continued) Message Description Action Routing is not supported by the switch. This switch or director does not support the Show Routes feature. Choose a different switch or director to show the route. SANtegrity Feature not installed. Please contact your sales representative. You selected Fabric Binding or Enterprise Fabric Mode from the Fabrics menu.
Information and Error Messages Table 31: HAFM Messages (Continued) 286 Message Description Action The Domain ID was not accepted. The World Wide Name and Domain ID must be unique in the Fabric Membership List. You attempted to add a detached switch to the Fabric Membership List through the Fabric Binding option (SANtegrity Binding feature), but a switch already exists in the fabric with the same domain ID. Enter a unique domain ID for the switch in the Add Detached Switch dialog box.
Information and Error Messages Table 31: HAFM Messages (Continued) Message Description The maximum number of nicknames has already been configured. The maximum number of nicknames that can be defined to the HAFM application was reached. Delete an existing nickname before adding a new nickname. The maximum number of open products has already been reached. The maximum number of open switches allowed was reached. Close an Element Manager session (existing open product) before opening a new session.
Information and Error Messages Table 31: HAFM Messages (Continued) 288 Message Description Action The maximum number of zones per zone set has already been configured. The maximum number of zones that can be defined in a zone set was reached. Delete an existing zone before adding a new zone to the zone set. The nickname does not exist. The entered nickname does not exist in the fabric. Configure the nickname to the appropriate product or select an existing nickname.
Information and Error Messages Table 31: HAFM Messages (Continued) Message Description Action This switch is currently part of this fabric and cannot be removed from the Fabric Membership List. Isolate the switch from the fabric prior to removing it from the Fabric Membership List. You attempted to remove a switch from the Fabric Membership List using the Fabric Binding option, but the switch is still part of the fabric.
Information and Error Messages Table 31: HAFM Messages (Continued) Message 290 Description Action You must define an SMTP server address. An SMTP server address must be defined and configured for e-mail to be activated. Define the SMTP server address at the Configure E-Mail dialog box. You must define at least one E-mail address. At least one e-mail address must be defined and configured for e-mail to be activated. Define an e-mail address at the Configure E-Mail dialog box.
Information and Error Messages Table 31: HAFM Messages (Continued) Message Description Action Zoning by port number is not supported in Open Fabric Mode. You cannot specify an item for zoning by port number if HAFM is in Open Fabric Mode. Either define zones by WWN of device or change to Homogeneous Fabric mode in the Configure Operation Mode dialog box of the Element Manager. Zoning name already exists. Duplicate zone names are not allowed in the zoning library.
Information and Error Messages Element Manager Messages This section lists Element Manager information and error messages in alphabetical order. Table 32: Element Manager Messages 292 Message Description Action A Preferred Path already exists between this Source Port and this Destination Domain ID. Please re-configure the desired path. For any source port, only one path may be defined to each destination domain ID. On the Add/Change Preferred Path dialog box, change the preferred path.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message Description Action Another Element Manager is currently performing a firmware install. Only one instance of the Element Manager can install a firmware version to the director at a time. Wait for the firmware installation process to complete and try the operation again. Are you sure you want to delete firmware version? This message requests confirmation to delete a firmware version.
Information and Error Messages Table 32: Element Manager Messages (Continued) 294 Message Description Action Cannot disable Insistent Domain ID while Fabric Binding is active. You attempted to disable the Insistent Domain ID parameter through the Configure Switch Parameters dialog box, but Fabric Binding is enabled. Disable Fabric Binding through the Fabric Binding dialog box before disabling these parameters. Cannot enable beaconing on a failed FRU.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message Description Action Cannot have E-Ports if Management Style is FICON unless SANtegrity feature is installed. Please contact your sales representative. Firmware is below the required level and you attempted to change management style from Open Systems to FICON management style with E_Ports configured, but SANtegrity Binding is not installed. Informational message.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message 296 Description Action Cannot retrieve current SNMP configuration. The director SNMP configuration cannot be retrieved by the Element Manager because the Ethernet link is down or busy. Retry the operation later. If the condition persists, contact the next level of support. Cannot retrieve diagnostics results.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message Description Action Cannot run diagnostics on a port that is failed. Port diagnostics (loopback tests) cannot be performed on a port that has failed any previous diagnostic (power-on diagnostic, online diagnostic, or loopback test). The amber LED associated with the port illuminates to indicate the failed state. Reset the port and perform diagnostics again. Cannot run diagnostics on an active E-port.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message 298 Description Action Cannot save port configuration. The port configuration cannot be saved at the Element Manager because the Ethernet link is down or busy. Retry the operation later. If the condition persists, contact the next level of support. Cannot save SNMP configuration. The SNMP configuration cannot be saved at the Element Manager because the Ethernet link is down or busy. Retry the operation later.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message Description Action Cannot set switch date and time. The switch date and time cannot be set at the Element Manager because the Ethernet link is down or busy. Retry the operation later. If the condition persists, contact the next level of support. Cannot set switch state. The director or switch state cannot be set at the Element Manager because the Ethernet link is down or busy. Retry the operation later.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message 300 Description Action Connection to management server lost. Click OK to exit application. The HAFM application at a remote workstation lost the network connection to the HAFM appliance. Start the HAFM application to connect to the HAFM appliance. Continuing may overwrite host programming. Continue? Configurations sent from the host may be overwritten by HAFM.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message Description Control Unit Port (CUP) name and port name are identical (FICON ONLY). Within the address configuration, one or more of the port names are the same as the CUP name. Make sure all names are unique for the ports and CUP name. Date entered is invalid. The date is entered incorrectly at the Configure Date and Time dialog box.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message 302 Description Action Director must be offline to configure. Clock alert mode is enabled through the Configure FICON Management Server dialog box and you attempted to enable Periodic Date/Time Synchronization through the Configure Date and Time dialog box. Disable clock alert mode through the Configure FICON Management Server dialog box. Disabling Insistent Domain ID will disable Fabric Binding.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message Description Action Duplicate Community names require identical write authorizations. Duplicate community names are entered at the Configure SNMP dialog box, and have different write authorizations. Delete the duplicate community name or make the write authorizations consistent. Element Manager error . The Element Manager encountered an internal error and cannot continue.
Information and Error Messages Table 32: Element Manager Messages (Continued) 304 Message Description Action Error transferring files < message >. An error occurred while transferring files from the PC hard drive to the Element Manager. The message varies, depending on the problem. Try the file transfer operation again. If the problem persists, contact the next level of support. Feature not supported. The ‘product name’ must be running version 05.00.00 or higher.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message Description Action Firmware file I/O error. A firmware download operation aborted because a file I/O error occurred. Retry the operation. If the problem persists, contact the next level of support. Firmware file not found. The firmware version is not installed (or was deleted) from the firmware library at the HAFM appliance. Add the firmware version to the library and retry the operation.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message 306 Description Action Invalid configuration name. Attempted to save an address configuration name with an invalid name. Use up to 24 alphanumeric characters, including spaces, hyphens, and underscores. Invalid feature key. The feature key was not recognized. Re-enter the feature key.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message Description Action Invalid response received from director. An error occurred at the director during a firmware download operation. Retry the firmware download operation. If the problem persists, contact the next level of support. Invalid serial number for this feature key. The serial number and the feature key did not match.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message 308 Description Action Invalid value for E_D_TOV. At the Configure Fabric Parameters dialog box, the error detect time-out value (E_D_TOV) must be an integer from 2 through 600 inclusive. Verify and enter a valid number. Invalid value for hour (0-23). At the Configure Date and Time dialog box, the HH value (hour) must be an integer from 0 through 23 inclusive. Verify and enter a valid time.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message Description Action Invalid value for threshold (1-99)%. Value entered for each port in the Configure Open Trunking dialog box must be in the range from 1 to 99. This message only displays if the optional Open Trunking feature is installed. Enter a number from 1 to 99 into the Threshold % column of the Configure Open Trunking dialog box. Invalid value for year.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message 310 Description Action Maximum number of versions already installed. The number of firmware versions that can be defined to the HAFM application’s firmware library (eight) was reached. Delete an existing firmware version before adding a new version. No file was selected. Action requires the selection of a file. Select a file. No firmware version file was selected.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message Description Action Open Trunking is not installed for this product. Please contact your sales representative. The Open Trunking feature key has not been enabled. This message only displays if the optional Open Trunking feature is installed. Enter the feature key into the Configure Feature Key dialog box and enable the key. If you require a feature key, see your account representative.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message 312 Description Action Port cannot swap to itself. Port addresses entered in the Swap Ports dialog box are the same. Ensure that address in the first and second Port Address fields are different. Port diagnostics cannot be performed on an inactive port. This displays when port diagnostics is run on a port in an inactive state. Run the diagnostics on an active port.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message Description Action SANtegrity Feature not installed. Please contact your sales representative. You selected Switch Binding from the Configure menu, but the optional SANtegrity Binding feature is not installed. Install the SANtegrity Binding key through the Configure Feature Key dialog box before using Switch Binding features. Send firmware failed. A firmware download operation failed.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message 314 Description Action The add firmware process has been aborted. You aborted the process to add a firmware version to the HAFM appliance’s firmware library. Verify the firmware addition is to be aborted, then click OK to continue. Switch clock alert mode must be cleared before enabling period synchronization.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message Description Action The following parameters cannot be disabled while Enterprise Fabric Mode is active: Insistent Domain ID, Rerouting Delay, Domain RSCNs. You attempted to disable these parameters in the Configure Switch Parameters dialog box while Enterprise Fabric Mode is enabled. Disable Enterprise Fabric Mode through the Enterprise Fabric Mode dialog box in HAFM, then disable the parameters.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message 316 Description Action The switch did not respond in the time allowed. While waiting to perform a requested action, the director or switch timed out. Retry the operation. If the condition persists, contact the next level of support. The switch is busy saving maintenance information. The director or switch cannot perform the requested action because it is busy saving maintenance information.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message Description Action This feature key does not include all of the features currently installed. Do you want to continue with feature key activation? The feature set currently installed for this system contains features that are not being installed with the new feature key. Click Yes to activate the feature key and remove current features not in the new feature set or No to cancel.
Information and Error Messages 318 Error Messages
Event Code Tables B An event is an occurrence (state change, problem detection, or problem correction) that requires user attention or that should be reported to a system administrator or service representative. An event usually indicates a switch operational state transition, but may also indicate an impending state change (threshold violation). An event may also provide information only, and not indicate an operational state change. Events are reported as event codes.
Event Code Tables — Major — Severe (not operational) 320 ■ Explanation—a complete explanation of what caused the event. ■ Action-the recommended course of action (if any) to resolve the problem. ■ Event Data—supplementary event data (if any) that displays in the Event Log in hexadecimal format. ■ Distribution—check marks in associated fields indicate where the event code is reported (director, HAFM appliance, or host).
Event Code Tables System Events (000 through 199) Event Code: 001 Message: System power-down. Severity: Informational. Explanation : The director was powered off or disconnected from the facility AC power source. The event code is distributed the next time the director powers on, but the date and time of the code reflect the power-off time. Action: No action required. Event Data: No supplementary data included with the event.
Event Code Tables Event Code: 011 Message: Login Server database invalid. Severity: Minor. Explanation: Following a CTP card failover or replacement, initial machine load (IML), or firmware download, the Login Server database failed its cyclic redundancy check (CRC) validation. All Fabric Services databases are initialized to an empty state, resulting in an implicit fabric logout of all attached devices. Action: Perform the data collection procedure and return the backup CD to HP support personnel.
Event Code Tables Event Code: 021 Message: Name Server database invalid. Severity: Minor. Explanation: Following a CTP card failover or replacement, IML, or firmware download, the Name Server database failed its CRC validation. All Fabric Services databases are initialized to an empty state, resulting in an implicit fabric logout of all attached devices. Action: Perform the data collection procedure and return the backup CD to HP support personnel.
Event Code Tables Event Code: 050 Message: Management Server unable to synchronize databases. Severity: Minor. Explanation: Following a CTP card reset or replacement, the HAFM appliance attempted to acquire an up-to-date copy of its databases from the other CTP card, but failed. All Management Services databases are initialized to an empty state, resulting in an implicit logout of all devices logged in to the HAFM appliance.
Event Code Tables Event Code: 052 Message: Management Server internal error, asynchronous status report activation, or mode register update occurred. Severity: Informational. Explanation: An internal operating error was detected by the HAFM appliance subsystem, an asynchronous status was reported to an attached host, or a mode register update occurred. Action: HAFM appliance internal error: Perform the data collection procedure and return the backup CD to HP Services support personnel.
Event Code Tables Distribution: Director EWS Event Log HAFM appliance System Error LED ✔ ✔ Event Log ✔ E-Mail ✔ Host Call Home Sense Info Link Incident ✔ Event Code: 061 Message: Fabric Controller database invalid. Severity: Minor. Explanation: Following a CTP card failover or replacement, IML, or firmware download, the Fabric Controller database failed its CRC validation.
Event Code Tables Distribution: Director EWS Event Log HAFM appliance System Error LED ✔ Event Log E-Mail Host Call Home Sense Info Link Incident ✔ Event Code: 063 Message: Remote switch has too many ISLs. Severity: Major. Explanation: The fabric element (director or switch) whose domain ID is indicated in the event data has too many ISLs attached, and that element is unreachable from this director. Please refer to the release notes for the supported number of interswitch links.
Event Code Tables Event Data: 328 The first byte of event data (byte 0) specifies the E_Port number. The fifth byte (byte 4) specifies the segmentation reason as follows: 1 = Incompatible operating parameters. Ether the resource allocation time out value (R_A_TOV) or error detect time out value (E_D_TOV) is inconsistent between the Director 2/140 and another fabric element (director or switch). Modify the R_A_TOV and E_D_TOV to make the values consistent for all fabric directors and switches.
Event Code Tables Event Code: 070 (continued) Distribution: Director EWS Event Log HAFM appliance System Error LED ✔ Event Log E-Mail Host Call Home Sense Info Link Incident ✔ Event Code: 071 Message: Director is isolated. Severity: Informational. Explanation: The director is isolated from other fabric elements (directors or switches). This event code is accompanied by one or more 070 event codes. Refer to the event data for the segmentation reason.
Event Code Tables Event Code: 071 (continued) Event Data (continued): 4 = Build fabric protocol error. A protocol error was detected during incorporation of the Director 2/140 into the fabric. Disconnect the E_Port link, then reconnect the link. If the condition persists, perform the data collection procedure and return the backup CD to HP support personnel. 5 = No principal switch. No director or switch in the fabric can become the principal switch. Modify the switch priority to any value other than 255.
Event Code Tables Event Code: 073 Message: Fabric initialization error. Severity: Informational. Explanation: An error was detected during the fabric initialization sequence, most likely caused by frame delivery errors. Event data is intended for engineering evaluation. Action: Perform the data collection procedure and return the backup CD to HP Services support personnel. Event Data: Byte 0 = error reason code for engineering evaluation. Byte 1 = reserved.
Event Code Tables Event Code: 080 Message: Unauthorized worldwide name. Severity: Informational. Explanation: The worldwide name of the device or director plugged in the indicated port is not authorized for that port. Action: Change the port binding definition or plug the correct device or director into this port. Event Data: Byte 0 = Port number reporting the unauthorized connection. Bytes 1–3 = reserved. Bytes 4–11 = WWN of the unauthorized device or fabric element.
Event Code Tables Event Data: The first byte of event data (byte 0) specifies the port number. The fifth byte (byte 4) specifies the isolation reason as follows: 1 = Unknown–Isolation reason is unknown, but probably caused by failure of a device attached to the director through an E_Port connection. Fault isolate the failed device or contact support personnel to report the problem. 2 = ISL connection not allowed–The port connection conflicts with the configured port type.
Event Code Tables Event Data Continued: A = Unauthorized port binding WWN–The device WWN or nickname used to configure port binding for this port is not valid. Reconfigure the port with the WWN or nickname authorized for the attached device. B = Unresponsive node–The attached node did not respond, resulting in a G_Port ELP timeout. Check the status of the attached device and clean the link’s fiber optic components (cable and connectors).
Event Code Tables Event Code: 090 Message: Database replication time out. Severity: Minor Explanation: Replication of a Fabric Services database from master CTP to backup has timed out. The backup CTP has been dumped and IPLed. After the backup CTP completes the IPL, its databases will be brought up to date and replication will resume.
Event Code Tables Event Code: 120 Message: Error detected while processing system management command. Severity: Informational. Explanation: This event occurs when the director receives an HAFM Management command that violates specified boundary conditions, typically as a result of a network error. The director rejects the command, drops the director-to-HAFM appliance Ethernet link, and forces error recovery processing. When the link recovers, the command can be retried.
Event Code Tables Event Code: 140 Message: Congestion detected on an ISL. Severity: Informational. Explanation: Open Trunking firmware detected an ISL with Fibre Channel traffic that previously exceeded the configured congestion threshold. Action: No action is required for an isolated event. If this event persists, relieve the congestion by adding parallel ISLs, increasing the ISL link speed, or moving device connections to a less-congested region of the fabric.
Event Code Tables Event Code: 142 Message: Low BB_Credit detected on an ISL. Severity: Informational. Explanation: Open Trunking firmware detected an ISL with no transmission BB_Credit for a period of time that exceeded the configured low BB_Credit threshold. This indicates downstream fabric congestion. Action: No action is required for an isolated event or if the reporting ISL approaches 100% throughput.
Event Code Tables Event Code: 150 Message: Zone merge failure. Severity: Informational. Explanation: During ISL initialization, the zone merge process failed. Either an incompatible zone set was detected or a problem occurred during delivery of a zone merge frame. This event code always precedes a 070 ISL segmentation event code, and represents the reply of an adjacent fabric element in response to a zone merge frame. Refer to the event data for the failure reason.
Event Code Tables Event Data: 340 Bytes 0–3 of the event data specify affected E_Port number(s). Bytes 8–11 specify the failure reason as follows: 01 = Invalid data length–An invalid data length condition caused an error in a zone merge frame. Disconnect the E_Port link, then reconnect the link. If the condition persists, perform the data collection procedure and return the backup CD to HP support personnel. 08 = Invalid zone set format–An invalid zone set format caused an error in a zone merge frame.
Event Code Tables Distribution: Director EWS Event Log ✔ Director 2/140 Service Manual HAFM appliance System Error LED ✔ Event Log E-Mail Host Call Home Sense Info Link Incident ✔ 341
Event Code Tables Power Supply Events (200 through 299) Event Code: 200 Message: Power supply AC voltage failure. Severity: Major. Explanation: Alternating current (AC) input to the indicated power supply is disconnected or AC circuitry in the power supply failed. The second power supply assumes the full operating load for the director. Action: Ensure the power supply is connected to facility AC power, and verify operation of the facility power source.
Event Code Tables Event Code: 202 Message: Power supply thermal failure. Severity: Major. Explanation: The thermal sensor associated with a power supply indicates an overheat condition that shut down the power supply. The second power supply assumes the full operating load for the director. Action: Replace the failed power supply. Perform the data collection procedure and return the backup CD and failed power supply to HP support personnel.
Event Code Tables Event Code: 204 Message: Power supply DC voltage recovery. Severity: Informational. Explanation: DC voltage recovered for the power supply. Both power supplies adjust to share operating load for the director. Action: No action required. Event Data: No supplementary data included with the event. Distribution: Director EWS Event Log HAFM appliance System Error LED ✔ Event Log E-Mail Host Call Home Sense Info Link Incident ✔ Event Code: 206 Message: Power supply removed.
Event Code Tables Event Code: 207 Message: Power supply installed. Severity: Informational. Explanation: A redundant power supply was installed with the director powered on and operational. Both power supplies adjust to share operating load for the director. Action: No action required. Event Data: No supplementary data included with the event.
Event Code Tables Fan Module Events (300 through 399) Event Code: 300 Message: Cooling fan propeller failed. Severity: Major. Explanation: One cooling fan (out of six) failed or is rotating at insufficient angular velocity. The remaining fans are operational. The amber LED illuminates at the rear of the fan module associated with the failed fan. Action: Replace the indicated fan module. Event Data: The first byte of event data (byte 0) specifies the failed fan number.
Event Code Tables Event Code: 302 Message: Cooling fan propeller failed. Severity: Major. Explanation: Three cooling fans (out of six) failed or are rotating at insufficient angular velocity. The remaining fans are operational. The amber LED illuminates at the rear of the fan modules associated with the failed fans. Action: Replace the indicated fan modules. Event Data: The first byte of event data (byte 0) specifies the failed fan numbers.
Event Code Tables Event Code: 304 Message: Cooling fan propeller failed. Severity: Major. Explanation: Five cooling fans (out of six) failed or are rotating at insufficient angular velocity. The remaining fan is operational. The amber LED illuminates at the rear of both fan modules. Action: Replace both fan modules Event Data: The first byte of event data (byte 0) specifies the failed fan numbers.
Event Code Tables Event Code: 310 Message: Cooling fan propeller recovered. Severity: Informational. Explanation: One cooling fan (out of six) recovered or the associated fan module was replaced. All fans are operational. Action: No action required. Event Data: The first byte of event data (byte 0) specifies the recovered fan number.
Event Code Tables Event Code: 312 Message: Cooling fan propeller recovered. Severity: Informational. Explanation: Three cooling fans (out of six) recovered or the associated fan modules were replaced. All fans are operational. Action: No action required. Event Data: The first byte of event data (byte 0) specifies the recovered fan numbers.
Event Code Tables Event Code: 314 Message: Cooling fan propeller recovered. Severity: Informational. Explanation: Five cooling fans (out of six) recovered or the associated fan modules were replaced. All fans are operational. Action: No action required. Event Data: The first byte of event data (byte 0) specifies the recovered fan numbers.
Event Code Tables Event Code: 320 Message: Fan module removed. Severity: Major. Explanation: A fan module was removed with the director powered on and operational. Action: Replace the indicated fan module. Event Data: No supplementary data included with the event. Distribution: Director EWS Event Log HAFM appliance System Error LED ✔ ✔ Event Log E-Mail Host Call Home Sense Info Link Incident ✔ Event Code: 321 Message: Fan module installed. Severity: Informational.
Event Code Tables CTP Card Events (400 through 499) Event Code: 400 Message: Power-up diagnostics failure. Severity: Major. Explanation: Power-on self tests (POSTs) detected a faulty field-replaceable unit (FRU) as indicated by the event data. Action: Replace the failed FRU with a functional FRU. Perform the data collection procedure and return the backup CD and faulty FRU to HP support personnel.
Event Code Tables Distribution: Director EWS Event Log HAFM appliance System Error LED Event Log ✔ E-Mail Host Call Home Sense Info Link Incident ✔ Event Code: 411 Message: Firmware fault. Severity: Major. Explanation: Firmware executing on the indicated CTP card encountered an unexpected operating condition and dumped the operating state to FLASH memory for retrieval and analysis.
Event Code Tables Distribution: Director EWS Event Log HAFM appliance System Error LED Event Log ✔ E-Mail Host Call Home Sense Info Link Incident ✔ Event Code: 413 Message: Backup CTP card POST failure. Severity: Major. Explanation: A backup CTP card was installed in the director and failed POSTs. Action: Replace the indicated CTP card with a functional card. Perform the data collection procedure and return the backup CD and faulty card to HP support personnel.
Event Code Tables Event Code: 415 Message: Backup CTP card removed. Severity: Informational. Explanation: The backup CTP card was removed while the director was powered on and operational. Action: No action required or install an operational backup CTP card. Event Data: No supplementary data included with this event.
Event Code Tables Distribution: Director EWS Event Log HAFM appliance System Error LED ✔ Event Log E-Mail Host Call Home Sense Info Link Incident ✔ Event Code: 418 Message: User-initiated CTP card switchover. Severity: Informational. Explanation: The backup CTP card became the active CTP card after a user-initiated switchover. The previously active CTP card is now the backup CTP card. Action: No action required. Event Data: No supplementary data included with this event.
Event Code Tables Event Code: 421 Message: Firmware download complete. Severity: Informational. Explanation: A director firmware version was downloaded from the HAFM appliance or Embedded Web Server interface. The event data indicates the firmware version in hexadecimal format xx.yy.zz bbbb, where xx is the release level, yy is the maintenance level, zz is the interim release level, and bbbb is the build ID. Action: No action required. Event Data: Bytes 0 and 1 = release level (xx).
Event Code Tables Event Code: 423 Message: CTP firmware download initiated. Severity: Informational. Explanation: The HAFM appliance initiated download of a new firmware version to the director. Action: No action required. Event Data: No supplementary data included with this event. Distribution: Director EWS Event Log HAFM appliance System Error LED ✔ Event Log E-Mail Host Call Home Sense Info Link Incident ✔ Event Code: 426 Message: Multiple ECC single-bit errors occurred.
Event Code Tables Event Code: 430 Message: Excessive Ethernet transmit errors. Severity: Informational. Explanation: Transmit error counters for the active CTP card Ethernet adapter (sum of all counters) exceeded a threshold. This does not indicate a CTP card failure; it indicates a problem with the Ethernet cable, hub, or device on the same Ethernet segment. Event data counters are represented in hexadecimal format with the least significant byte first.
Event Code Tables Action: Verify the Ethernet cable, hub, and other devices are properly connected and operational. Event Data: Bytes 0 through 3 = sum of all receive errors (total_recv_error). Bytes 4 through 7 = frame count where received frame had from 1 to 7 bits after last received full byte (dribble_bits_cnt). CRC error counter updated but frame not processed. Bytes 8 through 11 = frame count where received frame had bad CRC (CRC_error_cnt). Frame not processed.
Event Code Tables Event Code: 433 Message: Nonrecoverable Ethernet fault. Severity: Major. Explanation: A nonrecoverable error was detected on the CTP card Ethernet adapter and the LAN connection to the HAFM appliance or Internet terminated. All Fibre Channel switching functions remain unaffected. This event only occurs on a director with a single CTP card. Because Ethernet communication is lost, no failure indication is externally reported. Action: Replace the CTP card with a functional card.
Event Code Tables Event Code: 442 Message: Embedded port anomaly detected. Severity: Informational. Explanation: The CTP card detected a deviation in the normal operating mode or status of the embedded port. Action: No action required. An additional event code is generated if this incident exceeds an error threshold or results in a port failure. Event Data: Byte 0 = port number. Byte 1 = engineering reason code.port. Bytes 4 through 7 = elapsed millisecond tick count.
Event Code Tables Event Data: Bytes 0-12 are the sequence number from the system VPD. Bytes 13-31 are the OEM serial number obtained from the system VPD. Distribution: Director EWS Event Log HAFM appliance System Error LED ✔ Event Log E-Mail Host Call Home Sense Info Link Incident ✔ Event Code: 451 Message: Switch speed incompatibility detected.
Event Code Tables Event Data: None Distribution: Director EWS Event Log HAFM appliance System Error LED Event Log ✔ E-Mail Host Call Home Sense Info Link Incident ✔ Event Code: 453 Message: New feature key installed. Severity: Informational. Explanation: This event occurs when a new feature key is installed from the HAFM appliance or Embedded Web Server interface. The director performs an IPL when the feature key is enabled. Event data indicates which feature or features are installed.
Event Code Tables Action: The director found request data from the management tool to be larger or smaller than expected. The connection to the management tool will be temporarily lost. After the link is re-established, verify that all information changed in the managing tool is within the specified ranges. For example, verify that the zones and zone members in a zone set fall within the limits stated in the user manual. Try sending the request again.
Event Code Tables UPM Card Events (500 through 599) Event Code: 500 Message: UPM card hot-insertion initiated. Severity: Informational Explanation: Installation of a UPM card was initiated with the director powered on and operational. The event indicates that operational firmware detected the presence of the UPM card, but the card is not seated. When the card is seated in the director chassis and identified by firmware, an event code 501 is generated.
Event Code Tables Event Code: 502 Message: UPM card anomaly detected. Severity: Informational. Explanation: The CTP card detected a deviation in the normal operating mode or status of the indicated four-port UPM card. Action: No action required. An event code 504 is generated if the UPM card fails. Event Data: Byte 0 = UPM slot position (00 through 0F). Byte 1 = engineering reason code. Bytes 4 through 7 = elapsed millisecond tick count.
Event Code Tables Distribution: Director EWS Event Log HAFM appliance System Error LED ✔ Event Log E-Mail Host Call Home Sense Info Link Incident ✔ Event Code: 504 Message: UPM card failure. Severity: Major. Explanation: The indicated UPM card failed. Action: Replace the indicated UPM card with a functional UPM card of the same type. Perform the data collection procedure and return the backup CD and faulty card to HP support personnel.
Event Code Tables Event Data: Byte 0 = UPM slot position (00 through 0F). Bytes 4 through 7 = elapsed millisecond tick count. Bytes 8 and 9 = detected module identifier. Distribution: Director EWS Event Log HAFM appliance System Error LED Event Log ✔ E-Mail Host Call Home Sense Info Link Incident ✔ Event Code: 506 Message: Fibre Channel port failure. Severity: Major. Explanation: A Fibre Channel port on a UPM card failed.
Event Code Tables Event Code: 507 Message: Loopback diagnostics port failure. Severity: Informational. Explanation: A loopback diagnostic test detected a Fibre Channel port failure. Action: No action required. An event code 506 is generated if this diagnostic failure results in a hard port failure. Event Data: Byte 0 = port number (0-127 and 132-143). Byte 1 = engineering reason code. Bytes 4 through 7 = elapsed millisecond tick count. Bytes 8 through 11 = reason code specific.
Event Code Tables Event Data: Byte 0 = port number (0-127 and 132-143). Byte 1 = anomaly reason code. Bytes 4 through 7 = elapsed millisecond tick count. Bytes 8 and 9 = high-availability error callout #1. Bytes 10 and 11 = high-availability error callout #2. Byte 12 = detecting port. Byte 13 = connected port. Byte 14 = participating SBAR assembly. Bytes 16 and 17 = high-availability error callout #3. Bytes 18 and 19 = high-availability error callout #4.
Event Code Tables Distribution: Director EWS Event Log HAFM appliance System Error LED ✔ ✔ Event Log E-Mail ✔ Host Call Home Sense Info ✔ ✔ ✔ Link Incident Event Code: 510 Message: SFP optical transceiver hot-insertion initiated. Severity: Informational. Explanation: Installation of a small form factor pluggable (SFP) optical transceiver was initiated with the director powered on and operational. The event indicates that operational firmware detected the presence of the transceiver.
Event Code Tables Distribution: Director EWS Event Log HAFM appliance System Error LED ✔ Event Log E-Mail Host Call Home Sense Info Link Incident ✔ Event Code: 513 Message: SFP optical transceiver hot-removal completed. Severity: Informational. Explanation: An SFP optical transceiver was removed while the director was powered on and operational. Action: No action required. Event Data: Byte 0 = port number (0-127 and 132-143). Bytes 4 through 7 = elapsed millisecond tick count.
Event Code Tables Distribution: Director EWS Event Log ✔ HAFM appliance System Error LED Event Log ✔ ✔ E-Mail ✔ Host Call Home Sense Info ✔ ✔ Link Incident Event Code: 581 Message: Implicit incident. Severity: Major. Explanation: An attached OSI or FICON server recognized a condition caused by an event that occurred at the server. The event caused an implicit Fibre Channel link incident.
Event Code Tables Distribution: Director EWS Event Log HAFM appliance System Error LED Event Log E-Mail Host Call Home Sense Info Link Incident ✔ ✔ Event Code: 583 Message: Loss of signal or loss of synchronization. Severity: Major. Explanation: An attached OSI or FICON server recognized a loss-of-signal condition or a loss-of-synchronization condition that persisted for more than the specified receiver-transmitter timeout value (R_T_TOV).
Event Code Tables Distribution: Director EWS Event Log HAFM appliance System Error LED Event Log E-Mail Host Call Home Sense Info Link Incident ✔ ✔ Event Code: 585 Message: Primitive sequence timeout. Severity: Major. Explanation: An attached OSI or FICON server recognized either a link reset (LR) protocol timeout or a timeout while waiting for the appropriate response (while in a NOS receive state and after NOS was no longer recognized).
Event Code Tables Distribution: Director EWS Event Log HAFM appliance System Error LED Event Log ✔ 378 E-Mail Host Call Home Sense Info Link Incident ✔ Director 2/140 Service Manual
Event Code Tables SBAR Assembly Events (600 through 699) Event Code: 600 Message: SBAR assembly hot-insertion initiated. Severity: Informational Explanation: Installation of a backup SBAR was initiated with the director powered on and operational. The event indicates that operational firmware detected the presence of the SBAR, but the SBAR is not seated. When the SBAR is seated in the director chassis and identified by firmware, an event code 601 is generated.
Event Code Tables Event Code: 602 Message: SBAR assembly anomaly detected. Severity: Informational. Explanation: Director operational firmware detected a deviation in the normal operating mode or operating status of the indicated SBAR assembly. Action: No action required. An event code 604 is generated if the SBAR assembly fails. Event Data: Byte 0 = SBAR slot position (00 or 01). Byte 1 = anomaly reason code. Bytes 4 through 7 = elapsed millisecond tick count.
Event Code Tables Event Code: 603 Message: SBAR assembly hot-removal completed. Severity: Informational. Explanation: An SBAR assembly was removed with the director powered on and operational. Action: No action required. Event Data: Byte 0 = SBAR slot position (00 or 01). Bytes 4 through 7 = elapsed millisecond tick count.
Event Code Tables Event Code: 605 Message: SBAR assembly revision not supported. Severity: Minor. Explanation: The indicated SBAR assembly is not recognized and displays as uninstalled to the director firmware. Action: Ensure the director model supports the operating firmware version. If the firmware version is supported, replace the SBAR assembly with a functional assembly. Perform the data collection procedure and return the backup CD and faulty assembly to HP support personnel.
Event Code Tables Thermal Events (800 through 899) Event Code: 800 Message: High temperature warning (UPM card thermal sensor). Severity: Major. Explanation: The thermal sensor associated with a UPM card indicates the warm temperature threshold was reached or exceeded. Action: Replace the indicated UPM card with a functional UPM card of the same type. Perform the data collection procedure and return the backup CD and faulty card to HP support personnel.
Event Code Tables Event Code: 802 Message: UPM card shutdown due to thermal violation. Severity: Major. Explanation: An UPM card failed and was powered off because of excessive heat. This event follows an indication that the hot temperature threshold was reached or exceeded (event code 801). Action: Replace the failed UPM card with a functional UPM card of the same type. Perform the data collection procedure and return the backup CD and faulty card to HP support personnel.
Event Code Tables Event Code: 806 Message: Critically hot temperature warning (SBAR assembly thermal sensor). Severity: Major. Explanation: The thermal sensor associated with an SBAR assembly indicates the hot temperature threshold was reached or exceeded. Action: Replace the indicated SBAR assembly with a functional assembly. Perform the data collection procedure and return the backup CD and faulty assembly to HP support personnel. Event Data: No supplementary data included with this event.
Event Code Tables Event Code: 810 Message: High temperature warning (CTP card thermal sensor). Severity: Major. Explanation: The thermal sensor associated with a CTP card indicates the warm temperature threshold was reached or exceeded. Action: Replace the indicated CTP card with a functional card. Perform the data collection procedure and return the backup CD and faulty card to HP support personnel. Event Data: No supplementary data included with this event.
Event Code Tables Event Code: 812 Message: CTP card shutdown due to thermal violation. Severity: Major. Explanation: A CTP card failed and was powered off because of excessive heat. This event follows an indication that the hot temperature threshold was reached or exceeded (event code 811). If the active CTP card fails, the backup card takes over operation. If the backup CTP card fails, the active card is not impacted. Action: Replace the failed CTP card with a functional card.
Event Code Tables 388 Director 2/140 Service Manual
index 10/100 BaseT ethernet hub 20 A backing up, director configuration file 213 backplane removing and replacing 256 beaconing fault isolation 21 blocking port 202 UPM card 203 C call-home notification information, use of 163 reporting 29 channel wrap test, procedure 189 cleaning fiber-optic components 194 configuration changes, audit log 163 configuration data Director 2/140 Service Manual Index B Index AC filter module removal 253 AC module removing and replacing 244 applications management servi
Index diagnostic features, software 24 displaying information 184 element manager messages 292 embedded web server 27 ethernet link, MAP 92 event codes 319 event log recording events 319 fault isolation 21, 45 firmware 27 firmware library dialog box 206 firmware, release notes 207 general description 20 illustrated parts breakdown 263 IPL procedure 197 MAPs 34 ports blocking or unblocking 202 port list view 169 power-off procedure 196 power-on procedure 195 reset 198 setting online or offline 200 SNMP trap
Index exporting 165 viewing 165 exporting events 165 F fabric logout, MAP 138 fabric manager logs, list of 163 MAP 83 messages 272, 292 factory default settings, resetting 214 failure analysis 193 fan module removing and replacing 250 fan module events, event codes tables 346 fan modules MAP 107 fault isolation customer checklist 45 diagnostics 33 logs 163 maintenance approach 21 MAPs 34 SNMP traps 28 FC-PH 4.
Index H HAFM appliance ethernet link, MAP 92 event log 319 fault isolation 21 MAP 45 firmware versions, storing 206 MAP 83, 153 name 48, 86, 91, 100, 156, 158, 220 HAFM application diagnostic features 24 logs, list of 163 MAP 83 messages 272 hardware view displaying director information 184 hardware, MAP 153 help online user documentation 28 help, obtaining 17 hexagonal adapter 30 HP authorized reseller 17 firmware versions 207 home page 207 storage web site 17 technical support 17 hp StorageWorks director
Index MAP 0100-Power Distribution Analysis 69 MAP 0200-POST or IML Failure Analysis 78 MAP 0300-Console Application Problem Determination 83 MAP 0400-Loss of Console Communication 92 MAP 0500-FRU Failure Analysis 107 MAP 0600-Port Card Failure and Link Incident Analysis 115 MAP 0700-Fabric, ISL, and Segmented Port Problem Determination 138 quick start 34 messages element manager 292 fabric manager 272, 292 HAFM application 272 Microsoft Internet Explorer version 27 monitor panel 27 multiswitch fabric e_por
Index procedures blocking ports 202 data collection 192 external loopback test 187 FRU removal 223 FRU replacement 223 installing software 218 internal loopback test 184 IPL 197 managing configuration data 213 managing firmware versions 206 MAPs 34 power-off 196 power-on 195 reset 198 setting offline 200 setting online 200 unblocking ports 203 upgrading software 218 ProComm Plus 32 protective plug 30 Q quick start, MAPs 34 R rack stability, warning 16 rear-accessible FRUs, parts list 266 related document
Index traps, list of 28 software diagnostic features 24 installing 218 management services application 25 upgrading 218 spare parts See FRUs statistical information, performance view 171 status table director 25 subnet mask, default 34 swapping ports, procedure 190 symbols in text 13 symbols on equipment 14 system events 21 event codes tables 321 T TCP/IP MIB-II 28 technical support, HP 17 text symbols 13 thermal events, event codes tables 383 threshold alert port properties dialog box 177 reasons for 177
Index rack stability 16 symbols on equipment 14 web sites HP storage 17 Windows 2000 operating system MAP 83 396 Windows operating systems, versions 32 wrap plug multimode 30 singlemode 30 WWN port properties dialog box 175 Director 2/140 Service Manual
