hp StorageWorks director 2/64 service manual Part Number: AA-RS2EB-TE Second Edition (January 2003) This guide provides procedures for servicing the HP StorageWorks Director 2/64.
© Hewlett-Packard Company, 2003. All rights reserved. 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. This document contains proprietary information, which is protected by copyright.
Contents About This Guide Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Symbols in Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Module Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fan Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SBAR Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backplane. . . . . . . . . . . . . . . .
Contents Link Incident Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–9 Threshold Alert Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10 Using Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12 Port List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Install or Upgrade Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–57 4 FRU Removal and Replacement Procedural Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1 Remove and Replace FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2 ESD Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Glossary Index Figures 1–1 1–2 1–3 1–4 1–5 1–6 1–7 1–8 1–9 1–10 1–11 1–12 2–1 2–2 2–3 2–4 2–5 2–6 2–7 2–8 2–9 2–10 2–11 2–12 2–13 2–14 2–15 2–16 2–17 2–18 3–1 3–2 3–3 HAFM server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9 12-Port Ethernet hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10 Typical network configuration (one Ethernet connection) . . . . . . . . . . . . . . .
Contents 3–4 3–5 3–6 3–7 3–8 3–9 3–10 3–11 3–12 3–13 3–14 3–15 3–16 3–17 3–18 3–19 3–20 3–21 3–22 3–23 3–24 3–25 3–26 3–27 3–28 3–29 3–30 3–31 3–32 3–33 3–34 3–35 3–36 3–37 3–38 3–39 3–40 3–41 viii Hardware Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8 Link Incident Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–9 Threshold Alert Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 4–1 4–2 4–3 4–4 4–5 4–6 4–7 4–8 4–9 4–10 4–11 5–1 5–2 5–3 ESD grounding point (front) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3 ESD grounding point (rear). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3 CTP2 card removal and replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6 UPM card removal and replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 4–1 4–2 4–3 5–1 5–2 5–3 5–4 A–1 A–2 x Factory-set Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1 Concurrent FRU Names and ESD Requirements . . . . . . . . . . . . . . . . . . . . . . . 4–4 Nonconcurrent FRU Names and ESD Precautions . . . . . . . . . . . . . . . . . . . . . . 4–4 Front-Accessible FRU Parts List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2 Rear-Accessible FRU Parts List (Part 1). . . . . . . .
About This Guide This guide describes the service procedures for the HP StorageWorks Director 2/64. 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 Document Conventions The conventions in Table 1 apply. Table 1: Document Conventions Element Convention Cross-reference links Blue text: Figure 1 Key names, menu items, buttons, and dialog box titles Bold File names, application names, and text emphasis Italics User input, command names, system responses (output and messages) Monospace font Variables Monospace, italic font Website addresses Sans serif font (http://thenew.hp.
About This Guide Symbols on Equipment Any enclosed surface or area of the equipment marked with these symbols indicates the presence of electrical shock hazards. Enclosed area contains no operator serviceable parts. WARNING: To reduce the risk of injury from electrical shock hazards, do not open this enclosure. Any RJ-45 receptacle marked with these symbols indicates a network interface connection.
About This Guide Any product or assembly marked with these symbols indicates that the component exceeds the recommended weight for one individual to handle safely. WARNING: To reduce the risk of personal injury or damage to the equipment, observe local occupational health and safety requirements and guidelines for manually handling material. Rack Stability WARNING: To reduce the risk of personal injury or damage to the equipment, be sure that: • The leveling jacks are extended to the floor.
• Product serial numbers • Product model names and numbers • Applicable error messages • Operating system type and revision level • Detailed, specific questions HP Website The HP website has the latest information on this product, as well as the latest drivers. Access storage at: http://thenew.hp.com/country/us/eng/prodserv/storage.html. From this website, select the appropriate product or solution.
1 General Information 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 multiswitch 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 Directors are managed and controlled through an HP-supplied HAFM server with the HAFM and Director 2/64 Product Manager applications installed. The HAFM server is a notebook personal computer (PC) that provides a central point of control for up to 48 directors and/or edge switches. Multiple directors and the HAFM server communicate through the customer’s local area network (LAN).
General Information an interactive interface; no checking is done for pre-existing conditions and no prompts display to guide users through tasks. Refer to the hp StorageWorks CLI reference guide for directors and edge switches.
General Information (service required) LED on the FRU flashes. When unit beaconing is enabled, the system error indicator on the front bezel flashes. Beaconing does not affect port, FRU, or director operation. • Data collection through the Product Manager application to help isolate system problems. The data includes a memory dump file and audit, hardware, and engineering logs.
General Information CAUTION: If zoning is implemented by port number, a change to the director fiber-optic cable configuration disrupts zone operation and may incorrectly include or exclude a device from a zone. If zoning is implemented by WWN, removal and replacement of a device HBA or Fibre Channel interface (thereby changing the device WWN) disrupts zone operation and may incorrectly include or exclude a device from a zone. Zones are grouped into zone sets.
General Information — Fabric A unzoned and Fabric B zoned—The fabrics join successfully, and fabric A automatically inherits the zoning configuration from fabric B. — Fabric A zoned and Fabric B zoned—The fabrics join successfully only if the zone configurations can be merged. If the fabrics cannot join, the connecting E_Ports segment and the fabrics remain independent.
General Information Director Specifications This section lists physical characteristics, storage and shipping environment, operating environment, and service clearances for the Director 2/64. Physical Characteristics Dimensions: Height: 39.7 centimeters (15.7 inch) Width: 44.5 centimeters (17.5 inch) Depth: 54.6 centimeters (21.5 inch) Weight: 52.3 kilograms (115.0 pounds) Shipping weight: 76.
General Information Storage and Shipping Environment Protective packaging must be provided to protect the director under all shipping methods (domestic and international).
General Information Right side: No clearance required Left side: No clearance required HAFM Server Description The HAFM server (Figure 1–1) is a notebook personal computer (PC) that provides a central point of control for up to 48 LAN-connected directors or edge switches. The server is mounted in a slide-out drawer in the HP-supplied equipment rack. The HAFM server or Internet access to the Embedded Web Server interface is required to install, configure, and manage the director.
General Information HAFM Server Specifications The following list summarizes hardware specifications for the HAFM server notebook platform. Current platforms may ship with more enhanced hardware, such as a faster processor, additional random- access memory (RAM), or a higher-capacity hard drive or removable disk drive. • HP laptop server PC with color monitor, keyboard, keyboard-mounted trackpad (mouse), and U. S. power cord.
General Information Embedded Web Server Interface Administrators or operators with a browser-capable PC and an Internet connection can monitor and manage the director through an Embedded Web Server interface. The application provides a graphical user interface (GUI) similar to the Product Manager application, and supports director configuration, statistics monitoring, and basic operation.
General Information Ensure the correct director is selected for service (if the HAFM server manages multiple directors or other HP products) by enabling unit beaconing at the failed director. The amber system error LED on the director front bezel blinks when beaconing is enabled. Instructions to enable beaconing are incorporated into MAP steps.
General Information 1 2 Two Director 2/64s HP Ethernet hub 3 4 HAFM server Remote user workstation Figure 1–3: Typical network configuration (one Ethernet connection) • Part of a second HAFM server interface that connects to the customer’s private intranet and allows operation of the Product Manager application from remote user PCs or workstations. Connection to this LAN segment is optional and depends on customer requirements.
General Information 1 2 Director 2/64 Ethernet hub 3 4 HAFM server Remote user workstation Figure 1–4: Typical network configuration (two Ethernet connections) • Although this dual Ethernet connection is supported by HP, it is not OV-SNM compatible, requires installation of an additional PCMCIA LAN adapter card (not supplied by HP), and is not the recommended configuration for a typical new HP installation at a customer site.
General Information Minimum Remote Console Hardware Specifications Client HAFM and Product Manager applications download and install to remote workstations (from the HAFM server) using a standard web browser.
General Information Field-Replaceable Units The director provides a modular design that enables quick removal and replacement of FRUs. This section describes director FRUs and controls, connectors, and indicators associated with the FRUs. Figure 1–5 illustrates the front of the director.
General Information Figure 1–6 illustrates the rear of the director. 1 2 Redundant fan modules Power module assembly with AC power switch 3 Redundant serial crossbar (SBAR) assemblies Figure 1–6: Director FRUs (rear access) Front Bezel The bezel at the top front of the director includes an amber system error light-emitting diode (LED) and a green power LED. The power LED illuminates when the director is powered on and operational.
General Information CTP2 Card The director is delivered with two CTP2 cards. The active CTP2 card initializes and configures the director after power on and contains the microprocessor and associated logic that coordinate director operation. A CTP2 card provides an initial machine load (IML) button on the faceplate. When the button is pressed and held for three seconds, the director reloads firmware and resets the CTP2 card without switching off power or affecting operational fiber-optic links.
General Information 1 UPM An amber LED (at the top of the card) that illuminates if any port fails or blinks if FRU beaconing is enabled. 2 A bank of amber and green LEDs above the ports. One amber LED and one green LED are associated with each port and indicate port status as follows: • The green LED illuminates (or blinks if there is active traffic) and the amber LED extinguishes to indicate normal port operation. • The amber LED illuminates and the green LED extinguishes to indicate a port failure.
General Information • Shortwave Laser—Shortwave laser transceivers provide connections for transferring data over short distances (2 to 500 meters) through 50-micron or 62.5-micron multimode fiber. • Longwave Laser—Longwave laser transceivers provide connections for transferring data over long distances (up to 10 kilometers) through 9-micron singlemode fiber.
General Information • A power switch (circuit breaker) that controls AC power distribution to both power supplies. The breaker is set manually, or is automatically tripped by internal software if thermal sensors indicate the director is overheated. • A 9-pin maintenance port that provides a connection for a local terminal or dial-in connection for a remote terminal. Although the port is typically used by maintenance personnel, operations personnel use the port to configure network addresses.
General Information Backplane The backplane provides 48 VDC power distribution and connections for all logic cards. The backplane is a nonconcurrent FRU. The director must be powered off prior to FRU removal and replacement.
General Information HAFM and Product Manager Diagnostics NOTE: HAFM and Product 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. The HAFM and Product Manager applications provide a Java-based GUI to manage, monitor, and isolate problems for multiple directors and multiswitch fabrics.
General Information The user interface consists of the HAFM Services window (Figure 1–8), which provides HAFM application status and diagnostic information. The HAFM Services window consists of: • An event table that displays HAFM application events that occurred since the HAFM application was started. • A status line at the bottom of the panel that provides a status indicator and message area.
General Information • Product—The product associated with the event. Some events are associated with the HAFM application, while others are associated with a specific instance of the Product Manager application. In the latter case, the product (Director 2/64) and configured name (or IP address) associated with the instance are displayed. • Event—The numeric event code and a brief description of the event. Status Line The status line provides a status indicator and message area.
General Information The Embedded Web Server interface can be opened from a standard web browser running Netscape Navigator Version 4.6 (or higher) or Microsoft Internet Explorer Version 4.0 (or higher). At the browser, enter the IP address of the director as the Internet uniform resource locator (URL). When prompted at a login screen, enter a user name and password. When the interface opens, the default display is the View panel.
General Information This publication provides instructions for director fault isolation using the Embedded Web Server interface. See Diagnostics on page 2–1 for the fault isolation tasks. 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.
General Information • Assigned a service call from call center personnel upon receipt and confirmation of a director call-home event. Tools and Test Equipment This section describes tools and test equipment that may be required to test, service, and verify operation of the director and attached HAFM server. These tools are either supplied with the director or must be supplied by service personnel. Tools Supplied with the Director The following tools are supplied with the director.
General Information Figure 1–10: SFP fiber-optic loopback plug • Fiber-optic protective plug—For safety and port transceiver protection, fiber-optic protective plugs (Figure 1–11) must be inserted in all director ports without fiber-optic cables attached. The director is shipped with protective plugs installed in all ports.
General Information Tools Supplied by Service Personnel The following tools are expected to be supplied by service personnel performing director maintenance actions. Use of the tools may be required to perform one or more test, service, or verification tasks. • Scissors or pocket knife—A sharp cutting edge (scissors or knife blade) may be required to cut the protective strapping when unpacking replacement FRUs.
2 Diagnostics 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). Maintenance Analysis Procedures NOTE: HAFM and Product Manager screens in this manual may not match the screens on your server and workstation.
Quick Start Table 2–2 lists the MAPs. Fault isolation normally begins at MAP 0000: Start MAP on page 2–12. However, Table 2–3 lists the event codes and the corresponding MAPs. It is a quick start, if an event code is readily available.
Table 2–3: Event Codes Versus Maintenance Action (Continued) Event Code Explanation 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 Management server unable to synchronize databases. Go to MAP 0700: Fabric, ISL, and Segmented Port Problem Determination. 051 Management server database invalid.
Table 2–3: Event Codes Versus Maintenance Action (Continued) Event Code Explanation Action 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. Perform data collection procedure (Collecting Maintenance Data on page 3–37) and return Zip disk to HP support personnel. 074 ILS frame delivery error threshold exceeded.
Table 2–3: Event Codes Versus Maintenance Action (Continued) Event Code Explanation Action 120 Error while processing system management command. If this event persists, perform data collection procedure (Collecting Maintenance Data on page 3–37) and return Zip disk to HP support personnel. 121 Zone set activation failed zone set too large. Reduce size of zone set and retry. 200 Power supply AC voltage failure. Go to MAP 0100: Power Distribution Analysis. 201 Power supply DC voltage failure.
Table 2–3: Event Codes Versus Maintenance Action (Continued) Event Code Explanation Action 310 Cooling fan propeller recovered. No action required. 311 Cooling fan propeller recovered. No action required. 312 Cooling fan propeller recovered. No action required. 313 Cooling fan propeller recovered. No action required. 314 Cooling fan propeller recovered. No action required. 315 Cooling fan propeller recovered. No action required. 320 Fan module removed. Replace FRU.
Diagnostics Table 2–3: Event Codes Versus Maintenance Action (Continued) Event Code Explanation Action 422 CTP2 firmware synchronization complete. No action required. 423 CTP2 firmware download initiated. No action required. 430 Excessive Ethernet transmit errors. Go to MAP 0400: Loss of Console Communication. 431 Excessive Ethernet receive errors. Go to MAP 0400: Loss of Console Communication. 432 Ethernet adapter reset. Go to MAP 0400: Loss of Console Communication.
Diagnostics Table 2–3: Event Codes Versus Maintenance Action (Continued) Event Code 2–8 Explanation Action 452 Backup CTP2 incompatible with configured system settings. Replace the backup CTP2 with a version of hardware capable of supporting the user-configured settings, or adjust the user settings to be compatible with the backup CTP2, and reseat the backup CTP2. 453 New feature key installed. No action required. 460 Management request out of range.
Diagnostics Table 2–3: Event Codes Versus Maintenance Action (Continued) Event Code Explanation Action 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. 508 Fibre Channel port anomaly detected. No action required.
Diagnostics Table 2–3: Event Codes Versus Maintenance Action (Continued) Event Code 2–10 Explanation Action 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. No action required. 601 SBAR assembly recognized. No action required. 602 SBAR assembly anomaly detected.
Diagnostics Table 2–3: Event Codes Versus Maintenance Action (Continued) Event Code Explanation Action 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). Go to MAP 0500: FRU Failure Analysis. 811 Critically hot temperature warning (CTP2 card thermal sensor).
Diagnostics MAP 0000: Start MAP This MAP describes initial fault isolation for the Director 2/64. Fault isolation begins at the HAFM server, failed director, or Internet-connected personal computer (PC) running the Embedded Web Server interface or attached host. 1 Prior to fault isolation, acquire the following information from the customer: • A system configuration drawing or planning worksheet that includes the HAFM server, directors, other HP products, and device connections.
Diagnostics • Display a Dr. Watson for Windows 2000 dialog box? NO ↓ YES An HAFM server application problem is indicated. Event codes are not recorded. Go to MAP 0300: Console Application Problem Determination on page 2–49. Exit MAP. 4 Did the HAFM server crash and display a blue screen with the system dump file in hexadecimal format (blue screen of death)? NO ↓ YES An HAFM server application problem is indicated. Event codes are not recorded.
Diagnostics Figure 2–1: Products View Did the Products View display and is the HAFM application operational? YES ↓ NO An HAFM server hardware problem is indicated. Event codes are not recorded. Go to MAP 0800: Console PC Problem Determination on page 2–108. Exit MAP. 7 Inspect the alert indicators of each managed director at the top of the Products View.
Diagnostics • A red diamond with yellow background indicates that the director is not operational. • A gray square indicates that the status of the director is unknown. Does a gray square display as the background to the icon representing the director reporting the problem? YES ↓ NO Go to step 11. The gray square indicates the HAFM server cannot communicate with the director because: • The director-to-HAFM server Ethernet link failed.
Diagnostics Is the amber LED illuminated on both CTP2 cards? NO YES ↓ Failure of both CTP2 cards is indicated. Event codes are not recorded. Go to MAP 0500: FRU Failure Analysis on page 2–68. Exit MAP. 10 A director-to-HAFM server Ethernet link failure is indicated. Go to step 23 to obtain event codes. If no event codes are found, go to MAP 0400: Loss of Console Communication on page 2–55. Exit MAP.
Diagnostics Redundant FRU failures are indicated. Go to step 23 to obtain event codes. If no event codes are found, go to MAP 0500: FRU Failure Analysis on page 2–68. Exit MAP. 14 Does a yellow triangle (attention indicator) display as the background to the icon representing the director reporting the problem? YES ↓ NO Go to step 18. 15 Double-click the icon representing the director reporting the problem. The Hardware View displays.
Diagnostics A 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 2–68. Exit MAP. 18 A green circle displays as the background to 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.
Diagnostics 20 Does a yellow triangle (attention indicator) overlay a UPM card graphic? YES ↓ NO Go to step 22. 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 2–2. Figure 2–2: Port Properties dialog box 3. Inspect the Operational State field.
Diagnostics A message displays indicating a link incident problem. Go to step 23 to obtain event codes. If no event codes are found, go to MAP 0600: UPM Card Failure and Link Incident Analysis on page 2–76. Exit MAP. 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 or Port Card View, choose Logs > Link Incident Log. The Link Incident Log displays, as shown in Figure 2–3.
Diagnostics ↓ The director is operational. Exit MAP. A link incident problem is indicated. Go to step 23 to obtain event codes. If no event codes are found, go to MAP 0600: UPM Card Failure and Link Incident Analysis on page 2–76. Exit MAP. 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.
Diagnostics Return to the MAP step that sent you here. 24 Are you at the director reporting the problem? YES ↓ NO Go to step 36. 25 Is the power LED (green) at the director front bezel illuminated? NO YES ↓ Go to step 30. 26 Is the director connected to facility AC power and powered on? NO YES ↓ Go to step 29. 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.
Diagnostics ↓ A power distribution problem is indicated. Go to step 23 to obtain event codes. If no event codes are found, go to MAP 0100: Power Distribution Analysis on page 2–34. Exit MAP. 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.
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 a 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 A 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 2–68. 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 2–34. Exit MAP.
Diagnostics 2. Launch the PC browser application by double-clicking the appropriate icon at the Windows desktop. 3. At the Netsite field (Netscape Navigator) or Address field (Internet Explorer), type http://xxx.xxx.xxx.xxx, where xxx.xxx.xxx.xxx is the IP address of the director (obtained in step 1 on page 2-12). The Username And Password Required dialog box displays. 4. Type the user name and password obtained in step 1, and click OK.
Diagnostics 39 Is the Embedded Web Server interface operational with the View panel displayed? NO YES ↓ Go to step 44. 40 A Page cannot be found, Unable to locate the server, HTTP 404-file not found, or other similar message displays. The message indicates the web browser PC cannot communicate with the director because: • The director-to-PC Internet link could not be established. • AC power distribution in the director failed, or AC power was disconnected.
Diagnostics NO ↓ YES Failure of both CTP2 cards is indicated. Event codes are not recorded. Go to MAP 0500: FRU Failure Analysis on page 2–68. Exit MAP. 43 A director-to-PC Internet link problem (Internet too busy or IP address typed incorrectly) is indicated. 1. Wait approximately five minutes, then attempt to login 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.
Diagnostics Figure 2–6: View Port Properties panel Does the Beaconing field display an On message? YES ↓ NO Go to step 47. 46 Port beaconing is enabled. 1. Consult the customer and next level of support to determine the reason port beaconing is enabled.
Diagnostics 2. Disable port beaconing: a. At the View panel, choose Operations option at the left side of the panel. The Operations panel opens with the Port Beaconing page displayed. b. Click the Beaconing State check box for the port. The check mark disappears from the box and port beaconing is disabled. c. Return to the View panel (Port Properties tab). Continue. 47 At the View panel, does the Operational State field display a Segmented message? NO ↓ YES Port segmentation is indicated.
Diagnostics 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 2–7. Figure 2–7: View FRU Properties panel 2. Inspect the Status fields for both power supplies. Does the Status field display a Failed message for either power supply? NO ↓ YES A power supply failure is indicated. Go to step 52 to obtain event codes. If no event codes are found, go to MAP 0100: Power Distribution Analysis on page 2–34.
Diagnostics Does the State field display a Failed message for any of the FRUs? YES ↓ NO The director is operational. Exit MAP. A FRU failure is indicated. Continue to the next step to obtain event codes. If no event codes are found, go to MAP 0500: FRU Failure Analysis on page 2–68. Exit MAP. 52 Obtain event codes from the Embedded Web Server event log. NOTE: If multiple event codes are found, note all codes and associated severity levels.
Diagnostics Figure 2–8: Monitor Log panel Were one or more event codes found? NO YES ↓ Go to Table 2–3 on page 2-2. Return to the MAP step that sent you here. 53 You are at the console of an open systems interconnection (OSI) or Fibre Connection (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 Table 2–4: MAP 100: 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. Go to step 8. 3 A redundant power supply is disconnected from facility power, not properly installed, or has failed. Verify the power supply is connected to facility power. 1.
Diagnostics ↓ 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 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. • Input frequency between 47 and 63 Hz. Is facility power within specifications? NO ↓ YES Go to step 7.
Diagnostics YES ↓ NO Fault isolation is being performed at the HAFM server 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. If not, ask the customer set the circuit breakers on. 3.
Diagnostics ↓ 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 ↓ The director is operational. Exit MAP. 17 Both power supplies failed and must be removed and replaced (RRP: Redundant Power Supply on page 4–17). 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. Replace both original power supplies to avoid the cost of expending replacement FRUs. Continue.
Diagnostics 20 The backplane failed and must be removed and replaced (RRP: Backplane on page 4–29). • This procedure is nonconcurrent 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 gray square indicates the HAFM server cannot communicate with the director because: • The director-to-HAFM server 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 • 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. 27 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 MAP 0200: POST Failure Analysis When the director is powered on, it performs a series of power-on self-tests (POSTs). When POSTs complete, the director performs an initial program load (IPL) that loads firmware and brings the unit online. This MAP describes fault isolation for problems that may occur during the POST/IPL process. If an error is detected, the POST/IPL process continues in an attempt to initialize the director and bring it online.
Diagnostics 3 Table 2–5 lists event codes, brief explanations of the codes, and the associated steps that describe fault isolation procedures. Table 2–5: MAP 200: Event Codes Event Code Explanation Action 400 Power-up diagnostic failure. Go to step 4. 411 Firmware fault. Go to step 11. 413 Backup CTP2 card POST failure. Go to step 12. 4 POST/IPL diagnostics detected a FRU failure as indicated by an event code 400 with supplementary event data. 1.
Diagnostics 5 The backplane failed POSTs (indicated by a 01 FRU code) and must be removed and replaced (RRP: Backplane on page 4–29). • This procedure is nonconcurrent 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 Contact the next level of support. Exit MAP. 8 A fan module failed POSTs (indicated by a 05 FRU code) and must be removed and replaced (RRP: Redundant Fan Module on page 4–23). • 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 fan module replacement solve the problem? NO ↓ YES The director is operational. Exit MAP. Contact the next level of support. Exit MAP.
Diagnostics Contact the next level of support. Exit MAP. 11 POST/IPL diagnostics detected a firmware failure (as indicated by an event code 411) and performed an online dump. All Fibre Channel ports reset after the failure and devices momentarily logout, login, and resume operation. Perform the data collection procedure and return the information to HP for analysis by third-level support personnel. Exit MAP.
Diagnostics MAP 0300: Console Application Problem Determination This map describes isolation of HAFM server problems, including problems associated with the Windows 2000 operating system, and HAFM and Product Manager applications. 1 Did the HAFM server 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. Close the HAFM application. 1. Simultaneously press Ctrl + Alt + Delete.
Diagnostics 3. Choose (highlight) the HP StorageWorks HA-Fabric Manager entry and click End Task. The HAFM application closes. Continue. 3 Attempt to clear the problem by rebooting the HAFM server PC. 1. Choose Start > Shut Down. The Shut Down Windows dialog box displays. 2. At the Shut Down Windows dialog box, select Shut Down The Computer and click Yes to power off the PC. 3. Wait approximately 30 seconds and power on the PC. After POSTs complete, the Begin Logon dialog box displays. 4.
Diagnostics Figure 2–10: HAFM Login dialog box 5. At the HAFM Login dialog box, type a user name, password, and HAFM server name (obtained in MAP 0000: Start MAP on page 2–12, and all are case sensitive), and click Login. The application opens and the Products View displays. Did the Products View display and is the HAFM application operational? NO ↓ YES The problem is transient and the HAFM server is operational. Exit MAP. Contact the next level of support. Exit MAP.
Diagnostics NO ↓ YES An HAFM application error occurred. Click OK to close the dialog box and close the HAFM application. Go to step 3. 5 Did the HAFM application display a dialog box with the message The software version on this HAFM server is not compatible with the version on the remote HAFM server? YES ↓ NO Go to step 8. 6 The HAFM applications running on the HAFM server and client workstation are not at compatible release levels. Recommend to the customer that the downlevel version be upgraded.
Diagnostics ↓ A Product Manager application error occurred. Click OK to close the dialog box, and close the HAFM and Product Manager applications. Go to step 3. 9 Did the Product Manager application display a dialog box with the message Send firmware failed? YES ↓ NO Go to step 11. 10 An attempt to download a firmware version from the HAFM server hard drive to the director failed. Retry the operation (Manage Firmware Versions on page 3–48).
Diagnostics 13 Did the HAFM server lock up or crash and display a Dr. Watson for Windows 2000 dialog box? NO ↓ YES A Windows 2000 operating system or HAFM application error occurred. Click Cancel to close the dialog box and HAFM application. Go to step 3. 14 Did the HAFM server crash and display a blue screen with the system dump file in hexadecimal format (“blue screen of death”)? YES ↓ NO The HAFM server is operational. Exit MAP. 15 Attempt to clear the problem by power cycling the HAFM server PC. 1.
Diagnostics MAP 0400: Loss of Console Communication This MAP describes fault isolation of the Ethernet communication link between a director and the HAFM server, or between a director and a web browser PC running the Embedded Web Server interface. Failure indicators include: • At the Products View, a gray square at the alert panel and as the background to the icon representing the director reporting the problem.
Diagnostics Table 2–7: MAP 400: 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 server? YES ↓ NO Fault isolation is being performed through the Embedded Web Server interface. Go to step 25.
Diagnostics • 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. Is the director powered on? YES ↓ NO A power distribution problem is indicated. Go to MAP 0100: Power Distribution Analysis on page 2–34. Exit MAP. 6 At the director, inspect the amber LED at the top of each CTP2 card.
Diagnostics Table 2–8 lists the error messages and associated steps that describe fault isolation procedures. Table 2–8: MAP 400: 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. Go to step 23.
Diagnostics ↓ Go to step 11. 10 If appropriate, verify that the hubs are correctly daisy-chained. 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.
Diagnostics • If the problem is associated with an unrelated device, notify the customer and have the system administrator correct the problem. Did repair of an unrelated LAN-attached device solve the problem? NO ↓ YES The director-to-HAFM server connection is restored and is operational. Exit MAP. Contact the next level of support. Exit MAP. 14 The Ethernet adapter on the director’s active CTP2 card reset in response to an error.
Diagnostics 17 A director firmware upgrade is required (Download a Firmware Version to a Director on page 3–52). Perform the data collection procedure after the download. Did the director-to-HAFM server Ethernet connection recover? NO YES ↓ The director-to-HAFM server connection is restored and is operational. Exit MAP. Contact the next level of support. Exit MAP. 18 An instance of the HAFM application is open at another HAFM server and communicating with the director (duplicate session).
Diagnostics 5. Record the IP address, then click OK to close the dialog box. At the Network dialog box, click OK to close the dialog box. 6. Close the Control Panel window. Continue. 20 Configure the HAFM server reporting the Duplicate Session communication problem as a client. 1. At the Products View, click Logout/Exit and choose Logout. The HAFM Login dialog box displays. 2.
Diagnostics 3. Power on the maintenance terminal. After the PC powers on, the Windows desktop displays. 4. Choose Start > Programs > Accessories > HyperTerminal. The Connection Description dialog box displays. NOTE: The following steps describe inspecting the IP address using HyperTerminal serial communication software. 5. Type 64 in the Name field and click OK. The Connect To dialog box displays. 6.
Diagnostics 22 Define the director’s correct IP address to the HAFM server. 1. At the Products View, right-click the icon with the gray square representing the director reporting the problem. A menu displays. 2. Choose Modify. The Modify Network Address dialog box (Figure 2–11) displays. Figure 2–11: Modify Network Address dialog box 3. Type the correct IP address and click OK.
Diagnostics Figure 2–12: New Product dialog box 5. Type the configured IP address in the Network Address field. 6. Choose Director 2/64 from the Product Type list box and click OK. Did the IP address below the director icon change to the new entry and did the Ethernet connection recover? NO ↓ YES The director-to-HAFM server connection is restored and is operational. Exit MAP. 24 The product at the configured IP address is not a HP managed product. Notify the customer of the problem. 1.
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 (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 29 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 login 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 2–12).
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 2–9: MAP 500: Event Codes (Continued) Event Code Explanation Action 420 Backup CTP2 card NV-RAM failure. 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. Go to step 9. 805 High temperature warning (SBAR assembly thermal sensor). Go to step 9.
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 7 A CTP2 card failed and must be removed and replaced (RRP: Redundant CTP2 Card on page 4–5). • 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 CTP2 card replacement solve the problem? NO YES ↓ The director is operational. Exit MAP. Contact the next level of support. Exit MAP. 8 Inspect both SBAR assemblies at the rear of the director.
Diagnostics 10 Is fault isolation being performed at the HAFM server? YES ↓ NO Fault isolation is being performed at the Embedded Web Server interface. Go to step 18. 11 Is a blinking red and yellow diamond (failed FRU indicator) overlaying a fan module graphic at the Hardware View? NO ↓ YES A fan module failure is indicated. Go to step 5. 12 Is a blinking red and yellow diamond (failed FRU indicator) overlaying a CTP2 card graphic at the Hardware View? NO ↓ YES A CTP2 card failure is indicated.
Diagnostics The gray square indicates the HAFM server cannot communicate with the director because: • The director-to-HAFM server Ethernet link failed. • AC power distribution in the director failed, or AC power was disconnected. • Both of the director’s CTP2 cards failed. Continue. 15 At the director, inspect the amber LED at the top of each CTP2 card. Is the amber LED illuminated on both CTP2 cards? NO ↓ YES Failure of both CTP2 cards is indicated. Go to step 7.
Diagnostics 18 Is the Embedded Web Server interface operational? NO YES ↓ Go to step 22. 19 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 21 At the director, inspect the amber LED at the top of each CTP2 card. Is the amber LED illuminated on both CTP2 cards? NO ↓ YES Failure of both CTP2 cards is indicated. Go to step 7. Analysis for an Ethernet link failure is not described in this MAP. Go to MAP 0000: Start MAP on page 2–12. If this is the second time at this step, contact the next level of support. Exit MAP. 22 Inspect fan module operational states at the Embedded Web Server interface. 1.
Diagnostics Does the Status field display a Failed message for either SBAR assembly? NO YES ↓ An SBAR assembly failure is indicated. Go to step 9. The director is operational. Exit MAP. MAP 0600: UPM Card Failure and Link Incident Analysis This MAP describes fault isolation for UPM cards, shortwave laser small form factor pluggable (SFP) optical transceivers, and longwave laser SFP optical transceivers; and for Fibre Channel link incidents.
Diagnostics ↓ Go to step 4. 3 Table 2–10 lists event codes, brief explanations of the codes, and associated steps that describe fault isolation procedures. Table 2–10: MAP 600: Event Codes Event Code Explanation Action 080 Unauthorized world-wide name. Go to step 23. 504 UPM card failure. Go to step 7. 505 UPM card revision not supported. Go to step 36. 506 Fibre Channel port failure. Go to step 7. 507 Loopback diagnostics port failure. Go to step 14.
Diagnostics ↓ Fault isolation is being performed at the HAFM server or Embedded Web Server interface. Go to step 8. 5 Inspect the faceplates of UPM cards at the front of the director. Each card has an amber LED (at the top of the card) that illuminates if the card fails or if any Fibre Channel port fails. Each card also has a bank of amber and green LEDs above the ports. Each LED pair is associated with a corresponding port (for example, the top LED pair is associated with the top port).
Diagnostics 13 12 11 10 UPM Cards 9 8 43 3F 3B 37 33 2F 2B 27 63 59 55 51 47 43 39 35 42 3E 3A 36 32 2E 2A 26 62 58 54 50 46 42 38 34 41 3D 39 35 31 2D 29 25 61 57 53 49 45 41 37 33 40 3C 38 34 30 2C 28 24 60 56 52 48 44 40 36 32 CTP2 - 0 Card 14 CTP2 - 1 Card UPM Cards 15 7 6 5 4 3 2 1 0 23 1F 1B 17 13 0F 0B 07 31 23 27 19 15 11 07 03 22 1E 1A 16 12 0E 0A 06 30 22 26 18 14 10 06 02 21 1D 19 15 11 0D 09 05 29 25 21 17 13 09 05 01 20
Diagnostics NO ↓ YES The director is operational. Exit MAP. Contact the next level of support. Exit MAP. 8 Is fault isolation being performed at the HAFM server? YES ↓ NO Fault isolation is being performed at the Embedded Web Server interface. Go to step 38. 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.
Diagnostics 12 Inspect the port state and LED status for all ports with an attention indicator. 1. At the Port Card View, double-click the port graphic with the attention indicator. The Port Properties dialog box displays. 2. Inspect the Operational State field at the Port Properties dialog box, and the emulated green and amber LEDs adjacent to the port at the Port Card View. 3.
Diagnostics At the Hardware View or Port Card View, click Logs and choose Link Incident Log. The Link Incident Log displays. If a link incident occurred, the affected port number is listed with one of the following messages. Link interface incident-implicit incident. Link interface incident-bit-error threshold exceeded. Link failure-loss of signal or loss of synchronization. Link failure-not-operational primitive sequence (NOS) received. Link failure-primitive sequence timeout.
Diagnostics 15 An electronic circuit breaker on the UPM card may have tripped. To reset the circuit breaker, partially remove and reseat the UPM card for which external loopback tests failed (RRP: UPM Card on page 4–9). 1. Unseat and disconnect the UPM card from the backplane. Unseat the card only, do not remove it from the director chassis. 2. Reseat the UPM card in the backplane. 3. Perform an external loopback test on the UPM card.
Diagnostics 18 The port has an invalid attachment. The information in the Port Properties dialog box specifies the reason (Table 2–12). Table 2–12: MAP 600: Invalid Attachment Reasons and Actions Reasons Action Unknown Contact the next level of support. ISL connection not allowed on this port. Go to step 19. Incompatible switch at other end of ISL. Go to step 20. External loopback adapter connected to the port. Go to step 21. N-Port connection not allowed on this port. Go to step 19.
Diagnostics NO YES ↓ The director is operational. Exit MAP. Contact the next level of support. Exit MAP. 20 The director is configured for Open Fabric mode but the switch or director at the other end of the ISL is not configured to Open Fabric mode. The director is configured for S/390 mode but the switch or director at the other end of the ISL is not configured to S/390 mode. Configure the director operating mode: 1. Ensure the director is set offline (Set Offline State on page 3–44). 2.
Diagnostics 22 Remove the loopback plug from the port receptacle. If directed by the customer, connect a fiber-optic jumper cable attaching a device to the director. • If the port is operational and a device is not attached, both LEDs adjacent to the port extinguish and the port state is No Light. • If the port is operational and a device is attached, the green LED illuminates, the amber LED extinguishes, and the port state is Online.
Diagnostics 24 Clean the fiber-optic connectors on the 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 3–45). 3. Disconnect both ends of the fiber-optic cable. 4. Clean the fiber-optic connectors. (Clean Fiber-Optic Components on page 3–39). 5. Reconnect the fiber-optic cable. 6. Unblock the port (Unblock a Port on page 3–46).
Diagnostics 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. Did service of the HBAs solve the problem? NO ↓ YES Exit MAP. Contact the next level of support. Exit MAP. 28 The director and attached device are performing a Fibre Channel link reset. This is a transient state. Wait approximately 30 seconds and inspect port state and LED behavior.
Diagnostics Figure 2–15: Clear Link Incident Alert(s) 3. Choose This port (n) only option (where n is the port number) and click OK. The link incident clears. 4. Monitor port operation for approximately five minutes. Did the link incident recur? YES ↓ NO The problem is transient and the Fibre Channel link and director are operational. Exit MAP. 30 Inspect the fiber-optic jumper cable attached to the port and ensure the cable is not bent and connectors are not damaged.
Diagnostics YES ↓ NO The Fibre Channel link and director are operational. Exit MAP. 32 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 3–45). 3. Disconnect both ends of the fiber-optic jumper cable. 4. Clean the fiber-optic connectors (Clean Fiber-Optic Components on page 3–39). 5.
Diagnostics 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. 35 The director port reporting the problem is causing the recurrent link incident. The recurring link incident indicates port or UPM card degradation and a possible pending failure. Go to step 6. 36 A UPM card is not recognized by director firmware because the firmware version is not supported or the UPM card failed.
Diagnostics 39 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 NO YES ↓ A UPM card failure is indicated. Go to step 7. 42 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. Scroll down the View panel as necessary. 4.
Diagnostics • Figure 2–17 shows UPM card numbers (0 through 15), port numbers (00 through 63), and bolded logical port addresses (hexadecimal 04 through 43) for a FICON environment. 3. Perform an external loopback test for the port as part of FRU removal and replacement. Exit MAP.
Diagnostics MAP 0700: Fabric, ISL, and Segmented Port Problem Determination This MAP describes isolation of fabric logout, interswitch link (ISL), and E_Port segmentation problems. Failure indicators include: • An event code recorded at the Director 2/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 2–14: MAP 700: Event Codes (Continued) Event Code Explanation Action 050 Management server unable to synchronize databases. Go to step 8. 051 Management server database invalid. Go to step 8. 052 Management server internal error. Go to step 8. 060 Fabric controller unable to synchronize databases. Go to step 9. 061 Fabric controller database invalid. Go to step 9. 062 Maximum interswitch hop count exceeded. Go to step 10. 063 Received link state record too large.
Diagnostics 5 Inspect the port state and LED status for all ports with an attention indicator. 1. At the Port Card View, double-click the port graphic with the attention indicator. The Port Properties dialog box displays as shown on the following page. 2. Inspect the Operational State field at the Port Properties dialog box. Does the Operational State field indicate Segmented E_Port? YES ↓ NO Analysis for a UPM card failure or other link incident is not described in this MAP.
Diagnostics • Event code 011-Following a CTP2 card failover, the login server database failed cyclic redundancy check (CRC) validation. • Event code 020-Following a CTP2 card reset, the name server attempted to acquire a fabric server database copy from the other CTP2 card and failed. • Event code 021-Following CTP2 card failover, the name server database CRC validation. All attached devices resume operation after fabric login.
Diagnostics 10 As indicated by an event code 062, the fabric controller software detected a path to another director (or fabric element) in a multiswitch fabric that traverses more than three interswitch links (hops). Fibre Channel frames may persist in the fabric longer than timeout values allow. Advise the customer of the problem and work with the system administrator to reconfigure the fabric so the path between any two fabric elements does not traverse more than three hops.
Diagnostics A 071 event code indicates the director is isolated from all directors in a multiswitch fabric, and is accompanied by a 070 event code for each segmented E_Port. The 071 event code is resolved when all 070 events are corrected. Obtain supplementary event data for each 070 event code. 1. At the HAFM server’s Hardware View, select Event Log from the Logs menu. The Event Log displays. 2. Examine the first five bytes (0 through 4) of event data. 3.
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 both directors will set offline. Ensure the system administrator quiesces Fibre Channel frame traffic through the directors and sets attached devices offline. 3.
Diagnostics 2. Notify the customer both directors will set offline. Ensure the system administrator quiesces Fibre Channel frame traffic through the directors and sets attached devices offline. 3. Set both directors offline (Set Offline State on page 3–44). 4. At the Hardware View or Port Card View for the first director reporting the problem, choose Configure > Operating Parameters > Switch Parameters. The Configure Switch Parameters dialog box displays. 5.
Diagnostics 3. Click the Fabrics tab. In the left pane of the Fabrics View window, select the fabric of which the director is a member. The Fabrics View displays with the default Topology tab active. 4. Click the Zone Set tab at the bottom of the window. The Zone Set View displays with the Active Zone Set displayed (Figure 2–18). Figure 2–18: Zone Set View 5. Inspect zone names in the active zone set to determine the incompatible name. 6. Modify the incompatible zone name as directed by the customer: a.
Diagnostics e. In the left pane of the Fabric View window, select the fabric containing the zone name that was changed. Click the Zone Set tab. Verify that the message area below the Active Zone Set contains the message “The active zone set does not currently match the configured zone set.” f. To activate the zone set, click Configure and choose Active Zone Set. The Active Zone Set dialog box displays. Select the zone to be activated and click Next. g.
Diagnostics 18 Initial program load (IPL) the director (IPL the Director on page 3–41). Did the IPL solve the problem and did both directors join through the ISL to form a fabric? NO ↓ YES The directors, associated ISL, and multiswitch fabric are operational. Exit MAP. Perform the data collection procedure and contact the next level of support. Exit MAP. 19 A director E_Port segmented because no director in the fabric is capable of becoming the principal switch. 1.
Diagnostics 5. Set the director online (Set Online State on page 3–43). Did the switch priority change solve the problem and did both directors join through the ISL to form a fabric? NO ↓ YES The directors, associated ISL, and multiswitch fabric are operational. Exit MAP. Contact the next level of support. Exit MAP. 20 A director E_Port segmented (at an operational director) because a response to a verification check indicates an attached director is not operational. 1.
Diagnostics ↓ 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 2–12. If this is the second time at this step, contact the next level of support. Exit MAP. 23 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. Click the port number (0 through 63) of the segmented port. 3.
Diagnostics MAP 0800: Console PC Problem Determination This MAP describes isolation of hardware-related problems with the HAFM server platform. Although this MAP provides high-level fault isolation instructions, refer to the documentation provided with the PC for detailed problem determination and resolution. 1 At the HAFM server, close the HAFM application. 1. At the Products View, click Logout/Exit and choose Exit. The HAFM application closes. 2. Close any other applications that are running. Continue.
Diagnostics 3 Reboot the HAFM server PC and perform system diagnostics. 1. Choose Start > Shut Down. The Shut Down Windows dialog box displays. 2. At the Shut Down Windows dialog box, choose Shut Down The Computer and click Yes to power off the PC. 3. Wait approximately 30 seconds and power on the PC. After POSTs complete, the Begin Logon dialog box displays. 4. Simultaneously press Ctrl + Alt + Delete to display the Logon Information dialog box.
Diagnostics 6 Perform one of the following: • If the PC has standalone diagnostic test programs resident on the hard drive, perform the diagnostics. Refer to supporting documentation shipped with the PC for instructions. • If the PC does not have standalone diagnostic test programs resident on fixed disk, go to step 7. Did diagnostic test programs detect a problem? NO ↓ YES Refer to the supporting documentation shipped with the PC for instructions to resolve the problem. Exit MAP.
Diagnostics 8 Re-install the HAFM application (Install or Upgrade Software on page 3–57). Did the HAFM application install and open successfully? NO ↓ YES The PC is operational. Exit MAP. 9 Advise the customer and next level of support that the PC hard drive should be restored to its original factory configuration. If the customer and support personnel do not concur, go to step 10. 1. Restore the PC hard drive using the HAFM Server Restore/Boot CD shipped with the PC. Refer to the readme.
3 Repair Information This chapter describes repair and repair-related procedures used by service representatives for the Director 2/64 and associated field-replaceable units (FRUs). The following procedures are described: • Obtaining log information at the HAFM server. • Displaying and using HAFM server views. • Obtaining and interpreting port diagnostic and performance data, and performing port diagnostic loopback tests. • Channel wrap tests. • Swapping ports. • Collecting maintenance data.
Repair Information Factory Defaults Table 3–1 lists the defaults for the passwords, and IP, subnet, and gateway addresses. Table 3–1: 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 Product Manager screens in this manual may not match the screens on your server and workstation.
Repair Information Using Log Information The HAFM and Product Manager applications provide access to ten 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: • HAFM Audit Log. • HAFM Event Log. • Session Log. • Product Status Log. • Fabric Log.
Repair Information Figure 3–1: HAFM Event Log Information associated with a call-home failure is intended for use by maintenance personnel to fault isolate the problem (modem failure, no dial tone, etc.), while information provided in all other entries is generally intended for use by third-level support personnel to fault isolate more significant problems. To open the HAFM Event Log from the HAFM application, click Logs and choose Event Log.
Repair Information Product Status Log The Product Status Log as shown in Figure 3–2, records an entry when the status of a director changes. The log reflects the previous status and current status of the director, and indicates the instance of a Product Manager application that should be opened to investigate a problem. The information is useful to maintenance personnel for fault isolation and repair verification.
Repair Information • Fabric Status Changed–The column displays the type of change in the fabric (for example, a switch was added or removed, an ISL was added or removed, the fabric was renamed or persisted, or a zone set became active). • Description–The column displays a description of the change in the fabric.
Repair Information To open the Director 2/64 Event Log from the Product Manager application, click Logs and choose Event Log. The log contains the following columns: • Date/Time–The date and time the director event occurred. • Event–The three-digit event code associated with the event. See Appendix B, Event Code Tables for an explanation of event codes. • Description–A brief description of the event. • Severity–The severity of the event (Informational, Minor, Major, or Severe).
Repair Information Clear the Director 2/64 Event Log To ensure the Director 2/64 Event Log is up-to-date and not filled with archived events, periodically clear the log display. To clear the log, click Clear at the bottom of the log window. Hardware Log The Hardware Log as shown in Figure 3–4, displays a history of FRU removals and replacements (insertions) for the director. The information is useful to maintenance personnel for fault isolation and repair verification.
Repair Information • Position–A number representing the FRU chassis position. The chassis (slot) position for a nonredundant FRU is 0. The chassis positions for redundant FRUs are 0 and 1. The chassis positions for UPM cards are 0 through 15 inclusive. • Action–The action performed (Inserted or Removed). • Part Number–The part number of the inserted or removed FRU. • Serial Number–The serial number of the inserted or removed FRU.
Repair Information — Link failure-loss-of-signal or loss-of-synchronization. — Link failure-not-operational primitive sequence received. — Link failure-primitive sequence timeout. — Link failure-invalid primitive sequence received for current link state. See MAP 0600: UPM Card Failure and Link Incident Analysis on page 2–76 or MAP 0700: Fabric, ISL, and Segmented Port Problem Determination on page 2–95 for corrective actions in response to these link incident messages.
Repair Information Figure 3–6: Threshold Alert Log To open the Threshold Alert Log from the Product Manager application, click Logs and choose Threshold Alert Log. The log contains the following columns: • Date/Time–The date and time stamp for when the alert occurred. • Name–The name for the alert as configured through the Configure Threshold Alerts dialog box. • Port–The port number where the alert occurred. • Type–The type of alert: transmit (Tx) or receive (Rx).
Repair Information Using Views In addition to the Hardware View, the Product Manager application provides access to a series of views (windows) that provide information for administrators, users, and maintenance personnel. These views are accessed through the Hardware View or Fabrics View, and include the: • Port List View. • FRU List View. • Node List View. • Performance View. • Topology View. • Zone Set View.
Repair Information • Addr–The director logical port address (05 through 43 inclusive) in hexadecimal format (S/390 operating mode 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. Valid states are: — Online, offline, or testing. — Beaconing. — Invalid attachment. — Link incident or link reset. — No light, not operational, or port failure. — Segmented E_Port.
Repair Information • Reset the port. • Configure port binding. • Clear threshold alerts. FRU List View The FRU List View as shown in Figure 3–8, displays a list of all director FRUs. The information is useful to maintenance personnel for fault isolation and repair verification. Figure 3–8: FRU List View To open the FRU List View from the Hardware View, click View and choose FRU List. The FRU List View contains the following columns: • FRU–An acronym representing the FRU type.
Repair Information — UPM (or GSF)–UPM card. — PM–Port module — FAN–Fan module. — PWR–Power supply. • Position–A number representing the FRU chassis position. The chassis (slot) position for a nonredundant FRU is 0. The chassis positions for redundant FRUs are 0 and 1. The chassis positions for UPM cards are 0 through 15 inclusive. • Status–The FRU status (Active or Backup). • Part Number–The FRU part number. • Serial Number–The FRU serial number.
Repair Information Figure 3–9: Node List View • Port WWN–The eight-byte (16-digit) world-wide name (WWN) assigned to the port or Fibre Channel interface installed on the attached device. — If a nickname is not assigned to the WWN, the WWN is prefixed by the device manufacturer’s name. — If a nickname is assigned to the WWN, the nickname displays in place of the WWN. • BB_Credit–The buffer-to-buffer credit (BB_Credit) value assigned to a port attached to a device.
Repair Information Topology View To open the Topology View from the main HAFM or Products View, choose the Fabrics tab. In the left pane of the Fabrics View window, select the fabric of which the director is a member. The Topology View as shown in Figure 3–10, displays with the default Topology tab active. The left panel displays an expandable fabrics tree that lists managed fabrics, director, and switch elements in each fabric, and nodes (Fibre Channel devices) connected to fabric elements.
Repair Information An HAFM status bar at the bottom left corner of the view window displays colored icons (green circle, yellow triangle, red and yellow diamond, or gray square) that indicate the most degraded or critical status of any managed product, fabric, or the HAFM server. Messages display as required to the right of the colored icons. By double-clicking a fabric icon or right-clicking a fabric icon and selecting from menu options, a user opens the Product Manager application for the element.
Repair Information Zone members display as: • The unique 16-digit WWN identifying the device attached to the port. If a nickname is configured, the nickname displays instead. For example: 10:00:02:06:77:43:B0:1C • A unique domain ID (1 through 31 inclusive) and port number (0 through 63 inclusive) if zoned by port number. For example: Domain 1, Port 7 The information is also useful to maintenance personnel for fault isolating E_Port segmentation problems caused by incompatible zone sets.
Repair Information UPM card LEDs To obtain port or UPM card operational information, inspect the UPM card LEDs. The card faceplate contains: • An amber LED (at the top of the card) that illuminates if any port fails or blinks if FRU beaconing is enabled. • A bank of amber and green LEDs above the ports.
Repair Information Figure 3–12: Port Card View The status of the selected UPM card and operational states for all ports are visible on the Port Card View. These port operational states are defined in Table 3–2.
Repair Information Table 3–2: 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. If the port remains online, the green port LED remains illuminated. At the director UPM card, the green LED blinks when there is Fibre Channel traffic through the port.
Repair Information Table 3–2: Port Operational States (Continued) Port State Green LED Amber LED Alert Symbol Description 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. No Light Off Off None No signal (light) is received by the director port.
Repair Information Double-click a port connector to display the Port Properties dialog box, as shown in Figure 3–13. Figure 3–13: Port Properties dialog box The dialog box provides the following information: 3–24 • Port Number–The director port number (0 through 63 inclusive). • Port Name–The user-defined name or description for the port.
Repair Information • 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 displays adjacent to the status field. • Link Incident–If no link incidents are recorded, None displays in the status field. If a link incident is recorded, a summary displays describing the incident, and a yellow triangle displays adjacent to the status field.
Repair Information Table 3–3: Invalid Attachment Messages and Explanations (Continued) Message Explanation 05 External loopback adapter connected to the port. A loopback plug is connected to the port and there is no diagnostic test running. 06 N_Port connection not allowed on this port. The port type configuration does not match the actual port use. Port is configured as an E_Port, but attaches to a node device. 07 Non-homogeneous switch at other end of the ISL.
Repair Information — Build fabric protocol error. — No principal switch (no switch in fabric is capable of being principal switch). — No response from an attached switch. • Threshold Alert–If a threshold alert exists for the port, an alert indicator (yellow triangle) displays by the Threshold Alert field, and the configured name for the last alert received displays in the field.
Repair Information Figure 3–14: Performance View When the Performance View opens, no port statistics or errors display. Each port bar graph in the upper portion of the view displays the instantaneous transmit or receive activity level for the port, and is updated every five seconds. The relative value displayed is the greater of either the transmit or receive activity (whichever value is greatest when sampled).
Repair Information • If the port is an E_Port, the pop-up displays E_Port. • If the port is segmented, the pop-up displays Segmented E_Port. Click a port bar graph to display statistics values for the port (bottom half of the Performance View). Right-click a port bar graph to display statistics values for the port (bottom half of the Performance View) and access a menu to: • Open the Port Properties, Node Properties, or Port Technology dialog boxes. • Block or unblock the port.
Repair Information Perform Loopback Tests This section describes the procedures to perform an: • Internal loopback test–An internal loopback test checks UPM card circuitry, but does not check fiber-optic components of a port transceiver. The test is performed with a device attached to the port, but the test momentarily blocks the port and is disruptive to the attached device.
Repair Information c. Choose Reset Port. A reset warning message box displays. d. Click OK. The port resets. e. Click Back To Full View to return to the Hardware View. 6. Click Maintenance and choose Port Diagnostics. The Port Diagnostics dialog box displays, as shown in Figure 3–15. Figure 3–15: 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.
Repair Information — 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). NOTE: Click Stop Test at any time to abort the loopback test. 12.
Repair Information 4. At the Hardware View, verify the location of the port or UPM card to be tested. When the mouse cursor is passed over a graphical UPM card on the front view of the director, the card highlights with a blue border and a pop-up displays with the following information: — Port card type (UPM). — Chassis slot number (0 through 15 inclusive). — The four consecutive port numbers on the selected card. Valid port numbers are in the range of 0 through 63 inclusive. 5.
Repair Information — To select a UPM card for test, type the port number of any of the four ports an the card in the Port Number field, then choose All Ports On Card. 10. At the Diagnostics Test list box, choose External Loopback. 11. Click Next. Beaconing initiates for the port or UPM card selected for test. At the Hardware View, a yellow triangle displays at the top of the UPM card. At the Port Diagnostics dialog box, the message Loopback plugs must be installed on ports being diagnosed displays. 12.
Repair Information 18. Remove loopback plugs from the tested ports. 19. Reconnect fiber-optic jumper cables from devices to tested ports. Channel Wrap Test (S/390 only) A channel wrap test is a diagnostic procedure that checks S/390 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.
Repair Information Figure 3–16: Channel Wrap On for Port n dialog box 3. Perform the fibre link test at the S/390 host attached to the configured port. For test instructions, refer to the service documentation delivered with the S/390 system. Swapping Ports (S/390 only) Use the port swap procedure to swap a device connection and logical port address from a failed Fibre Channel port to an operational port.
Repair Information Figure 3–17: Swap Ports dialog box 5. At the First address and Second address fields, type the logical port addresses (in hexadecimal format) of the pair of ports to be swapped. The ports are automatically blocked during the procedure. 6. Choose the Unblock after swap check boxes to unblock the ports when the procedure completes. 7. Click Next. At the Swap Ports dialog box, the message Continuing this procedure requires varying the selected ports offline.
Repair Information Perform the maintenance data collection procedure after a firmware fault is corrected or a failed FRU is replaced to capture the data for analysis by third-level support personnel. Maintenance data includes the dump file, hardware log, audit log, and an engineering log viewable only by support personnel. To collect maintenance data: 1. At the HAFM server, open the HAFM application. The Products View displays. 2.
Repair Information Figure 3–19: Data Collection dialog box 7. Click Close to close the dialog box. 8. Remove the Zip disk with the newly-collected maintenance data from the HAFM server Zip drive. Return the Zip disk with the failed FRU to HP for failure analysis. 9. To ensure the QuikSync backup application operates normally, replace the original backup disk in the HAFM server Zip drive.
Repair Information 3. Gently wipe the end-face and other surfaces of the connector with an alcohol pad, as shown in 2 on Figure 3–20. Ensure the pad makes full contact with the surface to be cleaned. Wait approximately five seconds for cleaned surfaces to dry. 4. Repeat step 2 and step 3 of this procedure (second cleaning). 5. Repeat step 2 and step 3 of this procedure again (third cleaning), then reconnect the fiber-optic cable to the port. Power-On Procedure To power-on the director: 1.
Repair Information NOTE: When powering on the director after removing and replacing a faulty FRU, the amber system error LED may remain illuminated. Clear the system error LED as part of the replacement procedure. 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.
Repair Information • Resets the Ethernet local area network (LAN) interface on the active CTP2 card, causing the connection to the HAFM server to drop momentarily until the connection automatically recovers. • Automatically enables changes to an active zone configuration. • Keeps all fabric logins, name server registrations, and operating parameters intact. • Automatically sets the director online. The blocked or unblocked state of each port remains intact. To IPL the director: 1.
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. At the HAFM server, open the HAFM application. The Products View displays. 3. Double-click the icon representing the director to be set offline. The Hardware View for the selected director displays. 4. Click Maintenance and choose Set Online State.
Repair Information Block a Port To block an individual director port: 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. At the HAFM server, open the HAFM application. The Products View displays. 3. Double-click the icon representing the director for which a port will be blocked. The Hardware View for the selected director displays. 4.
Repair Information Block a UPM Card To block all four ports on a director UPM card: 1. Notify the customer the UPM card will be blocked. Ensure the customer’s system administrator quiesces Fibre Channel frame traffic through the ports and sets attached devices offline. 2. At the HAFM server, open the HAFM application. The Products View displays. 3. Double-click the icon representing the director for which a UPM card will be blocked. The Hardware View for the selected director displays. 4.
Repair Information 3. Double-click the UPM card for which a port will be unblocked. The Port Card View for the selected card displays. 4. Move the cursor over the port to be unblocked and right-click the mouse to open a list of menu options. 5. Choose Block Port. Note the check mark in the box adjacent to the menu item, indicating the port is blocked. The Unblocking Port warning box displays, as shown in Figure 3–26. Figure 3–26: Unblocking Port warning box 6. Click OK.
Repair Information Figure 3–27: 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. Manage Firmware Versions Firmware is the director’s internal operating code that is downloaded from the HAFM server and stored on a CTP2 card.
Repair Information Figure 3–28: Firmware Library dialog box 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 2/64 documentation kit CD.
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 server or PC hard drive. e. If the new firmware version was downloaded to a PC (not the HAFM server), transfer the firmware version file to the HAFM server by Zip disk, CD-ROM, or other electronic means. 2. At the HAFM server, open the HAFM application. The Products View displays. 3.
Repair Information 7. Enter a description (up to 24 characters in length) for the new firmware version and click OK. It is recommended the description include the installation date and text that uniquely identifies the firmware version. 8. A Transfer Complete message box displays indicating the new firmware version is stored on the HAFM server 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.
Repair Information 7. Click Close. Delete a Firmware Version To delete a director firmware version from the library stored on the HAFM server hard drive: 1. At the HAFM server, open the HAFM application. The Products View 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 and choose Firmware Library. The Director 2/64 Firmware Library dialog box displays. 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 server. a. Select About from the Help menu. 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 3–57). 3.
Repair Information 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 • Operating parameters (buffer-to-buffer credit (BB_Credit) value, error-detect time-out value (E_D_TOV), resource allocation time-out value (R_A_TOV), switch priority, and preferred domain ID). • Simple network management protocol (SNMP) configuration information, including trap recipients, community names, and write authorizations. • Zoning configuration information, including the active zone set and default zone state.
Repair Information Restore the Configuration To restore the director configuration file from the HAFM server: 1. Notify the customer the director will be set offline. Ensure the customer’s system administrator quiesces Fibre Channel frame traffic through the director and sets attached devices offline. 2. Set the director offline (Set Offline State on page 3–44). 3. At the HAFM server, open the HAFM application. The Products View displays. 4.
Repair Information 8. Click OK to close the dialog box and return to the Hardware View. Reset Configuration Data NOTE: This procedure resets the director IP address to the default value of 10.1.1.10 and may disrupt HAFM server-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.
Repair Information The HAFM application shipped with the director is provided on the HAFM Applications CD-ROM. Subsequent software versions for upgrading the director are provided to customers through the HAFM Applications CD-ROM or through the HP website. NOTE: When installing or upgrading a software version, follow all procedural information in Release Notes that accompany the software version. This information supplements information provided in this general procedure.
Repair Information 3. Choose Start > Run. The Run dialog box displays, as shown in Figure 3–40. Figure 3–40: Run dialog box 4. At the Run dialog box, select the directory path (hard drive or CD-ROM drive) and filename of the executable file (HAFM_SERVERINSTALL.EXE) using Browse. The directory path and filename display in the Open field. 5. Click OK.
Repair Information b. Type the user name and password and click OK. The Windows 2000 desktop displays. NOTE: If required, obtain the user name and password from the customer or next level of support. 8. The HAFM application automatically opens. At the HAFM Login window, enter a user name, password, and HAFM server name (all are case sensitive), and click Login. The application opens and the Products View displays.
4 FRU Removal and Replacement This chapter describes removal and replacement procedures (RRPs) used by authorized service representatives for all director field-replaceable units (FRUs). Do not perform a procedure in this chapter until a failure is isolated to a FRU. If fault isolation was not performed, go to MAP 0000: Start MAP on page 2–12. Factory Defaults Table 4–1 lists the defaults for the passwords, and IP, subnet, and gateway addresses.
FRU Removal and Replacement 3. After completing the steps of a detailed procedure that is referenced from another procedure, return to the initial (referencing) procedure and continue to the next step of that procedure. 4. After completing a replacement procedure, clear the event code reporting the failure and the event code reporting the recovery from the Director 2/64 Event Log (at the HAFM server), and extinguish the amber system error light- emitting diode (LED) at the director front bezel.
PWR OK TEMP 1 ILIM FAULT FRU Removal and Replacement Figure 4–1: ESD grounding point (front) 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 4–2. Touch the chassis once before performing any maintenance action, and once each minute while removing or replacing FRUs. 1 Figure 4–2: ESD grounding point (rear) Concurrent FRUs Table 4–2 lists concurrent FRUs.
FRU Removal and Replacement Table 4–2: Concurrent FRU Names and ESD Requirements ESD Precaution Requirement Concurrent FRU Name Control processor card (RRP: Redundant CTP2 Card on page 4-5) Yes Universal port module card (RRP: UPM Card on page 4-9) Yes Small form factor pluggable (SFP) optical transceiver (RRP: SFP Optical Transceiver on page 4-13) No UPM filler blank (RRP: UPM Filler Blank on page 4-16) No Power supply (RRP: Redundant Power Supply on page 4-17) Yes Serial crossbar assembly (RRP
FRU Removal and Replacement RRP: Redundant CTP2 Card Use the following procedures to remove or replace a redundant CTP2 card (two cards in the director) with the backup CTP2 card operational. A list of tools required is provided. CAUTION: Do not remove and replace a redundant CTP2 card if the backup CTP2 card is not fully operational and director power is on. The director IP address, configuration data, and other operating parameters will be lost.
FRU Removal and Replacement CAUTION: The torque tool supplied with the director is designed to tighten director logic cards and is set to release at a torque value of six inch-pounds. Do not use an Allen wrench or torque tool designed for use with another HP product. Use of the wrong tool may overtighten and damage logic cards. a. Insert the torque tool into the locking Allen screw at the bottom of the card. Turn the screw counterclockwise until the spring releases and the tool turns freely. b.
FRU Removal and Replacement Replacing a Redundant CTP2 Card To replace a redundant CTP2 card: 1. Wait approximately 20 seconds after removal of the failed CTP2 card to begin this replacement procedure. 2. Remove the replacement card from its protective antistatic bag. 3. Hold the card by its stiffener and insert it in the chassis card track, as shown in Figure 4–3. The label identifying the card should be at the top.
FRU Removal and Replacement — Do not reinstall the failed replacement CTP2 card because this can corrupt director firmware. Obtain a new CTP2 card and perform this replacement procedure. 6. Verify that synchronization is complete by viewing the Event Log. 7. Connect the Ethernet LAN cable to the RJ-45 connector on the faceplate of the replacement CTP2 card. 8. Disconnect the ESD wrist strap from the director chassis and your wrist. 9. Inspect the CTP2 card to ensure the amber LED is extinguished.
FRU Removal and Replacement 16. Clear the amber system error LED on the director bezel: a. At the Hardware View, right-click the front panel bezel graphic (away from a FRU) to open a menu. b. Click Clear System Error Light. RRP: UPM Card Use the following procedures to remove or replace a UPM card. A list of tools required is provided. Tools Required The following tools are required to perform these procedures. • ESD grounding cable and wrist strap.
FRU Removal and Replacement 4. Identify the defective UPM card from the amber LED on the card or failure information at the HAFM server’s Hardware View. 5. Block communication to the defective UPM card (Block a UPM Card on page 3–46). 6. Disconnect the fiber-optic jumper cable from each port on the defective card. Repeat this step for all four ports. a. Pull the keyed LC connector free from the port’s optical transceiver. b. Place a protective cap over the cable connector.
FRU Removal and Replacement Figure 4–4: UPM card 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 4–4. 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 4. Perform an external loopback test for all ports on the replacement UPM card (External Loopback Test on page 3–32). If the test fails, go to MAP 0000: Start MAP on page 2–12 to isolate the problem. 5. Reconnect a fiber-optic jumper cable to each port on the card. Inspect the label on the jumper cable to ensure the correct connection. Repeat this step for all four ports. a.
FRU Removal and Replacement 11. Restore communication to the replacement UPM card and set the card online as directed by the customer (Unblock a UPM Card on page 3–47). Inform the customer the UPM card is available for use. 12. Perform the data collection procedure (Collecting Maintenance Data on page 3–37). 13. Clear the amber system error LED on the director bezel: a. At the Hardware View, right-click the front panel bezel graphic (away from a FRU) to open a menu. b. Click Clear System Error Light.
FRU Removal and Replacement 5. Disconnect the fiber-optic jumper cable from the port: a. Pull the keyed LC free from the port’s optical transceiver. b. Place a protective cap over the cable connector. 6. Depending on the manufacturer, the optical transceiver may have a locking mechanism to secure the transceiver in the port receptacle, or the transceiver may have a pull tab to assist in removal. a.
FRU Removal and Replacement 2. Insert the transceiver into the port receptacle, as shown in Figure 4–5. 3. Perform an external loopback test for the port (External Loopback Test on page 3–32). If the test fails, go to MAP 0000: Start MAP on page 2–12 to isolate the problem. 4. Reconnect the fiber-optic jumper cable: a. Remove the protective cap from the cable connector and the protective plug from the port’s optical transceiver. Store the cap and plug in a suitable location for safekeeping. b.
FRU Removal and Replacement 9. Restore communication to the port with the replacement transceiver as directed by the customer (Unblock a Port on page 3–46). Inform the customer the port is available for use. 10. Clear the amber system error LED on the director bezel: a. At the Hardware View, right-click the front panel bezel graphic (away from a FRU) to open a menu. b. Click Clear System Error Light. RRP: UPM Filler Blank Use the following procedures to remove or replace a UPM filler blank.
FRU Removal and Replacement Figure 4–6: UPM filler blank 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 4–6. 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.
FRU Removal and Replacement Removing a Redundant Power Supply To remove a redundant power supply: 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. Follow ESD procedures by attaching a wrist strap to the director chassis and your wrist, as shown in Figure 4–1.
FRU Removal and Replacement 6. Pull the power supply (3) from the director. Support the power supply with one hand when performing this step. 7. Place the power supply in an antistatic bag to provide ESD protection. Replacing a Redundant Power Supply To replace a redundant power supply: 1. Remove the replacement power supply from its protective antistatic bag. 2. Inspect the rear of the power supply for bent or broken connector pins that may have been damaged during shipping.
FRU Removal and Replacement 9. If necessary, close and lock the equipment cabinet door. 10. Perform the data collection procedure (Collecting Maintenance Data on page 3–37). 11. Clear the amber system error LED on the director bezel: a. At the Hardware View, right-click the front panel bezel graphic (away from a FRU) to open a menu. b. Click Clear System Error Light.
FRU Removal and Replacement 4. Identify the defective SBAR assembly from the amber LED on the assembly or failure information at the HAFM server’s 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 4–8.
FRU Removal and Replacement 8. At the Hardware View, observe the graphic representing the replacement SBAR assembly 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 2–12 to isolate the problem. 9. At the Hardware View, double-click the graphic representing the replacement SBAR assembly to open the FRU Properties dialog box. Verify that information (FRU name, position, and state) is correct.
FRU Removal and Replacement 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. If the director is rack-mounted, unlock and open the cabinet rear door as directed by the customer representative. 2. Follow ESD procedures by attaching a wrist strap to the director chassis and your wrist, as shown in Figure 4–2.
FRU Removal and Replacement 7. Place the fan module in an antistatic bag to provide ESD protection. Replacing a Redundant Fan Module To replace the fan module: 1. Remove the replacement fan module from its protective antistatic bag. 2. Inspect the PWA on the underside of the fan module for bent or broken connector pins that may have been damaged during shipping. If any pins are damaged, obtain a new fan module. 3. Position the fan module at the rear of the director chassis, as shown in Figure 4–9.
FRU Removal and Replacement 12. Perform the data collection procedure (Collecting Maintenance Data on page 3–37). 13. Clear the amber system error LED on the director bezel: a. At the Hardware View, right-click the front panel bezel graphic (away from a FRU) to open a menu. b. Click Clear System Error Light. RRP: Power Module Assembly Use the following procedures to remove or replace the power module assembly. A list of tools required is provided.
FRU Removal and Replacement CAUTION: To avoid causing machine errors or damage while working on the director, follow ESD procedures by connecting a grounding cable to an approved bench grounding point and wearing an ESD wrist strap. 5. Unseat and disconnect (but do not remove) both power supplies (RRP: Redundant Power Supply on page 4–17). 6. Remove the RFI shield. 7. Remove both SBAR assemblies (RRP: Redundant SBAR Assembly on page 4–20). 8.
FRU Removal and Replacement Replacing a Power Module Assembly To replace the power module assembly: 1. Remove the replacement power module assembly from its protective antistatic bag. 2. Inspect the PWA side of the power module assembly for bent or broken connector pins that may have been damaged during shipping. If any pins are damaged, obtain a new assembly. 3. Position the power module assembly at the rear of the director chassis, as shown in Figure 4–10.
FRU Removal and Replacement 14. If required, clear the amber system error LED on the director bezel: a. At the Hardware View, right-click the front panel bezel graphic (away from a FRU) to open a menu. b. Click Clear System Error Light. 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. • Torque tool and hex adapter (provided with the director).
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 3–41).
FRU Removal and Replacement 10. Remove both fan modules (RRP: Redundant Fan Module on page 4–23). 11. Remove both SBAR assemblies (RRP: Redundant SBAR Assembly on page 4–20). 12. Remove the power module assembly (RRP: Power Module Assembly on page 4–26). 13. The backplane (1) is secured to the director chassis with 11 panhead Phillips screws, as shown in Figure 4–11. 1 SHR-2307 Figure 4–11: 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 4–11. c.
FRU Removal and Replacement d. Verify the card stiffener is flush with the front of the card cage and even with other director logic cards. 8. Disconnect the ESD wrist strap from the director chassis and your wrist. 9. Power on the director (Power-On Procedure on page 3–40). 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.
FRU Removal and Replacement 12. Initial machine load (IML) the director. At the front of the director, press and hold the white IML button on the faceplate of the active CTP2 card (green LED illuminated) for three seconds. 13. At the HAFM server’s 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 2–12 to isolate the problem. 14.
5 Illustrated Parts Breakdown 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 Figure 5–1: Front-accessible FRUs Table 5–1: Front-Accessible FRU Parts List Ref. Part Number Ref Qty.
Illustrated Parts Breakdown Table 5–1: Front-Accessible FRU Parts List (Continued) Ref. Part Number Description Qty. 6 292006-001 (*ESD*) Printed wiring assembly, universal port module (UPM), 4-port, LC (with shortwave optics) 8 to 16 7 254130-001 Filler blank, UPM 0 to 8 Rear-Accessible FRUs Figure 5–2 and Figure 5–3 illustrate rear-accessible FRUs, and Table 5–2 and Table 5–3 are the rear-accessible parts lists.
Illustrated Parts Breakdown Table 5–2: Rear-Accessible FRU Parts List (Part 1) Ref. Part Number Ref Description Qty. Base assembly, Director 2/64 1 not procurable Chassis assembly 1 2 254128-001 (*ESD*) Power distribution assembly 1 3 254133-001 (*ESD*) Printed wiring assembly, serial crossbar (SBAR) 2 4 254129-001 (*ESD*) Fan module 2 1 2 SHR 2307A Figure 5–3: Rear-accessible FRUs (part 2) Table 5–3: Rear-Accessible FRU Parts List (Part 2) Ref.
Illustrated Parts Breakdown Miscellaneous Parts Table 5–4 is the parts list for miscellaneous parts. Table 5–4: Miscellaneous Parts Ref. 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.
A Messages This appendix lists information and error messages that display in message boxes at the HP StorageWorks ha-fabric manager (HAFM) and Director 2/64 Product Manager applications. The first section of the appendix lists HAFM application messages. The second section lists Product Manager messages. The text of each message is followed by a description and recommended course of action. HAFM Application Messages This section lists HAFM application information and error messages in alphabetical order.
Table A–1: HAFM Messages (Continued) Message Description Action All zone members are logged. Attempt was made to display all zone members not logged-in using the Zone Set tab, but all members are currently logged in. Informational message. An HAFM application session is already active from this workstation. Only one instance of the HAFM application is allowed to be open per remote workstation. Close all but one of the HAFM application sessions.
Table A–1: HAFM Messages (Continued) Message Description Action Are you sure you want to remove all members from this zone? All members will be deleted from the selected zone. Click Yes to delete the members or No to cancel the operation. Cannot add a switch to a zone. The device that you are attempting to add to the zone is a switch, which cannot be added to a zone. Specify the port number or corresponding World Wide Name for the device you want to add to the zone. Cannot connect to HAFM server.
Table A–1: HAFM Messages (Continued) Message Description Action Cannot display route. All switches in route must be managed by the same server. You cannot show the route between devices that are attached to switches or directors managed by a different HAFM Server. Make sure devices named in Show Routes dialog box are attached to products managed by this HAFM Server. Cannot display route. All switches in route must support routing.
Table A–1: 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 click Modify. Cannot modify product. The selected product cannot be modified. Verify the HAFM server-to-product link is up. • If the link is up, the HAFM server may be busy. • Another Product Manager instance may be open. • The user may not have permission to modify the product.
Table A–1: HAFM Messages (Continued) Message 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 HAFM for a fabric to exist. Identify an existing switch or director to HAFM using the New Product dialog box. Click OK to remove all contents from log. This action deletes all contents from the selected log. Click OK to delete the log contents or Cancel to cancel the operation.
Table A–1: HAFM Messages (Continued) Message Description Action Download complete. Click OK and start the HAFM. Download of the HAFM and Product Manager applications 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.
Table A–1: HAFM Messages (Continued) Message Description Action Error connecting to switch. While viewing routes, the HAFM server was unable to connect to the switch. The switch failed or the switch-to-HAFM server 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. If the problem persists, contact the next level of support. Error creating zone set.
Table A–1: HAFM Messages (Continued) Message Description Action Fabric Log will be lost once the fabric unpersists. Do you want to continue? When you unpersist a fabric, the corresponding fabric log is deleted. Click Yes to unpersist the fabric or No to cancel the operation. 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.
Table A–1: HAFM Messages (Continued) Message Description Action HAFM server could not log you on. Verify your username and password. The incorrect username and password (both case sensitive) were used while attempting to login to the HAFM application. Verify the user name and password with the customer’s network administrator and retry the operation. HAFM server is shutting down. Connection will be terminated. The HAFM application is closing and terminating communication with the attached product.
Table A–1: HAFM Messages (Continued) Message Description Action 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. Invalid port number. Valid ports are (0-< nn >). You have specified an invalid port number. Specify a valid port number, in the range 0 to the maximum number of ports on the product minus 1. For example, for a switch with 32 ports, the valid port range is 0–31.
Table A–1: HAFM Messages (Continued) Message Description Action Invalid UDP port number. The specified user datagram protocol (UDP) port number is invalid. The number must be an integer from 1 through 65535 inclusive. Verify and enter a valid UDP port number. Invalid World-Wide Name. The specified world-wide name format is invalid. The valid format is eight two-digit hexadecimal numbers separated by colons (xx:xx:xx:xx:xx:xx:xx :xx). Enter a world-wide name using the correct format.
Table A–1: HAFM Messages (Continued) Message Description Action Limit exceeded. You cannot add a new product or user to HAFM if the maximum number of that resource already exists on the system. Delete unneeded products or users from the system, before attempting to add any new ones. Management session is already active from this workstation. An instance of the HAFM application is already open at this workstation. Close the previous session of the HAFM application before starting a new one.
Table A–1: HAFM Messages (Continued) Message Description Action No user selected. A user was not selected when the command was attempted. Choose a user and try again. No zone member selected. A zoning operation was attempted without a zone member selected. Choose a zone member and try the operation again. No zone selected. A zoning operation was attempted without a zone selected. Choose a zone and try the operation again. No zone selected or zone no longer exists.
Table A–1: HAFM Messages (Continued) Message Description Action Password and confirmation don’t match. Entries in the password field and confirmation password field do not match. The entries are case sensitive and must be the same. Enter the password and confirmation password again. Product Manager instance is currently open. A product cannot be deleted while an instance of the Product Manager application is open. Close the Product Manager application, then delete the product.
Table A–1: 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. User selected Fabric Binding or Enterprise Fabric Mode from the Fabrics menu, but the SANtegrity feature was not installed.
Table A–1: HAFM Messages (Continued) Message Description Action The Domain ID was not accepted. The World Wide Name and Domain ID must be unique in the Fabric Membership List. User attempted to add a detached switch to the Fabric Membership List through the Fabric Binding option (SANtegrity 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.
Table A–1: HAFM Messages (Continued) Message Description Action The maximum number of HAFM sessions has been reached. A maximum of four concurrent remote management sessions can be configured at the Session Options dialog box. The specified number was reached. Increase the number of remote sessions allowed (if less than eight) or terminate a session before attempting to initiate a new session. The maximum number of members has already been configured. The maximum number of unique members is 4097.
Table A–1: HAFM Messages (Continued) Message Description Action The maximum number of remote network addresses has already been configured. A maximum of four IP addresses for remote workstations can be configured at the Session Options dialog box. That number was reached. Delete an existing IP address before adding a new IP address. The maximum number of users has already been configured. The number of users (32) that can be defined to the HAFM application was reached.
Table A–1: HAFM Messages (Continued) Message Description Action The software version on this HAFM server is not compatible with the version on the remote HAFM server. A second HAFM server PC (client) connecting to the HAFM server must be running the same software version to log in. Upgrade the software version on the downlevel HAFM server PC. The zoning library conversion must be completed before continuing. The zoning library conversion is incomplete and the requested operation cannot continue.
Table A–1: HAFM Messages (Continued) Message Description Action This user name has already been assigned. The specified user name is already assigned and configured. Modify (to make it unique) or delete the duplicate name. This Worldwide Name was not accepted. The World Wide Name and Domain ID must be unique in the Fabric Membership List.
Table A–1: HAFM Messages (Continued) Message Description Action You must define an SMTP server address. A simple mail transfer protocol (SMTP) server address must be defined and configured for e-mail to be activated. Define the SMTP server address at the Configure E-Mail dialog box. You must define at least one E-mail address. At least one e-mail address must be defined and configured for e-mail to be activated. Define an e-mail address at the Configure E-Mail dialog box.
Table A–1: HAFM Messages (Continued) Message Description Action Zones configured with port numbers are ignored in Open Fabric Mode. While in Open Fabric mode, zones configured using port numbers are enforced through world-wide names. Informational message only no action is required. Zones must be defined before creating a zone set. You cannot create a zone set without any zones defined for HAFM. Define zones using the New Zone dialog box. Zoning by port number is ignored in Open Fabric Mode.
Director 2/64 Product Manager Messages This section lists Director 2/64 Product Manager information and error messages in alphabetical order. Table A–2: Product Manager Messages Message Description Action A Product Manager instance is already open. Only one instance of the Product Manager application can be open at one time. Close the open Product Manager application so the desired instance of the Product Manager application can be opened.
Table A–2: Product Manager Messages (Continued) Message Description Action Are you sure you want to send firmware version? This message requests confirmation to send a firmware version from the HAFM server’s firmware library to the director. Click Yes to send the firmware version or No to abort the operation. Cannot have spaces in field. Spaces are not allowed as part of the entry for this field. Delete spaces from the field entry. Cannot install firmware to a director with a failed CTP card.
Table A–2: Product Manager Messages (Continued) Message Description Action Cannot retrieve diagnostics results. director diagnostic results cannot be retrieved by the Product Manager application because the Ethernet link is down or busy. Retry the operation later. If the condition persists, contact the next level of support. Cannot retrieve director date and time. The director date and time cannot be retrieved by the Product Manager application because the Ethernet link is down or busy.
Table A–2: Product Manager Messages (Continued) Message Description Action Cannot retrieve port statistics. Port statistics cannot be retrieved by the Product Manager application because the Ethernet link is down or busy. Retry the operation later. If the condition persists, contact the next level of support. Cannot run diagnostics on a port that is failed.
Table A–2: Product Manager Messages (Continued) Message Description Action Cannot save port configuration. The port configuration cannot be saved at the Product Manager application 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 director SNMP configuration cannot be saved at the Product Manager application because the Ethernet link is down or busy. Retry the operation later.
Table A–2: Product Manager Messages (Continued) Message Description Action Cannot start data collection. The data collection procedure cannot be started by the Product Manager application because the Ethernet link is down or busy. Retry the operation later. If the condition persists, contact the next level of support. Cannot start firmware install while CTP synchronization is in progress. The director’s CTP2 cards are synchronizing and firmware cannot be installed until synchronization is complete.
Table A–2: Product Manager Messages (Continued) Message Description Action Could not find firmware file. A firmware version could not be found because the data directory structure for the HAFM server is corrupt. Reinstall the HAFM and Product Manager applications. If the condition persists, contact the next level of support. Could not remove dump files from server. Dump files could not be deleted from the HAFM server because the notebook PC or Product Manager application is busy.
Table A–2: Product Manager Messages (Continued) Message Description Action Device applications should be terminated before starting diagnostics. Press NEXT to continue. Port diagnostics (loopback tests) cannot be performed on a port while an attached device application is running. Terminate the device application and perform diagnostics again. Director clock alert must be cleared before enabling period synchronization.
Table A–2: Product Manager Messages (Continued) Message Description Action Error retrieving port information. An error occurred at the Product Manager application while retrieving port information because the Ethernet link is down or busy. Retry the operation later. If the condition persists, contact the next level of support. Error retrieving port statistics. An error occurred at the Product Manager application while retrieving port statistics because the Ethernet link is down or busy.
Table A–2: Product Manager Messages (Continued) Message Description Action File transfer is in progress. A firmware file is being transferred from the HAFM server hard drive, or a data collection file is being transferred to a diskette. Informational message only—no action is required. Firmware download timed out. A firmware download operation timed out and aborted. Retry the operation. If the problem persists, contact the next level of support. Firmware file I/O error.
Table A–2: Product Manager Messages (Continued) Message Description Action Invalid port address. An invalid port address has been entered. Verify port address through the Configure Addresses “Active” dialog box (S/390 mode only) and re-enter. Invalid port number. The Fibre Channel number entered is invalid. The port number must be an integer from 0 through 63 inclusive. Verify and enter a valid port number. Invalid response received from director.
Table A–2: Product Manager Messages (Continued) Message Description Action Invalid value for day (1 - 31). At the Configure Date and Time dialog box, the DD value (day) must be an integer from 1 through 31 inclusive. Verify and enter a valid date. Invalid value for E_D_TOV. At the Configure Operating 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).
Table A–2: Product Manager Messages (Continued) Message Description Action Invalid value for R_A_TOV. At the Configure Operating Parameters dialog box, the resource allocation time-out value (R_A_TOV) must be an integer from 10 through 1200 inclusive. Verify and enter a valid number. Invalid value for second (0 - 59). At the Configure Date and Time dialog box, the SS value (second) must be an integer from 0 through 59 inclusive. Verify and enter a valid time. Invalid value for year.
Table A–2: Product Manager Messages (Continued) Message Description Action Log is currently in use. Access to the log is denied because the log was opened by another instance of the Product Manager application. Retry the operation later. If the condition persists, contact the next level of support. Maximum number of versions already installed. The number of firmware versions that can be defined to the HAFM application’s firmware library was reached.
Table A–2: Product Manager Messages (Continued) Message Description Action Performing this action will overwrite the date/time on the director. Warning that occurs when configuring the date and time through the Configure Date and Time dialog box, that the new time or date will overwrite the existing time or date set for the director. Verify that you want to overwrite the current date or time. Performing this operation will change the current state to Offline.
Table A–2: Product Manager Messages (Continued) Message Description Action Product Manager error < error number 5001 or 5002 >. At the Configure Operating Parameters dialog box, the R_A_TOV entry must be greater than E_D_TOV entry. Verify and change one of the entries to make the relationship valid. Product Manager instance is currently open. A Product Manager window is open. Informational message only. Send firmware failed. A firmware download operation failed.
Table A–2: Product Manager Messages (Continued) Message Description Action The add firmware process has been aborted. The user aborted the process to add a firmware version to the HAFM server’s firmware library. Verify the firmware addition is to be aborted, then click OK to continue. The data collection process failed. An error occurred while performing the data collection procedure. Try the data collection procedure again. If the problem persists, contact the next level of support.
Table A–2: Product Manager Messages (Continued) Message Description Action The firmware version already exists. This firmware version already exists in HAFM server’s firmware library. Informational message only—no action is required. The link to the director is not available. The Ethernet connection between the HAFM server and the director is down or unavailable. Establish and verify the network connection. The HAFM server is busy processing a request from another Product Manager.
Event Code Tables B Event Code Tables An event is an occurrence (state change, problem detection, or problem correction) that requires user attention or that should be reported to a system administrator or service representative. An event usually indicates a switch operational state transition, but may also indicate an impending state change (threshold violation). An event may also provide information only, and not indicate an operational state change. Events are reported as event codes.
Event Code Tables — Major. — Severe (not operational). B–2 • Explanation-a complete explanation of what caused the event. • Action-the recommended course of action (if any) to resolve the problem. • Event Data-supplementary event data (if any) that displays in the event log in hexadecimal format. • Distribution-check marks in associated fields indicate where the event code is reported (director, HAFM server, or host).
Event Code Tables System Events (000 through 199) Event Code: 001 Message: System power-down. Severity: Informational. Explanation: The director was powered off or disconnected from the facility AC power source. The event code is distributed the next time the director powers on, but the date and time of the code reflect the power-off time. Action: No action required. Event Data: No supplementary data included with the event.
Event Code Tables Event Code: 011 Message: Login Server database invalid. Severity: Minor. Explanation: Following a 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 Zip disk 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 Zip disk 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 Management Server 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 Management Server.
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 Management Server subsystem, an asynchronous status was reported to an attached host, or a mode register update occurred. Action: Management Server internal error: Perform the data collection procedure and return the Zip disk 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 seven 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 Event Code: 070 Message: E_Port is segmented. 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) Distribution: Director EWS Event Log HAFM Server System Error LED ✔ Event Log E-Mail Host Call Home Sense Info Link Incident ✔ Event Code: 071 Message: Director is isolated. Severity: Informational. Explanation: The director is isolated from other fabric elements (directors or switches). This event code is accompanied by one or more 070 event codes. Refer to the event data for the segmentation reason.
Event Code Tables Event Code: 071 (continued) Event Data (continued): Distribution: 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, reconnect the link, and IPL the director. If the condition persists, perform the data collection procedure and return the Zip disk to HP support personnel. 5 = No principal switch. No director or switch in the fabric can become the principal switch.
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 Server 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 Event Code: 081 Message: Invalid attachment. 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: 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: 120 Message: Error detected while processing system management command. Severity: Informational. Explanation: This event occurs when the director receives an HAFM Management command that violates specified boundary conditions, typically as a result of a network error. The director rejects the command, drops the director-to-HAFM Server Ethernet link, and forces error recovery processing. When the link recovers, the command can be retried.
Event Code Tables Power Supply Events (200 through 299) Event Code: 200 Message: Power supply AC voltage failure. Severity: Major. Explanation: Alternating current (AC) input to the indicated power supply is disconnected or AC circuitry in the power supply failed. The second power supply assumes the full operating load for the director. Action: Ensure the power supply is connected to facility AC power, and verify operation of the facility power source.
Event Code Tables Event Code: 202 Message: Power supply thermal failure. Severity: Major. Explanation: The thermal sensor associated with a power supply indicates an overheat condition that shut down the power supply. The second power supply assumes the full operating load for the director. Action: Replace the failed power supply. Perform the data collection procedure and return the Zip disk and failed power supply to HP support personnel.
Event Code Tables Event Code: 204 Message: Power supply DC voltage recovery. Severity: Informational. Explanation: DC voltage recovered for the power supply. Both power supplies adjust to share operating load for the director. Action: No action required. Event Data: No supplementary data included with the event. Distribution: Director EWS Event Log HAFM Server System Error LED ✔ Event Log E-Mail Host Call Home Sense Info Link Incident ✔ Event Code: 206 Message: Power supply removed.
Event Code Tables Event Code: 207 Message: Power supply installed. Severity: Informational. Explanation: A redundant power supply was installed with the director powered on and operational. Both power supplies adjust to share operating load for the director. Action: No action required. Event Data: No supplementary data included with the event.
Event Code Tables Fan Module Events (300 through 399) Event Code: 300 Message: Cooling fan propeller failed. Severity: Major. Explanation: One cooling fan (out of six) failed or is rotating at insufficient angular velocity. The remaining fans are operational. The amber LED illuminates at the rear of the fan module associated with the failed fan. Action: Replace the indicated fan module. Event Data: The first byte of event data (byte 0) specifies the failed fan number.
Event Code Tables Event Code: 302 Message: Cooling fan propeller failed. Severity: Major. Explanation: Three cooling fans (out of six) failed or are rotating at insufficient angular velocity. The remaining fans are operational. The amber LED illuminates at the rear of the fan modules associated with the failed fans. Action: Replace the indicated fan modules. Event Data: The first byte of event data (byte 0) specifies the failed fan numbers.
Event Code Tables Event Code: 304 Message: Cooling fan propeller failed. Severity: Major. Explanation: Five cooling fans (out of six) failed or are rotating at insufficient angular velocity. The remaining fan is operational. The amber LED illuminates at the rear of both fan modules. Action: Replace both fan modules Event Data: The first byte of event data (byte 0) specifies the failed fan numbers.
Event Code Tables Event Code: 310 Message: Cooling fan propeller recovered. Severity: Informational. Explanation: One cooling fan (out of six) recovered or the associated fan module was replaced. All fans are operational. Action: No action required. Event Data: The first byte of event data (byte 0) specifies the recovered fan number.
Event Code Tables Event Code: 312 Message: Cooling fan propeller recovered. Severity: Informational. Explanation: Three cooling fans (out of six) recovered or the associated fan modules were replaced. All fans are operational. Action: No action required. Event Data: The first byte of event data (byte 0) specifies the recovered fan numbers.
Event Code Tables Event Code: 314 Message: Cooling fan propeller recovered. Severity: Informational. Explanation: Five cooling fans (out of six) recovered or the associated fan modules were replaced. All fans are operational. Action: No action required. Event Data: The first byte of event data (byte 0) specifies the recovered fan numbers.
Event Code Tables Event Code: 320 Message: Fan module removed. Severity: Major. Explanation: A fan module was removed with the director powered on and operational. Action: Replace the indicated fan module. Event Data: No supplementary data included with the event. Distribution: Director EWS Event Log HAFM Server 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 Zip disk and faulty FRU to HP support personnel.
Event Code Tables Event Code: 410 Message: CTP 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 Product Manager application, 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: 413 Message: Backup CTP card POST failure. Severity: Major. Explanation: A backup CTP2 card was installed in the director and failed POSTs. Action: Replace the indicated CTP2 card with a functional card. Perform the data collection procedure and return the Zip disk and faulty card to HP support personnel. Event Data: No supplementary data included with this event.
Event Code Tables Event Code: 415 Message: Backup CTP card removed. Severity: Informational. Explanation: The backup CTP2 card was removed while the director was powered on and operational. Action: No action required or install an operational backup CTP2 card. Event Data: No supplementary data included with this event.
Event Code Tables Event Code: 417 Message: CTP card firmware synchronization initiated. Severity: Informational. Explanation: The active CTP2 card initiated a firmware synchronization with the backup CTP2 card. Action: No action required. Event Data: No supplementary data included with this event. Distribution: Director EWS Event Log HAFM Server System Error LED ✔ Event Log E-Mail Host Call Home Sense Info Link Incident ✔ Event Code: 418 Message: User-initiated CTP card switchover.
Event Code Tables Event Code: 420 Message: Backup CTP card non-volatile memory failure. Severity: Major. Explanation: The backup CTP2 card detected a non-volatile memory failure. The failure has no impact on the active CTP2 card. Action: Replace the indicated CTP2 card with a functional card. Perform the data collection procedure and return the Zip disk and faulty card to HP support personnel. Event Data: Byte 0 = non-volatile memory area identifier.
Event Code Tables Event Code: 422 Message: CTP firmware synchronization complete. Severity: Informational. Explanation: Active CTP2 card synchronization with the backup CTP2 card complete. Action: No action required. Event Data: No supplementary data included with this event. Distribution: Director EWS Event Log HAFM Server System Error LED ✔ Event Log E-Mail Host Call Home Sense Info Link Incident ✔ Event Code: 423 Message: CTP firmware download initiated. Severity: Informational.
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 server connection terminates, but automatically recovers after the reset. Action: Perform the data collection procedure and return the Zip disk 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 Zip disk 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 was 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: 451 Message: Switch speed incompatibility detected. Severity: Informational Explanation: The event occurs when the configured switch speed saved in NVRAM conflicts with the speed capability of the switch. This event may occur when backup CTP2 hardware running an early version of software (below 1.3) is improperly synchronized with a CTP2 operating at greater than 1Gb/s. Action: None.
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 Server 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 management server.
Event Code Tables UPM Card Events (500 through 599) Event Code: 500 Message: UPM card hot-insertion initiated. Severity: Informational Explanation: Installation of an UPM card was initiated with the director powered on and operational. The event indicates that operational firmware detected the presence of the UPM card, but the card is not seated. When the card is seated in the director chassis and identified by firmware, an event code 501 is generated.
Event Code Tables Event Code: 502 Message: UPM card anomaly detected. Severity: Informational. Explanation: The 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.
Event Code Tables Event Code: 503 Message: UPM card hot-removal completed. Severity: Informational. Explanation: An 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 Server System Error LED ✔ Event Log Host E-Mail 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 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 Zip disk 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 an 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 Zip disk 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 (00 through 63). Byte 1 = engineering reason code. Bytes 4 through 7 = elapsed millisecond tick count. Bytes 8 through 11 = reason code specific. Byte 12 = test type.
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 (00 through 63). Byte 1 = anomaly reason code. Bytes 4 through 7 = elapsed millisecond tick count.
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 (00 through 63). Bytes 4 through 7 = elapsed millisecond tick count.
Event Code Tables Event Code: 513 Message: SFP optical transceiver hot-removal completed. Severity: Informational. Explanation: A SFP optical transceiver was removed while the director was powered on and operational. Action: No action required. Event Data: Byte 0 = port number (00 through 63). Bytes 4 through 7 = elapsed millisecond tick count.
Event Code Tables Event Code: 581 Message: Implicit incident. Severity: Major. Explanation: An attached open systems interconnection (OSI) or Fibre Connection (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: A 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: 585 Message: Primitive sequence timeout. Severity: Major. Explanation: An attached OSI or FICON server recognized either a link reset (LR) protocol timeout or a timeout while waiting for the appropriate response (while in a NOS receive state and after NOS was not longer recognized). Action: A 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 Event Code: 602 Message: SBAR assembly anomaly detected. Severity: Informational. Explanation: Director operational firmware detected a deviation in the normal operating mode or operating status of the indicated SBAR assembly. Action: No action required. An event code 604 is generated if the SBAR assembly fails. Event Data: Byte 0 = SBAR slot position (00 or 01). Byte 1 = anomaly reason code. Bytes 4 through 7 = elapsed millisecond tick count.
Event Code Tables Event Code: 603 Message: SBAR assembly hot-removal completed. Severity: Informational. Explanation: An SBAR assembly was removed with the director powered on and operational. Action: No action required. Event Data: Byte 0 = SBAR slot position (00 or 01). Bytes 4 through 7 = elapsed millisecond tick count.
Event Code Tables Event Code: 605 Message: SBAR assembly revision not supported. Severity: Minor. Explanation: The indicated SBAR assembly is not recognized and displays 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 Zip disk and faulty assembly to HP support personnel.
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 an 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 Zip disk 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 Zip disk 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 Zip disk and faulty assembly to HP support personnel. Event Data: No supplementary data included with this event.
Event Code Tables Event Code: 810 Message: High temperature warning (CTP card thermal sensor). Severity: Major. Explanation: The thermal sensor associated with a 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 Zip disk and faulty card to HP support personnel. Event Data: No supplementary data included with this event.
Event Code Tables Event Code: 812 Message: CTP card shutdown due to thermal violation. Severity: Major. Explanation: A 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.
Glossary This glossary defines terms used in this guide or related to this product and is not a comprehensive glossary of computer terms. access control Method of control (with associated permissions) by which a set of devices can access other devices across a network. See also persistent binding and zoning. active FRU A redundant field-replaceable unit that is operating as the active and not the backup FRU. Contrast with backup FRU.
Glossary audit log Log summarizing actions (audit trail) made by the user. authentication Verification of identity for a person or process. backplane The backplane provides 48 VDC power distribution and connections for all logic cards. backup FRU When an active FRU fails, an identical backup FRU takes over operation automatically (failover) to maintain director and Fibre Channel link operation. Contrast with active FRU. BB_Credit See buffer-to-buffer credit.
Glossary broadcast frames Data packet, also known as a broadcast packet, whose destination address specifies all computers on a network. buffer Storage area for data in transit. Buffers compensate for differences in processing speeds between devices. See also buffer-to-buffer credit. buffer-to-buffer credit (BB_Credit) Indicates the maximum number of frames a port can transmit without receiving a receive ready signal from the receiving device.
Glossary Class 2 Fibre Channel service Provides a connectionless (not dedicated) service with notification of delivery or nondelivery between two N_Ports. In-order delivery of frames is not guaranteed. Class 3 Fibre Channel service Provides a connectionless (not dedicated) service without notification of delivery or nondelivery between two N_Ports. Also known as datagram. community profile Information that specifies which management objects are available to what management domain or SNMP community name.
Glossary CRC See cyclic redundancy check. CTP/CTP2 card See control processor (CTP2) card. cyclic redundancy check (CRC) System of error checking performed at both the sending and receiving station using the value of a particular character generated by a cyclic algorithm. When the values generated at each station are identical, data integrity is confirmed. DASD Acronym for direct access storage device. datagram See Class 3 Fibre Channel service.
Glossary Director An intelligent Fibre Channel switching device providing any-to-any port connectivity between nodes (end devices) on a switched fabric. The director sends data transmissions (data frames) between nodes in accordance with the address information present in the frame headers of those transmissions. Director Product Manager application See Product Manager application.
Glossary Ethernet A widely implemented local area network (LAN) protocol that uses a bus or star topology and serves as the basis for the IEEE 802.3 standard, which specifies the physical and software layers. Baseband LAN allows multiple station access to the transmission medium at will without prior coordination and which avoids or resolves contention. Ethernet hub A device used to LAN-connect the HAFM server and managed directors.
Glossary FE-MIB See Fibre Channel fabric element. fiber Physical media types supported by the Fibre Channel specification, such as optical fiber, copper twisted pair, and coaxial cable. fiber optics Branch of optical technology concerned with the transmission of light pulses through fibers made of transparent materials such as glass, fused silica, and plastic.
Glossary FICON Management Server An optional feature that can be enabled on the director or switch through the Product Manager application. When enabled, host control and management of the director or switch is provided through an S/390 Parallel Enterprise or 2/Series Server attached to a director or switch port. FRU See field-replaceable unit. gateway A multi-homed host used to route network traffic from one network to another, and to pass network traffic from one protocol to another.
Glossary high availability A performance feature characterized by hardware component redundancy and hot-swappability (enabling non-disruptive maintenance). High-availability systems maximize system uptime while providing superior reliability, availability, and serviceability. homogeneous fabric A fabric consisting of only HP products. hop Data transfer from one fabric node to another node. hop count The number of hops a unit of information traverses in a fabric.
Glossary information message Software message that indicates to a user that a function is performing normally or has completed normally. See also error message and warning message. initial machine load (IML) Hardware reset for all installed CTP2 cards on the director. It does not affect other hardware. It is initiated by pushing the white button on a director’s CTP2 card. initial program load (IPL) Process of initializing the device and causing the operating system to start.
Glossary IOCP See input/output configuration program. IP address See internet protocol address. IPL See initial program load. ISL See interswitch link. jumper cable Optical cable that provides physical attachment between two devices or between a device and a distribution panel. Contrast with trunk cable.
Glossary logical unit number (LUN) In Fibre Channel addressing, a logical unit number is a number assigned to a storage device which, in combination with the storage device’s node port’s world wide name, represents a unique identifier for a logical device on a storage area network. loopback plug In a fiber optic environment, a type of duplex connector used to wrap the optical output signal of a device directly to the optical input.
Glossary Media Access Control (MAC) address Hardware address of a node (device) connected to a network. MIB See management information base. multicast Delivery of a single transmission to multiple destination node ports (N_Ports). Can be one to many or many to many. All members of the group are identified by one IP address. See also broadcast. multi-switch fabric Fibre Channel fabric created by linking more than one director or switching device within a fabric.
Glossary nondisruptive maintenance Ability to service FRUs (including maintenance, installation, removal and replacement) while normal operations continue without interruption. See also concurrent maintenance. N_Port See node port. offline sequence (OLS) Sequence sent by the transmitting port to indicate that it is attempting to initialize a link and has detected a problem in doing so. OLS See offline sequence.
Glossary password Unique string of characters known to the computer system and to a user who must specify it to gain full or limited access to a system and to the information stored within it. path In a network, any route between any two ports. persistent binding A form of server-level access control that uses configuration information to bind a server to a specific Fibre Channel storage volume (or logical device) using a unit number.
Glossary Product Manager application Application that implements the management user interface for a specified director. When a product instance is opened from the HAFM application’s Products View, the director Product Manager application is invoked. product name User-configurable identifier assigned to a managed product. Typically, this name is stored on the product itself. For the Director 2/64, the product name can also be accessed by an SNMP manager as the system name.
Glossary RFI Acronym for radio frequency interference. SAN See storage area network. SA/OS 390 See system automation for operating system 390 (SA OS/390). SBAR See serial crossbar assembly. SC Acronym for subscriber connector. segmented E_Port Expansion port (E_Port) that has ceased to function as an E_Port within a multi-switch fabric due to an incompatibility between the fabrics that it joins. See also expansion port. SEL Acronym for system error light.
Glossary SNMP community Also known as SNMP community string. An SNMP community is a cluster of managed products (in SNMP terminology, hosts) to which a server or managed product running the SNMP agent belongs. SNMP community name The name assigned to a given SNMP community. Queries from an SNMP management station to a device running an SNMP agent will only elicit a response if those queries are addressed with the correct SNMP community name. SSP See system services processor.
Glossary TCP/IP See transmission control protocol/internet protocol. topology Logical and/or physical arrangement of stations on a network. transmission control protocol/internet protocol (TCP/IP) A suite of communication protocols used to connect host systems to the Internet. See also network address. trap Unsolicited notification of an event originating from an SNMP managed device and directed to an SNMP network management station.
Glossary vital product data (VPD) System-level data stored by the backplane in the electrically erasable programmable read-only memory. This data includes serial numbers and identifies the manufacturer. VPD See vital product data. warning message Software message that indicates a possible error was detected. See also error message and information message. world wide name (WWN) Eight-byte address that uniquely identifies a switch, or a node (end device) on global networks. wrap plug See loopback plug.
Index 10/100 BaseT ethernet hub 1–1 10/100 Mbps ethernet port 1–18 10/100 Mbps LAN connectors 1–9 A AC filter module removal 4–26 AC system harness 1–21 acoustical noise, director 1–7 active zone set, zone set view 3–18 airflow clearances, director 1–7 AIX operating system 1–15 altitude operating environment 1–8 shipping and storage environment 1–8 angular velocity, of fans 1–21 applications management services 1–23 ASN.
Index CTP2 cards description 1–18 event codes tables B–29 failover 1–18 firmware, managing 3–48 FLASH memory 3–37 LEDs 1–18 MAP 2–68 NV-RAM, backing up 3–54 resetting 1–18 customer checklist for fault isolation 2–12 D data collection, procedure 3–37 default settings, resetting 3–57 degraded fabric performance, causes of 1–5 diagnostic features, software 1–22 diagnostic functions, list of 1–26 diagnostics embedded web server 1–25 HAFM application 1–23 MAPs 2–1 port diagnostics 3–19 product manager 1–23 dia
Index MAP 2–95 multiswitch fabrics 1–5 reasons for 3–25 zone set view 3–19 E_ports UPM card 1–19 electric shock, warning 3–40 electrostatic discharge grounding cable 1–30 wrist strap 1–30 electrostatic discharge (ESD) information 4–2 repair procedures, caution 3–2 e-mail notification reporting 1–27 embedded port subsystem 1–18 embedded web server 1–9, 1–25 ethernet link, MAP 2–55 fault isolation 2–12 interface 1–11 EP subsystem 1–18 equipment rack 1–1 service clearances 1–8 equipment symbols xi error detec
Index fault isolation customer checklist 2–12 diagnostics 2–1 FRU list view 3–14 intranet service caution 1–14 logs 3–3 maintenance approach 1–11 MAPs 2–1 SNMP traps 1–27 zone set view 3–19 FC fabric element MIB, version 1–4 FC-PH 4.
Index description 1–9 ethernet link, MAP 2–55 event log B–1 fault isolation 1–11 MAP 2–12 Fibre Alliance MIB 1–4 firmware versions, storing 3–48 MAP 2–49, 2–108 remote workstation 1–2 session log 3–4 specifications 1–10 hard drive 1–10 hard drives remote workstation 1–15 hardware log 3–8 hardware, MAP 2–108 HBA, zoning 1–4 heat dissipation, director 1–7 help online user documentation 1–26 help, obtaining xii hexagonal adapter 1–28 HP authorized reseller xiii firmware versions 3–49 home page 3–49 technical
Index refreshing 3–10 link incident, problem descriptions, list of 3–9 Linux operating system, version 1–15 logs audit director 3–6 HAFM application 3–3 event director 3–6, 3–7 HAFM application 3–3 fabric 3–5 hardware 3–8 link incident 3–9 list of 3–3 product status 3–5 session 3–4 longwave laser transceivers 1–20 loopback tests external 3–32 internal 3–30 performing 3–30 M maintenance analysis procedures See MAPs maintenance approach 1–11 maintenance data, collecting 3–37 maintenance functions, list of 1
Index version 1–26 network addresses, product status log 3–5 node list view 3–15 nodes, types, list of 3–15 notebook PC 1–9 null modem cable 1–29 NV-RAM, backing up 3–54 O OFC class 1 laser transceivers 1–18 offline state, setting 3–44 online state, setting 3–43 online user documentation 1–26 operating environment, director 1–8 operations panel 1–26 optic transceivers 1–19 out-of-band, management access methods 1–2 P part numbers front-accessible FRUs 5–1 miscellaneous FRUs 5–5 rear-accessible FRUs 5–3 p
Index power-on 3–40 setting offline 3–43 setting online 3–43 unblocking ports 3–46 upgrading software 3–57 ProComm Plus 1–30 product manager diagnostic features 1–23 FRU list view 3–14 logs, list of 3–3 MAP 2–49 messages A–24 MIB variable, modifying 1–27 node list view 3–15 performance view 3–16, 3–27 port card view 3–20 port list view 3–12 SNMP agent 1–2 topology view 3–17 zone set view 3–18 product status log 3–5 protective plug 1–29 public intranet, service caution 1–14 Q quick start, MAPs 2–2 R rack
Index grounding cable with wrist strap 1–30 ESD information 4–2 repair procedures 3–2 fiber-optic protective plug 1–29 SBAR assembly description 1–21 event codes B–56 failover 1–21 frame transmission 1–18 LEDs 1–21 MAP 2–68 removing and replacing 4–20 tools 4–20 segmentation causes of 1–6 MAP 2–95 serial numbers, FRUs, hardware log 3–9 service maintenance and diagnostic functions 1–26 service caution public intranet 1–14 serviceability director features 1–3 session log 3–4 setting offline state 3–44 online
Index UPM cards 4–9 UPM filler blank 4–16 topology view 3–17 torque tool 1–28 trap messages maximum recipients 1–4 U UltraSPARC-II processor 1–15 unblocking port 3–46 UPM card 3–47 UNIX workstation, specifications 1–15 upgrading software 3–57 UPM cards blocking 3–46 description 1–18 event codes B–44 heat dissipation 1–7 inband management 1–2 LEDs 3–20 loopback tests, performing 3–30 MAP 2–76 port card view 3–20 ports, blocking or unblocking 3–44 removing and replacing 4–9 tools 4–9 unblocking 3–47 UPM fil
Index Windows 2000 1–10 Windows 2000 operating system MAP 2–49 Windows operating systems, versions 1–15, 1–30 workstation, UNIX 1–15 world wide name, caution, zoning 1–4 wrap plug multimode 1–28 singlemode 1–28 WWN node list view 2–86, 3–16 port properties dialog box 3–24 director 2/64 service manual zone member 3–19 zoning, caution 1–4 Z Zip drive 1–10 zone set definition 1–5 zone set view 3–18 zones, definition of 1–4 zoning features 1–4 joining, rules of 1–5 Index–11
