IBM TotalStorage SAN140M Installation And Service Manual

Director
Table of Contents

Advertisement

Quick Links

IBM TotalStorage SAN140M Director
Installation and Service Manual
Service information: 2027 / 140
Read Before Using
This product contains software that is licensed under written license agreements. Your use of such software is subject to
the license agreements under which they are provided.
GC26-7664-04

Advertisement

Table of Contents
loading

Summary of Contents for IBM TotalStorage SAN140M

  • Page 1 IBM TotalStorage SAN140M Director Installation and Service Manual Service information: 2027 / 140 Read Before Using This product contains software that is licensed under written license agreements. Your use of such software is subject to the license agreements under which they are provided.
  • Page 3 IBM TotalStorage SAN140M Director Installation and Service Manual Service information: 2027 / 140 GC26-7664-04...
  • Page 4 ® Order publications through your IBM representative or the IBM branch office serving your locality. © Copyright International Business Machines Corporation 2004, 2006. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract...
  • Page 5: Table Of Contents

    Task 2: Unpack, inspect, and install the Ethernet hub (optional)26 Unpack and inspect the Ethernet hub ........27 Desktop installation..............27 Rack-mount installation.............29 Task 3: Unpack, inspect, and install the director......30 Rack-mount installation.............31 Task 4: Configure director at the EFCM Basic Edition interface (optional) .....................33 © Copyright IBM Corp. 2006...
  • Page 6 Configure director identification ..........34 Configure date and time............35 Configure parameters ..............36 Configure fabric parameters ............. 38 Configure network information ..........39 Configure basic port information..........41 Configure port BB_Credit ............42 Configure port NPIV..............42 Configure SNMP ................ 43 Enable CLI ...................
  • Page 7 Configure threshold alerts ............81 Enable EFCM Basic Edition and Telnet access .......84 Configure, enable, and test e-mail notification.......84 Configure and enable Ethernet events........86 Configure, enable, and test call-home event notification..86 Configure security ..............87 Configure interswitch links ............88 Task 19: Back up configuration data..........89 Task 20: Cable Fibre Channel ports ..........91 Task 21: Configure Zoning (Optional) ..........92 Task 22: Connect director to a fabric element (optional) ....92...
  • Page 8 cation)..................181 Block or unblock a port (EFCM Basic Edition)..... 182 Swapping ports ................183 Performing channel wrap tests (FICON) ........185 Collecting maintenance data............186 Collecting maintenance data (Element Management applica- tion)..................... 186 Collecting maintenance data (EFCM Basic Edition) ... 187 Powering the director on or off............
  • Page 9 RRP: Optical transceiver (SFP and XFP) ........223 RRP: Filler panel (UPM and XPM) ..........227 RRP: Power supply ................229 RRP: AC module ................232 RRP: Fan module................235 RRP: Power/system error LED assembly ........239 RRP: SBAR assembly ...............241 RRP: Backplane.................244 Chapter 6 Illustrated parts breakdown RoHS Information..............251 Front-accessible FRUs..............253 Rear-accessible FRUs ...............255...
  • Page 10 Requirements ................... 341 Restore management server procedure ........342 Glossary ........................347 Notices ......................... 373 Trademarks ..................375 Electronic emission notices............. 375 Laser Compliance Statement ..........375 Federal Communications Commission (FCC) Class A State- ment .................... 376 Industry Canada Class A Emission Compliance Statement ..Avis de conformité...
  • Page 11 Address properties dialog box (IP Address page) ........68 New feature key dialog box ................72 Configure date and time dialog box ............73 Configure identification dialog box ............. 75 Configure switch parameters dialog box ............ 76 © Copyright IBM Corp. 2006...
  • Page 12 Configure fabric parameters dialog box ............. 77 Configure ports dialog box ................79 Configure SNMP dialog box ................ 81 New threshold alert dialog box (Screen 1) ..........82 New threshold alert dialog box (Screen 2) ..........83 New threshold alert dialog box (Screen 3) ..........84 Email event notification setup dialog box ..........
  • Page 13 Miscellaneous parts ..................258 Power cords and receptacles ............... 259 24-Port Ethernet hub ..................340 Figures...
  • Page 14 SAN140M Installation and Service Manual...
  • Page 15 Tables IBM products and SAN management documentation ......xvi Element Manager alert symbols, messages, and status ......15 Factory-set defaults (director) ..............23 Installation Task summary ................24 Operational states and symbols ..............70 Factory-set defaults ..................95 MAP summary ....................95 Event codes versus maintenance action ............
  • Page 16 SAN140M Installation and Service Manual...
  • Page 17: Preface

    (SAN) technology, and Fibre Channel technology. The IBM TotalStorage SAN140M director is to be installed and serviced by qualified IBM service representatives only. The director contains no customer-serviceable parts that require internal access to the product during normal operation or prescribed maintenance conditions.
  • Page 18: Ibm Products And San Management Documentation

    IBM and McDATA publications Some of the documentation that is applicable to IBM TotalStorage products is provided by McDATA Corporation. The documents often are identified by a McDATA product name that corresponds to the IBM product name. Table 1 lists the IBM product name, the corresponding McDATA product name, the applicable software, and the documentation that is relevant to the product.
  • Page 19: Where To Get Help

    • E/OS SNMP Support Manual (620-000131) Edition • E/OS Command Line Interface User Manual (620-000134) Ordering printed manuals To order a printed copy of this publication, contact your IBM Branch office or you can locate (and purchase) books online at: http://www.elink.ibmlink.ibm.com/public/applications/publications/cgib in/pbi.cgi?.
  • Page 20 Department GZW 9000 South Rita Road Tucson, Arizona 85744-001 U.S.A When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
  • Page 21 Safety and environmental notices ATTENTION ! The IBM Total Storage SAN140M director is not designed to be installed and serviced by customers. Installation and servicing of the director should be performed only by qualified service representatives. Safety notices and labels When using this product, observe the danger, caution, and attention notices contained in this guide.
  • Page 22 DANGER To prevent a possible shock from touching two surfaces with different protective ground (earth), use one hand, when possible, to connect or disconnect signal cables. (D001) DANGER Overloading a branch circuit is potentially a fire hazard and a shock hazard under certain conditions.
  • Page 23 DANGER Electrical voltage and current from power, telephone, and communication cables are hazardous. To avoid a shock hazard: • Do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration of this product during an electrical storm. • Connect all power cords to a properly wired and grounded electrical outlet.
  • Page 24 can be either danger or caution notices, depending upon the level of the hazard. The actual product safety labels may differ from these sample safety labels: DANGER Hazardous voltage, current, or energy levels are present inside any component that has this label attached. (L001) DANGER Rack-mounted devices are not to be used as a shelf or work space.
  • Page 25 If the symbol is... It means..A hazardous electrical condition with less severity than electrical danger. A generally hazardous condition not represented by other safety symbols. A specification of product weight that requires safe lifting practices. The weight range of the product is listed below the graphic, and the wording of the caution varies, depending on the weight of the device.
  • Page 26 CAUTION The doors and covers to the product are to be closed at all times except for service by trained service personnel. All covers must be replaced and doors locked at the conclusion of the service operation. (C013) CAUTION The system contains circuit cards and/or assemblies that contain lead solder.
  • Page 27 Rack-mount safety information Danger Always lower the leveling pads on the rack cabinet. Always install stabilizer brackets on the rack cabinet. To avoid hazardous conditions due to uneven mechanical loading, always install the heaviest devices in the bottom of the rack cabinet.
  • Page 28 (For sliding drawers.) Do not pull out or install any drawer or feature if the rack stabilizer brackets are not attached to the rack. Do not pull out more than one drawer at a time. The rack may become unstable if you pull out more than one drawer at a time. (For fixed drawers.) This drawer is a fixed drawer and should not be moved for servicing unless specified by manufacturer.
  • Page 29 Ensure that all devices, shelves, drawers, doors, and cables are secure. Ensure that the four leveling pads are raised to their highest position. Ensure that there is no stabilizer bracket installed on the rack cabinet during movement. (R002) Attention notices An attention notice indicates the possibility of damage to a program, device, or system, or to data.
  • Page 30 IBM encourages owners of information technology (IT) equipment to responsibly recycle their equipment when it is no longer needed. IBM offers a variety of product return programs and services in several countries to assist equipment owners in recycling their IT products. Information on IBM product recycling offerings can be found on IBM’s Internet site at...
  • Page 31 In the United States, IBM has established a return process for reuse, recycling, or proper disposal of used IBM sealed lead acid, nickel cadmium, nickel metal hydride, and other battery packs from IBM Equipment.
  • Page 32 For Taiwan: Cable warning WARNING Handling the cord on this product or cords associated with accessories sold with this product, will expose you to lead, a chemical known to the State of California to cause cancer, and birth defects or other reproductive harm. Wash hands after handling. SAN140M Installation and Service Manual...
  • Page 33: General Information

    Chapter 1: General information ® The IBM TotalStorage SAN140M director provides up to 140 ports of high-performance, dynamic Fibre Channel connectivity for switched fabric devices in a storage area network (SAN). The director provides a broad bandwidth (1, 2 or 10 gigabits per second), redundant switched data paths, and long transmission distances.
  • Page 34 Up to three hubs can be daisy-chained to provide additional Ethernet connections as more directors (or other IBM managed products) are installed on a customer network. As an option, administrators or operators with a browser-capable PC and an Internet connection can monitor and manage the director through the EFCM Basic Edition interface.
  • Page 35: Cabinet-Mounted San140M Directors And Management Server

    ENTER Figure 1 Cabinet-mounted SAN140M directors and management server Location Description Ethernet hub Director Management server Director Director Chapter 1: General information...
  • Page 36: Field-Replaceable Units

    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. Director FRUs accessed from the front (Figure 2) include the: •...
  • Page 37: Director Frus (Rear Access)

    • Universal port module (UPM) cards (2 Gbps). • 10 Gbps port module (XPM) cards. • Serial crossbar (SBAR) assemblies. • Power supplies. • AC modules. • Power/System Error LED Assembly (not shown). • Backplane (not shown). Director FRUs (rear access) Figure 3 Location Description...
  • Page 38: Power/System Led Assembly

    Power/system LED assembly The bezel at the top front of the director includes an amber system error light-emitting diode (LED) and a green power LED. These LEDs are actuated and controlled by a Power/System LED Assembly which is accessed from the rear of the director. The power LED lights up when the director is powered on and operational.
  • Page 39: Upm Card

    • Ports, causing all Fibre Channel connections to drop momentarily until the connections automatically recover. This causes attached devices to log out and log back in, therefore data frames lost during director reset must be retransmitted. A reset should only be performed if a CTP card failure is indicated. As a precaution, the RESET button is flush mounted to protect against inadvertent activation.
  • Page 40: Upm Card Leds And Connectors

    • Four duplex LC connectors for attaching fiber-optic cables. • 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. One amber LED and one green LED are associated with each port and indicate port status as follows: —...
  • Page 41: Xpm Card

    Location Description Card LED Port LEDs Port connectors XPM card Each XPM card (Figure 5) provides one full-duplex generic port (G_Port) that transmits or receives data at 10 gigabits per second (Gbps). The card faceplate contains: • One duplex LC connector for attaching fiber-optic cables. •...
  • Page 42: Sfp And Xfp Transceivers

    SFP and XFP transceivers Singlemode or multimode fiber-optic cables attach to director ports through 2 Gbps small form-factor pluggable (SFP, Figure 6 - for UPM cards) or 10 Gbps form-factor pluggable (XFP, Figure 7 - for XPM cards) optic transceivers. The fiber-optic transceivers provide duplex ®...
  • Page 43: Power Supply

    Figure 7 Ten Gbps form-factor pluggable (XFP) transceiver Power supply Redundant, load-sharing power supplies step down and rectify facility input power to provide 48-volt direct current (VDC) power to director FRUs. The power supplies also provide overvoltage and overcurrent protection. Either power supply can be replaced while the director is powered on and operational.
  • Page 44: Fan Module

    • An input filter and AC system harness (internal to the FRU) that provides the wiring to connect the AC power connectors to the power supplies (through the backplane). Fan module Three fan modules, each containing one system fan (three system fans total), provide cooling for director FRUs, as well as redundancy for continued operation if a fan fails.
  • Page 45: Error-Detection, Reporting, And Serviceability Features

    Error-detection, reporting, and serviceability features The director provides the following error detection, reporting, and serviceability features: • Light-emitting diodes (LEDs) on director FRUs and the front bezel that provide visual indicators of hardware status or malfunctions. • Redundant FRUs (logic cards, power supplies, and cooling fans) that are removed or replaced without disrupting director or Fibre Channel link operation.
  • Page 46: Element Manager Status Indicators

    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. • An internal modem for use by support personnel to dial-in to the management server for event notification and to perform remote diagnostics.
  • Page 47: Tools And Test Equipment

    that describe the condition of the director and its FRUs. These alert symbols, messages, and a description are summarized in Table Element Manager alert symbols, messages, and status Table 2 Symbol Message Description Fully operational All components and installed ports are operational. Redundant failure A redundant component has failed, and the backup component has taken over.
  • Page 48: Torque Tool And Hex Adapter

    SAN140M 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 IBM product. Use of the wrong tool may overtighten and damage logic cards.
  • Page 49: Tools Supplied By Service Personnel

    • Fiber-optic protective plug - For safety and port transceiver protection, fiber-optic protective plugs (Figure 11) must be inserted in all director ports without fiber-optic cables attached. The director is shipped with protective plugs installed in all ports. Fiber-optic protective plug Figure 11 •...
  • Page 50: Director Management

    ® • T10 Torts tool - The tool is required to rack-mount the director or to remove, replace, adjust or tighten various chassis or cabinet components. • Electrostatic discharge (ESD) grounding cable with attached wrist strap - Use of the ESD wrist strap is required when working in and around the director card cage.
  • Page 51: Ordering The Lift Tool

    • Customer-supplied PC or UNIX-based platform with the server and client Element Manager application installed. • Simple network management protocol (SNMP). An SNMP agent is implemented through the SAN management application that allows administrators on SNMP management workstations to access director management information using any standard network management tool.
  • Page 52: United States Locations

    • You do not record parts usage. • Return the lift tool and the 24-inch load plate to the parts center after you complete the installation or removal of the Director. United States locations In the United States, call UPS Logistics at 800-528-6070 to order the lift tool and the 24-inch load plate.
  • Page 53 Contact your branch office tools coordinator or your region specialist if you have any questions or concerns. Chapter 1: General information...
  • Page 54 SAN140M Installation and Service Manual...
  • Page 55: Installation Tasks

    EFCM Basic Edition interface user name (case sensitive) Administrator EFCM Basic Edition interface password (case sensitive) password Customer-level password (maintenance port access) password Maintenance-level password (maintenance port access) level-2 IP address 10.1.1.10 Subnet mask 255.0.0.0 Gateway address 0.0.0.0 © Copyright IBM Corp. 2006...
  • Page 56: Installation Task Summary

    • Preparing the director for the customer or some consultant to configure. IBM does not install the EFCM Basic program, install the management server, or configure the machine for use. Table 4 summarizes the installation tasks for the director and optional Ethernet hub.
  • Page 57 Installation Task summary (Continued) Table 4 Task number and description Required or optional Page Task 11: Assign user names and passwords Required if management server is used. Task 12: Configure the director to the management Required if management server is used. application Task 13: Record or verify server restore information Required if management server is used.
  • Page 58: Task 1: Verify Installation Requirements

    Task 1: Verify installation requirements Verify that the following requirements are met prior to director and management interface installation. Ensure: • A site plan and planning tasks are complete. Refer to the IBM TotalStorage Products in a SAN Environment Planning Manual, GC26-7675. •...
  • Page 59: Unpack And Inspect The Ethernet Hub

    Ensure the packaged items correspond to the items listed on the enclosed bill of materials. 3. If any items are damaged or missing, call the IBM Quality Hotline toll-free at 1-800-442-6773 within the United States and Canada. In other locations direct dial 770-858-8459.
  • Page 60: Patch Cable And Mdi Selector Configuration

    a. To connect the top and middle stacked hubs, connect an RJ-45 patch cable to port 24 of the top hub, then connect the cable to port 12 of the middle hub. b. To connect the bottom and middle stacked hubs, connect a second RJ-45 patch cable to port 24 of the middle hub, then connect the cable to port 12 of the bottom hub.
  • Page 61: Rack-Mount Installation

    Rack-mount installation Perform the following steps to install and configure up to three Ethernet hubs in a cabinet or 19-inch equipment rack. A pointed instrument (pencil tip or bent paper clip), #2 Phillips screwdriver, and 1/8-inch Allen wrench are required. 1.
  • Page 62: Task 3: Unpack, Inspect, And Install The Director

    c. Use a pointed instrument to set the medium-dependent interface (MDI) switch on the top and middle hubs to MDI (in) (Figure 13, 1 and 2). Set the MDI switch on the bottom hub to MDIX (out) (Figure 13, 3). NOTE: To connect two hubs, follow step b step c...
  • Page 63: Rack-Mount Installation

    3. If any items are damaged or missing, call the IBM Quality Hotline toll-free at 1-800-442-6773 within the United States and Canada. In other locations direct dial 770-858-8459. Rack-mount installation CAUTION The weight of this part or unit is more than 55 kg (121.2 lb.). It takes specially-trained persons and/or a lifting device to safely lift this part or unit.
  • Page 64: Ac Power Connections (Director)

    6. Connect the remaining ends of the AC power cords to separate (for redundancy) rack power strips. NOTE: The director does not have a power switch. Therefore the director powers on when its power cords are connected to facility or rack power. Figure 15 AC power connections (director) 7.
  • Page 65: Task 4: Configure Director At The Efcm Basic Edition Interface (Optional)

    12. If a POST error or other malfunction occurs, go to Chapter 3, Maintenance analysis procedures (MAPS) to isolate the problem. 13. Perform one of the following: — If the director will be managed through the EFCM Basic Edition interface, go to Task 4: Configure director at the EFCM Basic Edition interface (optional).
  • Page 66: Configure Director Identification

    8. Selectively perform the following tasks according to customer requirements: • Product - includes identification, date and time, parameters, fabric parameters, and network addresses. • Ports - includes basic information, buffer-to-buffer credits (BB_Credits), and N_Port identifier virtualization (NPIV). • Management - includes SNMP trap message recipients, command line interface (CLI), open systems management server (OSMS), secure socket layer (SSL) encryption.
  • Page 67: Configure Date And Time

    Identification view Figure 16 Configure date and time Perform this procedure to configure director date and time. 1. Select Switch and Date & Time from the Configure menu at any view. The Date Time View displays (Figure 17). a. Click Date fields that require change, and type numbers in the following ranges: •...
  • Page 68: Configure Parameters

    Date time view Figure 17 Configure parameters Perform this procedure to configure director operating parameters. 1. Set the director offline (Setting the director online or offline page 190). 2. Select Switch and Parameters from the Configure menu at any view. The Parameters View displays (Figure 18).
  • Page 69 b. At the Rerouting Delay field, check (enable) or uncheck the parameter. When enabled, traffic is delayed through the fabric by the error detect time out value (E_D_TOV). This delay ensures Fibre Channel frames are delivered to their destination in order. c.
  • Page 70: Configure Fabric Parameters

    Configure fabric parameters Perform this procedure to configure fabric operating parameters. 1. Set the director offline (Setting the director online or offline page 190). 2. Select Switch and Fabric Parameters from the Configure menu at any view. The Fabric Parameters View displays (Figure 19).
  • Page 71: Configure Network Information

    Available selections are: • McDATA Fabric 1.0 - Select this option if the director is fabric-attached only to other IBM directors or switches operating in McDATA fabric mode. • Open Fabric 1.0 - Select this option (default) for managing...
  • Page 72: Network View

    Network view Figure 20 a. At the IP Address field, type the new value (default is 10.1.1.10). b. At the Subnet Mask field, type the new value (default is 255.0.0.0). c. At the Gateway Address field, type the new value (default is 0.0.0.0).
  • Page 73: Configure Basic Port Information

    e. Click close (X) at the upper right corner of the DOS window to close the window and return to the Windows desktop. 4. Perform a power-on reset (POR) (IML, IPL, or reset the director page 192). 5. At the PC, launch the browser application (Internet Explorer or Netscape Navigator).
  • Page 74: Configure Port Bb_Credit

    2. Click OK to save and activate changes. Basic information view Figure 21 Configure port BB_Credit Perform this procedure to configure port receive BB_Credit. 1. Set all or a subset of user-specified ports offline (Blocking and unblocking ports on page 181). 2.
  • Page 75: Configure Snmp

    (Install PFE keys (optional) on page 47). Perform this procedure to configure ports for NPIV connectivity. 1. Select Ports and NPIV from the Configure menu at any view. The NPIV View displays. 2. Click Enable to activate director NPIV operation. 3.
  • Page 76: Enable Cli

    c. Check the Enable Authentication Traps check box to enable transmission of SNMP trap messages to recipients. d. For each configured recipient, type a community name of 32 alphanumeric characters or less in the Name field. The name is incorporated in SNMP trap messages to ensure against unauthorized viewing.
  • Page 77: Enable Or Disable Host Control

    CLI view Figure 23 Enable or disable host control Perform this procedure to toggle (enable or disable) host control of the director through the OSMS. To enable or disable OSMS and host control: 1. Select OSMS from the Configure menu at any view. The OSMS View displays (Figure 24).
  • Page 78: Configure Ssl Encryption

    Configure SSL encryption SSL is a protocol that encrypts internet communications. The protocol uses key encryption and includes a digital certificate that enables server authentication and SSL session initialization. To configure SSL encryption: 1. Select SSL from the Configure menu at any view. The SSL View displays (Figure 25).
  • Page 79: Install Pfe Keys (Optional)

    SSL view Figure 25 Install PFE keys (optional) The following PFE-keyed options are available: • Element Manager application - This feature enables out-of-band director management through an Element Manager interface. Directors are delivered with the application enabled for a 31-day grace period.
  • Page 80 Keys are encoded to work only with the serial number of the installed director. Record the key to re-install the feature if required. If the director fails and is replaced, obtain new PFE keys from IBM). Have the serial numbers of the failed and replacement directors, and the old PFE key number or transaction code.
  • Page 81: Configure Security

    4. After the director reset, the message "Feature installation complete. Click here to login." displays. 5. Click here to login and start a new EFCM Basic Edition session. The Enter Network Password dialog box displays. Maintenance feature installation view Figure 26 Configure security This section describes optional director security features configured through Security menu selections.
  • Page 82: Configure Interswitch Links

    — Software settings - Use this page to configure challenge handshake authentication protocol (CHAP) controlled management interface access (out-of-band and inband) to the director. — Device settings - Use this page to configure a CHAP secret authentication sequence for nodes (devices) attached to the director through E_Ports or N_ports.
  • Page 83: Task 5: Configure Director Network Information (Optional)

    path PFE keys must be installed (Install PFE keys (optional) page 47). Features include: • OpenTrunking - Use the OpenTrunking View to optimize ISL bandwidth. The feature monitors data rates (congestion and BB_Credit starvation) through multiple ISLs and load balances traffic (from congested to uncongested links) accordingly.
  • Page 84 • Gateway address - The default gateway address is 0.0.0.0. If the director is installed on a public LAN, the gateway address must be changed to the address of the corporate intranet local router. Verify the LAN installation with the customer. If one director is installed on a dedicated LAN, network addresses do not require change.
  • Page 85: Connection Description Dialog Box

    Connection description dialog box Figure 27 5. Type a descriptive director name in the Name field and click OK. The Connect To dialog box displays. 6. Ensure the Connect using field displays COM1 or COM2 (depending on the port connection to the director), and click OK. The COMn Properties dialog box displays, where n is 1 or 2.
  • Page 86 — IP Address (default is 10.1.1.10). — Subnet Mask (default is 255.0.0.0). — Gateway Address (default is 0.0.0.0). — Auto Negotiate. — Speed. — Duplex. Only the IP Address, Subnet Mask, and Gateway Address fields are configurable. 10. Change the IP address, subnet mask, and gateway address as directed by the customer.
  • Page 87: Task 6: Configure Server Password And Network Addresses

    — If the director is delivered separately from the management server, go to Task 6: Configure server password and network addresses following. — If the director is delivered as part of an equipment cabinet, go Task 6: Configure server password and network addresses page 55.
  • Page 88: Configure Private Lan Addresses

    Configure private LAN addresses To configure TCP/IP network information for the private LAN connection (LAN 2): 1. At the management server LCD panel, press ENTER. The Welcome!! or operational information message changes to an Input Password 0**** message. 2. Input the default or changed password, and press ENTER. The LAN 1 Setting?? message appears at the LCD panel.
  • Page 89: Task 7: Configure Management Server Information

    5. Press ENTER. The LAN 1 IP address changes and the default subnet mask of 255.0.0.0 appears. 6. Input a new subnet mask, then press ENTER. A Save Change? Yes, Save!! message appears. 7. Press ENTER. A Wait a moment! message appears at the LCD panel, the panel returns to the LAN 1 Setting?? message, and the LAN 1 subnet mask changes.
  • Page 90: Configure Management Server Names

    4. Click the Send Ctrl-Alt-Del button at the top of the window to log on to the server desktop. The Log On to Windows dialog box displays. NOTE: Do not simultaneously press the Ctrl, Alt, and Delete keys. This action logs the user on to the browser-capable PC, not the server. 5.
  • Page 91: Configure Gateway And Dns Server Addresses

    Figure 28 Identification changes dialog box Configure gateway and DNS server addresses To configure gateway and DNS server IP addresses for the private LAN connection (LAN 2) and public LAN connection (LAN 1): 1. At the Windows desktop, click Start at the left side of the task bar (bottom of the desktop), then sequentially select Settings, Control Panel, and Network and Dial-up Connections.
  • Page 92: Internet Protocol (Tcp/Ip) Properties Dialog Box

    Internet protocol (TCP/IP) properties dialog box Figure 29 5. The Use the following IP address radio button is enabled and the IP address and Subnet mask fields display network information configured while performing Task 6: Configure server password and network addresses on page 55.
  • Page 93: Task 8: Configure Windows Operating System Users

    Task 8: Configure Windows operating system users Configure password access for all authorized Windows (server) users. It is also recommended to change the default administrator password. To configure users: 1. At the Windows desktop, click Start at the left side of the task bar (bottom of the desktop), then sequentially select Settings, Control Panel, and Users and Passwords.
  • Page 94: Change User Properties

    5. Click Finish. New user information is added and the wizard closes. Record the user information for reference. 6. If no other users are to be added, close all dialog boxes and return to the Windows desktop. Add new user wizard Figure 30 Change user properties To change existing user properties:...
  • Page 95: Task 9: Set Management Server Date And Time

    Properties dialog box (General tab) Figure 31 Task 9: Set management server date and time SAN Management application logs are stamped with the server date and time, and the director system clock is synchronized with the server date and time by default. To set the server date and time: 1.
  • Page 96: Date/Time Properties Dialog Box (Time Zone Tab)

    Date/time properties dialog box (Time Zone tab) Figure 32 3. To change the time zone: a. Select the appropriate time zone from the drop-down list at the top of the dialog box. b. If instructed by the customer, select the Automatically adjust clock for daylight saving changes check box.
  • Page 97: Task 10: Configure The Call-Home Feature (Optional)

    The Call Home Configuration dialog box displays. 3. At the Call Center Phone Number field, enter the telephone number for IBM technical support. Include necessary information, such as the country code, area code, or any prefix required to access a telephone line outside the facility.
  • Page 98: Task 11: Assign User Names And Passwords

    4. At the Local Phone Number field, enter the telephone number for access to the local server. Include necessary information such as the country code or area code. 5. Click OK to save the configured telephone numbers and close the dialog box.
  • Page 99: Task 12: Configure The Director To The Management Application

    6. Enter information in fields as directed by the customer: • Description - Type a new user name up to 16 alphanumeric characters in length. Control characters and spaces are not valid. The user name is case-sensitive. • Email Address - Type one or more new user e-mail addresses. Separate multiple addresses with a semicolon.
  • Page 100: Task 13: Record Or Verify Server Restore Information

    6. Click OK to save the entered information and define the director to the SAN management application. Close all dialog boxes and return to the EFCM main window. Address properties dialog box (IP Address page) Figure 35 Task 13: Record or verify server restore information Windows operating system configuration information must be recorded to restore the server in case of hard drive failure (Appendix...
  • Page 101: Task 14: Verify Director-To-Server Communication

    • IP address - default is 192.168.0.1. • Subnet mask - default is 255.0.0.0. • Gateway address - default is blank. • DNS server IP address - default is blank. d. Verify the default computer name (MGMTSERVER) or changed computer name was recorded. 2.
  • Page 102: Task 15: Configure Pfe Key (Optional)

    Operational states and symbols Table 5 Operational state Status symbol Operational - Communication is established, the product is operational, No status and no failures are indicated. Go to Task 15: Configure PFE key symbol (optional) on page 70. Degraded - Communication is established, but the product is operating in degraded mode and requires service.
  • Page 103 Keys are encoded to work only with the serial number of the installed product. Record the key to re-install the feature if required. If the product fails and is replaced, obtain new PFE keys from IBM. Have the serial numbers of the failed and replacement products, and the old PFE key number or transaction code.
  • Page 104: Task 16: Configure Management Server (Optional)

    Figure 36 New feature key dialog box 3. Type the PFE key (case-sensitive xxxx-xxxx-xxxx-xx format) and click OK. The Enable Feature Key dialog box displays. 4. Verify the feature description appears in the New Features panel and click OK. A Warning dialog box displays with the message Installing this feature key causes an IPL and momentary loss of the LAN connection.
  • Page 105: Task 17: Set Director Date And Time

    Task 17: Set director date and time Log entries are stamped with the date and time received from the director. To set the effective date and time for the director: 1. Select Date/Time from the Configure menu at any view. The Configure Date and Time dialog box displays (Figure 37).
  • Page 106: Task 18: Configure The Element Manager Application

    • Second (SS): 0 through 59. d. Click Activate to set the director date and time and close the dialog box. 3. To set the director to periodically synchronize date and time with the SAN management application: a. Click the Periodic Date/Time Synchronization check box to select the option (check mark in the box).
  • Page 107: Configure Director Identification

    Configure director identification Perform this procedure to configure the director identification. The Name, Location, and Contact variables correspond respectively to the SNMP variables sysName, sysLocation, and sysContact, and are used by management workstations when obtaining director data. 1. Select Identification from the Configure menu at any view. The Configure Identification dialog box displays (Figure 38).
  • Page 108: Configure Switch Parameters Dialog Box

    2. Select Operating Parameters and Switch Parameters from the Configure menu at any view. The Configure Switch Parameters dialog box displays (Figure 39). Figure 39 Configure switch parameters dialog box a. At the Preferred Domain ID field, type a value between 1 through 31.
  • Page 109: Configure Fabric Parameters

    f. At the NPIV field, check (enable) or uncheck (disable) N_Port identifier virtualization. NPIV allows multiple (up to 256) Fibre Channel addresses to be assigned to a node (N_Port). 3. Click Activate to save the information and close the dialog box. 4.
  • Page 110 Available selections are: • McDATA Fabric 1.0 - Select this option if the director is fabric-attached only to other IBM directors or switches operating in McDATA fabric mode. • Open Fabric 1.0 - Select this option (default) for managing...
  • Page 111: Configure Ports

    Configure ports To configure Fibre Channel ports: 1. At the Hardware View, select Ports from the Configure menu. The Configure Ports dialog box displays (Figure 41). Configure ports dialog box Figure 41 a. For each port to be configured, type a port name of 24 alphanumeric characters or less in the associated Name field.
  • Page 112: Configure Snmp

    e. Select from the drop-down list in the Type column to configure the port type. Available selections are fabric port (F_Port), expansion port (E_Port), generic port (G_Port), generic mixed port (GX_Port), and fabric mixed port (FX_Port). f. Select from the drop-down list in the Speed column to configure the port transmission rate.
  • Page 113: Configure Threshold Alerts

    Configure SNMP dialog box Figure 42 a. Click Enable SNMP Agent and Enable Authentication Traps to activate the installed agent and enable transmission of SNMP trap messages to recipients. b. Select the appropriate FA MIB from the Fibre Alliance MIB Trap Version drop-down list.
  • Page 114: New Threshold Alert Dialog Box (Screen 1)

    • An attention indicator (yellow triangle) associated with a port at the Hardware View, Port List View, or Port Properties dialog box. • Data recorded in the Threshold Alert Log. To configure threshold alerts: 1. Select Threshold Alerts from the Configure menu at any view. The Configure Threshold Alert(s) dialog box displays.
  • Page 115: New Threshold Alert Dialog Box (Screen 2)

    New threshold alert dialog box (Screen 2) Figure 44 6. Type a value from 1 through 100 in the % utilization field. When throughput reaches the specified percentage of port capacity, a threshold alert occurs. 7. Enter the cumulative minutes for which the % utilization should exist during the notification interval before an alert is generated.
  • Page 116: Enable Efcm Basic Edition And Telnet Access

    12. Click Finish. The Configure Threshold Alerts dialog box reappears listing the name, type, and state of the alert configured. 13. To activate the alert, highlight (select) the alert and click Activate. Figure 45 New threshold alert dialog box (Screen 3) Enable EFCM Basic Edition and Telnet access Perform this procedure to enable EFCM Basic Edition interface and Telnet access through the maintenance port.
  • Page 117: Email Event Notification Setup Dialog Box

    2. At the EFCM main window, select Event Notification and Email from the Monitor menu. The Email Event Notification Setup dialog box displays (Figure 46). Email event notification setup dialog box Figure 46 3. To enable e-mail transmission to configured addresses, click the Enable Email Event Notification check box.
  • Page 118: Configure And Enable Ethernet Events

    12. Click OK to save the information and close the dialog box. 13. Maximize the Element Manager application. 14. Select Enable E-Mail Notification from the Maintenance menu at any view. A check mark appears to indicate e-mail notification for the product is enabled.
  • Page 119: Configure Security

    3. Click the Enable Call Home Event Notification check box. A check mark appears to indicate call-home event notification is enabled. NOTE: The enable function must be activated for each product through the Element Manager application. 4. Click Send Test. A call-home test message is sent. 5.
  • Page 120: Configure Interswitch Links

    • Enterprise Fabric Mode - Use the Enterprise Fabric Mode option from the Configure menu (SAN management application) to enable or disable EFM. Fabric binding is activated when EFM is enabled. • Fabric binding - Use the Fabric Binding from the Configure option from the Configure menu (SAN management application) to lock parameters of a fabric in accordance with the user configuration.
  • Page 121: Task 19: Back Up Configuration Data

    To configure optional features, refer to the EFC Manager Software Release 9.0 User Manual (620-000170) for instructions. If no additional options or features are to be configured, go to Task 19: Back up configuration data following. Task 19: Back up configuration data For the EFCM application, critical configuration data is stored on the management server hard drive in the following directories: •...
  • Page 122: Incd Icon (Unformatted Cd)

    InCD icon (unformatted CD) Figure 47 2. Back up the director configuration file to the server (Managing configuration data on page 202). 3. Close the Element Manager application and return to the SAN management application. 4. Close the SAN management application by selecting Shutdown from the SAN menu.
  • Page 123: Task 20: Cable Fibre Channel Ports

    f. Type the default Windows user name and password and click OK. The server Windows desktop opens and the EFCM Log In dialog box displays. NOTE: The default Windows user name is Administrator and the default password is password. Both are case-sensitive. g.
  • Page 124: Task 21: Configure Zoning (Optional)

    Task 21: Configure Zoning (Optional) Perform this procedure to configure, change, add, or delete zones; and to configure, change, enable, or disable zone sets. • Zone - A zone is a group of devices that can access each other through port-to-port connections. Devices in the same zone can recognize and communicate with each other;...
  • Page 125 1. Ensure the fabric element is defined to the SAN management application or accessible by the EFCM Basic Edition interface. If the fabric element must be defined, refer to the appropriate switch or director installation manual for instructions. 2. Ensure the preferred domain ID for the director is unique and does not conflict with the ID of another switch or director participating in the fabric.
  • Page 126 c. Ensure the Operational State field displays Online and the Reason field displays N/A or is blank. If an ISL segmentation or other problem is indicated, go to Chapter 3, Maintenance analysis procedures (MAPS) to isolate the problem. If no problems are indicated, installation tasks are complete.
  • Page 127: Factory Defaults

    Quick start Table 7 lists and summarizes MAPs. Fault isolation normally begins MAP 0000: Start MAP. MAP summary Table 7 Page MAP 0000: Start MAP MAP 0100: Power distribution analysis MAP 0200: POST failure analysis © Copyright IBM Corp. 2006...
  • Page 128: Event Codes Versus Maintenance Action

    Table 7 MAP summary (Continued) Page MAP 0300: Loss of server communication MAP 0400: FRU failure analysis MAP 0500: Port failure or link incident analysis MAP 0600: Fabric or ISL problem analysis Table 8 lists event codes, corresponding MAP references, and provides a quick start guide if an event code is readily available.
  • Page 129 Event codes versus maintenance action (Continued) Table 8 Event code Explanation Action Switch is isolated. Go to 0600. E_Port connected to unsupported switch. Go to 0600. Fabric initialization error. Go to Collecting maintenance data on page 4–186 Collecting maintenance data on page 4–186 ILS frame delivery error threshold exceeded.
  • Page 130 Table 8 Event codes versus maintenance action (Continued) Event code Explanation Action Power supply installed. No action required. Power supply false shutdown. Go to 0100. Cooling fan propeller failed. Go to 0400. Cooling fan propeller failed. Go to 0400. Cooling fan propeller failed. Go to 0400.
  • Page 131 Event codes versus maintenance action (Continued) Table 8 Event code Explanation Action CTP card firmware synchronization initiated. No action required. User-initiated CTP card switchover. No action required. Backup CTP card NV-RAM failure. Go to 0400. Firmware download complete. No action required. CTP firmware synchronization complete.
  • Page 132 Table 8 Event codes versus maintenance action (Continued) Event code Explanation Action Fibre Channel port failure. Go to 0500. Loopback diagnostics port failure. Go to 0500. Fibre Channel port anomaly detected. No action required. Optical transceiver hot-insertion initiated. No action required. Optical transceiver nonfatal error.
  • Page 133 Event codes versus maintenance action (Continued) Table 8 Event code Explanation Action User initiated SBAR switch-over. No action required. SBAR fan failure. Go to 0400. Failed SBAR fan recovered. No action required. High temperature warning (port module thermal sensor). Go to 0400.
  • Page 134: Map 0000: Start Map

    MAP 0000: Start MAP This MAP describes initial fault isolation beginning at the: • Director. • Browser-capable PC with Internet connectivity to the firmware- resident Enterprise Fabric Connectivity Manager (EFCM) Basic Edition interface. • Management server running storage area network (SAN) management and Element Manager applications.
  • Page 135 ↓ A FRU failure, power-on self-test (POST) failure, link incident, interswitch link (ISL) problem, fenced E_Port, or segmented E_Port is indicated. To obtain event codes that identify the failure, go to step Is the product management interface (browser PC, management server, or OSI host console) powered on and operational? ↓...
  • Page 136 Perform a data collection and contact the next level of support (Collecting maintenance data on page 186). Exit MAP. Inspect product status at the management interface: a. For the product reporting the problem: — EFCM Basic Edition - Select Hardware from the Product menu at any view.
  • Page 137 b. If a link incident occurred, the 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. —...
  • Page 138 b. Record the event code and associated date, time, and severity (Informational, Minor, Major, or Severe). c. If multiple event codes are found, record all codes and severity levels. Record the date, time, and sequence, and determine if all codes are related to the reported problem. Begin fault isolation with the most recent event code with the highest severity level.
  • Page 139: Map 0100: Power Distribution Analysis

    MAP 0100: Power distribution analysis This MAP describes fault isolation for the product power distribution system, including defective AC power cords or power supplies. The failure indicator is: • Failure of the product to power on. • Event codes observed at the Event Log (EFCM Basic Edition or Element Manager interface).
  • Page 140 As indicated by visual inspection or an event code, one or more power supplies failed and must be replaced (RRP: Power supply page 229). • The procedure is concurrent and performed while the product is operational. • Perform a data collection as part of FRU removal and replacement.
  • Page 141 c. Ensure AC power cords are not damaged. If damaged, replace the cords. Was the maintenance action successful? ↓ The product is operational. Exit MAP. Verify power supply operation. a. Inspect each power supply to determine if the amber failure LED is lit.
  • Page 142: Map 0200: Post Failure Analysis

    MAP 0200: POST failure analysis This MAP describes fault isolation for power-on self-test (POST) failure. The failure indicator are event codes observed at the Event Log (EFCM Basic Edition or Element Manager interface). Table 10 lists event codes, explanations, and MAP steps. MAP 200 event codes Table 10 Event...
  • Page 143 The backplane failed POSTs (indicated by a FRU code 01) and must be replaced (RRP: Backplane on page 244). • 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.
  • Page 144 ↓ The director appears operational. Exit MAP. Contact the next level of support. Exit MAP. A fan module failed POSTs (indicated by a FRU code 05) and must be replaced (RRP: Fan module on page 235). • This procedure is concurrent and can be performed while director power is on.
  • Page 145 A port card failed POSTs (indicated by FRU codes 08 through 0F) and must be replaced (RRP: Port module card (UPM and XPM) page 218). • 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.
  • Page 146: Map 0300: Loss Of Server Communication

    MAP 0300: Loss of server communication This MAP describes fault isolation for the product to browser PC Internet connection (EFCM Basic Edition interface) or the product to management server LAN connection. The failure indicator is: • A Page cannot be found, Unable to locate the server, HTTP 404 - file not found, or similar message (browser PC).
  • Page 147 ↓ A power distribution problem is indicated. Go to MAP 0100: Power distribution analysis. Exit MAP. A product-to-PC link problem (Internet too busy or IP address typed incorrectly) or an Ethernet port failure is indicated. a. Wait approximately five minutes, then attempt to login to the product.
  • Page 148: Map 300 Error Messages

    • Audio emanations and airflow from fans. Is the product powered on? ↓ A power distribution problem is indicated. Go to MAP 0100: Power distribution analysis. Exit MAP. At the SAN management application’s physical map, right-click the status icon for the product reporting the problem and select Element Manager from the pop-up menu.
  • Page 149: Daisy-Chained Ethernet Hubs

    c. Ensure Ethernet cables are not damaged. If damaged, replace the cables. Was the maintenance action successful? ↓ The management server connection is restored. Exit MAP. Does the configuration use multiple daisy-chained Ethernet hubs? ↓ Go to step Verify hubs are correctly daisy-chained. a.
  • Page 150 Was the maintenance action successful? ↓ The management server connection is restored. Exit MAP. Verify operation of Ethernet hubs. Inspect each hub for indications of being powered on, such as: • Green Power LED lit. • Green Status LEDs lit. Is a failure indicated? ↓...
  • Page 151 A protocol mismatch occurred because the SAN management application and the product firmware are not at compatible release levels. Recommend to the customer the downlevel version (software or firmware) be upgraded. Does the SAN management application require upgrade? ↓ Go to step Upgrade the SAN management application (Install or upgrade...
  • Page 152 Determine the IP address of the management server running the first instance of the SAN management application. a. After the server powers on and successfully completes POSTs, the LCD panel displays a Welcome!! message and continuously cycles through and displays operational information. b.
  • Page 153 a. Using a Phillips screwdriver, remove the protective cap from the 9-pin maintenance port. Connect one end of the RS-232 modem cable to the port. b. Connect the other cable end to a 9-pin serial communication port (COM1 or COM2) at the rear of the maintenance terminal PC. c.
  • Page 154 m. Power off the maintenance terminal and disconnect the modem cable. Replace the protective cap over the maintenance port. Continue. Define the product IP address (determined in step 21) to the management server. a. At the SAN management application, select Setup from the Discover menu.
  • Page 155 f. Type the product subnet mask (determined by the network administrator) in the Subnet Mask field. g. Click the Product Type and Access tab. Select Switch from the Product Type drop-down list and type customer-specified values in the User ID, Password, and Retype Password fields. h.
  • Page 156: Map 0400: Fru Failure Analysis

    MAP 0400: FRU failure analysis This MAP describes fault isolation for product FRUs. The failure indicator is: • Illumination of the associated amber LED. • Event codes observed at the Event Log (EFCM Basic Edition or Element Manager interface). Table 13 lists event codes, explanations, and MAP steps.
  • Page 157 MAP 400: Event codes (Continued) Table 13 Event Explanation Action code Critically hot temperature warning (SBAR assembly Go to step thermal sensor). SBAR assembly shutdown due to thermal violation. Go to step High temperature warning (CTP card thermal sensor). Go to step Critically hot temperature warning (CTP card thermal Go to...
  • Page 158 ↓ Contact the next level of support. Exit MAP. The product is operational. Exit MAP. An intermittent synchronous dynamic random access memory (SDRAM) problem may indicate a CTP card failure. Is the event code a recurring problem? ↓ A CTP card failure is indicated. Go to step Perform a data collection (Collecting maintenance data...
  • Page 159 An SBAR assembly is not recognized by director firmware because the firmware version is not supported or the SBAR assembly failed. Advise the customer of the problem and determine the correct firmware version to download. Download the firmware (Download and install firmware on page 195).
  • Page 160: Map 0500: Port Failure Or Link Incident Analysis

    MAP 0500: Port failure or link incident analysis This MAP describes fault isolation for the SFP or XFP optical transceivers and Fibre Channel link incidents. The failure indicator is: • Event codes observed at the Event Log (EFCM Basic Edition or Element Manager interface).
  • Page 161: Link Incident Messages

    MAP 500: Event codes (Continued) Table 14 Event Explanation Action code High temperature warning (port card thermal sensor). Go to step Critically hot temperature warning (port card thermal Go to step sensor). Port card shutdown due to thermal violation. Go to step Table 15 lists link incident messages and MAP steps.
  • Page 162: Invalid Attachment Reasons And Actions

    Incompatible switch. Go to step Loopback plug connected. Go to step N-Port connection not allowed. Go to step Non-IBM switch at other end. Go to step E_Port capability disabled. Go to step Unauthorized port binding WWN. Go to step Unresponsive node.
  • Page 163 Fabric 1.0 mode. • The product is configured to operate in Open Fabric 1.0 mode and is connected to a legacy IBM switch at the incorrect exchange link parameter (ELP) revision level. • The product is configured to operate in Open Fabric 1.0 mode and is connected to a non-IBM switch at the incorrect ELP revision level.
  • Page 164 Select McDATA Fabric 1.0 or Open Fabric 1.0 from the Interop Mode drop-down list. — Select McDATA Fabric 1.0 if the product is attached only to other IBM directors or switches operating in McDATA Fabric 1.0 mode. — Select Open Fabric 1.0 if the product is attached to directors or switches produced by open-fabric compliant original equipment manufacturers (OEMs).
  • Page 165 Contact the next level of support. Exit MAP. An ISL connection is not allowed because E_Port capability is disabled. Install the full-fabric PFE key to enable E_port capability (Task 15: Configure PFE key (optional) on page 70 and Install PFE keys (optional) on page 47).
  • Page 166 • EFCM Basic Edition - Refer to the EFCM Basic Edition User Manual (620-000240) for instructions. • Element Manager - Refer to the Element Manager User Manual (620-000153). Was the maintenance action successful? ↓ The product port is operational. Exit MAP. Contact the next level of support.
  • Page 167: Inactive Port Reasons And Actions

    ↓ The product port is operational. Exit MAP. Contact the next level of support. Exit MAP. A port is set to an inactive state. a. At the Event Log, examine the first two bytes of event data. b. Byte 0 specifies the port reporting the problem. Byte 1 specifies the inactive reason (Table 17).
  • Page 168 b. If necessary, use the vertical scroll bar to display the information row for the inactive port. c. Select (click) the Speed field and configure the port. d. Click OK or Activate. Was the maintenance action successful? ↓ The product port is operational. Exit MAP. Contact the next level of support.
  • Page 169: Upm (Or Xpm) Card Diagram (Front)

    b. At the Element Manager: 1. At the Hardware View, right-click the port. A pop-up menu appears. 2. Select Reset Port. The message This operation will cause a link reset to be sent to the attached device displays. 3. Click OK. The port resets. c.
  • Page 170: Upm (Or Xpm) Card Diagram (Rear)

    UPM Cards UPM Cards SBAR - 1 Module SBAR - 0 Module UPM (or XPM) card diagram (rear) Figure 50 • Replace the transceiver with a transceiver of the same type (shortwave or longwave) and speed. • Perform an external loopback test (Performing loopback tests page 175).
  • Page 171 (See Performing loopback tests on page 175). • Perform the data collection procedure as part of FRU removal and replacement (Collecting maintenance data on page 186). Did port card replacement solve the problem? ↓ The director appears operational. Exit MAP. Contact the next level of support.
  • Page 172 ↓ The product port is operational. Exit MAP. Disconnect the fiber-optic jumper cable from the port and connect the cable to a spare port. Is a link incident reported at the new port? ↓ The port reporting the problem is causing the link incident. This indicates port degradation and a possible pending failure.
  • Page 173: Map 0600: Fabric Or Isl Problem Analysis

    MAP 0600: Fabric or ISL problem analysis This MAP describes fault isolation for fabric, interswitch link (ISL), fenced E_Port, and segmented E_Port problems. The failure indicator is an event code observed at the Event Log (EFCM Basic Edition or Element Manager interface). Table 18 lists event codes, explanations, and MAP steps.
  • Page 174 A minor error occurred that caused the Fabric Services database to be re-initialized to an empty state, and a disruptive fabric logout and login occurred for all attached devices. Indications are: • Event code 011 - The Login Server database failed cyclic redundancy check (CRC) validation.
  • Page 175: E_Port Segmentation Reasons And Actions

    Fabric Controller software detected: • A fabric element with more than 32 ISLs (SAN management application Version 3.2 or earlier). • A fabric element with more than 128 ISLs (SAN management application Version 3.3 or later). Fibre Channel frames may be lost or directed in loops because of potential fabric routing problems.
  • Page 176 E_Port segmentation reasons and actions (Continued) Table 19 Byte 4 Segmentation reason Action Build fabric protocol error. Go to step No principal switch. Go to step No response from attached switch (hello timeout). Go to step An 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.
  • Page 177 Was the maintenance action successful? ↓ The fabric, ISL, and product are operational. Exit MAP. Contact the next level of support. Exit MAP. An E_Port segmented because two fabric elements had duplicate domain IDs. a. Determine the desired domain ID (1 through 31 inclusive) for each product.
  • Page 178 An E_Port segmented because two products had incompatible zoning configurations. An identical zone name is recognized in the active zone set for both products, but the zones contain different members. a. Determine the desired zone name change for one of the affected products.
  • Page 179 Reset the product (IML, IPL, or reset the director on page 4–192). Was the maintenance action successful? ↓ The fabric, ISL, and product are operational. Exit MAP. Perform a data collection and contact the next level of support. Exit MAP. An E_Port segmented because no product in the fabric is capable of becoming the principal switch.
  • Page 180: Port Fence Codes And Actions

    Was the maintenance action successful? ↓ The fabric, ISL, and product are operational. Exit MAP. Contact the next level of support. Exit MAP. An E_Port segmented (operational product) because a response (hello timeout) to a verification check indicates an attached switch is not operational.
  • Page 181 An E_Port is fenced because of a protocol error. Depending on failure cause, additional information and event codes are available at the product or attached switch. Perform one of the following: • The E_Port is segmented and accompanied by primary event code 070.
  • Page 182 — SAN management application - Refer to the EFC Manager Software Release 9.0 User Manual (620-000170) for instructions. — Element Manager - Refer to the Element Manager User Manual (620-000153) for instructions. b. Unblock the port (Blocking and unblocking ports on page 4–181).
  • Page 183: Fabric Merge Failure Reasons And Actions

    No action is required for an isolated event or if the reporting ISL approaches 100% throughput. If the event persists, perform one of the following: • Relieve the congestion by adding parallel ISLs between the fabric elements reporting the problem. •...
  • Page 184 Table 21 Fabric merge failure reasons and actions (Continued) Bytes 8 - 11 Merge failure reason Action Retry limit reached. Go to step Invalid response length. Go to step Invalid response code. Go to step A zone merge process failed during ISL initialization. The following list explains the reason: •...
  • Page 185 Obtain supplementary error code data for event code 150. At the Event Log, examine bytes 12 through 15 of event data that specify the error code. Record the error code. Perform a data collection and send the CD to support personnel for analysis.
  • Page 186 SAN140M Installation and Service Manual...
  • Page 187: Repair Information

    Setting the director online or offline. • Performing an initial machine load (IML), initial program load (IPL), or director reset. • Cleaning fiber-optic components. • Downloading director firmware and software. • Installing or upgrading software. • Managing configuration data. © Copyright IBM Corp. 2006...
  • Page 188: Factory Defaults

    Factory defaults Table 22 lists the defaults for the passwords, and IP, subnet, and gateway addresses. Factory-set defaults Table 22 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 the following: 1.
  • Page 189: Obtaining Log Information

    Obtaining log information The SAN management application, Element Manager application, and EFCM Basic Edition interface provide access to logs with information for administration, operation, and maintenance personnel. • Logs accessed through the SAN management application (EFCM). Fabric-log information: — Event log. —...
  • Page 190 Event log The Event Log records simple network management protocol (SNMP) trap events, client-server communication errors, and other problems recorded by the SAN management application. Information provided is generally intended for use by third-level support personnel to fault isolate significant problems. The log describes: •...
  • Page 191: Element Manager Logs

    • Previous Status - The status of the director prior to the reported status change (Operational, Degraded, Failed, OutofBand Online, or Unknown). An Unknown status indicates the SAN management application cannot communicate with the director. • New Status - The status of the director after the reported status change (Operational, Degraded, Failed, OutofBand Online, or Unknown).
  • Page 192 • 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. Link incident log The Link Incident Log records Fibre Channel link incident events and causes.
  • Page 193 • Interval - The time interval during which the throughput is measured and an alert can generate. This is set through the Configure Threshold Alerts dialog box. Open trunking log The Open Trunking Log records ISL congestion events that cause Fibre Channel traffic to be routed through an alternate ISL.
  • Page 194: Efcm Basic Edition Logs

    NOTE: Identical entries are recorded in the wrapping and non-wrapping logs. When the non-wrapping log fills, old records are overwritten. The wrapping log preserves all records. Switch fabric log The Switch Fabric Log records the time and nature of changes made to a multiswitch fabric that affect this product.
  • Page 195 Link incident log The Link Incident Log records Fibre Channel link incident events and causes. The log describes: • Date/Time - The date and time the link incident occurred. • Port - The port number that reported the link incident. •...
  • Page 196 Fabric log The Fabric Log records the time and nature of changes made to a multiswitch fabric. The information is useful for isolating zoning or fabric-wide problems. The log describes: • Count - The cumulative count of log entries (wrapping or non-wrapping).
  • Page 197: Obtaining Port Diagnostic Information

    Obtaining port diagnostic information Fibre Channel port diagnostic information can be obtained by: • Inspecting port LEDs at the port card faceplates or emulated port LEDs at the Element Manager Hardware View. • Inspecting parameters at the Element Manager application. •...
  • Page 198: Element Manager Application Diagnostics

    Table 23 Port operational states (Continued) Port Green Amber Alert Description State symbol No Light None No signal (light) is received by the director port. This is a normal condition when there is no cable attached to the port or when the attached device is powered off. The port is inactive.
  • Page 199: Port List View

    Port list view To open the Port List View, click the Port List tab at any view (Figure 51). A row of information for each port appears. Port list view Figure 51 The view provides the following information: • Port # - The director port number. •...
  • Page 200 indicator on each bar graph (high-water mark) remains at the highest level reached since the port was set online. In addition, the following statistical information appears: • Class 2 Statistics - These statistics include the number of 4-byte words transmitted and received, and the number of Class 2 frames transmitted, received, busied, or rejected.
  • Page 201: Port Properties Dialog Box

    Port properties To open the Port Properties dialog box (Figure 52), double-click a port dialog box graphic at the Hardware View or a port row at the Port List View. Port properties dialog box Figure 52 The dialog box provides the following information: NOTE: If the Open Trunking feature is installed, an additional item, Congested Threshold %, appears in the Port Properties dialog box.
  • Page 202 • Operating Speed - The operating speed of the port (Not Established, 1 Gbps, 2 Gbps, or 10 Gbps (with XPM)). • Fibre Channel Address - The logical port address (hexadecimal format). Not applicable for E_Ports. • Port WWN - The Fibre Channel WWN of the port. •...
  • Page 203: Port Technology Dialog Box

    • Reason - A summary appears describing the reason if the port state is Segmented E_Port, Invalid Attachment, or Inactive. For any other port state, the reason field is blank or N/A. • Threshold Alert- If a threshold alert exists for the port, an alert indicator (yellow triangle) and the configured name for the alert appear.
  • Page 204: Efcm Basic Edition Diagnostics

    EFCM Basic Edition diagnostics The EFCM Basic Edition interface provides access to port diagnostic information, as well. Port list view To open the Port List View, select Port List from the Product menu at any view. As an example, the figure shows POM data in the lower panel (Figure 54).
  • Page 205 • Transceiver - Installed transceiver type (SFP or Unknown). Inspect port properties At the Port List View, click a physical port number listed in the Port column. Physical properties for the selected port appear in the lower panel of the view: •...
  • Page 206 • Transceiver Type - The installed transceiver type (SFP or Unknown). If the port has a digital diagnostics (DD) enabled optical transceiver installed, product firmware displays a table of reported temperature, voltage, current, transceiver power, and receiver power. Optical transceivers also provide vendor-specific threshold values for these parameters.
  • Page 207: Performing Loopback Tests

    • Class 2 Statistics - These statistics include the number of 4-byte words transmitted and received, and the number of Class 2 frames transmitted, received, busied, or rejected. • Class 3 Statistics - These statistics include the number of 4-byte words transmitted and received, and the number of Class 3 frames transmitted, received, or discarded.
  • Page 208: Port Diagnostics Dialog Box

    2. At the Element Manager application, select Port Diagnostics from the Maintenance menu. The Port Diagnostics dialog box displays (Figure 55). 3. Type the port number to be tested or select all ports at the Port Select area of the dialog box. 4.
  • Page 209: External Loopback Test (Element Manager Application)

    c. Click OK. The port resets. 10. Notify the customer that the test is complete and the attached device can be set online. External loopback test (Element Manager application) To perform an external loopback at the Element Manager application: 1. Notify the customer that a disruptive external loopback test will be performed and the attached device must be disconnected.
  • Page 210: Internal Loopback Test (Efcm Basic Edition)

    13. Reset the port: a. At the Hardware View, right-click the port graphic. A pop-up menu appears. b. Select Reset Port. A message box displays, indicating a link reset will occur. c. Click OK. The port resets. 14. Notify the customer the test is complete and the device can be reconnected to the switch and set online.
  • Page 211: Diagnostics View

    Diagnostics view Figure 56 3. Type the port number to be tested in the Targeted Port Number field. 4. At the Diagnostic Test list box, select the Internal Loopback option. 5. Click Start. The test begins and: a. The Diagnostics View changes to a Diagnostics - Executing View. b.
  • Page 212: External Loopback Test (Efcm Basic Edition)

    c. Click OK at the bottom of the page. The port resets and the message Your changes have been successfully activated. appears. 8. Notify the customer that the test is complete and the attached device can be set online. External loopback test (EFCM Basic Edition) To perform an external loopback at the EFCM Basic Edition interface: 1.
  • Page 213: Blocking And Unblocking Ports

    b. For the tested port, click the check box in the Reset column. A check mark in the box indicates the port reset option is enabled. c. Click OK at the bottom of the page. The port resets and the message Your changes have been successfully activated.
  • Page 214: Block Or Unblock A Port (Efcm Basic Edition)

    • A check mark appears adjacent to the Block Port or Block All Ports menu option. — To unblock a port or port card: Select the Block Port or Block All Ports menu option. Note the check mark in the box adjacent to the menu item, indicating the port or port card is blocked.
  • Page 215: Swapping Ports

    2. Perform one of the following: — Click the check box for the selected port in the Blocked column to block the port or ports. A check mark in the box indicates the port is blocked. — Click the check box for the selected port in the Blocked column to remove the check mark and unblock the port or ports.
  • Page 216: Swap Ports Dialog Box

    Swap ports dialog box Figure 58 2. Select the radio button associated with the product management style and enter the decimal port numbers (open systems style) or hexadecimal port addresses (FICON style) of the ports to be swapped. The FC Address fields update dynamically. 3.
  • Page 217: Performing Channel Wrap Tests (Ficon)

    Performing channel wrap tests (FICON) A channel wrap test is a diagnostic procedure that checks host-to-director FICON 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.
  • Page 218: Collecting Maintenance Data

    Collecting maintenance data When director operational firmware detects a critical error or FRU failure, the director automatically copies the contents of dynamic random access memory (DRAM) to a dump area in FLASH memory on the active CTP card, then initiates a failover to the operational FRU.
  • Page 219: Collecting Maintenance Data (Efcm Basic Edition)

    2. Remove the backup CD from the management server compact disk-rewritable (CD-RW) drive and insert a blank rewritable CD. 3. At the Save Data Collection dialog box, select the compact disc drive (D:\) from the Look in drop-down menu, type a descriptive name for the collected maintenance data in the File name field, then click Save.
  • Page 220: Powering The Director On Or Off

    3. Insert a blank diskette in the floppy drive of the PC communicating with the EFCM Basic Edition interface. 4. At the Save As dialog box, select the floppy drive (A:\) from the Save in drop-down menu, type a descriptive name for the zipped (.zip) dump file in the File name field, and click Save.
  • Page 221: Power-Off Procedure

    NOTE: The director does not have a power switch. Therefore the director powers on when its power cords are connected to facility power. 2. The director powers on and performs power-on self-tests (POSTs). During POSTs: — Amber LEDs on both CTP cards and all port cards illuminate momentarily.
  • Page 222: Setting The Director Online Or Offline

    3. Remove the director power cords from facility power. The director powers off. 4. If servicing the director, disconnect power cord(s) from the input AC module at the bottom rear of the director. This step is not required when performing a power cycle. Setting the director online or offline This section describes procedures to set the director online or offline.
  • Page 223: Set Online Or Offline (Efcm Basic Edition)

    Set online or offline (EFCM Basic Edition) To set the director online or offline from the EFCM Basic Edition interface: 1. At the EFCM Basic Edition interface, select Switch from the Maintenance menu at any view. The Switch View displays (Figure 61).
  • Page 224: Iml, Ipl, Or Reset The Director

    IML, IPL, or reset the director An IML or reset is performed at the CTP front panel using the IML or the RESET button. An IPL is performed through the Element Manager application. The EFCM Basic Edition interface does not provide an IML, IPL, or director reset function.
  • Page 225: Ipl The Director (Element Manager Application)

    — The icon representing unknown status displays in the status area (SAN management application). — Illustrated FRUs disappear, and appear again as the connection is re-established. IPL the director (Element Manager application) To IPL the director from the Element Manager application: 1.
  • Page 226: Cleaning Fiber-Optic Components

    — The director-to-management server Ethernet link drops momentarily and the following occur at the Hardware View: • As the network connection drops, the Status table turns yellow, the Status field displays No Link, and the State field displays Link Timeout. •...
  • Page 227: Download And Install Firmware

    The firmware version shipped with the product is provided on the System Version XX.YY.ZZ CD-ROM. Subsequent (upgrade) firmware versions are provided to customers through IBM. NOTE: When upgrading firmware or software, follow all procedural information contained in release notes or engineering change (EC) instructions that accompany the version.
  • Page 228: Download And Install Firmware To Director (Element Manager Application)

    Download and install firmware to director (Element Manager application) To download a firmware version to the director from the Element Manager application: NOTE: When downloading a firmware version, follow all procedural information contained in release notes or EC instructions that accompany the firmware version.
  • Page 229 7. The new firmware version and associated description appear in the Firmware Library dialog box. 8. Select the firmware version to be downloaded and click Send. The send function verifies existence of certain director conditions before the download begins. If an error occurs, a message displays indicating the problem must be fixed before firmware is downloaded.
  • Page 230: Download And Install Firmware To Director (Efcm Basic Edition)

    Download and install firmware to director (EFCM Basic Edition) To download a firmware version to the director from the EFCM Basic Edition interface: NOTE: When downloading a firmware version, follow all procedural information contained in release notes or EC instructions that accompany the firmware version.
  • Page 231: Install Or Upgrade Software

    The SAN management application (software) shipped with the product is provided on the EFC Management Applications CD-ROM. Subsequent (upgrade) software versions are provided to customers through IBM. NOTE: When upgrading firmware or software, follow all procedural information contained in release notes or engineering change (EC) instructions that accompany the version.
  • Page 232: Installshield Wizard Dialog Box

    — Ensure the desired software version is resident on the server hard drive. Refer to Download and install firmware on page 195 for instructions. 2. At the server’s Windows desktop, click Start at the left side of the task bar, then select the Run option. The Run dialog box displays. 3.
  • Page 233 b. Select the Restart option from the list box and click OK. The server powers down and restarts. During the reboot process the LAN connection between the server and browser-capable PC drops momentarily, and the TightVNC viewer displays a network error. c.
  • Page 234: Managing Configuration Data

    Managing configuration data The Element Manager and the EFCM Basic Edition applications provide options to: • Back up and restore the configuration file stored in NV-RAM on the CTP cards. • Reset the configuration file to factory defaults. ATTENTION! The director must be set offline prior to restoring or resetting the configuration file.
  • Page 235: Reset Configuration Data (Element Manager Application)

    5. Click Yes. A Restore dialog box displays, indicating the restore is in progress. 6. When the operation finishes, the Restore dialog box displays a Restore complete message. Click Close to close the dialog box. Reset configuration data (Element Manager application) When configuration data is reset to factory defaults, the director defaults to the factory-set IP address and all optional features are disabled.
  • Page 236: Address Properties Dialog Box

    b. The icon representing unknown status appears adjacent to the icon representing the reset director, indicating that the director is not communicating with the management server. c. At the SAN management application, select Setup from the Discover menu. The Discover Setup dialog box displays. d.
  • Page 237: Back Up Configuration (Efcm Basic Edition)

    d. At the Discover Setup dialog box, click OK. The director is no longer defined to the management server. e. Change a director IP address through the maintenance port (Task 5: Configure director network information (optional) page 51). f. Identify the switch to the SAN management application (Task 12: Configure the director to the management application page 67).
  • Page 238: Restore Configuration (Efcm Basic Edition)

    Restore configuration (EFCM Basic Edition) To restore the director configuration file from the PC communicating with the EFCM Basic Edition interface: 1. Notify the customer that the director will be set offline. Ensure the system administrator quiesces Fibre Channel traffic through the director and sets attached devices offline.
  • Page 239 1. Notify the customer that the director will be set offline. Ensure that the system administrator quiesces Fibre Channel traffic through the director and sets attached devices offline. 2. Set the director offline (Setting the director online or offline page 190). 3.
  • Page 240 SAN140M Installation and Service Manual...
  • Page 241: Chapter 5 Removal And Replacement Procedures (Rrps)

    CAUTION statements, and statements listed in the preface of this manual. 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. © Copyright IBM Corp. 2006...
  • Page 242: Removing And Replacing Frus

    4. After completing a replacement procedure, clear the event code reporting the failure and the event code reporting the recovery from the Event Log (at the management server or EFCM Basic Edition interface), and turn off the amber system error light- emitting diode (LED) at the director front bezel.
  • Page 243: Esd Grounding Points

    ESD grounding points Figure 69 Location Description ESD grounding points Chapter 5: Removal and replacement procedures (RRPs)
  • Page 244: Concurrent Frus

    Concurrent FRUs Table 25 lists the concurrent FRUs. Concurrent FRUs are removed and replaced while the director is powered on and operational. The table also lists ESD precautions (yes or no) for each FRU, and references the page number of the removal and replacement procedure.
  • Page 245: Rrp: Ctp Card

    RRP: CTP card Use the following procedures to remove or replace a CTP card (two cards in the director) with the backup CTP card operational. A list of tools required is provided. ATTENTION! Do not remove and replace a CTP card if the backup CTP card is not fully operational and director power is on.
  • Page 246 Do not use an Allen wrench or torque tool designed for use with another IBM product. Use of the wrong tool may overtighten and damage logic cards.
  • Page 247: Ctp Card Removal And Replacement

    CTP card removal and replacement Figure 70 Location Description CTP card Replacement To replace a CTP card: 1. Wait approximately 20 seconds after removal of the failed CTP card to begin this replacement procedure. 2. Remove the replacement card from its protective anti-static bag. 3.
  • Page 248 CTP card, the card may be unusable due to partially-loaded firmware. — If after ten minutes the replacement CTP card does not appear to be operational, perform the data collection procedure and return the failed replacement card to IBM (Collecting maintenance data on page 186).
  • Page 249 12. At the management server or at a web browser connected to the EFCM Basic Edition interface, inspect the Event Log. Ensure the following event codes appear in the log: — 410 - CTP card reset. — 416 - Backup CTP installed. —...
  • Page 250: Rrp: Port Module Card (Upm And Xpm)

    b. Click the Sys Err Light tab. The Switch page displays with the Sys Err Light tab selected. A System Error Light is ON message displays on the page. c. Click Clear Light. 17. If necessary, close and lock the equipment cabinet door. RRP: Port module card (UPM and XPM) Use the following procedures to remove or replace a UPMor XPM (port) card.
  • Page 251 ATTENTION! To avoid causing machine errors or damage while working on the director, follow ESD procedures by connecting a grounding cable to the director chassis and wearing an ESD wrist strap. 4. Follow ESD procedures by attaching a wrist strap to the director chassis and your wrist (Figure 69).
  • Page 252: Upm (Shown) Or Xpm Card Removal And Replacement

    Do not use an Allen wrench or torque tool designed for use with another IBM product. Use of the wrong tool may overtighten and damage logic cards.
  • Page 253 Replacement To replace a port card: NOTE: The spring-loaded (lock) Allen screws are colored yellow and are mounted near yellow "lock" symbols on the frame. 1. Remove the replacement card from its protective anti-static bag. 2. Hold the card by its stiffener. Orient the card so that the locking Allen screw (yellow) on the card aligns with the yellow "lock"...
  • Page 254 9. Disconnect the ESD wrist strap from the director chassis and your wrist. 10. Inspect the port card to ensure all amber LEDs are turned off. If any amber LEDs are lit, go to Chapter 3, Maintenance analysis procedures (MAPS) to isolate the problem.
  • Page 255: Rrp: Optical Transceiver (Sfp And Xfp)

    a. Click the Switch tab at the Operations panel. The Operations panel opens with the Switch page displayed. b. Click the Sys Err Light tab. The Switch page displays with the Sys Err Light tab selected. A System Error Light is ON message displays on the page.
  • Page 256 4. Identify the defective port transceiver from the amber LED on the port card or failure information at the management server Port Card View. 5. Block communication to the port (Blocking and unblocking ports page 181). 6. Follow ESD procedures by attaching a wrist strap to the director chassis and your wrist (Figure 69).
  • Page 257: Sfp (Shown) Or Xfp Optical Transceiver Removal And Replacement

    SFP (shown) or XFP optical transceiver removal and replacement Figure 72 Location Description SFP (shown) or XFP optical transceiver Replacement To replace an optical transceiver: 1. Remove the transceiver from its packaging. 2. Insert the transceiver into the port receptacle (Figure 72).
  • Page 258 b. Clean the cable and port connectors (IML, IPL, or reset the director on page 192). c. Insert the keyed LC cable connector into port optical transceiver. 5. Disconnect the ESD wrist strap from the director chassis and your wrist. 6.
  • Page 259: Rrp: Filler Panel (Upm And Xpm)

    b. Click the Clear System Error Light menu selection. — If at a web browser connected to the EFCM Basic Edition interface: a. Click the Switch tab at the Operations panel. The Operations panel opens with the Switch page displayed. b.
  • Page 260: Upm Or Xpm Filler Panel Removal And Replacement

    5. Insert the torque tool into each locking Allen screw (Figure 73). Turn each screw counter-clockwise until the spring releases and the tool turns freely. 6. Pull the filler panel out and remove it from the director chassis. UPM or XPM filler panel removal and replacement Figure 73 Location Description...
  • Page 261: Rrp: Power Supply

    6. If necessary, close and lock the equipment cabinet door. RRP: Power supply Use the following procedures to remove or replace a power supply. A list of tools required is provided. Tools required The following tools are required to perform these procedures. •...
  • Page 262: Power Supply Removal And Replacement

    Power supply removal and replacement Figure 74 Location Description Power supply AC module 5. Pull the power supply from the director AC module (Figure 74). Support the power supply with one hand. 6. Place the power supply in an anti-static bag to provide ESD protection.
  • Page 263 3. Insert the power supply into the chassis guide of the AC module, then push the power supply toward the backplane to engage the connector pins. 4. Disconnect the ESD wrist strap from the director chassis and your wrist. 5. Inspect the power supply to ensure the green PWR OK LED is lit and all amber LEDs are turned off.
  • Page 264: Rrp: Ac Module

    b. Click the Sys Err Light tab. The Switch page displays with the Sys Err Light tab selected. A System Error Light is ON message displays on the page. c. Click Clear Light. 10. If necessary, close and lock the equipment cabinet door. RRP: AC module Use the following procedures to remove or replace the AC module.
  • Page 265: Ac Module Removal And Replacement

    ATTENTION! To avoid causing machine errors or damage while working on the director, follow ESD procedures by connecting a grounding cable to the director chassis and wearing an ESD wrist strap. 3. Follow ESD procedures by attaching a wrist strap to the director chassis and your wrist (Figure 69).
  • Page 266 7. Place the AC module in an anti-static bag to provide ESD protection. Replacement To replace the AC module: 1. Remove the replacement AC module from its protective anti-static bag. 2. Inspect the printed wiring assembly (PWA) side of the AC module for bent or broken connector pins that may have been damaged during shipping.
  • Page 267: Rrp: Fan Module

    11. Perform one of the following to clear the system error (ERR) LED: — If at the management server, open the Hardware View and: a. Right-click the front panel bezel graphic (away from a FRU) to open a menu. b. Click the Clear System Error Light menu selection. —...
  • Page 268 — If the director is installed in a customer-supplied equipment cabinet, unlock and open the cabinet rear door as directed by the customer representative. ATTENTION! Do not remove a fan module unless a replacement module is available. Operation of the director for more than 10 minutes with only two fan modules may cause one or more thermal sensors to post event codes.
  • Page 269: Fan Module Removal And Replacement

    Fan module removal and replacement Figure 76 Location Description Fan module 6. Pull the module from the director. Support the fan module with one hand. 7. Place the fan module in an anti-static bag to provide ESD protection. Replacement To replace the fan module: 1.
  • Page 270 4. Using a standard flat-tip screwdriver, tighten the two captive screws that secure the fan module to the director chassis. 5. Disconnect the ESD wrist strap from the director chassis and your wrist. 6. Inspect the fan module to ensure the amber LED is unlit. If the LED is lit, go to Chapter 3, Maintenance analysis procedures (MAPS) to isolate the problem.
  • Page 271: Rrp: Power/System Error Led Assembly

    b. Click the Sys Err Light tab. The Switch page displays with the Sys Err Light tab selected. A System Error Light is ON message displays on the page. c. Click Clear Light. 12. If necessary, close and lock the equipment cabinet door. RRP: Power/system error LED assembly Use the following procedures to remove or replace the Power/System Error LED assembly.
  • Page 272: Power/System Error Led Assembly Removal And Replacement

    Figure 77 Power/System error LED assembly removal and replacement Location Description Fan modules Power/system error LED assembly Replacement To replace the Power/System Error LED assembly: 1. Remove the replacement Power/System Error LED assembly from its protective anti-static bag. 2. Replace the Power/System LED assembly. 3.
  • Page 273: Rrp: Sbar Assembly

    RRP: SBAR assembly Use the following procedures to remove or replace an SBAR assembly. A list of tools required is provided. Tools required The following tools are required to perform these procedures. • Door key with 5/16-inch socket. • Standard flat-tip screwdriver. •...
  • Page 274: Sbar Assembly Removal And Replacement

    SBAR assembly removal and replacement Figure 78 Location Description SBAR assembly 6. Using the handles, pull the SBAR assembly out of the director chassis. Support the assembly with one hand. 7. Place the SBAR assembly in an anti-static bag to provide ESD protection.
  • Page 275 6. Inspect the assembly to ensure the amber LED is turned off. If the amber LED is lit, go to Chapter 3, Maintenance analysis procedures (MAPS) to isolate the problem. 7. Replace the RFI shield. 8. At the management server or at a web browser connected to the EFCM Basic Edition interface, inspect the Event Log.
  • Page 276: Rrp: Backplane

    a. Click the Switch tab at the Operations panel. The Operations panel opens with the Switch page displayed. b. Click the Sys Err Light tab. The Switch page displays with the Sys Err Light tab selected. A System Error Light is ON message displays on the page.
  • Page 277 If the director is not communicating with the management server (Director Properties dialog box is not available), obtain the serial number while performing step 2. Notify the customer that the director will be powered off. Ensure the customer system administrator quiesces Fibre Channel frame traffic through the director and sets attached devices offline.
  • Page 278: Backplane Removal And Replacement

    11. Remove the AC modules (RRP: AC module on page 232). 12. Remove the fan modules (RRP: Fan module on page 235). 13. Remove the SBAR assemblies (RRP: SBAR assembly on page 241). 14. Unplug the Power/System LED assembly cable from the backplane.
  • Page 279 1. Remove the replacement backplane from its protective anti-static bag. Inspect the backplane PWA to ensure no connector pins are damaged. 2. Align the guide pins on the back of the backplane with the alignment holes in the card cage. 3.
  • Page 280 19. Reprogram the replacement backplane with the original director serial number: a. Remove the protective cap from the 9-pin maintenance port at the rear of the director (a flat-tip screwdriver may be required). Connect the 9-pin end of the RS-232 modem cable to the port.
  • Page 281 23. Perform one of the following to clear the system error (ERR) LED: — If at the management server, open the Hardware View and: a. Right-click the front panel bezel graphic (away from a FRU) to open a menu. b. Click the Clear System Error Light menu selection. —...
  • Page 282 SAN140M Installation and Service Manual...
  • Page 283: Illustrated Parts Breakdown

    Exploded-view illustrations portray the director disassembly sequence for clarity. Illustrated FRUs and parts are numerically keyed to associated parts lists. The parts lists include IBM part numbers, descriptions, and quantities. An (*ESD*) symbol precedes the description of a FRU containing electrostatic discharge (ESD) sensitive components.
  • Page 284 NOTE: A part in a non-RoHS compliant unit (serial number not ending in an alpha character) can be replaced by either a non-RoHS compliant or a RoHS compliant part. SAN140M Installation and Service Manual...
  • Page 285: Front-Accessible Frus

    Front-accessible FRUs Figure 80 illustrates the front-accessible FRUs and Table 27 is the parts list. The table includes reference numbers to Figure 80, part numbers, descriptions, and quantities. Front-accessible FRUs Figure 80 Chapter 6: Illustrated parts breakdown...
  • Page 286: Front-Accessible Fru Parts List

    Table 27 Front-accessible FRU parts list Non-RoHS part RoHS part Ref. numbers numbers Description Qty. Figure Reference Reference Base assembly, director Item 1 Reference Reference Filler panel, CTP 23R0269 23R0827 (*ESD*) Printed wiring assembly, 10 Gbps port module (XPM), 1-port, LC, (pluggable optics not included) Reference Reference...
  • Page 287: Rear-Accessible Frus

    Rear-accessible FRUs Figure 81 Figure 82 illustrate the rear-accessible FRUs, and Table Table 29 are the parts lists. The table includes reference numbers to Figure 81, part numbers, descriptions, and quantities. Figure 81 Rear-accessible FRUs (part 1) Chapter 6: Illustrated parts breakdown...
  • Page 288: Rear-Accessible Fru Parts List (Part 1)

    Rear-accessible FRU parts list (part 1) Table 28 Non-RoHS part Non-RoHS part Ref. number numbers Description Qty. Figure 81, Item 1 Reference Reference Base assembly, director 22R2244 23R0673 (*ESD*) LED assembly, power/system error 22R2236 23R0661 (*ESD*) Fan module Table 27 Table 27 (*ESD*) Printed wiring assembly, universal port 16 to 35...
  • Page 289: Rear-Accessible Frus (Part 2)

    Rear-accessible FRUs (part 2) Figure 82 Rear-accessible FRU parts list (part 2) Table 29 Non-RoHS part RoHS part Ref. numbers numbers Description Qty. Figure 82, Item 1 Reference Reference Base assembly, director 22R2239 23R0664 (*ESD*) Printed wiring assembly, backplane Reference Reference Cage assembly, rear card Reference...
  • Page 290: Miscellaneous Parts

    Miscellaneous parts Figure 83 illustrates the miscellaneous parts, and Table 30 is the parts list. The table includes reference numbers to Figure 83, part numbers, descriptions, and quantities. Miscellaneous parts Figure 83 Table 30 Miscellaneous parts Ref. Part number Description Qty.
  • Page 291: Power Cords And Receptacles

    Power cords and receptacles Figure 84 illustrates the optional power cords and receptacles and Table 31 is the parts list. The table includes reference numbers to Figure 84, feature numbers, and descriptions. 6, 10,14 11, 12,13 Power cords and receptacles Figure 84 Chapter 6: Illustrated parts breakdown...
  • Page 292: Power Cord And Receptacle List

    Power cord and receptacle list Table 31 Ref. Part Number Description Figure 84, Item 1 22R2265 Power cord, AC, United Kingdom BS 1363 right angle, 250 volts, 10 amps, 2.8 meters Receptacle: BS 1363 Reference Power cord, AC, European Community CEE 7/7 straight, 250 volts, 10 amps, 2.5 meters Receptacle: CEE 7 Reference...
  • Page 293 Power cord and receptacle list (Continued) Table 31 Ref. Part Number Description Reference Power cord, AC, North America NEMA L6-15P straight, twist-lock, 250 volts, 10 amps, 2.8 meters Receptacle: NEMA L6-15R Reference Power cord, AC, North America NEMA L6-15P straight, twist-lock, 250 volts, 10 amps, 2.8 meters Receptacle: NEMA L6-15R Reference Power cord, AC, Japan...
  • Page 294 SAN140M Installation and Service Manual...
  • Page 295: Event Code Tables

    In addition to numerical event codes, the tables in this appendix also provide a: • Message - A brief text string that describes the event. • Severity - A severity level that indicates event criticality as follows: — Informational. — Minor. — Major. © Copyright IBM Corp. 2006...
  • Page 296 — Severe (not operational). • Explanation - An 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 appears in the event log in hexadecimal format.
  • Page 297: System Events (000 Through 199)

    CTP card, but failed. 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 CD to IBM support personnel. Event Data: No supplementary data included with this event.
  • Page 298 (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 CD to IBM support personnel. Event Data: No supplementary data included with this event.
  • Page 299 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 CD to IBM support personnel. Event Data: No supplementary data included with this event.
  • Page 300 CTP card, but failed. All management services databases are initialized to an empty state, resulting in an implicit logout of all devices logged in to the management server. Action: Perform the data collection procedure and return the CD to IBM support personnel. Event Data: No supplementary data included with this event.
  • Page 301 Explanation: An internal operating error was detected by the management server application. Action: Management server application internal error: Perform the data collection procedure and return the CD to IBM support personnel. Event Data: Supplementary data consists of reporting tasks of type eMST_SB2, with component_id eMSCID_SB2_CHPGM.
  • Page 302 CRC validation. All fabric controller databases are initialized to an empty state, resulting in a momentary loss of interswitch communication capability. Action: Perform the data collection procedure and return the CD to IBM support personnel. Event Data: No supplementary data included with this event.
  • Page 303 Severity: Informational. Explanation: The fabric controller software detected that the ESS response from the indicated domain has not been received after the maximum number of attempts. Event posts in IBM interop mode only. Action: No action required. Event Data: Byte 0 = domain ID of the fabric element (director or switch) not receiving a response to an ESS message.
  • Page 304 (directors or switches). The director E_Port (at the operational director) times out and segments if the attached device does not respond. Check the status of the attached director or switch. If the condition persists, perform the data collection procedure (at the attached device) and return the CD to IBM support personnel.
  • Page 305 (directors or switches). The director E_Port (at the operational director) times out and segments if the attached device does not respond. Check the status of the attached director or switch. If the condition persists, perform the data collection procedure (at the attached device) and return the CD to IBM support personnel.
  • Page 306 An error was detected during the fabric initialization sequence, most likely caused by frame delivery errors. Event data is intended for engineering evaluation. Action: Perform the data collection procedure and return the CD to IBM support personnel. Event Data: Byte 0 = error reason code for engineering evaluation.
  • Page 307 (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. Action: Perform the data collection procedure and return the CD to IBM support personnel. Event Data: Byte 0 = E_Port number reporting the problem.
  • Page 308 (directors or switches). The director E_Port (at the operational director) times out and segments if the attached device does not respond. Check the status of the attached director or switch. If the condition persists, perform the data collection procedure (at the attached device) and return the CD to IBM support personnel.
  • Page 309 Event code: 080 Message: Unauthorized worldwide name. Severity: Informational. Explanation: The worldwide name of the device or director plugged in the indicated port is not authorized for that port. Action: Change the port binding definition or plug the correct device or director into this port. Event Data: Byte 0 = Port number reporting the unauthorized connection.
  • Page 310 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.
  • Page 311 11 = Fabric mode mismatch - Based on the ELP revision level, a connection was not allowed because a IBM switch in legacy mode is attached to a IBM switch in Open Fabric mode, or a IBM switch in Open Fabric mode is attached to an OEM switch at an incorrect ELP revision level.
  • Page 312 Event code: 082 Message: Port fencing - port fenced. Severity: Informational. Explanation: Port is disabled (blocked) due to meeting the threshold criteria defined in the port fencing policy. The fence type is indicated in the event data. Action: Identify the responsible application or hardware and fix. Hardware may include components such as ports, ISLs, and extenders.
  • Page 313 3 = Switch speed conflict - The port cannot operate at the configured product (backplane or CTP Card) speed. 4 = Optics speed conflict - The port transceiver does not support the configured port speed. 5 - No SBAR - A serial crossbar (SBAR) is not installed. Not applicable to IBM machine type 2026 fabric switches.
  • Page 314 Action: Perform a data collection for this director using the SAN management application. Save the data file to the management server CD drive, and return the CD to IBM support personnel. Event Data: Bytes 0 - 3: Type of replication operation that timed out.
  • Page 315 No action is required for an isolated event. If this event persists, perform a data collection for this director using the SAN management application. Save the data file to the management server CD drive, and return the CD to IBM support personnel. Event Data: No supplementary data included with the event.
  • Page 316 Event code: 140 Message: Congestion detected on an ISL. Severity: Informational. Explanation: OpenTrunking firmware detected an ISL with Fibre Channel traffic that exceeded the configured congestion threshold. Action: No action is required for an isolated event. If this event persists, relieve the congestion by adding parallel ISLs, increasing the ISL link speed, or moving device connections to a less-congested region of the fabric.
  • Page 317 Event code: 142 Message: Low BB_Credit detected on an ISL. Severity: Informational. Explanation: OpenTrunking firmware detected an ISL with no transmission BB_Credit for a period of time that exceeded the configured low BB_Credit threshold. This indicates downstream fabric congestion. Action: No action is required for an isolated event or if the reporting ISL approaches 100% throughput.
  • Page 318 Event code: 150 Message: Zone merge failure. Severity: Informational. Explanation: During ISL initialization, the zone merge process failed. Either an incompatible zone set was detected or a problem occurred during delivery of a zone merge frame. This event code always precedes a 070 ISL segmentation event code, and represents the reply of an adjacent fabric element in response to a zone merge frame.
  • Page 319 Action: Depends on the failure reason. In most cases, perform the data collection procedure on the managing switch and the managed switch, and return the CD to IBM support personnel. Event Data: Reason codes were mapped from the software implementation (FC-SW2 protocol) so decoding them is complicated and may require engineering assistance.
  • Page 320: Power Supply Events (200 Through 299)

    Ensure the power supply is connected to facility AC power, and verify operation of the facility power source. If the AC voltage does not recover (indicated by event code 203), replace the failed power supply. Perform the data collection procedure and return the CD and failed power supply to IBM support personnel. Event Data: No supplementary data included with this event.
  • Page 321 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 CD and failed power supply to IBM support personnel. Event Data: No supplementary data included with this event.
  • Page 322 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 Management Server...
  • Page 323 Action: Confirm operation of facility power. If subsequent power loss events occur, replace the failed power supply. Perform the data collection procedure and return the CD and failed power supply to IBM support personnel. Event Data: No supplementary data included with this event.
  • Page 324: Fan Module Events (300 Through 399)

    Fan module events (300 through 399) Event code: 300 Message: Cooling fan propeller failed. Severity: Major. Explanation: One cooling fan failed or is rotating at insufficient angular velocity. The remaining fans are operational. The amber LED turns on at the rear of the fan module associated with the failed fan. Action: Replace the indicated fan module.
  • Page 325 Event code: 302 Message: Cooling fan propeller failed. Severity: Major. Explanation: Three cooling fans failed or are rotating at insufficient angular velocity. The remaining fans are operational. The amber LED turns on at the rear of the fan modules associated with the failed fans. Action: Replace the indicated fan modules.
  • Page 326 Event code: 304 Message: Cooling fan propeller failed. Severity: Major. Explanation: Five cooling fans failed or are rotating at insufficient angular velocity. The remaining fans are operational. The amber LED turns on at the rear of the fan modules associated with the failed fans. Action: Replace the indicated fan modules.
  • Page 327 Event code: 310 Message: Cooling fan propeller recovered. Severity: Informational. Explanation: One cooling fan recovered or the associated fan module was replaced. One fan is operational. Action: No action required. Event Data: The first byte of event data (byte 0) specifies the recovered fan number. Distribution: Director Management Server...
  • Page 328 Event code: 312 Message: Cooling fan propeller recovered. Severity: Informational. Explanation: Three cooling fans recovered or the associated fan modules were replaced. Three fans are operational. Action: No action required. Event Data: The first byte of event data (byte 0) specifies the recovered fan numbers. Distribution: Director Management Server...
  • Page 329 Event code: 314 Message: Cooling fan propeller recovered. Severity: Informational. Explanation: Five cooling fans recovered or the associated fan modules were replaced. Five fans are operational. Action: No action required. Event Data: The first byte of event data (byte 0) specifies the recovered fan numbers. Distribution: Director Management Server...
  • Page 330 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 Management Server Host Nonvolatile System...
  • Page 331 Event code: 333 Message: Rear bottom fan tray removed. Severity: Major. Explanation: A fan module has been removed. Action: Replace the fan module immediately. Event Data: No supplementary data included with the event. Distribution: Director Management Server Host Nonvolatile System Event Log E-Mail Call-Home...
  • Page 332: Ctp Card Events (400 Through 499)

    Action: Replace the failed FRU with a functional FRU. Perform the data collection procedure and return the CD and faulty FRU to IBM support personnel. Event Data: Byte 0 = FRU code as follows: 01 = backplane, 02 = CTP card, 03 = SBAR, 05 = fan module, 06 = power supply, and 08 through 0F = port cards.
  • Page 333 A non-disruptive failover to the backup CTP card occurs. When the dump and subsequent IPL complete, the faulty CTP card re-initializes to become a the backup. Action: Perform the data collection procedure and return the CD to IBM support personnel. Event Data: Bytes 0 - 3 = fault identifier, least significant byte first.
  • Page 334 A backup CTP card was installed in the director and failed POSTs. Action: Replace the indicated CTP card with a functional card. Perform the data collection procedure and return the CD and faulty card to IBM support personnel. Event Data: No supplementary data included with this event.
  • Page 335 Event code: 415 Message: Backup CTP card removed. Severity: Informational. Explanation: The backup CTP card was removed while the director was powered on and operational. Action: Install an operational backup CTP card. Event Data: No supplementary data included with this event. Distribution: Director Management Server...
  • Page 336 Event code: 417 Message: CTP card firmware synchronization initiated. Severity: Informational. Explanation: The active CTP card initiated a firmware synchronization with the backup CTP card. Action: No action required. Event Data: No supplementary data included with this event. Distribution: Director Management Server Host Nonvolatile...
  • Page 337 The backup CTP card detected a NVRAM memory failure. The failure has no impact on the active CTP card. Action: Replace the indicated CTP card with a functional card. Perform the data collection procedure and return the CD and faulty card to IBM support personnel. Event Data: Byte 0 = NVRAM area identifier.
  • Page 338 Event code: 422 Message: CTP firmware synchronization complete. Severity: Informational. Explanation: Active CTP card synchronization with the backup CTP card complete. Action: No action required. Event Data: No supplementary data included with this event. Distribution: Director Management Server Host Nonvolatile System Event Log E-Mail...
  • Page 339 Action: Replace the indicated CTP card with a functional card. Perform the data collection procedure and return the CD and faulty card to IBM support personnel. Event Data: Each byte of data represents the ID of the port module with which the backup CTP was unable to communicate.
  • Page 340 The embedded port hardware detected a fatal CTP card error. Action: Replace the indicated CTP card with a functional card. Perform the data collection procedure and return the CD and faulty card to IBM support personnel. Event Data: Byte 0 = CTP slot position.
  • Page 341 Event code: 442 Message: Embedded port anomaly detected. Severity: Informational. Explanation: The CTP card detected a deviation in the normal operating mode or status of the embedded port. Action: No action required. Additional event code is generated if incident exceeds error threshold or causes a port failure. Event Data: Byte 0 = port number.
  • Page 342 Distribution: Director Management Server Host Nonvolatile System Event Log E-Mail Call-Home Sense Info Link Incident System Error LED Event Log Event code: 453 Message: New feature key installed. Severity: Informational. Explanation: This event occurs when a new feature key is installed from the management server or Web server. The director performs an IPL when the feature key is enabled.
  • Page 343: Port Card (Upm And Xpm) Events (500 Through 599)

    Port card (UPM and XPM) events (500 through 599) Event code: 500 Message: Port card hot-insertion initiated. Severity: Informational Explanation: Installation of a port card was initiated with the director powered on and operational. The event indicates that operational firmware detected the presence of the port 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.
  • Page 344 Event code: 502 Message: Port module anomaly detected. Severity: Informational. Explanation: The CTP card detected a deviation in the normal operating mode or status of the indicated port card. Action: No action required. An event code 504 is generated if the port card fails. Event Data: Byte 0 = port card slot position.
  • Page 345 Action: Replace the indicated port card with a functional port card of the same type. Perform the data collection procedure and return the CD and faulty card to IBM support personnel. Event Data: Byte 0 = port card slot position.
  • Page 346 Other ports remain operational if their LEDs are unlit. Action: Replace the indicated port card with a functional port card of the same type. Perform the data collection procedure and return the CD and faulty card to IBM support personnel. Event Data: Byte 0 = port number.
  • Page 347 Replace the indicated port card with a functional port card of the same type. Perform the data collection procedure and return the CD and faulty card to IBM support personnel. A failed path may also be recovered by performing a port reset with the SAN management application, however any newly detected errors may cause the path to re-fail.
  • Page 348 Distribution: Director Management Server Host Nonvolatile System Event Log E-Mail Call-Home Sense Info Link Incident System Error LED Event Log Event code: 510 Message: SFP/XFP optical transceiver hot-insertion initiated. Severity: Informational. Explanation: Installation of an SFP or XFP optical transceiver was initiated with the director powered on and operational. The event indicates that operational firmware detected the presence of the transceiver.
  • Page 349 Event code: 512 Message: SFP/XFP optical transceiver nonfatal error. Severity: Minor. Explanation: Director firmware detected an SFP or XFP optical transceiver non-fatal error. Action: Replace the failed transceiver with a functional transceiver of the same type. Event Data: Byte 0 = port number. Byte 2 = type of optics: Bit 1 = SFP;...
  • Page 350 Event code: 514 Message: SFP/XFP optical transceiver failure. Severity: Major. Explanation: An SFP or XFP optical transceiver failed. The amber LED corresponding to the port turns on to indicate the failure. Other ports remain operational if their LEDs are unlit. Action: Replace the failed transceiver with a functional transceiver of the same type.
  • Page 351 Monitor the performance of the port module (and associated port modules). If persistent resets occur, or if other system errors are recorded against the module, replace the indicated port card with a functional port card of the same type. Perform the data collection procedure and return the CD and faulty card to IBM support personnel. Event Data: Byte 0 = slot number.
  • Page 352 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).
  • Page 353 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).
  • Page 354 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).
  • Page 355: Sbar Events (600 Through 699)

    SBAR events (600 through 699) Event code: 600 Message: SBAR 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.
  • Page 356 Event code: 602 Message: SBAR anomaly detected. Severity: Informational. Explanation: Director operational firmware detected a deviation in the normal operating mode or operating status of the indicated SBAR. Action: No action required. An event code 604 is generated if the SBAR fails. Event Data: Byte 0 = SBAR slot position.
  • Page 357 SBAR is not impacted. Action: Replace the failed SBAR with a functional assembly. Perform the data collection procedure and return the CD and faulty assembly to IBM support personnel. Event Data: Byte 0 = SBAR slot position.
  • Page 358 Event code: 607 Message: Director contains no operational SBARs. Severity: Severe. Explanation: The director firmware does not recognize an installed SBAR. Action: Install at least one functional SBAR and power-on reset (POR) the director. Event Data: Bytes 4 - 7 = elapsed millisecond tick count. Distribution: Director Management Server...
  • Page 359 Monitor the performance of the SBAR. If persistent resets occur, or if other system errors are recorded against the module, replace the indicated SBAR with a functional SBAR. Perform the data collection procedure and return the CD and faulty card to IBM support personnel. Event Data: Byte 0 = SBAR slot position.
  • Page 360 Event code: 621 Message: Failed SBAR fan recovered. Severity: Informational. Explanation: System software has detected that one or more failed SBAR fan modules has recovered. Action: None. Event Data: Bytes 0 - 3 = reserved. Bytes 4 - 7 = elapsed millisecond tick count. Bytes 8 and 9 = failed SBAR fan count.
  • Page 361: Thermal Events (800 Through 899)

    Action: Replace the indicated port card with a functional port card of the same type. Perform the data collection procedure and return the CD and faulty card to IBM support personnel. Event Data: No supplementary data included with this event.
  • Page 362 Action: Replace the failed port card with a functional port card of the same type. Perform the data collection procedure and return the CD and faulty card to IBM support personnel. Event Data: No supplementary data included with this event.
  • Page 363 The thermal sensor associated with an SBAR indicates the hot temperature threshold was reached or exceeded. Action: Replace the indicated SBAR with a functional assembly. Perform the data collection procedure and return the CD and faulty assembly to IBM support personnel. Event Data: No supplementary data included with this event.
  • Page 364 The thermal sensor associated with a CTP card indicates the warm temperature threshold was reached or exceeded. Action: Replace the indicated CTP card with a functional card. Perform the data collection procedure and return the CD and faulty card to IBM support personnel. Event Data: No supplementary data included with this event. Distribution:...
  • Page 365 If the backup CTP card fails, the active card is not impacted. Action: Replace the failed CTP card with a functional card. Perform the data collection procedure and return the CD and faulty card to IBM support personnel. Event Data: No supplementary data included with this event.
  • Page 366 SAN140M Installation and Service Manual...
  • Page 367: Director Specifications

    Input voltage: 200 to 240 VAC Input current: 4.2 amps at 208 VAC Input frequency: 47 to 63 Hz Plan for single phase or phase-to-phase connections and 15-ampere dedicated service Heat dissipation Nominal: 841 watts (2,873 BTUs/hr) © Copyright IBM Corp. 2006...
  • Page 368: Cooling Airflow Clearances (Director Chassis)

    Cooling airflow clearances (director chassis) Right and left side: 2.5 centimeters (1.0 inches) Front and rear: 7.6 centimeters (3.0 inches) Top and bottom: No clearance required Acoustical noise 70.0 dB “A” scale Shipping and storage environment Protective packaging must be provided to protect the director under all shipping methods (domestic and international).
  • Page 369: Sanc40M Equipment Cabinet Service Clearances

    Maximum wet-bulb temperature: 27° C (81° F) Altitude: 3,048 meters (10,000 feet) Inclination: 10° maximum SANC40M equipment cabinet service clearances Front: 91.4 centimeters (36.0 inches) Rear: 91.4 centimeters (36.0 inches) Right side: No clearance required Left side: No clearance required Appendix B: Director specifications...
  • Page 370 SAN140M Installation and Service Manual...
  • Page 371: Management Server And Ethernet Hub

    (CD-RW) drive. • 56K internal modem. • Two 10/100 Mbps Ethernet adapters with RJ-45 connectors. Ethernet hub description The management server and managed directors or switches connect through a 10/100 Base-T IBM-qualified Ethernet hub (Figure 85). © Copyright IBM Corp. 2006...
  • Page 372 Figure 85 Hubs can be daisy-chained to provide additional connections as more directors or switches (or other IBM managed products) are installed on a network. Multiple hubs are daisy-chained by attaching RJ-45 Ethernet patch cables and configuring each hub through a medium- dependent interface (MDI) switch.
  • Page 373: Restore Management Server

    SNMP trap recipients, E-mail recipients, and Ethernet event notifications). — All log files (SAN management application and Element Manager logs). — Zoning library (all zone set and zone definitions). — Firmware library. © Copyright IBM Corp. 2006...
  • Page 374: Restore Management Server Procedure

    — Call-home settings. — Configuration data for each managed director (stored on the server and in NV-RAM on each director or switch). • Windows 2000 configuration information - Windows 2000 network addresses, date and time information, user information, and the product identification are recorded during installation of the management server.
  • Page 375 8. Configure Windows 2000 configuration information as required by the customer: a. Configure the computer and workgroup names for the server. If required, change the server gateway address and DNS server IP address to conform to the customer LAN addressing plan (Task 7: Configure management server information page 57).
  • Page 376 17. Power off and reboot the server. a. At the Windows 2000 desktop, click Start at the left side of the task bar (bottom of the desktop), then select Shut Down. The Shut Down Windows dialog box displays. b. Select the Restart option from the list box and click OK. The server powers down and restarts.
  • Page 377 h. Click Login. The application opens and the EFCM main window appears. Appendix D: Restore management server...
  • Page 378 SAN140M Installation and Service Manual...
  • Page 379: Glossary

    10 Gbps port module A printed circuit board (140M director only) that provides port card connections that support 10.5200 Gbps Fibre Channel communication. Port connectivity is provided through XFP optical transceivers. Contrast with universal port module card. © Copyright IBM Corp. 2006...
  • Page 380 The zone set active for a multiswitch fabric, and created when a active zone set user-specified zone set is enabled. See also zone zone set. AL_PA arbitrated loop physical address. (1) An information processing system, for example, a payroll application application, an airline reservation application, or a network application.
  • Page 381 bidirectional The capability to simultaneously communicate in both directions over a single connection, with flow control. Synonymous with full-duplex. A digital 0 or 1, and abbreviated with a lower case b. Synonymous with binary digit. Contrast with byte. The number of bits received incorrectly divided by the total number bit error rate of bits transmitted.
  • Page 382 Class 2 Fibre Channel Provides connectionless multiplexed Fibre Channel service between service fabric-attached node ports (N_Ports) with acknowledgement of frame delivery or nondelivery. Class 2 service is best suited for mainstream computing applications. Class 3 Fibre Channel Provides connectionless multiplexed Fibre Channel service between service fabric-attached node ports (N_Ports) without acknowledgement of frame delivery or nondelivery.
  • Page 383 control processor card A printed circuit board that provides the microprocessor and control logic for all directors and switches. The CTP card also initializes hardware components after system power-on. The board may also provide an RJ-45 Ethernet connector. control unit port An internal director or switch port, embedded on the CTP card, that communicates with channels to report errors and link initialization.
  • Page 384 group of servers connected and named to simplify network administration and security. (2) For TCP/IP applications, the naming system used in a hierarchical network. (3) A Fibre Channel term describing the most significant byte in the N_Port identifier of a Fibre Channel device.
  • Page 385 EFC Manager application, all director and switch-specific Element Manager applications, and the Cluster Manager application. Enterprise Systems A computer architecture introduced by IBM in 1988 as ESA/370. The Architecture architecture added access registers to improve virtual memory management and increase storage from 2 gigabyte to 6 terabytes. The architecture was enhanced with the introduction of ESA/390 in 1990.
  • Page 386 Ethernet A widely-implemented 10 or 100-Mbps LAN protocol that uses a bus or star topology based on the IEEE 802.3 standard. The protocol provides carrier-sense multiple access, and resolves signal contention using collision detection and transmission. event code A three-digit number that identifies an event that occurred at a director, switch, or the management server.
  • Page 387 Fibre Channel Physical and Signaling Interface. feature enablement After purchasing a an additional product feature, IBM provides a unique feature enablement key to the customer. A feature key is a case-sensitive alphanumeric string consisting of dashes, uppercase characters, and lowercase characters.
  • Page 388 Fibre Connection An IBM architecture, technology, and set of products and services introduced in 1999 and based on the Fibre Channel Standard. FICON technology uses fiber-optic cables as the data transmission medium, and significantly improves I/O performance.
  • Page 389 field-replaceable unit An assembly removed and replaced in its entirety (on site) when any assembly components fails. FLOGI fabric login. fabric loop port. FL_Port FPM card fibre port module card. F_Port fabric port. field-replaceable unit. FSPF fibre shortest path first. The capability to simultaneously communicate in both directions full-duplex over a single connection, with flow control.
  • Page 390 is provided through SC duplex optical transceivers. Contrast with fibre port module card universal port module card. See gigahertz. gigabit A unit of measure for data storage, equal to 134,217,728 bytes. A gigabit is generally approximated as one eighth of a gigabyte. A removable port connector (serial DB9, serial HSSDC, or fiber-optic) gigabit interface converter...
  • Page 391 half-duplex The capability to communicate in both directions over a single connection, but not simultaneously (except for link control frames). Contrast with full-duplex. A log recorded at the Element Manager application that displays a Hardware Log history of FRU removals and replacements (insertions) for a director or switch.
  • Page 392 inband management Management of a director or switch through a Fibre Channel or FICON port connection to a management server. Contrast with out-of-band management. initial machine load A software operation that reloads director or switch firmware and resets the Ethernet LAN interface. An IML is typically performed by pressing the IML button at the director or switch front panel.
  • Page 393 local area network. laser Acronym for light amplification by stimulated emission of radiation. A device that produces a powerful, narrow beam of coherent light of a single wavelength by simulating the emissions of photons from atoms, molecules, or ions. latency For Fibre Channel applications, the time elapsed between receipt of a data frame at a switch’s incoming F_Port to retransmission of the data through the switch’s outgoing F_Port to a destination N_Port.
  • Page 394 identified in a SAN when the LUN combines with the WWN of the storage device’s N_Port. A transmitted LIP sequence enables initialization of a Fibre Channel loop initialization primitive sequence arbitrated loop. An arbitrated loop must initialize prior to operation and when configuration changes are detected.
  • Page 395 megabit A unit of measure for data storage, equal to 1,048,576 bits. A megabit is generally approximated as one million bits. megabyte A unit of measure for data storage, equal to 1,048,576 bytes. A megabyte is generally approximated as one million bytes. A printed circuit board (ED-5000 Director only) that provides the message path mechanism for messages to be sent and received between director...
  • Page 396 FICON management server. open-systems mode The management mode used to specify director or switch port connectivity when the product is attached to other IBM products or OSI-compliant devices as part of an open fabric. Contrast with S/390 mode. Operating System/390...
  • Page 397 out-of-band Management of a director or switch through an Ethernet port management connection to a management server. Contrast with inband management. 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.
  • Page 398 public device An arbitrated loop device that can transmit a FLOGI command a switch, receive acknowledgement from the switch’s login server, register with the switch’s name server, and communicate with fabric-attached devices. Contrast with private device. public loop A public arbitrated loop is connected to a switched fabric. All devices attached to the loop can communicate with each other, and public devices attached to the loop can communicate with fabric-attached devices.
  • Page 399 S/390 mode The management mode used to specify director or switch port connectivity when the product is attached to an IBM System/390 (generation 5 or later) or zSeries 900 Parallel Enterprise Server with one or more FICON channel cards installed. Contrast with open-systems mode.
  • Page 400 communicates with another device using the full switch bandwidth. During frame transmission between the device pair, no other switch ports or attached devices can communicate. Contrast with switched mode. simple mail transfer The TCP/IP standard protocol for transferring electronic mail protocol messages from one machine to another.
  • Page 401 depends on the class of network to which the computer is connecting. The mask indicates the digits to search in a longer network address, and allows a router to avoid handling the entire address. Typically, a subnet represents all devices configured at one location, building, or on the same LAN.
  • Page 402 transmission control A layered set of protocols (network and transport) that allows protocol/Internet sharing of applications among devices in a high-speed LAN protocol communication environment. trap An unsolicited notification of an event originating from an SNMP- managed device and directed to an SNMP network management station.
  • Page 403 vital product data System-level data stored by FRUs in electrically erasable programmable read-only memory. VPD identifies the manufacturer and includes the FRU part number and serial number. vital product data. wide area network. well-known address A set of address identifiers defined in the Fibre Channel Physical and Signaling Interface specification that access global server functions such as a login server, management server, or name server.
  • Page 404 connections. Nonmember devices cannot. See also active zone set, zone set, and zoning. A device (server, storage device, or other peripheral) included in a zone member zone. Zone members are identified by port number or WWN. zone set A group of zones activated or deactivated as one entity. See also active zone set and zone.
  • Page 405: Notices

    This information was developed for products and services offered in the U. S. A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area.
  • Page 406 The materials at those web sites are not part of the materials for this IBM product and use of those web sites is at your own risk.
  • Page 407: Trademarks

    Trademarks The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: IBM, ESCON, eServer, FICON. McDATA, EFC Manager, EFCM, Eclipse, OPENready, SANpilot, SANvergence, SANtegrity, Enterprise Operating System, E/OS, E/OSi, and E/OSn are trademarks of McDATA Corporation and its subsidiaries in the United States, other countries, or both.
  • Page 408: Federal Communications Commission (Fcc) Class A Statement

    IBM is not responsible for any radio or television interference caused by unauthorized changes or modifications to this equipment.
  • Page 409: Germany Electromagnetic Compatibility Directive

    Diese Einrichtung kann im Wohnbereich Funkstorungen verursachen; in diesem Fall kann vom Betreiber verlangt werden, angemessene Masnahmen durchzuführen und dafür aufzukommen.” Anmerkung: Um die Einhaltung des EMVG sicherzustellen, sind die Geräte wie in den IBM Handbüchern angegeben zu installieren und zu betreiben.
  • Page 410: People's Republic Of China Class A Electronic Emission Statement

    People’s Republic of China Class A Electronic Emission Statement Korean Class A Electronic Emission Statement Japan VCCI Class A ITE Electronic Emission Statement SAN140M Installation and Service Manual...
  • Page 411: Index

    BB_Credit Code of Federal Regulations configure laser compliance Element Manager command line interface description disable beaconing EFCM Basic Edition enable bezel EFCM Basic Edition binding © Copyright IBM Corp. 2006...
  • Page 412 concurrent FRUs table date and time configuration data DNS domain name managing IP address configuration file name back up password EFCM Basic Edition subnet mask SAN management application OpenTrunking restore Element Manager EFCM Basic Edition OSMS SAN management application EFCM Basic Edition configure Element Manager access control list...
  • Page 413 Windows users user name 66, 91, zone sets SAN management application password zones SAN management application user name cooling fan fault isolation TightVNC password 57, 90, 201, CTP card Windows description password 58, 91, event codes user name 58, 91, failover Windows 2000 password fault isolation...
  • Page 414 reset 6, 192, performance view SBAR assembly port list view setting online or offline 188, SNMP shipping environment Element Manager application specifications configure storage environment configure PFE key tools supplied EFCM Basic Edition weight Element Manager door key embedded port log download switch fabric log firmware from filecenter...
  • Page 415 error detection configure event codes EFCM Basic Edition error reporting SAN management application event codes description error-detection features, director enable EFCM Basic Edition FRUs SAN management application illustration Enterprise Fabric Mode removing and replacing fabric log grounding point EFCM Basic Edition front fabric parameters information...
  • Page 416 field-replaceable units See FRUs gateway address filecenter change director address 39, download firmware default 156, download software director default 23, firmware management server default download version from filecenter grounding point FL_Port front configure 41, FLASH memory Flexport Technology hardware log configure PFE key hardware view EFCM Basic Edition...
  • Page 417 Task 16 - Configure PFE key (optional) Task 17 - Configure management server lasers, compliance statement (optional) LCD panel Task 18 - Set product date and time configure private server network addresses Task 19 - Configure the Element Manager application configure public server network addresses Task 2 - Unpack, inspect, and install the Ethernet hub (optional)
  • Page 418 external configure PFE key EFCM Basic Edition EFCM Basic Edition SAN management application Element Manager internal network address, product status log EFCM Basic Edition network information performing configure director EFCM Basic Edition maintenance port configure management server MAC address, director nonconcurrent FRUs table maintenance analysis procedures NPIV...
  • Page 419 configure at management server Element Manager customer-level director 23, port card default 156, internal loopback test management server LCD panel operational states default EFCM Basic Edition port fencing default maintenance port 53, configure default SAN management application 66, 91, SAN management application 201, description default TightVNC 57, 90, 201,...
  • Page 420 preferred path remove and replace procedures configure See RRPs Element Manager repair procedures configure PFE key IML, IPL, or reset the director repair EFCM Basic Edition procedures description IML, IPL or reset the director preventive maintenance, cleaning fiber-optic install or upgrade software components repair procedures, notes procedural notes...
  • Page 421 information SAN management application repair procedures Enterprise Fabric Mode fiber-optic protective plug SANtegrity authentication laser compliance SANtegrity binding SAN management application segmented E_Port default description password 66, 91, fault isolation user name 66, 91, serial numbers, FRUs, hardware log default password serviceability features, director default user name setting...
  • Page 422 enable SBAR assembly EFCM Basic Edition SFP optical transceiver Element Manager supplied by service personnel switch fabric log supplied with director switch priority 38, UPM card system error LED UPM filler panel system events XPM card event codes XPM filler panel system services processor torque tool caution...
  • Page 423 power supply XFP optical transceiver XPM card description weight, director LEDs 9, wet-bulb temperature loopback test, performing operating environment ports, blocking or unblocking shipping and storage environment removing and replacing Windows XPM filler panel, removing and replacing configure users default password 58, 91, user name 58, 91, zone sets...
  • Page 424 SAN140M Installation and Service Manual...
  • Page 425 Thank you for your responses. May we contact you? h Yes h No When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any way it believes appropriate without incurring any obligation to you. Name...
  • Page 426 Readers’ Comments — We’d Like to Hear from You Cut or Fold Along Line GC26-7664-04 Fold and Tape Please do not staple Fold and Tape _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ NO POSTAGE NECESSARY IF MAILED IN THE...
  • Page 428 Printed in USA GC26-7664-04...

Table of Contents