Service Manual hp StorageWorks Director 2/64 Product Version: FW v06.xx/HAFM SW v08.02.00 Fourth Edition (July 2004) Part Number: AA–RS2ED–TE This guide provides procedures for servicing the HP StorageWorks Director 2/64.
© Copyright 2001–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 Tools and Test Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tools Supplied with the Director . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tools Supplied by Service Personnel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Performing Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internal Loopback Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External Loopback Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Wrap Test (FICON) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Swapping Ports (FICON). . . . . . . . . . . . .
Contents Non-Concurrent FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RRP: Redundant CTP2 Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tools Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing a Redundant CTP2 Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing a Redundant CTP2 card . . . . . . .
Contents 5 Illustrated Parts Breakdown. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265 Front-Accessible FRUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Rear-Accessible FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Miscellaneous Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 19 20 21 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 8 Task Manager dialog box, Applications tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Dr. Watson for Windows dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Ethernet Hubs, Daisy-Chained. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 LCD panel (LAN 2 IP address) . .
Contents 57 58 59 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 Unblock All Ports dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Firmware Library dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New Firmware Version dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New Firmware Description dialog box . . . . . . . . . . . . . . .
Contents 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 10 Byte 0 FRU Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 MAP 0400: Event Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 MAP 0400: Error Messages and Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 MAP 0500: Event Codes . . . . . . . . . . . . . . . . . . .
About this Guide About this Guide This guide describes the service procedures for the HP StorageWorks Director 2/64.
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/64. 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 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 Power supplies or systems marked with these symbols indicate the presence of multiple sources of power. WARNING: To reduce the risk of personal injury from electrical shock, remove all power cords to completely disconnect power from the power supplies and systems. Any product or assembly marked with these symbols indicates that the component exceeds the recommended weight for one individual to handle safely.
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/64 Service Manual
General Information 1 The HP StorageWorks Director 2/64 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/64 is a second-generation, 32-port product (expandable to 64 ports) that provides dynamic switched connections between Fibre Channel servers and devices in a SAN environment. Directors (from one to four) can be configured to order in an HP-supplied equipment rack, which can provide up to 256 ports in a single cabinet.
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.
General Information Rear View Figure 2 displays FRUs accessible from the rear of the director.
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 the HAFM application and the Element Manager. The HAFM and Element Manager 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 The left panel of this view is the product list, which is an expandable list of the fabrics, the products in the fabrics, and the nodes connected to the products. The Physical Map displays graphical fabric elements and ISLs for a multi-switch fabric. The graphical representation of the fabric emulates the configuration and operational status of the corresponding real fabric. Note that a single director without ISLs is still considered a fabric.
General Information Figure 3: HAFM Services window 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 Status Line The status line provides a status indicator and message area. HAFM status symbols are explained in Table 2. The HAFM application icon (upper left corner of the window) is dynamic and matches the status indicator. This feature allows users and service personnel to observe the status when the application is minimized to the Windows 2000 task bar. The message area briefly displays messages during HAFM application startup to indicate the progress of startup activities.
General Information Service personnel can perform monitoring, configuration, maintenance and diagnostic functions as follows: ■ View panel—Quickly inspect and determine the operational status of the director, and inspect director properties and operating parameters, FRU properties, and Fibre Channel port properties. ■ Configure panel—Configure or change: — Director Fibre Channel ports. — Director identification, date and time, operating parameters, and network addresses. — SNMP trap message recipients.
General Information SNMP Trap Message Support Unsolicited SNMP trap messages that indicate director operational state changes or failure conditions can be customer-configured to be transmitted to up to 12 management workstations. If installed on a dedicated Ethernet LAN, the workstations communicate directly with each director. If installed on a customer intranet, workstations communicate with directors through the HAFM appliance.
General Information E-Mail and Call-Home Support If e-mail notification and call-home support are configured for the director as part of the customer support process, service personnel may be: ■ Notified of a director problem by e-mail message, either directly or through a system administrator at the customer site or call center. ■ Assigned a service call from call center personnel upon receipt and confirmation of a director call-home event.
General Information ■ Fiber optic loopback plug—An SFP multi-mode (shortwave laser) or single-mode (longwave laser) loopback plug (Figure 5) is required to perform port loopback diagnostic tests. Four multi-mode loopback plugs are shipped with the director. Both plug types are shipped if shortwave laser and longwave laser transceivers are installed.
General Information ■ 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 ■ Maintenance terminal (desktop or notebook PC)—The PC is required to configure director network addresses and acquire Event Log information through the maintenance port. The PC must have: — The Microsoft Windows 98, Windows 2000, Windows XP, or Windows Millennium Edition operating system installed. — RS-232 serial communication software installed, such as ProComm Plus or HyperTerminal. HyperTerminal is provided with Windows operating systems.
General Information 34 Director 2/64 Service Manual
Diagnostics 2 This chapter describes diagnostic procedures used by service representatives to fault isolate the Director 2/64 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 Quick Start Table 4 lists the MAPs. Fault isolation normally begins at “MAP 0000: Start MAP” on page 46.
Diagnostics Table 5: Event Codes and Corresponding Maintenance Action (Continued) Event Code 38 Explanation Action 020 Name server unable to synchronize databases. Go to MAP 0700: Fabric, ISL, and Segmented Port Problem Determination. 021 Name server database invalid. Go to MAP 0700: Fabric, ISL, and Segmented Port Problem Determination. 031 SNMP request received from unauthorized community. Add community name. 050 HAFM appliance unable to synchronize databases.
Diagnostics Table 5: Event Codes and Corresponding Maintenance Action (Continued) Event Code Explanation Action 071 Director is isolated. Go to MAP 0700: Fabric, ISL, and Segmented Port Problem Determination. 072 E_Port connected to unsupported switch. Go to MAP 0700: Fabric, ISL, and Segmented Port Problem Determination. 073 Fabric initialization error. Event data intended for engineering evaluation.
Diagnostics Table 5: Event Codes and Corresponding Maintenance Action (Continued) Event Code 40 Explanation Action 120 Error while processing system management command. If this event persists, perform data collection procedure (“Collecting Maintenance Data” on page 197) and return backup CD to HP support personnel. 121 Zone set activation failed–zone set too large. Reduce size of zone set and retry. 140 Congestion detected on an ISL.
Diagnostics Table 5: Event Codes and Corresponding Maintenance Action (Continued) Event Code Explanation Action 206 Power supply removed. Replace FRU. 207 Power supply installed. No action required. 208 Power supply false shutdown. Go to MAP 0100: Power Distribution Analysis. 300 Cooling fan propeller failed. Go to MAP 0500: FRU Failure Analysis 301 Cooling fan propeller failed. Go to MAP 0500: FRU Failure Analysis. 302 Cooling fan propeller failed. Go to MAP 0500: FRU Failure Analysis.
Diagnostics Table 5: Event Codes and Corresponding Maintenance Action (Continued) Event Code 42 Explanation Action 412 CTP2 watchdog timer reset. Perform data collection procedure (“Collecting Maintenance Data” on page 197) and return backup CD to HP support personnel. 413 Backup CTP2 card POST failure. Go to MAP 0200: POST Failure Analysis. 414 Backup CTP2 card failed. Go to MAP 0500: FRU Failure Analysis. 415 Backup CTP2 card removed. Replace FRU. 416 Backup CTP2 card installed.
Diagnostics Table 5: Event Codes and Corresponding Maintenance Action (Continued) Event Code Explanation 433 Non-recoverable Ethernet fault. Go to MAP 0500: FRU Failure Analysis. 440 Embedded port hardware failed. Go to MAP 0500: FRU Failure Analysis. 442 Embedded port anomaly detected. No action required. 445 ASIC detected a system anomaly. No action required. 450 Serial Number mismatch detected.
Diagnostics Table 5: Event Codes and Corresponding Maintenance Action (Continued) Event Code 44 Explanation Action 504 UPM card failure. Go to MAP 0600: UPM Card Failure and Link Incident Analysis. 505 UPM card revision not supported. Go to MAP 0600: UPM Card Failure and Link Incident Analysis. 506 Fibre Channel port failure. Go to MAP 0600: UPM Card Failure and Link Incident Analysis. 507 Loopback diagnostics port failure. Go to MAP 0600: UPM Card Failure and Link Incident Analysis.
Diagnostics Table 5: Event Codes and Corresponding Maintenance Action (Continued) Event Code Explanation Action 584 Not operational primitive sequence received. Go to MAP 0600: UPM Card Failure and Link Incident Analysis. 585 Primitive sequence timeout. Go to MAP 0600: UPM Card Failure and Link Incident Analysis. 586 Invalid primitive sequence received for current link state. Go to MAP 0600: UPM Card Failure and Link Incident Analysis. 600 SBAR assembly hot-insertion initiated.
Diagnostics Table 5: Event Codes and Corresponding Maintenance Action (Continued) Event Code Explanation Action 805 High temperature warning (SBAR assembly thermal sensor). Go to MAP 0500: FRU Failure Analysis. 806 Critically hot temperature warning (SBAR assembly thermal sensor). Go to MAP 0500: FRU Failure Analysis. 807 SBAR assembly shutdown due to thermal violation. Go to MAP 0500: FRU Failure Analysis. 810 High temperature warning (CTP2 card thermal sensor).
Diagnostics — The Windows 2000 user name and password. These are required when prompted during any MAP or repair procedure that directs the HAFM appliance to be rebooted. — The user name, maintenance password, and HAFM appliance name. All are case-sensitive and required when prompted at the HAFM 8 Log In dialog box. ■ If performing fault isolation using the Embedded Web Server interface, the director user name and password.
Diagnostics 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 ↓ A HAFM appliance application problem is indicated. Event codes are not recorded. Go to “MAP 0300: HAFM Appliance Software Problem Determination” on page 87. Exit MAP. 5 Is the HAFM application active? NO YES ↓ Go to step 7. 6 Reboot the HAFM appliance. 1. Click Start > Shut Down. The Shut Down Windows dialog box displays. 2.
Diagnostics d. Ignore the message. After ten seconds, the server performs the boot sequence from the basic input/output system (BIOS). During the boot sequence, the server performs additional POST 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 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 into.
Diagnostics Did the View All - HAFM 8 window display and is the HAFM application operational? YES NO ↓ A 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 157. Exit MAP. 7 Inspect the alert indicators of each managed director at the main window physical map or product list.
Diagnostics 8 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 CTP2 card and illuminated green PWR OK LEDs on both power supplies. ■ Audio emanations and airflow from cooling fans.
Diagnostics 12 Double-click the icon representing the director reporting the problem. The Hardware View displays. At the Hardware View: ■ Observe the director Status table is yellow and the director status is NOT OPERATIONAL. ■ Inspect FRUs for a blinking red and yellow diamond (failed FRU indicator) that overlays the FRU graphic. 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.
Diagnostics 15 Double-click the icon representing the director reporting the problem. The Hardware View displays. At the Hardware View: ■ Verify the Director 2/64 Status table is yellow and the director status is Minor Failure or Redundant Failure. ■ Inspect FRUs for a blinking red and yellow diamond (failed FRU indicator) that overlays the FRU graphic. Does a blinking red and yellow diamond overlay a power supply graphic? NO YES ↓ A power supply failure is indicated.
Diagnostics 18 No colored attention indicator is associated with the icon representing the director reporting the problem. Although the director is operational, a minor problem may exist. Double-click the icon representing the director reporting the problem. The Hardware View displays. At the Hardware View: ■ Inspect CTP2 cards, SBAR assemblies, and fan modules for a yellow triangle that overlays the FRU graphic and indicates FRU beaconing is enabled.
Diagnostics 21 Inspect the port state and LED status for all UPM cards with an attention indicator. 1. Double-click the UPM card. The Port Card View displays. 2. Double-click the port graphic with the attention indicator. The Port Properties dialog box displays, as shown in Figure 11. 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.
Diagnostics 22 A link incident may have occurred, but the LIN alerts option is not enabled for the port, and the attention indicator does not display. 1. At the Hardware View, click Logs > Link Incident Log. The Link Incident Log displays, as shown in Figure 12. Figure 12: Link Incident Log 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.
Diagnostics 23 Obtain event codes from the director 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 has been recovered. 1. At the Hardware View, click Logs > Event Log.
Diagnostics 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. 27 Connect the director to facility AC power and set the power switch (circuit breaker) at the rear of the director 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 28 Is the power LED (green) at the director front bezel illuminated? NO YES ↓ Go to step 30. 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 252). Exit MAP.
Diagnostics 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. 2. Disable unit beaconing. a. At the Hardware View, right-click the front bezel graphic (away from an FRU). A menu displays. b. Click Enable Unit Beaconing. The check mark disappears from the box adjacent to the option, and unit beaconing is disabled.
Diagnostics 34 Is the amber LED on a CTP2 card, SBAR assembly, or fan module illuminated? NO YES ↓ An FRU failure is indicated. Go to step 23 to obtain event codes. If no event codes are found, go to “MAP 0500: FRU Failure Analysis” on page 110. Exit MAP. 35 Is the green PWR OK LED on a power supply extinguished? NO YES ↓ A power supply failure 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 71. Exit MAP.
Diagnostics 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). The Username And Password Required dialog box displays. 4. Type the user name and password obtained in step 1, and click OK. The Embedded Web Server interface opens with the View panel displayed, as shown in Figure 14. Figure 14: View panel Continue.
Diagnostics 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. ■ Both of the director’s CTP2 cards failed. Continue.
Diagnostics 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. 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). The Username and Password Required dialog box displays. 3.
Diagnostics 45 Inspect Fibre Channel port operational states. 1. At the View panel, click the Port Properties tab. The View Port Properties panel displays, as shown in Figure 15. 2. Inspect the Beaconing and Operational State fields. Figure 15: View Port Properties panel Does the Beaconing field display an On message? 66 YES NO ↓ Go to step 47.
Diagnostics 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, click Operations 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. The check mark disappears from the box and port beaconing is disabled. c. Return to the View panel (Port Properties tab). Continue.
Diagnostics 49 Repeat step 45 through step 48 for each remaining Fibre Channel port for which a problem is suspected. Is a problem indicated for any of the ports? NO YES ↓ Go to step 52 to obtain event codes. If no event codes are found, go to “MAP 0600: UPM Card Failure and Link Incident Analysis” on page 118. Exit MAP. 50 Inspect power supply operational states. 1. At the View panel, click the FRU Properties tab. The View FRU Properties panel displays, as shown in Figure 16.
Diagnostics 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 71. Exit MAP. 51 Inspect the Status fields for director FRUs, including CTP2 cards, SBAR assemblies, fan modules, and the backplane.
Diagnostics 4. Record all event codes that may relate to the reported problem. Figure 17: Monitor Log panel Were one or more event codes found? NO YES ↓ Go to Table 5 on page 37. 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.
Diagnostics 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. 582—Link interface incident—bit-error threshold exceeded. 583—Link failure—loss of signal or loss of synchronization. 584—Link failure—not-operational primitive sequence (NOS) received. 585—Link failure—primitive sequence timeout.
Diagnostics 2 Table 6 lists event codes, brief explanations of the codes, and the associated steps that describe fault isolation procedures. Table 6: MAP 0100: Event Codes Event Code Explanation Action 200 Power supply AC voltage failure. Go to step 3 201 Power supply DC voltage failure. Go to step 7 202 Power supply thermal failure. Go to step 7 208 Power supply false shutdown.
Diagnostics Is a failure indicated? YES NO ↓ The director is operational. Exit MAP. 5 Ensure the indicated power supply is correctly installed and seated in the director. If required, partially remove and reseat the power supply. Was a corrective action performed? YES NO ↓ Go to step 7. 6 Verify redundant power supply operation. 1. Inspect the power supply and ensure the green PWR OK LED illuminates and all amber LEDs extinguish. 2.
Diagnostics Did power supply replacement solve the problem? NO YES ↓ The director is operational. Exit MAP. Contact the next level of support. Exit MAP. 8 Power sense circuitry is defective in the indicated power supply or there is a problem with facility input power. Have the customer inspect and verify that facility power is within specifications. These specifications are: ■ One single-phase connection for each power supply. ■ Input power between 100 and 240 VAC, and between 2 and 4 amps.
Diagnostics 10 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 21. 11 Verify the director is connected to facility power and is powered on. 1. Ensure AC power cords (PS0 and PS1) are connected to the rear of the director and to facility power receptacles. If not, connect the cords as directed by the customer. 2. Ensure associated facility circuit breakers are on.
Diagnostics 13 Does inspection of a power supply indicate a failure (green PWR OK LED extinguished and one or more amber LEDs illuminated)? NO YES ↓ A redundant power supply failed. Go to step 7. The director is operational. Exit MAP. 14 The director’s AC power distribution system failed. Possible causes include failure of: ■ Both power supplies. ■ Power module assembly. ■ Backplane.
Diagnostics Is a dual power supply failure still indicated? YES NO ↓ The director is operational. Exit MAP. 17 Both power supplies failed and must be removed and replaced (“RRP: Redundant Power Supply” on page 245). Perform the data collection procedure as part of FRU removal and replacement. Did dual power supply replacement solve the problem? NO YES ↓ The director is operational. Exit MAP. A dual power supply failure is not confirmed.
Diagnostics 20 The backplane failed and must be removed and replaced (“RRP: Backplane” on page 258). ■ This procedure is non-concurrent and must be performed while director power is off. ■ Perform the data collection procedure as part of FRU removal and replacement. Did backplane replacement solve the problem? NO YES ↓ The director is operational. Exit MAP. Contact the next level of support. Exit MAP.
Diagnostics The grey square indicates the HAFM appliance cannot communicate with the director because: ■ The director-to-HAFM appliance Ethernet link failed. ■ AC power distribution in the director failed, or AC power was disconnected. ■ Both of the director’s CTP2 cards failed. Continue. 24 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.
Diagnostics 26 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. ■ Both of the director’s CTP2 cards failed. Continue.
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 46. 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 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 258). ■ This procedure is non-concurrent and must be performed while director power is off. ■ Perform the data collection procedure as part of FRU removal and replacement.
Diagnostics Did CTP2 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 248). ■ 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 245). ■ 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 CTP2 card failed POST/IPL diagnostics (as indicated by an event code 413) and must be removed and replaced (“RRP: Redundant CTP2 Card” on page 231). ■ 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 CTP2 card if the backup CTP2 card is not fully operational and director power is on.
Diagnostics MAP 0300: HAFM Appliance Software Problem Determination This map describes isolation of HAFM appliance problems, including problems associated with the Windows 2000 operating system, HAFM application, and Element Manager. 1 Did the HAFM appliance lock up or crash without displaying a warning or error message? YES NO ↓ Go to step 4. 2 An application or operating system problem is indicated.
Diagnostics 2. At the Windows 2000 Security dialog box, click Task Manager. The Windows 2000 Task Manager dialog box displays with the Applications tab open, as shown in Figure 19. Figure 19: Task Manager dialog box, Applications tab 3. Click the View All - HAFM 8 entry and then click End Task. The HAFM application closes. 4. Close the Task Manager dialog box. Continue. 3 Attempt to clear the problem by rebooting the HAFM appliance. 1. Click Start > Shut Down. The Shut Down Windows dialog box displays.
Diagnostics c. After a few seconds, the LCD panel displays a message, as shown in Figure 8 on page 48. d. Ignore the message. After ten seconds, the HAFM appliance performs the boot sequence from the basic input/output system (BIOS).
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. 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 ↓ A HAFM application error occurred.
Diagnostics 7 Upgrade the downlevel HAFM application (“Install or Upgrade Software” on page 223). 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 the HAFM application and the Element Manager.
Diagnostics 11 Did the Element Manager display a dialog box with the message The data collection process failed? YES NO ↓ Go to step 13. 12 The data collection process failed. Retry the process using a new backup CD (“Collecting Maintenance Data” on page 197). Did the data collection process complete? NO YES ↓ Return the backup 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.
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 server performs additional POSTs 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 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 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. Go to step 14 3 Is fault isolation being performed at the HAFM appliance? YES NO ↓ Fault isolation is being performed through the Embedded Web Server interface.
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 CTP2 card, and illuminated green PWR OK LEDs on both power supplies. ■ Audio emanations and airflow from cooling fans.
Diagnostics Table 10 lists the link failure reasons 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 14 The Ethernet adapter on the director’s active CTP2 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 backup CD to HP for analysis by third-level support personnel. Exit MAP. 15 A protocol mismatch occurred because the HAFM application (running on the HAFM appliance) and the director firmware are not at compatible release levels.
Diagnostics 18 An instance of the HAFM application is open at another HAFM appliance and communicating with the director (duplicate session). Notify the customer and either: ■ Power off the HAFM appliance running the second instance of the application, or ■ Configure the HAFM appliance running the second instance of the application as a client workstation.
Diagnostics 3. Depending on switch-to-server LAN connectivity, record the appropriate IP address (LAN 1 or LAN 2). Continue. 20 Configure the HAFM appliance reporting the Duplicate Session communication problem as a client. 1. At the HAFM main window, click SAN > Logout. The HAFM 8 Log In dialog box displays. 2. 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.
Diagnostics 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. The tools are provided with the director or by service personnel. To verify the IP address: 1. Remove the protective cap from the 9-pin maintenance port at the rear of the director (a Phillips-tip screwdriver may be required).
Diagnostics 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/64 HyperTerminal window displays with a C> prompt at the bottom of the window. 9. At the C> prompt, type the ipconfig command and press the Enter key. The Director 2/64 HyperTerminal window displays with configuration information listed (including the IP address). 10. Record the director’s IP address. 11. Click File > Exit.
Diagnostics 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 OK. 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 23 An incorrect product type is defined to the HAFM appliance. 1. At the HAFM main window, right-click the icon with the grey square and yellow exclamation point (representing the product reporting the problem) at the Physical Map. A menu displays. 2. Click Delete. A Warning dialog box displays, as shown in Figure 26. Figure 26: HAFM message dialog box 3. Click Yes to delete the director. 4. At the HAFM main window, click Discover > Setup.
Diagnostics 25 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 (Ethernet) link could not be established. ■ AC power distribution in the director failed, or AC power was disconnected. ■ Both of the director’s CTP2 cards failed. Continue.
Diagnostics 28 Either a director-to-PC Internet link problem (Internet too busy or IP address typed incorrectly) or a director Ethernet port failure is indicated. 1. Wait approximately five minutes, then attempt to log in to the director again. 2. 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 “MAP 0000: Start MAP” on page 46).
Diagnostics MAP 0500: FRU Failure Analysis This MAP describes fault isolation for the CTP2 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 Explanation Action 420 Backup CTP2 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 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. Does inspection of a director fan module indicate a failure? Indicators include: ■ The amber LED is illuminated but not blinking (beaconing) on one or both fan modules. ■ One or more cooling fans are not rotating. YES NO ↓ Go to step 6.
Diagnostics 6 Inspect the faceplates of both CTP2 cards at the front of the director. Is the amber LED at the top of a CTP2 card illuminated but not blinking (beaconing)? YES NO ↓ Go to step 8. 7 A CTP2 card failed and must be removed and replaced (“RRP: Redundant CTP2 Card” on page 231). ■ 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 248). ■ 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/64 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 215). Perform the data collection procedure after the download. Continue. 17 Did the firmware download solve the problem? NO YES ↓ The director is operational. Exit MAP.
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 CTP2 card. ■ At least one green PWR OK LED illuminated on a power supply.
Diagnostics 23 Inspect CTP2 card operational states at the Embedded Web Server interface. Inspect the Status fields for both CTP2 cards. Does the Status field display a Failed message for either CTP2 card? NO YES ↓ A CTP2 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 7 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 6 A Fibre Channel port failed, and the SFP optical transceiver must be removed and replaced (“RRP: SFP Optical Transceiver” on page 241). ■ This procedure is concurrent and can be performed while director power is on. ■ Verify location of the failed port. For an OSI environment, Figure 27 and Figure 28 show UPM card numbers (0 through 15) and port numbers (00 through 63).
Diagnostics 7 A UPM card failed, and the card must be removed and replaced (“RRP: UPM Card” on page 236). ■ This procedure is concurrent and can be performed while director power is on. ■ Verify location of the failed card (Figure 27 and Figure 28 on page 121). For an OSI environment, Figure 27 nd Figure 28 show UPM card numbers (0 through15) and port numbers (00 through 63).
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 (Continued) Operational State Green LED Amber LED Action Testing On Blinking External loopback test in process. Exit MAP. Beaconing Off or On Blinking Go to step 17 Invalid Attachment On Off Go to step 18 Link Reset Off Off Go to step 32 Link Incident Off Off Go to step 33 Segmented E_Port On Off Go to MAP 0700: Fabric, ISL, and Segmented Port Problem Determination.
Diagnostics 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. Click Reset Port. A Reset Port n message box displays, where n is the port number. c. Click OK. The port resets. 2. Perform an external loopback test for all ports that were reset. Did resetting ports solve the problem? NO YES ↓ The director is operational. Exit MAP.
Diagnostics 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 Hardware View, right-click the port graphic. A menu displays. b. Click Enable Beaconing. The check mark disappears from the box adjacent to the option, and port beaconing is disabled. Was port beaconing enabled because port failure or degradation was suspected? YES NO ↓ The director is operational. Exit MAP.
Diagnostics 19 The port has an invalid attachment. The Reason field in the Port Properties dialog box specifies the reason. See Table 14 for a list of reasons and appropriate actions. Table 14: MAP 0600: Invalid Attachment Reasons and Actions Reasons 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. Go to step 21 External loopback adapter connected to the port.
Diagnostics ■ Click expansion port (E_Port) if the port is cabled to a fabric element (director or switch) to form an ISL. 4. Click Activate to save the configuration information and close the dialog box. Did reconfiguring the port type solve the problem? NO YES ↓ The director is operational. Exit MAP. Contact the next level of support. Exit MAP.
Diagnostics 3. Select the operating mode by clicking one of the following options on the Interop Mode drop-down list: ■ Open Fabric 1.0 ■ Homogeneous 4. Click Activate to save the selection and close the window. Did configuring the operating mode solve the problem? NO YES ↓ The director is operational. Exit MAP. Contact the next level of support. Exit MAP. 22 A loopback plug is connected to the port and there is no diagnostic test running.
Diagnostics 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). Check the port status and clean the fiber-optic connectors on the cable. 1. Notify the customer the port will be blocked.
Diagnostics 26 An SBAR assembly failed and must be removed and replaced (“RRP: Redundant SBAR Assembly” on page 248). ■ 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 check box 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 Figure 33: Clear Link Incident Alert(s) dialog box 5. Make sure the This port (n) only option (where n is the port number) is selected and click OK. The link incident clears. 6. 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.
Diagnostics 36 Clean fiber optic connectors on the jumper cable. 1. Notify the customer the port will be blocked. Ensure the customer’s system administrator quiesces Fibre Channel frame traffic through the port and sets the attached device offline. 2. Block the port (“Block a Port” on page 207). 3. Disconnect both ends of the fiber optic jumper cable. 4. Clean the fiber optic connectors (“Clean Fiber Optic Components” on page 199). 5. Reconnect the fiber optic jumper cable. 6.
Diagnostics 38 The attached device is causing the recurrent link incident. Notify the customer of the problem and have the system administrator: 1. Inspect and verify operation of the attached device. 2. Repair the attached device if a failure is indicated. 3. Monitor port operation for approximately five minutes. Did the link incident recur? YES NO ↓ The attached device, Fibre Channel link, and director are operational. Exit MAP.
Diagnostics 43 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. ■ Both of the director’s CTP2 cards failed. Continue.
Diagnostics Does the Status field display a Failed message for a UPM card? NO YES ↓ A UPM card failure is indicated. Go to step 7. 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 through 63) for which a failure is suspected to display properties for that port. 3. Inspect the Operational State field.
Diagnostics 47 Install an SFP optical transceiver in the port receptacle (“RRP: SFP Optical Transceiver” on page 241). 1. This procedure is concurrent and can be performed while director power is on. 2. Verify location of the uninstalled port transceiver. ■ For an OSI environment, Figure 34 and Figure 35 page 140 show UPM card numbers (0 through15) and port numbers (00 through 63).
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/64 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 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. Go to step 12 072 E_Port connected to unsupported switch.
Diagnostics 5 Inspect the port state and LED status for all ports with an attention indicator. 1. At the Hardware View, double-click the port with the attention indicator. The Port card View displays 2. Double-click the port with the attention indicator. The Port Properties dialog box displays. 3. Inspect the Operational State field in the Port Properties dialog box.
Diagnostics 7 A minor error occurred that caused fabric services databases to be reinitialized to an empty state. As a result, a disruptive fabric logout and login occurred for all attached devices. The following list explains the errors. ■ Event code 010—Following a CTP2 card reset, the login server attempted to acquire a fabric server database copy from the other CTP2 card and failed.
Diagnostics 9 A minor error occurred that caused fabric controller databases to be reinitialized to an empty state. As a result, the director briefly lost interswitch link capability. The following list explains the errors. ■ Event code 060—Following CTP2 card reset, the fabric controller attempted to acquire a database copy from the other CTP2 card and failed. ■ Event code 061—Following CTP2 card failover, the fabric controller database failed CRC validation.
Diagnostics 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. 12 A 070 event code indicates an E_Port detected an incompatibility with an attached director and prevented the directors from forming a multi-switch fabric. A segmented E_port cannot transmit Class 2 or Class 3 Fibre Channel traffic.
Diagnostics 14 A director E_Port segmented because the error detect time out value (E_D_TOV) or resource allocation time-out value (R_A_TOV) is incompatible with the attached fabric element. 1. Contact HP customer support or engineering personnel to determine the recommended E_D_TOV and R_A_TOV values for both directors. 2. Notify the customer that both directors will set offline. Ensure the system administrator quiesces Fibre Channel frame traffic through the directors and sets attached devices offline.
Diagnostics 3. Set both directors offline (“Set Offline State” on page 206). 4. At the Hardware View for the first director reporting the problem, click Configure > Operating Parameters > Switch Parameters. The Configure Switch Parameters dialog box displays, as shown in Figure 36. Figure 36: Configure Switch Parameters dialog box 5. Type the customer-determined preferred domain ID value, then click Activate. 6.
Diagnostics 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. Work with the system administrator to determine the desired zone name change for one of the affected directors. Zone names must conform to the following rules: ■ The name must be 64 characters or fewer in length.
Diagnostics 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. 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 on page 149. b.
Diagnostics 17 A director E_Port segmented because a build fabric protocol error was detected. 1. Disconnect the fiber optic jumper cable from the segmented E_Port. 2. Reconnect the cable to the same port. Did disconnecting and reconnecting the cable 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.
Diagnostics 4. At the Switch Priority field, select a switch priority (Principal, Never Principal, or Default). The switch priority value designates the fabric’s principal switch. The principal switch is assigned a priority of 1 and controls the allocation and distribution of domain IDs for all fabric directors and switches (including itself). Principal is the highest priority setting, Default is the next highest, and Never Principal is the lowest priority setting.
Diagnostics 21 A 140 event code occurs only if the optional OpenTrunking feature is enabled. The event code indicates OpenTrunking firmware detected an ISL with Fibre Channel traffic that exceeds the configured congestion threshold. No action is required for an isolated event. However, if this event persists, perform one of the following: ■ Relieve the congestion by adding parallel ISLs between the directors or switches reporting the problem.
Diagnostics Did the corrective action solve the problem and relieve the reported low BB_Credit condition? NO YES ↓ The ISL is operational. Exit MAP. Contact the next level of support. Exit MAP. 23 A 150 event code indicates a zone merge failed during ISL initialization. Either an incompatible zone set was detected or a problem occurred during delivery of a zone merge frame.
Diagnostics 24 A zone merge failed during ISL initialization. The following list explains the reason: ■ Failure reason 01—An invalid data length condition caused an error in a zone merge frame. ■ Failure reason 08—An invalid zone set format caused an error in a zone merge frame. ■ Failure reason F0—A retry limit reached condition caused an error in a zone merge frame. ■ Failure reason F1—An invalid response length condition caused an error in a zone merge frame.
Diagnostics 26 Is the Embedded Web Server interface operational? YES NO ↓ Analysis for an Ethernet link, AC power distribution, or CTP2 card failure is not described in this MAP. Go to “MAP 0000: Start MAP” on page 46. If this is the second time at this step, contact the next level of support. Exit MAP. 27 Inspect the Fibre Channel port segmentation reason at the Embedded Web Server interface. 1. At the View panel, click the Port Properties tab. The View panel (Port Properties tab) displays. 2.
Diagnostics MAP 0800: HAFM Appliance or Web Browser PC Hardware Problem Determination This MAP describes isolation of hardware-related problems with the HAFM appliance platform. Although this MAP provides high-level fault isolation instructions, refer to the documentation provided with the HAFM appliance for detailed problem determination and resolution.
Diagnostics 4 At the HAFM appliance, close the HAFM application. 1. At the HAFM main window, click SAN > Exit. The HAFM application closes. 2. Close any other applications that are running. Continue. 5 Inspect the available random access memory (RAM). The computer must have a minimum of 128 megabytes (MB) of memory to run the Windows 2000 operating system and HAFM application. 1. Right-click anywhere in the Windows 2000 task bar at the bottom of the desktop. A menu displays. 2. Click Task Manager.
Diagnostics b. The green hard disk drive (HDD) LED blinks momentarily, and processor speed and random-access memory information display momentarily at the LCD panel. c. After a few seconds, the LCD panel displays a message, as shown in Figure 8 on page 48. d. Ignore the message. After ten seconds, the server performs the boot sequence from the basic input/output system (BIOS).
Diagnostics 7 After rebooting the HAFM 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. 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.
Diagnostics 9 Perform one of the following: ■ If the HAFM appliance has standalone diagnostic test programs resident on the hard drive, perform the diagnostics. Refer to supporting documentation shipped with the HAFM appliance for instructions. ■ If the HAFM appliance does not have standalone diagnostic test programs resident on hard drive, go to step 10.
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 server operational information. 5. After rebooting the server at the LCD panel, log on to the HAFM appliance Windows 2000 desktop through a LAN connection to a browser-capable PC.
Diagnostics Did the View All - HAFM 8 window display and is the HAFM application operational? NO YES ↓ The HAFM appliance is operational. Exit MAP. 11 Re-install the HAFM application (“Install or Upgrade Software” on page 223). Did the HAFM application install and open successfully? NO YES ↓ The HAFM appliance is operational. Exit MAP. 12 Advise the customer and next level of support that the HAFM appliance hard drive should be restored to its original factory configuration.
Diagnostics 164 Director 2/64 Service Manual
Repair Information 3 This chapter describes repair and repair-related procedures used by service representatives for the Director 2/64 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 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/64 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/64 Event Log. The information is useful to maintenance personnel for fault isolation and repair verification.
Repair Information ■ EWS Open Trunking Re-Route Log—Displays interswitch link (ISL) congestion events that cause Fibre Channel traffic to be routed through an alternate ISL. Entries reflect the traffic re-route status at the managed director. ■ EWS Link Incident Log—Displays Fibre Channel link incident events recorded at the EWS interface. Entries reflect the cause of the link incident.
Repair Information Exporting Log Data You can export HAFM log data in tab-delimited format. This feature is useful for providing the data to a third-party or including it in a report. 1. Click Monitor > Logs, then click one of the options. The View Logs dialog box displays, as shown in Figure 39 on page 169. 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.
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 172 Green LED Amber LED Alert Symbol Description Link Incident Off Off Yellow Triangle A link incident occurred on the port. The alert symbol displays at the Port Card View, Port List View, and Hardware View. Link Reset Off Off Yellow Triangle The director and attached device are performing a link reset operation to recover the link connection. This is a transient state that should not persist.
Repair Information HAFM Appliance To obtain port operational information at the HAFM appliance (Director 2/64 Element Manager), inspect parameters at the: ■ Port List View ■ Performance View ■ Port Properties dialog box ■ Port Technology dialog box Viewing the Port List View The Port List View provides status information for all director ports. The information is useful to maintenance personnel for isolating port problems. To open the Port List View, perform the following: 1.
Repair Information The Port List View provides status information in the following columns: ■ #—The director port number (0 through 63 inclusive). ■ Addr—The director logical port address (05 through 43 inclusive) 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 ■ Swap one Fibre Channel port address with another. This menu option displays only when the director is configured for FICON management style. ■ Clear link incident alerts. ■ Reset the port. ■ Configure port binding. ■ Clear threshold alerts. Viewing the Performance View To view performance data, perform the following: 1. At the Hardware View, click the Performance tab. The Performance View displays, as shown in Figure 41.
Repair Information Each port graph has 20 green-bar level indicators corresponding to 5% of the maximum throughput for the port (either transmit or receive). If any activity is detected for a port, at least one green bar appears. A red indicator on each port bar graph (high-water mark) remains at the highest level the graph has reached since the port was set online. The indicator does not display if the port is offline, and it is reset to the bottom of the graph if the port detects a loss of light.
Repair Information ■ Class 3 statistics—These entries provide information about Class 3 traffic, including: — Class 3 frames received and transmitted. — Four-byte words received and transmitted. — Discarded frames. ■ Error statistics—The Performance View displays the following error statistics for the port: — Link failures—Link failures are recorded in response to an NOS, protocol time-out, or port failure.
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 Viewing Port Properties To open the Port Properties dialog box, perform the following: 1. Double-click a port in the Port Card View or a port row in the Port List View. The Port Properties dialog box displays, as shown in Figure 42. Figure 42: Port Properties dialog box The Port Properties dialog box provides the following information: Note: If the Open Trunking feature is installed, an additional item, Congested Threshold %, displays in the Port Properties dialog box.
Repair Information ■ Block Configuration—A user-configured state for the port (Blocked or Unblocked). ■ 10-100 km Configuration—Extended distance buffering. This can be enabled or disabled for the port through the Configure Ports dialog box. ■ LIN Alerts Configuration—A user-specified state for the port (On or Off), configured through the Configure Ports dialog box. ■ 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 Port Technology To open the Port Technology dialog box, perform the following: 1. Right-click a port in the Port Card View or the Port List View. The Port menu displays. 2. Click 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—Director port number (0 through 63 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, click Monitor on 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 63 inclusive) appears. Each row consists of the following columns: ■ Port #—The director port number.
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, click Monitor on 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 The # of Wraps column tracks the number of times the counter wraps for rapidly-growing statistics. The maximum counter value is 232 entries. The page displays the following tables of cumulative port statistics and error count values for a selected port: ■ 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.
Repair Information — Delimiter errors—Received frames had frame delimiter errors, indicating the frame arrived at the director port corrupted. Frame corruption may be caused by device disconnection, an optical transceiver failure at the device, a bad fiber optic cable, or a poor cable connection. — 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.
Repair Information Viewing the Port Properties Page When the EWS interface opens, the View panel appears as the default panel. To view the Port Properties, perform the following: 1. At the View panel, click the Port Properties tab. The View panel displays with the Port Properties page open, as shown in Figure 46. Figure 46: View panel (Port Properties page) The Port Properties page displays information for one port.
Repair Information ■ Type—The type of port (G_Port if nothing is attached to the port, F_Port if a device is attached to the port, and E_Port if the port is connected to another director or switch as part of an ISL). ■ Operating Speed—The operating speed (Not Established, 1 Gb/sec, or 2 Gb/sec). ■ Fibre Channel Address — The port’s Fibre Channel address identifier. ■ Port WWN—The Fibre Channel world wide name (WWN) for the port. ■ Attached Port WNN—The WWN of the node logged into the port.
Repair Information Internal Loopback Test To perform an internal loopback test for a single port or a UPM card (four ports): 1. Notify the customer a disruptive internal loopback test will be performed on a port or UPM card. Ensure the customer’s system administrator quiesces Fibre Channel frame traffic through the port or UPM card, and sets attached devices offline. Note: At the start of the loopback test, the port or UPM card can be online, offline, blocked, or unblocked.
Repair Information 6. Click Maintenance > Port Diagnostics. The Port Diagnostics dialog box displays, as shown in Figure 47. Figure 47: Port Diagnostics dialog box 7. Select a port or UPM card for test: — To select an individual port for test, type the port number (0 through 63) 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 click All ports on card. 8.
Repair Information 11. Click Start Test. The test begins and: — Start Test changes to Stop Test. — The message Port xx: TEST RUNNING displays, where xx is the port number. If a UPM card is tested, the message displays for all four ports. — A red progress bar (indicating percent completion) travels from left to right across the Completion Status field. As a port is tested, the amber LED flashes (beacons) and the green LED extinguishes (indicating the port is blocked).
Repair Information 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. Ensure the customer’s system administrator quiesces Fibre Channel frame traffic through the port or UPM card and sets attached devices offline.
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 14. Click Start Test. The test begins and: — Start Test changes to Stop Test. — The message Port xx: TEST RUNNING displays, where xx is the port number. If a UPM card is tested, the message displays for all four ports. — 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).
Repair Information Channel Wrap Test (FICON) A channel wrap test is a diagnostic procedure that checks FICON host-to-director link connectivity by returning the output of the host as input. The test is host initiated, and transmits ECHO extended link service (ELS) command frames to a director port enabled for channel wrapping. The director port echoes the frames back to the host. To perform a channel wrap test for a director-attached host: 1.
Repair Information Swapping Ports (FICON) Use the port swap procedure to swap a device connection and logical port address from a failed Fibre Channel port to an operational port. Because both ports are blocked during the procedure, director communication with the attached device is momentarily disrupted. To perform the port swap procedure for a pair of director ports: 1. Notify the customer a port swap procedure will be performed and a fiber optic cable or cables will be disconnected.
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 CTP2 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/64. 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/64 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 IML the Director from the CTP Front Panel To IML the director from the CTP front panel, perform the following: 1. Press and hold the IML button for approximately three seconds. 2. During the IML, the director-to-HAFM appliance Ethernet link drops momentarily and the following occur at the Hardware View: — As the network connection drops, the Director 2/64 Status table turns yellow, the Status field displays No Link, and the State field displays Link Timeout.
Repair Information 4. Click Yes to IPL the director. During the IPL, the director-to-HAFM appliance Ethernet link drops momentarily and the following occur at the Element Manager: — As the network connection drops, the Director 2/64 Status table turns yellow, the Status field displays No Link, and the State field displays a reason message. — In the HAFM Physical Map, the director icon displays a grey square, indicating director status is unknown.
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. Click 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 7. Click OK. The following occur to indicate the port is blocked (and offline): — The emulated green LED associated with the port extinguishes at the Port Card View. — The green LED associated with the port extinguishes at the director. — 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.
Repair Information Unblock a Port To unblock an individual director port: 1. Open the HAFM application. The View All - HAFM 8 main window displays. 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.
Repair Information 5. Click Unblock All Ports. The Unblock All Ports dialog box displays, as shown in Figure 57. 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 CTP2 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 8 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 web site.
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. 9. The new firmware version and associated description display in the Director 2/64 Firmware Library dialog box. 10. Click Close. 11. To send the firmware version to a director, see “Download a Firmware Version to a Director” on page 215.
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. Click Maintenance > Firmware Library. The Director 2/64 Firmware Library dialog box displays, as shown in Figure 58 on page 211. 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. Click 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 223). 3.
Repair Information 7. Click Yes. The Send Firmware dialog box displays. As the download begins, a Writing data to FLASH message displays at the top of the dialog box, followed by a Sending Files message. This message remains as a progress bar travels across the dialog box to show percent completion of the download. The bar progresses to 50% when the last file is transmitted to the first CTP2 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 CTP2 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 4. Click Backup. When the backup process finishes, the Backup Complete dialog box displays, as shown in Figure 65. 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.
Repair Information Reset Configuration Data Note: This procedure resets the director IP address to the default value of 10.1.1.10 and may disrupt HAFM appliance-to-director communication. All configured feature (PFE) keys must be re-entered. 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.
Repair Information 9. To restart a HAFM appliance session using the default IP address of 10.1.1.10: a. Close the Director 2/64 Element Manager and return to the HAFM application. A grey square with a yellow exclamation mark displays adjacent to the icon representing the reset director, indicating the director is not communicating with the HAFM appliance. b. At the HAFM application, click Discover > Setup. The Discover Setup dialog box displays, as shown in Figure 68.
Repair Information 10. Change the director IP address and restart the HAFM appliance session as follows: a. A grey square with a yellow exclamation mark displays adjacent to the icon representing the reset director, indicating director is not communicating with the HAFM appliance. b. Delete the icon representing the reset director. At the HAFM application, click Discover > Setup. The Discover Setup dialog box displays, as shown in Figure 68 on page 221. c.
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/64 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 application’s CD-ROM or through the HP web site.
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. Click 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.
Repair Information 226 Director 2/64 Service Manual
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 an FRU. If fault isolation was not performed, go to “MAP 0000: Start MAP” on page 46.
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 Remove and Replace 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. Concurrent FRUs can be removed and replaced while the director is powered on and operational. ■ A list of non-concurrent FRUs. Non-concurrent FRUs can only be removed and replaced after the director is powered off.
FRU Removal and Replacement The ESD grounding point for the rear of the chassis (1) is located at the bottom center, directly below the maintenance port, as shown in Figure 73. Touch the chassis once before performing any maintenance action, and once each minute while removing or replacing FRUs. 1 Figure 73: ESD grounding point (rear) Concurrent FRUs Table 25 lists concurrent FRUs. Concurrent FRUs can be removed and replaced while the director is powered on and operational.
FRU Removal and Replacement Table 25: Concurrent FRU Names and ESD Requirements (Continued) ESD Precaution Requirement Concurrent FRU Name Power supply (“RRP: Redundant Power Supply” on page 245) Yes Serial crossbar assembly (“RRP: Redundant SBAR Assembly” on page 248) Yes Fan module (“RRP: Redundant Fan Module” on page 252) Yes Non-Concurrent FRUs Table 26 lists non-concurrent FRUs. Non-concurrent FRUs are removed and replaced after the director is powered off.
FRU Removal and Replacement Tools Required The following tools are required to perform these procedures. ■ ESD grounding cable and wrist strap. ■ Torque tool and hex adapter (provided with the director). Removing a Redundant CTP2 Card To remove a redundant CTP2 card: 1. If the director is installed in a stand-alone configuration, go to step 2. If the director is rack-mounted, unlock and open the cabinet front door as directed by the customer representative. 2.
FRU Removal and Replacement b. Insert the torque tool(1) into the cam Allen screw at the top of the card(2). To unseat the CTP2 card and cam it out of the backplane, turn the screw counterclockwise until the tool turns freely, as shown in Figure 74. 2 StorageWo rks SAN 6064 1 SHR-2286 Figure 74: CTP2 card removal and replacement 6. Pull the CTP2 card from its card track and remove it from the director chassis. Place the card in an antistatic bag to provide ESD protection.
FRU Removal and Replacement 4. Secure the CTP2 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 CTP2 card to ensure the amber LED is extinguished. If the amber LED is illuminated, go to “MAP 0000: Start MAP” on page 46 to isolate the problem. 10. At the Hardware View, click Logs > Event Log. The Event Log displays. Ensure the following event codes display in the log: — 410—CTP2 card reset. — 416—Backup CTP2 installed. — 422—CTP2 firmware synchronization complete (only if the firmware versions on the two CTP2 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 3. Follow ESD procedures by attaching a wrist strap to the director chassis and your wrist, as shown in Figure 72 on page 229. 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.
FRU Removal and Replacement 7. The UPM card is secured to the director chassis with two captive Allen screws. The bottom screw is spring-loaded and locks the UPM card in place. The top screw cams the UPM card into and out of the backplane. Caution: The torque tool supplied with the Director 2/64 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.
FRU Removal and Replacement Replacing a 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 75 on page 238. 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.
FRU Removal and Replacement 8. At the Hardware View, click Logs > Event Log. The Event Log displays. Ensure the following event codes display in the log: — 500—Port card hot-insertion initiated. — 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 46 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.
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 an SFP Optical Transceiver To remove an SFP optical transceiver: 1.
FRU Removal and Replacement UPM 1 SHR-2287 Figure 76: SFP optical transceiver removal and replacement Replacing an 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 76. 3. Perform an external loopback test for the port (“External Loopback Test” on page 192). If the test fails, go to “MAP 0000: Start MAP” on page 46 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 46 to isolate the problem. 6. At the Hardware View, click 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 46 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 a UPM 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 Replacing a UPM 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 77. 3. To secure the filler blank, sequentially insert the torque tool into each locking Allen screw. Turn each screw clockwise until you feel the torque tool release and hear a clicking sound. As each screw turns clockwise, the filler blank locks into place. 4.
FRU Removal and Replacement 3. Identify the defective power supply from the extinguished green PWR OK LED on the supply or failure information at the Hardware View. 4. Push the locking pin to the left (1) to release the cam lever at the top of the power supply, as shown in Figure 78. 5. Pull the cam lever out and to the right (2) to cam the power supply out of the director chassis. Figure 78: Redundant power supply removal and replacement 6. Pull the power supply (3) from the director.
FRU Removal and Replacement 3. Orient the power supply with the cam lever disengaged and pulled out, as shown in Figure 78. a. Insert the power supply into the director chassis guide, then push the power supply toward the backplane to engage the connector pins. b. Push the cam lever in and to the left to cam the power supply into the director chassis. Ensure the locking pin is engaged in the cam lever. 4. Disconnect the ESD wrist strap from the director chassis and your wrist. 5.
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. 11. If necessary, close and lock the equipment cabinet door.
FRU Removal and Replacement 4. Identify the defective SBAR assembly from the amber LED on the assembly or failure information at the Hardware View. 5. The SBAR assembly is secured to the director backplane with two brass Allen screws. Both screws cam the assembly into and out of the backplane.
FRU Removal and Replacement Replacing a Redundant SBAR Assembly To replace a redundant SBAR assembly: 1. Remove the replacement SBAR assembly from its protective antistatic bag. 2. Inspect the printed wiring assembly (PWA) side of the SBAR assembly for bent or broken connector pins that may have been damaged during shipping. If any pins are damaged, obtain a new assembly. 3. Orient the SBAR assembly, as shown in Figure 79.
FRU Removal and Replacement 8. Perform one of the following to verify SBAR 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 46 to isolate the problem. — At the EWS interface, open the Switch tab at the View panel and ensure no amber LEDs illuminate that indicate a SBAR failure.
FRU Removal and Replacement 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. ■ Standard flat-tip screwdriver. ■ ESD grounding cable and wrist strap. Removing a Redundant Fan Module To remove a redundant fan module: 1. If the director is installed in a stand-alone configuration, go to step 2.
FRU Removal and Replacement 1 Figure 80: Fan module removal and replacement SHR 2304 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 7. At the Hardware View, click Logs > Event Log. The Event Log displays. Ensure an event code 321 (fan FRU inserted) displays in the log. If an event code 321 does not display in the log, go to “MAP 0000: Start MAP” on page 46 to isolate the problem. 8.
FRU Removal and Replacement RRP: Power Module Assembly Use the following procedures to remove or replace the power module assembly. A list of tools required is provided. Tools Required The following tools are required to perform these procedures. ■ Standard flat-tip screwdriver. ■ Standard cross-tip (Phillips) screwdriver. ■ ESD grounding cable and wrist strap. Removing a Power Module Assembly To remove the power module assembly: 1. Notify the customer the director will be powered off.
FRU Removal and Replacement 7. Remove both SBAR assemblies (“RRP: Redundant SBAR Assembly” on page 248). 8. Six panhead Phillips screws (two at the top and four at the bottom) secure the power module assembly (1) to the director chassis, as shown in Figure 81. Using a standard Phillips screwdriver, loosen and remove the screws. 1 Figure 81: Power module assembly removal and replacement 9. Pull the power module assembly (with the SBAR assembly support shelf) out of the director chassis.
FRU Removal and Replacement 4. Using a standard Phillips screwdriver, insert and tighten the six panhead Phillips screws that secure the power module assembly. 5. Replace both SBAR assemblies (“RRP: Redundant SBAR Assembly” on page 248). 6. Replace the RFI shield. 7. Seat and connect both power supplies (“RRP: Redundant Power Supply” on page 245). 8. Disconnect the ESD wrist strap from the director chassis and your wrist. 9. Power on the director (“Power-On Procedure” on page 200). 10.
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: 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 customer representative. 4. Power off and unplug the director (“Power-Off Procedure” on page 201).
FRU Removal and Replacement 10. Remove both fan modules (“RRP: Redundant Fan Module” on page 252). 11. Remove both SBAR assemblies (“RRP: Redundant SBAR Assembly” on page 248). 12. Remove the power module assembly (“RRP: Power Module Assembly” on page 255). 13. The backplane (1) is secured to the director chassis with 11 panhead Phillips screws, as shown in Figure 82. 1 SHR-2307 Figure 82: Backplane removal and replacement Remove the backplane: a.
FRU Removal and Replacement Replacing a Backplane To replace the backplane and all FRUs disconnected from the backplane: 1. Replace the backplane: a. Remove the replacement backplane from its protective antistatic bag. Inspect the backplane PWA to ensure no connector pins are damaged. b. Align the guide pins on the back of the backplane with the alignment holes in the director chassis, as shown in Figure 82. c.
FRU Removal and Replacement 9. Power on the director (“Power-On Procedure” on page 200). 10. Verify that POSTs complete and the green power LED on the front bezel, green LED on the active CTP2 card, and green PWR OK LEDs on both power supplies remain illuminated. If a problem is indicated, go to “MAP 0000: Start MAP” on page 46 to isolate the problem. 11. Reprogram the replacement backplane with the original director serial number: a.
FRU Removal and Replacement 13. At the Hardware View, observe all FRU graphics 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 46 to isolate the problem. 14. Perform the data collection procedure (“Collecting Maintenance Data” on page 197). 15. Perform one of the following to clear the system error (ERR) LED: — If at the HAFM application, open the Hardware View and: a.
FRU Removal and Replacement 264 Director 2/64 Service Manual
Illustrated Parts Breakdown 5 This chapter provides an illustrated parts breakdown for all Director 2/64 field-replaceable units (FRUs). Exploded-view assembly drawings are provided for: ■ Front-accessible FRUs ■ Rear-accessible FRUs ■ Miscellaneous parts Exploded-view illustrations portray the director disassembly sequence for clarity. Illustrated FRUs are numerically keyed to associated parts lists. The parts lists also include HP part numbers, descriptions, and quantities.
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. Figure 83: Front-accessible FRUs Table 27: Front-Accessible FRU Parts List Ref. Part Number Ref 266 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 4 3 2 S Figure 84: Rear-accessible FRUs (part 1) Table 28: Rear-Accessible FRU Parts List (Part 1) Ref. Part Number Ref 268 Description Qty.
Illustrated Parts Breakdown 1 2 SHR-2307A Figure 85: Rear-accessible FRUs (part 2) Table 29: Rear-Accessible FRU Parts List (Part 2) Ref. Part Number Ref Description Qty.
Illustrated Parts Breakdown Miscellaneous Parts Table 30 is the parts list for miscellaneous parts Table 30: Miscellaneous Parts . Ref. 270 Part Number Description Ref 254138-001 Power cord, 120 VAC, United States Ref 258754-001 Power cord, AC, 5-15R Ref 254139-001 Power cord, AC Adapter/Jumper, 2.
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) Message 274 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 Action 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. The maximum number of products has already been configured. The number of managed HP switches (48) that can be defined to the HAFM application was reached.
Information and Error Messages Table 31: HAFM Messages (Continued) Message 288 Description Action The nickname is already assigned. Either use a different name or do not save the name as a nickname. The entered nickname already exists in the fabric. Each nickname must be unique. Define a different nickname. The software version on this management server is not compatible with the version on the remote management server.
Information and Error Messages Table 31: HAFM Messages (Continued) Message Description Action This World Wide Name 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 an entry already exists in the Fabric Membership List with the same World Wide Name (WWN).
Information and Error Messages Table 31: HAFM Messages (Continued) Message 290 Description Action You must define at least one remote network address. At least one IP address for a remote workstation must be configured for a remote session to be activated. Define an IP address for at least one remote workstation at the Remote Access dialog box. You must download the HAFM client via the web install.
Information and Error Messages Element Manager Messages This section lists Element Manager information and error messages in alphabetical order. Table 32: Element Manager Messages 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 292 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) 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) 294 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 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) 296 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 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 298 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 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) 300 Message Description Action 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 Description 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 302 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) 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 304 Description Action 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. Incompatible configuration between management style and management server.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message 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. Ensure that you type each character in the correct case (upper or lower), include the dashes, and do not add any spaces at the end.
Information and Error Messages Table 32: Element Manager Messages (Continued) Message 306 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 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 308 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 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) 310 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 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) 312 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 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) 314 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 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. Retry the operation later.
Information and Error Messages Table 32: Element Manager Messages (Continued) 316 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 Director 2/64 Service Manual 317
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 ■ Severity—a severity level that indicates event criticality as follows: — Informational — Minor — 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.
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 CTP2 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 CTP2 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 CTP2 card reset or replacement, the HAFM appliance attempted to acquire an up-to-date copy of its databases from the other CTP2 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 Event Code: 060 Message: Fabric Controller unable to synchronize databases. Severity: Minor. Explanation: Following a CTP2 card reset or replacement, the Fabric Controller attempted to acquire an up-to-date copy of its databases from the other CTP2 card, but failed. All Fabric Controller databases are initialized to an empty state, resulting in a momentary loss of interswitch communication capability.
Event Code Tables Event Code: 062 Message: Maximum interswitch hop count exceeded. Severity: Informational. Explanation: The fabric controller software detected that a path to another fabric element (director or switch) traverses more than three interswitch links (ISLs or hops). This may result in Fibre Channel frames persisting in the fabric longer than standard timeout values allow.
Event Code Tables Severity: Informational. Explanation: A director E_Port recognized an incompatibility with an attached fabric element (director or switch), preventing the director from participating in the fabric. A segmented port does not transmit Class 2 or Class 3 traffic (data from attached devices), but transmits Class F traffic (management and control data from the attached director or switch). Refer to the event data for the segmentation reason.
Event Code Tables Event Code: 070 (Continued) Event Data (Continued): 7 = ELP retransmission failure timeout. A Director 2/64 that exhibits a hardware or link failure attempted to join a fabric and transmitted multiple exchange link protocol (ELP) frames to a fabric element (director or switch). However, because of the problem, the director did not receive responses to the ELP frames, and did not receive a fabric login (FLOGI) frame.
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/64 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: 072 Message: E_Port connected to unsupported switch. Severity: Informational. Explanation: The director is attached (through an ISL) to an incompatible fabric element (director or switch). Action: Disconnect the ISL. 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: 073 Message: Fabric initialization error.
Event Code Tables Event Code: 074 Message: ILS frame delivery error threshold exceeded. Severity: Informational. Explanation: Fabric controller frame delivery errors exceeded an E_Port threshold and caused fabric initialization problems (073 event code). Most fabric initialization problems are caused by control frame delivery errors, as indicated by this code. Event data is intended for engineering evaluation.
Event Code Tables Severity: Informational. Explanation: A director port recognized an incompatibility with the attached fabric element or device and isolated the port. An isolated port does not transmit Class 2, Class 3, or Class F traffic. Refer to the event data for the reason. Action: Action depends on the reason specified in the event data. Event Data: The first byte of event data (byte 0) specifies the port number.
Event Code Tables Event Code: 081 (Continued) Event Data Continued: C = ESA security mismatch–Processing of the Exchange Security Attribute (ESA) frame detected a security feature mismatch. The fabric binding and director binding parameters for this director and the attached fabric element must agree. Ensure the parameters for both fabric elements are compatible or disable the fabric and director binding features.
Event Code Tables Event Code: 090 Message: Database replication time out. Severity: Minor Explanation: Replication of a Fabric Services database from master CTP2 to backup has timed out. The backup CTP2 has been dumped and IPLed. After the backup CTP2 completes the IPL, its databases will be brought up to date and replication will resume.
Event Code Tables Event Code: 091 Message: Database replication discontinued. Severity: Informational Explanation: Replication of Fabric Services databases from master CTP2 to backup has been discontinued because the backup CTP2 has failed or been removed. Action: This event will occur any time the backup CTP2 fails or is removed and does not require any additional action; when the backup CTP2 is recovered/replaced, 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 a 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: 143 Message: Low BB_Credit relieved on an ISL. Severity: Informational. Explanation: Open Trunking firmware detected an ISL with no transmission BB_Credit for a period of time that previously exceeded the configured low BB_Credit threshold. The low-credit condition is now relieved. Action: No action required. Event Data: Byte 0 = Port number reporting low BB_Credit relieved.
Event Code Tables Event Code: 150 (Continued) Event Data: 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.
Event Code Tables Event Code: 150 (Continued) Event Data (Continued): Bytes 12–15 of the event data specify error codes as follows: 01 = Completion fail. 03 = Zone merge error–too many zones. 04 = Zone merge error–incompatible zones. 05 = Zone merge error–too long if reason = 0A. 06 = Zone set definition too long. 07 = Zone set name too short or not authorized. 08 = Invalid number of zones. 09 = Zone merge error–default zone statesincompatible if reason = 0A. 0A = Invalid protocol.
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 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 Data: No supplementary data included with this event.
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 HAFM appliance EWS Event Log 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 CTP2 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 Event Code: 410 Message: CTP2 card reset. Severity: Informational. Explanation: The indicated CTP2 card reset after a director power-on, CTP2 card installation, hardware IML (CTP2 card faceplate), or software IPL. An IPL can be user-initiated at the Element Manager, or occur automatically after a firmware fault (event code 411). The event data indicates the type of reset. Action: No action required.
Event Code Tables Event Code: 412 Message: CTP2 watchdog timer reset. Severity: Informational. Explanation: The hardware watchdog timer expired and caused the CTP2 card to reset. Action: Perform the data collection procedure and return the backup CD to HP support personnel. Event Data: Byte 0 = reset type as follows: 00 = task switch did not occur within approximately one second, 01 = interrupt servicing blocked for more than approximately one second.
Event Code Tables Event Code: 414 Message: Backup CTP2 card failure. Severity: Major. Explanation: The backup CTP2 card failed. Action: Replace the indicated CTP2 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: 416 Message: Backup CTP2 card installed. Severity: Informational. Explanation: A backup CTP2 card was installed while the director was powered on and operational. 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: 417 Message: CTP2 card firmware synchronization initiated.
Event Code Tables Event Code: 418 Message: User-initiated CTP2 card switchover. Severity: Informational. Explanation: The backup CTP2 card became the active CTP2 card after a user-initiated switchover. The previously active CTP2 card is now the backup CTP2 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 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. Severity: Minor.
Event Code Tables Event Code: 430 Message: Excessive Ethernet transmit errors. Severity: Informational. Explanation: Transmit error counters for the active CTP2 card Ethernet adapter (sum of all counters) exceeded a threshold. This does not indicate a CTP2 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 Event Code: 431 Message: Excessive Ethernet receive errors. Severity: Informational. Explanation: Receive error counters for the active CTP2 card Ethernet adapter (sum of all counters) exceeded a threshold. This does not indicate a CTP2 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 Event Code: 432 Message: Ethernet adapter reset. Severity: Minor. Explanation: The active CTP2 card Ethernet adapter was reset in response to an internally detected error. A card failure is not indicated. The director-to-HAFM appliance connection terminates, but automatically recovers after the reset. Action: Perform the data collection procedure and return the backup CD to HP support personnel.
Event Code Tables Event Code: 440 Message: Embedded port hardware failed. Severity: Major. Explanation: The embedded port hardware detected a fatal CTP2 card error. Action: Replace the indicated CTP2 card with a functional card. Perform the data collection procedure and return the backup CD and faulty card to HP support personnel. Event Data: Byte 0 = CTP2 slot position (00 or 01). Byte 1 = engineering reason code Bytes 4 through 7 = elapsed millisecond tick count.
Event Code Tables Event Code: 442 Message: Embedded port anomaly detected. Severity: Informational. Explanation: The CTP2 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 Code: 450 Message: Serial number mismatch detected. Severity: Informational Explanation: This event occurs when the sequence number or OEM serial number in the system VPD (read from the backplane) does not match the sequence number and serial number that were saved in NVRAM the last time the switch was IPLed. This event will occur normally when a CTP2 is moved from one switch to the master position of another switch.
Event Code Tables 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. Action: No action required. Event Data: Byte 0 = feature description as follows: 00 through 04 = Flexport, 06 = open-system HAFM appliance.
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 Severity: Informational. Explanation: The CTP2 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. Bytes 8 and 9 = high-availability error callout #1 Bytes 10 and 11 = high-availability error callout #2.
Event Code Tables Event Code: 503 Message: UPM card hot-removal completed. Severity: Informational. Explanation: A UPM card was removed with the director powered on and operational. Action: No action required. Event Data: Byte 0 = UPM slot position (00 through 0F). Bytes 4 through 7 = elapsed millisecond tick count. 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.
Event Code Tables Event Code: 505 Message: UPM card revision not supported. Severity: Minor. Explanation: The indicated UPM card is not recognized and the four ports display as uninstalled to the director firmware. Action: Ensure the director model supports the operating firmware version. If the firmware version is supported, replace the UPM 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: 506 Message: Fibre Channel port failure. Severity: Major. Explanation: A Fibre Channel port on a UPM card failed. The amber LED corresponding to the port illuminates to indicate the failure. Other ports remain operational if their LEDs are extinguished. 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: 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 Code: 508 Message: Fibre Channel port anomaly detected. Severity: Informational. Explanation: The CTP2 card detected a deviation in the normal operating mode or status of the indicated Fibre Channel port. Action: No action required. An event code 506 is generated if this anomaly results in a hard port failure. Event Data: Byte 0 = port number (0-127 and 132-143). Byte 1 = anomaly reason code. Bytes 4 through 7 = elapsed millisecond tick count.
Event Code Tables Event Code: 509 Message: Fibre Channel path failure. Severity: Major. Explanation: One or more of the backplane data paths has been removed from service, thus reducing the bandwidth capabilities of the associated port. This does not prevent the port from frame reception or transmission, but it does limit the potential throughput of the port. Normally the amber Service Required LED on the port associated with the failing path is illuminated to indicate the degraded status.
Event Code Tables 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. 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 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 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. Action: A link incident record (LIR) is generated and sent to the attached server using the reporting procedure defined in T11/99-017v0 (OSI) or the FICON architecture document (FICON).
Event Code Tables 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). Action: An LIR is generated and sent to the attached server using the reporting procedure defined in T11/99-017v0 (OSI) or the FICON architecture document (FICON).
Event Code Tables 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). Action: An LIR is generated and sent to the attached server using the reporting procedure defined in T11/99-017v0 (OSI) or the FICON architecture document (FICON).
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 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. Bytes 8 and 9 = high-availability error callout #1.
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 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 Data: Byte 0 = SBAR slot position (00 or 01).
Event Code Tables Event Code: 608 Message: User initiated SBAR switch-over. Severity: Informational. Explanation: The backup SBAR has become the active SBAR at a user’s request. The previously active SBAR is now the backup SBAR. Action: No action required. Event Data: There is no supplementary data included with this event.
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 Explanation: The thermal sensor associated with a CTP2 card indicates the warm temperature threshold was reached or exceeded. Action: Replace the indicated CTP2 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: CTP2 card shutdown due to thermal violation. Severity: Major. Explanation: A CTP2 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 CTP2 card fails, the backup card takes over operation. If the backup CTP2 card fails, the active card is not impacted. Action: Replace the failed CTP2 card with a functional card.
Event Code Tables 392 Director 2/64 Service Manual
Index 10/100 BaseT ethernet hub 20 10-100 km configuration, port properties dialog box 180 A backing up, director configuration file 218 backplane removing and replacing 258 beaconing fault isolation 21 blocking port 207 UPM card 208 C call-home notification information, use of 167 reporting 30 channel wrap test, procedure 195 cleaning fiber-optic components 199 configuration changes, audit log 167 Director 2/64 Service Manual Index B Index AC filter module removal 255 applications management servi
Index dialog boxes configure switch parameters 148, 151 director diagnostic features, software 24 displaying information 188 element manager messages 292 embedded web server 27 ethernet link, MAP 95 event codes 319 event log recording events 319 fault isolation 21, 46 firmware 27 firmware library dialog box 211 firmware, release notes 212 general description 20 illustrated parts breakdown 265 IPL procedure 202 MAPs 36 ports blocking or unblocking 207 port list view 173 power-off procedure 201 power-on proc
Index events exporting 170 viewing 169 exporting events 170 F fabric logout, MAP 141 fabric manager logs, list of 167 MAP 87 messages 272, 292 factory default settings, resetting 220 failure analysis 198 fan module removing and replacing 252 fan module events, event codes tables 347 fan modules MAP 110 fault isolation customer checklist 46 diagnostics 35 logs 167 maintenance approach 21 MAPs 36 SNMP traps 29 FC-PH 4.
Index G gateway address, default 36 getting help 17 grounding point front 229 rear 230 H HAFM appliance ethernet link, MAP 95 event log 319 name 50, 89, 94, 103, 160, 162, 225 HAFM application diagnostic features 24 logs, list of 167 MAP 87 messages 272 HAFM server fault isolation 21 MAP 46 firmware versions, storing 211 MAP 87, 157 hardware view displaying director information 188 hardware, MAP 157 help online user documentation 28 help, obtaining 17 hexagonal adapter 30 HP authorized reseller 17 firmwar
Index M N maintenance analysis procedures See MAPs maintenance approach 21 maintenance data, collecting 197 maintenance functions, list of 28 management services application description 25 managing, configuration data 218 MAPs 35, 36 definition 21 MAP 0000-Start Map 46 MAP 0100-Power Distribution Analysis 71 MAP 0200-POST or IML Failure Analysis 81 MAP 0300-HAFM Appliance Software Problem Determination 87 MAP 0400-Loss of HAFM or Web Browser PC Communication 95 MAP 0500-FRU Failure Analysis 110 MAP 0600-
Index ports blocking 207 diagnostics, performing 170 operational states, list of 171 performance statistics 184 port properties 187 port technology 182, 187 unblocking 209 POSTs MAP 81 power distribution system MAP 71 power module assembly removing and replacing 255 power supply removing and replacing 245 power supply events, event codes tables 343 power-off procedure 201 power-on procedure 200 power-on self-tests, MAP 81 preventive maintenance, cleaning fiber-optic components 199 procedural notes 166 proc
Index S safety basic ESD note 228 electric shock, warning 200 electrostatic discharge grounding cable with wrist strap 32 ESD information 229 repair procedures 166 fiber-optic protective plug 31 SBAR assembly event codes 382 MAP 110 removing and replacing 248 tools 248 segmentation MAP 141 service maintenance and diagnostic functions 27 setting offline state 206 online state 205 SFP optical transceivers MAP 118 removing and replacing 241 tools 241 small form factor optical transceivers See SFP optical tran
Index tools 236 unblocking 209 UPM filler blank removing and replacing 244 tools 244 viewing events 169 views performance 175 port list 173 V W versions director firmware 27 firmware adding 212 deleting 215 determining 211 downloading 215 managing 211 modifying description 214 Internet Explorer 27 Netscape Navigator 27 Windows operating systems 33 view panel 28 warning rack stability 16 symbols on equipment 14 web sites HP storage 17 Windows 2000 operating system MAP 87 Windows operating systems, vers
