Intrepid® 6140 Director Installation and Service Manual P/N 620-000157-420 REV A 380 Interlocken Crescent Broomfield, CO 80021-3464 Corporate Headquarters: 800-545-5773 Sales E-mail: sales@mcdata.com Web: www.mcdata.
Record of Revisions and Updates Revision Date Description 620-000157-000 9/2002 Initial release of the manual 620-000157-100 10/2002 Updates to describe Release 6.2 and 6.3 of the Enterprise Fabric Connectivity Manager application. 620-000157-200 2/2003 Updates to describe Release 7.1 of the Enterprise Fabric Connectivity Manager application. New cover and new format. 620-000157-201 6/2003 Updates to describe new firmware and software download procedures from McDATA’s home page.
Seventh Edition No part of this publication may be reproduced or distributed in any form or by any means, or stored in a database or retrieval system, without prior written consent of McDATA Corporation. The information contained in this document is subject to change without notice. McDATA Corporation assumes no responsibility for any errors that may appear.
iv Intrepid® 6140 Director Installation and Service Manual
Contents Preface.......................................................................................................................... xvii Chapter 1 General Information Director Description .........................................................................1-1 Field-Replaceable Units ...................................................................1-4 Power/System LED Assembly ................................................1-5 CTP Card.........................................................
Contents Unpack and Inspect Ethernet Hub .........................................2-6 Desktop Installation ..................................................................2-6 Rack-Mount Installation ...........................................................2-8 Task 3: Unpack, Inspect, and Install the Director.........................2-9 Task 4: Configure Director at the EFCM Basic Edition Interface (Optional).........................................................................................
Contents Task 17: Configure Management Server (Optional).................. 2-53 Task 18: Set Director Date and Time............................................ 2-54 Task 19: Configure the Element Manager Application............. 2-55 Configure Director Identification ......................................... 2-56 Configure Director Parameters ............................................. 2-56 Configure Fabric Parameters................................................. 2-58 Configure Ports .................
Contents Port LED Diagnostics..............................................................4-11 Element Manager Application Diagnostics .........................4-12 EFCM Basic Edition Diagnostics ...........................................4-17 Performing Loopback Tests...........................................................4-21 Internal Loopback Test (Element Manager Application) ..4-21 External Loopback Test (Element Manager Application) .4-23 Internal Loopback Test (EFCM Basic Edition) ..............
Contents Reset Configuration Data (EFCM Basic Edition) ............... 4-55 Chapter 5 Removal and Replacement Procedures (RRPs) Factory Defaults ........................................................................ 5-1 Procedural Notes....................................................................... 5-2 Removing and Replacing FRUs ..................................................... 5-3 ESD Information........................................................................ 5-3 Concurrent FRUs..
Contents Appendix C Management Server and Ethernet Hub Management Server Description................................................... C-1 Management Server Specifications ........................................ C-2 Ethernet Hub Description .............................................................. C-2 Appendix D Restore Management Server Requirements ...................................................................................D-1 Restore Management Server Procedure .........................
Figures 1-1 1-2 1-3 1-4 1-5 1-6 1-7 1-8 1-9 1-10 1-11 1-12 Cabinet-Mounted Intrepid 6140 Directors and Management Server ... 1-3 Director FRUs (Front Access) ..................................................................... 1-4 Director FRUs (Rear Access) ....................................................................... 1-5 UPM Card LEDs and Connectors .............................................................. 1-8 XPM Card LEDs and Connectors .................................................
Figures xii 2-17 2-18 2-19 2-20 2-21 2-22 2-23 2-24 2-25 2-26 2-27 2-28 2-29 2-30 2-31 2-32 2-33 2-34 2-35 2-36 2-37 Identification Changes Dialog Box ........................................................... 2-40 Internet Protocol (TCP/IP) Properties Dialog Box ................................. 2-41 Add New User Wizard ............................................................................... 2-43 Properties Dialog Box (General Tab) ........................................................
Figures 4-18 4-19 4-20 4-21 4-22 4-23 Backup and Restore Configuration Dialog Box ..................................... Reset Configuration Dialog Box ............................................................... Discover Setup Dialog Box ........................................................................ Address Properties Dialog Box ................................................................ Backup Configuration View .....................................................................
Figures xiv Intrepid® 6140 Director Installation and Service Manual
Tables 1-1 Element Manager Alert Symbols, Messages, and Status ...................... 1-14 2-1 2-2 2-3 2-4 Factory-Set Defaults (Director) ................................................................... 2-1 Factory-Set Defaults (Management Server) .............................................. 2-2 Installation Task Summary ......................................................................... 2-3 Operational States and Symbols ...............................................................
Tables xvi 5-3 Nonconcurrent FRU ...................................................................................... 5-5 6-1 6-2 6-3 6-4 6-5 Front-Accessible FRU Parts List .................................................................. 6-3 Rear-Accessible FRU Parts List (Part 1) ..................................................... 6-5 Rear-Accessible FRU Parts List (Part 2) ..................................................... 6-6 Miscellaneous Parts ............................................
Preface This publication is part of a documentation suite that supports the McDATA® Intrepid® 6140 (ED-6140) Director. Who Should Use This Manual This publication is intended for use by installation and service representatives experienced with the director, storage area network (SAN) technology, and Fibre Channel technology. Organization of This Manual This publication includes six chapters and four appendices organized as follows: Chapter 1, General Information.
Preface Chapter 3, Maintenance Analysis Procedures (MAPS). This chapter describes maintenance analysis procedures (MAPs) to fault isolate a director problem to an individual FRU. Chapter 4, Repair Information. This chapter describes supplementary diagnostic and repair procedures for a failed director.
Preface Related Publications Ordering Printed Manuals Other publications that provide additional information about the director include: • McDATA Products in a SAN Environment Planning Manual (620-000124). • McDATA Intrepid 6140 and 6064 Directors Element Manager User Manual (620-000153). • McDATA Enterprise Fabric Connectivity Manager User Manual (620-005001). • McDATA EFCM Basic Edition User Manual (620-000240). • McDATA SNMP Support Manual (620-000131).
Preface Forwarding Publication Comments We welcome comments about this publication. Please send comments to the McDATA Solution Center by telephone, fax, or e-mail. The numbers and e-mail address are listed above. Please identify the manual, page numbers, and details. Trademarks The following terms, indicated by a registered trademark symbol (®) or trademark symbol (™) on first use in this publication, are trademarks of McDATA Corporation or SANavigator, Inc.
Preface measures are required to correct the interference. Any modifications or changes made to the ED-6140 without explicit approval from McDATA, by means of a written endorsement or through published literature, will invalidate the service contract and void the warranty agreement with McDATA.
Preface Dangers and Cautions The following DANGER statements appear in this publication and describe safety practices that must be observed while installing or servicing the director. A DANGER statement provides essential information or instructions for which disregard or noncompliance may result in death or severe personal injury. DANGER Use the supplied power cords. Ensure the facility power receptacle is the correct type, supplies the required voltage, and is properly grounded.
1 General Information The McDATA® Intrepid® 6140 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 (2 or 10 gigabits per second), redundant switched data paths, and long transmission distances. This chapter presents information and features of the director and its management, including: • Director description. • Field-replaceable units (FRUs).
General Information 1 computing environments, and provides data transmission and flow control between device node ports (N_Ports) as dictated by the Fibre Channel Physical and Signaling Interface (FC-PH 4.3). Through interswitch links (ISLs), the director can also connect to one or more additional directors to form a Fibre Channel multiswitch fabric.
General Information 1 Figure 1-1 Cabinet-Mounted Intrepid 6140 Directors and Management Server Director Description 1-3
General Information 1 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 1-2) include the: Figure 1-2 • Universal port module (UPM) cards (2 Gbps). • 10 Gbps port module (XPM) cards. • Control processor (CTP) cards.
General Information 1 Figure 1-3 Power/System LED Assembly Director FRUs (Rear Access) 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 illuminates when the director is powered on and operational.
General Information 1 When the IML button is pressed, held for three seconds, and released, the director performs an IML that reloads the firmware from FLASH memory. This operation is not disruptive to Fibre Channel traffic. When the RESET button is pressed and held for three seconds, the director performs a reset. A reset is disruptive and resets the: • Microprocessor and functional logic for the CTP card and reloads the firmware from FLASH memory.
General Information 1 card fails. Both LEDs are extinguished on an operational backup card. The amber LED blinks if FRU beaconing is enabled. UPM Card Each UPM card (Figure 1-4) provides four full-duplex generic ports (G_Ports) that transmit or receive data at 2 gigabits per second (Gbps). G_Port functionality depends on the type of cable attachment.
General Information 1 Figure 1-4 XPM Card 1-8 UPM Card LEDs and Connectors Each XPM card (Figure 1-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. • Amber and green LEDs that indicate port status similar to the LEDs on the UPM cards (UPM Card on page 1-7).
General Information 1 Figure 1-5 XPM Card LEDs and Connectors SFP and XFP Transceivers Singlemode or multimode fiber-optic cables attach to director ports through 2 Gbps small form-factor pluggable (SFP, Figure 1-6 - for UPM cards) or 10 Gbps form-factor pluggable (XFP, Figure 1-7 - for XPM cards) optic transceivers. The fiber-optic transceivers provide duplex LC® connectors and can be detached from director ports for easy replacement. NOTE: SFP and XFP transceivers are not interchangeable.
General Information 1 Power Supply 1-10 Figure 1-6 Small Form-Factor Pluggable (SFP) transceiver Figure 1-7 Ten Gbps Form-Factor Pluggable (XFP) Transceiver 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.
General Information 1 Each power supply has a separate backplane connection to allow for different AC power sources. The power supplies are input rated at 180 to 264 volts alternating current (VAC). The faceplate of each power supply provides the following status LEDs: AC Module Fan Module • A green AC OK LED illuminates if the power supply is operational and receiving AC power. • A green DC OK LED illuminates if the power supply is operational and producing DC power.
General Information 1 transmission without interruption. Failover to the backup assembly is transparent to attached devices. Each SBAR assembly consists of a card and steel carriage that mounts flush on the backplane. The carriage provides protection for the back of the card, distributes cooling airflow, and assists in aligning the assembly during installation.
General Information 1 • An RS-232 maintenance port at the rear of the director (port access is password protected) that enables installation or service personnel to change the director’s internet protocol (IP) address, subnet mask, and gateway address; or to run diagnostics and isolate system problems through a local or remote terminal.
General Information 1 • SNMP management using the Fibre Channel Fabric Element MIB (Version 1.1), transmission control protocol/internet protocol (TCP/IP) MIB-II definition (RFC 1157), or a product-specific private enterprise MIB that runs on each director. Up to six authorized management workstations can be configured through the Element Manager application or EFCM Basic Edition interface to receive unsolicited SNMP trap messages.
General Information 1 Table 1-1 Element Manager Alert Symbols, Messages, and Status (continued) Symbol Message Description Loading firmware The system is busy loading new firmware, but the system is otherwise operational. Not operational A critical failure has occurred that prevents the director from performing fundamental switching operations. o Link time-out o Protocol mismatch o Never connected Director status is unknown.
General Information 1 Figure 1-8 Torque Tool and Hex Adapter • Figure 1-9 Door Key • Figure 1-10 Loopback plug - An SFP multimode (shortwave laser) or singlemode (longwave laser) loopback plug (Figure 1-10) is required to perform port loopback diagnostic tests. One loopback plug is shipped with the director, depending on the type of port transceivers installed. Both plugs are shipped if shortwave laser and longwave laser transceivers are installed.
General Information 1 Figure 1-11 Fiber-Optic Protective Plug • Figure 1-12 Tools Supplied by Service Personnel Null modem cable - An asynchronous RS-232 null modem cable (Figure 1-12) is required to configure director network addresses and acquire event log information through the maintenance port. The cable has nine conductors and DB-9 male and female connectors.
General Information 1 • Maintenance terminal (desktop or notebook PC) - The PC is required to configure director network addresses and acquire event log information through the maintenance port. The PC must have: — The Microsoft Windows 98, Windows 2000, Windows XP, or Millennium Edition operating system installed. — RS-232 serial communication software (such as ProComm Plus™ or HyperTerminal) installed. HyperTerminal is provided with Windows operating systems.
General Information 1 • 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. Administrators can assign internet protocol (IP) addresses and corresponding community names for up to 12 SNMP workstations functioning as SNMP trap message recipients. Refer to the McDATA SNMP Support Manual (620-000131).
General Information 1 1-20 Intrepid® 6140 Director Installation and Service Manual
2 Installation Tasks This chapter describes tasks to install, configure, and verify operation of the Intrepid 6140 Director using a storage area network (SAN) management application or the EFCM Basic Edition interface. The director can be installed in a Fabricenter equipment cabinet, in any standard 19-in equipment rack, or mounted on a table top. Factory Defaults Table 2-1 lists factory-set defaults for the director.
Installation Tasks 2 Table 2-2 lists factory-set defaults for the management server (running a SAN management application).
Installation Tasks 2 Installation Task Summary Table 2-3 summarizes the installation tasks for the director, optional management server, and optional Ethernet hub. The table describes each task, states if the task is optional, and lists the page reference. Table 2-3 Installation Task Summary Task Number and Description Required or Optional Page Task 1: Verify Installation Requirements Required.
Installation Tasks 2 Table 2-3 2-4 Installation Task Summary (continued) Task Number and Description Required or Optional Task 18: Set Director Date and Time Required if management server is used. 2-54 Task 19: Configure the Element Manager Application Required if management server is used. 2-55 Task 20: Back Up Configuration Data Required if management server is used. 2-70 Task 21: Cable Fibre Channel Ports Required.
Installation Tasks 2 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 McDATA Products in a SAN Environment - Planning Manual (620-000124). • Fibre Channel SAN design is complete. Refer to the McDATA Products in a SAN Environment - Planning Manual (620-000124).
Installation Tasks 2 • An Internet connection to a browser-capable PC (EFCM Basic Edition interface). Connection of a LAN segment with multiple products to the Internet may require installation of a 24-port Ethernet hub. Follow the instructions in Unpack and Inspect Ethernet Hub below to unpack, inspect, and install the Ethernet hub, but: • If the existing Ethernet LAN segment is adequate for connectivity and a hub is not delivered, this task is not required.
Installation Tasks 2 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. c. As shown in use a pointed instrument to set the medium-dependent interface (MDI) switch on the top and middle hubs to MDI (in) (Figure 2-1, 1 and 2).
Installation Tasks 2 Rack-Mount Installation Perform the following steps to install and configure up to three Ethernet hubs in a Fabricenter 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. Secure one mounting bracket to each side of the first hub (Figure 2-2). Use the two brackets and four pan-head Phillips screws (8/32 x 0.5-inch) provided.
Installation Tasks 2 c. As shown in use a pointed instrument to set the medium-dependent interface (MDI) switch on the top and middle hubs to MDI (in) (Figure 2-1, 1 and 2). Set the MDI switch on the bottom hub to MDIX (out) (Figure 2-1, 3). NOTE: To connect two hubs, follow step b and step c (middle and bottom hub) instructions. 6. Connect a power cord to a rack power strip and the receptacle at the rear of each hub.
Installation Tasks 2 3. Locate the rack-mount position. The director is 20 inches (12 U) high. 4. Verify all FRUs, including the SFP and XFP optical transceivers, logic cards, fans, and power supplies are installed as ordered. 5. Open the rack-mount kit and inspect the contents. Refer to the enclosed bill of materials and verify all parts are delivered. 6. Using installation instructions delivered with the rack-mount kit and a #2 Phillips screwdriver, install the director in the equipment cabinet.
Installation Tasks 2 10. Power on the rack power strips. 11. Inspect the front panel of each rack-mounted Ethernet hub. Ensure each green Power LED illuminates. 12. The director powers on and performs POSTs. During POSTs: — Amber LEDs on both CTP cards and all port cards illuminate momentarily. — The green LED on each CTP card (active and backup) and each port card illuminate as the card is tested. — Green LEDs associated with Fibre Channel ports sequentially illuminate as the ports are tested. 13.
Installation Tasks 2 2. Connect the remaining end of the Ethernet cable to the Internet or LAN segment as directed by the customer. If the hub installed in Task 2: Unpack, Inspect, and Install the Ethernet Hub (Optional) provides connectivity, connect the cable to any available hub port. 3. At the PC, launch the browser application (Internet Explorer or Netscape Navigator). 4. Enter the default Internet Protocol (IP) address of the director (10.1.1.10) as the uniform resource locator (URL).
Installation Tasks 2 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 Switch and Identification from the Configure menu at any view. The Identification View displays (Figure 2-4). a.
Installation Tasks 2 1. Select Switch and Date & Time from the Configure menu at any view. The Date Time View displays (Figure 2-5). a. Click Date fields that require change, and type numbers in the following ranges: • Month (MM): 1 through 12. • Day (DD): 1 through 31. • Year (YYYY): greater than 1980. b. Click Time fields that require change, and type numbers in the following ranges: • Hour (HH): 0 through 23. • Minute (MM): 0 through 59. • Second (SS): 0 through 59. 2.
Installation Tasks 2 Figure 2-6 Parameters View a. At the Insistent Domain ID field, check (enable) or uncheck the parameter. When enabled, the value configured in the Preferred Domain ID field becomes the active domain ID when the fabric initializes. 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.
Installation Tasks 2 g. At the Preferred Domain ID field, type a value between 1 through 31. This value uniquely identifies each fabric element. NOTE: An ISL between fabric elements with identical domain IDs segments and prevents communication. h. At the ISL FSPF Cost Configuration field, select Default or Equal. to calculate fabric shortest path first (FSPF) cost. • By Port Speed - The fastest fabric path is determined by port (ISL) speed. FSPF cost is inversely proportional to ISL speed.
Installation Tasks 2 a. At the R_A_TOV field, type a value between 10 through 1200 tenths of a second (one through 120 seconds). Ten seconds (100) is the recommended value. The R_A_TOV value must exceed the E_D_TOV value. b. At the E_D_TOV field, type a value between 2 through 600 tenths of a second (0.2 through 60 seconds). Two seconds (20) is the recommended value. NOTE: Fabric elements must be set to the same R_A_TOV and E_D_TOV values.
Installation Tasks 2 Configure Network Information Verify the LAN installation with the network administrator. • If one director is installed on a dedicated LAN, network information (IP address, subnet mask, and gateway address) does not require change. • If multiple directors are installed or a public LAN segment is used, network information must be changed to conform to the LAN addressing plan. Perform this procedure to change director network information. 1.
Installation Tasks 2 3. Update the address resolution protocol (ARP) table for the browser PC. a. Close the EFCM Basic Edition interface and all browser applications. b. At the Windows desktop, click Start at the left side of the task bar. The Windows Workstation menu displays. c. At the Windows Workstation menu, sequentially select the Programs and Command Prompt options. A disk operating system (DOS) window displays. d. Delete the director old IP address from the ARP table.
Installation Tasks 2 c. Click the check box in the FAN column to enable or disable the fabric address notification (FAN) feature (default is enabled). A check mark in the box indicates FAN is enabled. When the feature is enabled, the port transmits FAN frames after loop initialization to verify that FC-AL devices are still logged in. d. Select from the drop-down list in the Type column to configure the port type.
Installation Tasks 2 2. Select Ports and RX BB_Credit from the Configure menu at any view. The RX BB_Credit View displays. 3. Perform one of the following: — To set all offline ports to default values, click Default. — To set an offline port to a user-specified value, type the desired value in the RX BB_Credit column. 4. Click OK to save and activate changes. 5. Set ports online (Blocking and Unblocking Ports on page 4-27 ).
Installation Tasks 2 Figure 2-10 SNMP View a. Click Enable to activate the installed SNMP agent. b. Select the Fibre Alliance management information base (FA MIB) from the FA MIB Version drop-down list. Valid selections are FA MIB Version 3.0 or FA MIB Version 3.1. 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.
Installation Tasks 2 Enable CLI Perform this procedure to toggle (enable or disable) the state of the director command line interface (CLI). To change the CLI state: 1. Select CLI from the Configure menu at any view. The CLI View displays (Figure 2-11). 2. Perform one of the following: • Click Enable to activate the CLI. • Click Disable to deactivate the CLI. 3. Check the Use SSH check box to enable secure shell (SSH) protocol.
Installation Tasks 2 • Click Disable to deactivate OSMS. 3. Check the Enable Host Control check box to activate host control of the director. 4. Click OK to save and activate changes. Figure 2-12 OSMS View 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.
Installation Tasks 2 4. To define the expiration period (in days) of the digital certificate, type a value between 30 and 3650 in the Expires in field. The default is 365 days. Click Generate to generate a new certificate. 5. To define a renegotiation parameter (in megabytes) for the SSL session key, type a value between 50 and 10000 in the Renegotiate after field. The value defines the MB of data transmitted over the connection before triggering the regeneration of a new SSL session key.
Installation Tasks 2 • Flexport Technology - A Flexport Technology product is delivered at a discount without all Fibre Channel ports enabled. When additional port capacity is required, the remaining ports are incrementally enabled through this feature. • Full volatility - This feature ensures no Fibre Channel frames are stored after the director is powered off or fails, and a memory dump file (that possibly includes classified data frames) is not included as part of the data collection procedure.
Installation Tasks 2 Feature status is indicated by a green check mark (installed) or a red (uninstalled). Flexport Technology status is indicated by the number of installed ports. Click a feature title in the Feature panel and a description appears in the Feature Details panel. 2. Type the key in the Feature Key field and click Update. The interface refreshes and indicates the update changes in the Feature panel. NOTE: When OK is selected, all features are updated with new features. 3. Click OK.
Installation Tasks 2 Figure 2-14 Maintenance Feature Installation View Configure Security This section describes optional director security features configured through Security menu selections. The enhanced SANtegrity PFE keys (SANtegrity authentication and SANtegrity binding) must be installed (Install PFE Keys (Optional) on page 2-25).
Installation Tasks 2 — 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. — Port settings - Use this page to override director-level authentication settings and enable or disable device communication on a per-port basis.
Installation Tasks 2 • 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. • Preferred path - Use the Preferred Path View to specify and configure one or more ISL data paths between multiple fabric elements. At each fabric element, a preferred path consists of a source port, exit port, and destination Domain_ID.
Installation Tasks 2 Verify the LAN installation with the customer. If one director is installed on a dedicated LAN, network addresses do not require change. Go to Task 6: Unpack, Inspect, and Install the Management Server on page 2-34. If multiple products are installed or a public LAN segment is used, network addresses must be changed to conform to the customer LAN addressing plan. Perform the following steps to change a product IP address, subnet mask, or gateway address.
Installation Tasks 2 Figure 2-15 Connection Description Dialog Box 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. 7. Configure Port Settings parameters: — Bits per second - 115200. — Data bits - 8. — Parity - None. — Stop bits - 1. — Flow control - Hardware or None.
Installation Tasks 2 — 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. To change the addresses, type the following at the C > prompt and press Enter. ipconfig xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy zzz.zzz.zzz.zzz The IP address is xxx.xxx.xxx.
Installation Tasks 2 — If the director is delivered separately from the management server, go to Task 6: Unpack, Inspect, and Install the Management Server following. — If the director is delivered as part of a Fabricenter equipment cabinet, go to Task 7: Configure Server Password and Network Addresses on page 2-36. Task 6: Unpack, Inspect, and Install the Management Server The management server is a rack-mount unit with SAN management and Element Manager applications installed.
Installation Tasks 2 4. Connect the server to the Ethernet LAN segment or Ethernet hub (private LAN interface): a. Connect one end of the Ethernet patch cable (supplied) to the right RJ-45 adapter (LAN 2) at the rear of the server (Figure 2-16). Figure 2-16 1U Management Server Connections b. Connect the remaining end of the Ethernet cable to the LAN: • If the server is installed on a LAN segment, connect the cable to the LAN as directed.
Installation Tasks 2 8. When the power cord is connected, the server powers on and performs power-on self-tests (POSTs). During POSTs: a. The green liquid crystal display (LCD) panel illuminates. b. The green hard disk drive (HDD) LED blinks momentarily, and processor speed and random-access memory information display momentarily at the LCD panel. c. After a few seconds, the LCD panel displays a Boot from LAN? Press message. d. Ignore the message.
Installation Tasks 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 password (9999), and press ENTER. A LAN 1 Setting?? message appears at the LCD panel. 3. Press the down-arrow button several times until the Change Password? option appears at the LCD panel, then press ENTER. A New Password 0**** message appears. 4. Input a new 4-digit numeric password, then press ENTER.
Installation Tasks 2 Configure Public LAN Addresses (Optional) To optionally configure TCP/IP network information for the public LAN connection (LAN 1): 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. 3. Press ENTER and the default IP address of 192.168.0.1. appears. 4.
Installation Tasks 2 2. At the PC, enter the LAN 2 IP address of the server, followed by :5800, as the Internet uniform resource locator (URL). Use the following format: http://xxx.xxx.xxx.xxx:5800 Where xxx.xxx.xxx.xxx is the default IP address of 10.1.1.1 or the IP address configured while performing Task 7: Configure Server Password and Network Addresses on page 2-36. The VNC Authentication screen displays. 3. Type the default password and click OK. The Welcome to Windows dialog box displays.
Installation Tasks 2 4. At the Computer Name field, change the name to MGMTSERVER. Click (select) the Workgroup radio button, change the name to WORKGROUP, and click OK. The dialog box closes. 5. Record the computer and workgroup names for reference. 6. Close all dialog boxes and return to the Windows desktop.
Installation Tasks 2 Figure 2-18 Internet Protocol (TCP/IP) Properties Dialog Box 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 7: Configure Server Password and Network Addresses on page 2-36. 6. At the Default gateway field, enter the gateway address obtained from the customer. 7. Select (enable) the Use the following DNS server addresses radio button.
Installation Tasks 2 Task 9: 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. The Users and Passwords dialog box displays. 2.
Installation Tasks 2 4. Select the Standard user, Restricted user, or Other radio button. If the Other radio button is selected, choose the type of access from the adjacent list box. 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. Figure 2-19 Add New User Wizard Change User Properties To change existing user properties: 1.
Installation Tasks 2 5. If no other users will be changed, close all dialog boxes and return to the Windows desktop. Figure 2-20 Properties Dialog Box (General Tab) Task 10: 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.
Installation Tasks 2 Figure 2-21 Date/Time Properties Dialog Box (Time Zone Tab) 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. c. Click Apply. Record time zone and daylight savings information for reference. 4. Click the Date & Time tab.
Installation Tasks 2 Figure 2-22 Date/Time Properties Dialog Box (Date & Time Tab) Task 11: Configure the Call-Home Feature (Optional) The management server has an optional call-home feature that provides automatic dial-out through the internal modem to a service support facility to report director problems. The problem is logged into the support facility tracking system for resolution. To configure the call-home feature: 1.
Installation Tasks 2 Task 12: Assign User Names and Passwords In addition to password access for the Windows operating system, users must be configured for SAN management application access. To assign application user names and passwords: 1. At the Windows desktop, open the SANavigator Log In or EFCM Log In dialog box . 2. Type the SAN management application default user ID and password and select a server or IP address from the Network Address drop-down list.
Installation Tasks 2 • User ID - Type a unique user ID for the new user. • Secure password - Type a password up to 16 alphanumeric characters in length. Control characters and spaces are not valid. The password is case-sensitive. • Retype Password - To confirm the password, enter the password exactly as in the Secure Password field. 7. To enable e-mail notification for the new user, select (click) the Enable check box. An unchecked box indicates e-mail notification is not enabled. 8.
Installation Tasks 2 Figure 2-24 Address Properties Dialog Box (IP Address Page) Task 14: 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 D, Restore Management Server). Record or verify the following information: 1.
Installation Tasks 2 • 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. Verify user passwords and other information were recorded (during Task 9: Configure Windows Operating System Users). 3. Verify date and time information was recorded (during Task 10: Set Management Server Date and Time). a. Verify the time zone was recorded. b.
Installation Tasks 2 Table 2-4 Operational States and Symbols Operational State Status Symbol Operational - Communication is established, the product is operational, and no failures are indicated. Go to Task 16: Configure PFE Key (Optional) on page 2-51. No status symbol Degraded - Communication is established, but the product is operating in degraded mode and requires service. This condition is typical if a port or redundant FRU fails. Go to step 2.
Installation Tasks 2 During the grace period, a No Feature Key dialog box appears when the Element Manager application opens. Click OK to close the dialog box and use the application. In addition, the message Element Manager license key has not been installed - Please follow up instructions to update permanent key appears splashed across all views.
Installation Tasks 2 Figure 2-25 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. The operation is nondisruptive to Fibre Channel traffic. Do you wish to continue? 5.
Installation Tasks 2 Task 18: 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 2-26). Date and time can be set manually, or set to be periodically updated by the SAN management application (the director and application synchronize at least once daily).
Installation Tasks 2 • 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). Date and Time fields are greyed out and not selectable. Perform one of the following: • Click Activate to enable synchronization and close the dialog box.
Installation Tasks 2 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 2-27). a.
Installation Tasks 2 2. Select Operating Parameters and Switch Parameters from the Configure menu at any view. The Configure Switch Parameters dialog box displays (Figure 2-28). Figure 2-28 Configure Switch Parameters Dialog Box a. At the Preferred Domain ID field, type a value between 1 through 31. This value uniquely identifies each fabric element. NOTE: An ISL between fabric elements with identical domain IDs segments and prevents communication. b.
Installation Tasks 2 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. Set the director online (Setting the Director Online or Offline on page 4-36). Configure Fabric Parameters Perform this procedure to configure fabric operating parameters. 1.
Installation Tasks 2 b. At the E_D_TOV field, type a value between 2 through 600 tenths of a second (0.2 through 60 seconds). NOTE: If the switch is attached to a fabric element, the switch and element must be set to the same E_D_TOV value. If the values are not identical, the E_Port connection to the element segments and the switch cannot communicate with the fabric. In addition, the E_D_TOV value must be less than the R_A_TOV value. c.
Installation Tasks 2 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 2-30). Figure 2-30 Configure Ports Dialog Box a. For each port to be configured, type a port name of 24 alphanumeric characters or less in the associated Name field. The port name should characterize the device to which the port is attached. b. The director provides a port buffer pool of 150 receive BB_Credits.
Installation Tasks 2 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. Available selections are auto-negotiate between 1.0625 and 2.1250 Gbps operation (Negotiate), 1.0625 Gbps operation (1 Gb/sec), and 2.
Installation Tasks 2 Figure 2-31 Configure SNMP Dialog Box 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. Valid selections are FA MIB Version 3.0 or FA MIB Version 3.1. c. For each configured recipient, type a community name of 32 alphanumeric characters or less in the Community Name field.
Installation Tasks 2 • 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. If alerts are configured, they display in table format showing the alert name, type, and state. 2. Click New.
Installation Tasks 2 Figure 2-33 New Threshold Alert Dialog Box (Screen 2) 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. Select the At any time radio button to specify that an alert occur when the % utilization is reached.
Installation Tasks 2 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 2-34 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. To enable the functions: 1.
Installation Tasks 2 2. At the SANavigator or EFCM main window, select Event Notification and Email from the Monitor menu. The Email Event Notification Setup dialog box displays (Figure 2-35). Figure 2-35 Email Event Notification Setup Dialog Box 3. To enable e-mail transmission to configured addresses, click the Enable Email Event Notification check box. A check mark appears when transmission is enabled. 4. Type the IP address or DNS host name of the SMTP server in the E-mail Server field. 5.
Installation Tasks 2 11. Click Send Test Email. A test message is sent to configured recipients. 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. NOTE: The enable function must be activated for each product through the Element Manager application.
Installation Tasks 2 1. Minimize the Element Manager application and return to the SAN management application. 2. At the SANavigator or EFCM main window, select Event Notification and Call Home from the Monitor menu. The Call Home Event Notification Setup dialog box displays. 3. Click the Enable Call Home Event Notification check box. A check mark appears to indicate call-home event notification is enabled.
Installation Tasks 2 — IP Access Control - Configure a list of device IP addresses or a range of device IP addresses authorized to communicate with the product. — RADIUS Servers - Configure RADIUS servers. A RADIUS server stores and authenticates passwords and CHAP secrets. • 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.
Installation Tasks 2 • Preferred path - Use the Preferred Path option from the Configure menu (Element Manager application) to specify and configure one or more ISL data paths between multiple fabric elements. At each fabric element, a preferred path consists of a source port, exit port, and destination Domain_ID.
Installation Tasks 2 and verified while performing Task 14: Record or Verify Server Restore Information. To back up server configuration data and create a base restore CD: 1. Insert a blank rewritable CD into the CD-RW drive and format the CD: a. At the Windows desktop, locate the InCD icon (1) at the right side of the task bar (Figure 2-36). The icon is indicated by a red down arrow. b. Right-click the icon and select Format (F). The first window of the InCD wizard displays. c.
Installation Tasks 2 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. After the management server reboots, click Login again. The VNC Authentication screen displays. d. Type the default password and click OK. The Welcome to Windows dialog box displays.
Installation Tasks 2 Task 21: Cable Fibre Channel Ports Perform this task to cable Fibre Channel ports and connect devices: 1. Route fiber-optic jumper cables from Fibre Channel devices, FC-AL devices, or fabric elements to director ports. 2. Connect device cables to optical port transceivers as directed by the customer. 3.
Installation Tasks 2 • A zone set name cannot contain spaces. • Valid characters are alphanumerics and the caret ( ^ ), hyphen ( - ), underscore ( _ ), or dollar ( $ ) symbols. • A zone set name can have a maximum of 64 characters. If the installation is performed from the EFCM Basic Edition interface, refer to the McDATA EFCM Basic Edition User Manual (620-000240) for instructions. If the installation is performed from the management server, refer to the SANavigator Software Release 4.
Installation Tasks 2 — If the values must be changed from the management server, refer to Task 19: Configure the Element Manager Application on page 2-55. 4. Route a multimode or singlemode fiber-optic cable (depending on the type of transceiver installed) from an E_Port of the fabric element to the front of the director. 5. Connect the fiber-optic cable to a director port as directed by the customer. 6. If the director is managed through the management server, go to step 7.
Installation Tasks 2 • Technical publications. • Firmware and software upgrades. • Technical newsletters. • Release notes. To register with the Filecenter: 1. At the server with Internet access, open the McDATA home page (http://mcdata.com). Select File Center from the Support menu. The Filecenter home page opens (Figure 2-37). Figure 2-37 McDATA Filecenter Home Page 2. Select (click) the New User Registration option at the top of the home page.
Installation Tasks 2 3. Complete fields as required and click Register. The registration is complete and Filecenter login information is transmitted to the e-mail address specified. 4. At the browser PC, close the Internet session. If no director problems are indicated, installation tasks are complete.
Installation Tasks 2 2-78 Intrepid® 6140 Director Installation and Service Manual
3 Maintenance Analysis Procedures (MAPS) This chapter describes maintenance analysis procedures (MAPs) used by service representatives to fault isolate Intrepid 6140 Director problems or failures to the field-replaceable unit (FRU) level. MAPs provide information to interpret system events and isolate a failure to a FRU.
Maintenence Analysis Procedures Quick Start Table 3-2 lists and summarizes MAPs. Fault isolation normally begins at MAP 0000: Start MAP.
Maintenence Analysis Procedures Table 3-3 Event Code Event Codes versus Maintenance Action (Continued) Explanation Action 060 Fabric controller unable to synchronize databases. Go to MAP 0600. 061 Fabric Controller database invalid. Go to MAP 0600. 062 Maximum interswitch hop count exceeded. Go to MAP 0600. 063 Remote switch has too many ISLs. Go to MAP 0600. 064 ESS response from indicated domain ID not received after maximum tries. No action required. 070 E_Port is segmented.
Maintenence Analysis Procedures Table 3-3 Event Code 3-4 Event Codes versus Maintenance Action (Continued) Explanation Action 151 Fabric configuration failure. Go to Collecting Maintenance Data on page 4–32. 200 Power supply AC voltage failure. Go to MAP 0100. 201 Power supply DC voltage failure. Go to MAP 0100. 202 Power supply thermal failure. Go to MAP 0100. 203 Power supply AC voltage recovery. No action required. 204 Power supply DC voltage recovery. No action required.
Maintenence Analysis Procedures Table 3-3 Event Code Event Codes versus Maintenance Action (Continued) Explanation Action 410 CTP card reset. No action required. 411 Firmware fault. Go to MAP 0200. 412 CTP watchdog timer reset. Go to Collecting Maintenance Data on page 4–32. 413 Backup CTP card POST failure. Go to MAP 0200. 414 Backup CTP card failed. Go to MAP 0400. 415 Backup CTP card removed. Replace FRU. 416 Backup CTP card installed. No action required.
Maintenence Analysis Procedures Table 3-3 Event Code 3-6 Event Codes versus Maintenance Action (Continued) Explanation Action 453 New feature key installed. No action required. 500 Port card hot-insertion initiated. No action required. 501 Port card recognized. No action required. 502 Port module anomaly detected. No action required. 503 Port card hot-removal completed. No action required. 504 Port module card failure. Go to MAP 0500. 505 Port module revision not supported.
Maintenence Analysis Procedures Table 3-3 Event Code Event Codes versus Maintenance Action (Continued) Explanation Action 600 SBAR assembly hot-insertion initiated. No action required. 601 SBAR assembly recognized. No action required. 602 SBAR assembly anomaly detected. No action required. 603 SBAR assembly hot-removal completed. No action required. 604 SBAR assembly failure. Go to MAP 0400. 605 SBAR assembly revision not supported. Go to MAP 0400.
Maintenence Analysis Procedures MAP 0000: Start MAP This MAP describes initial fault isolation beginning at the: • Director. • Browser-capable PC with Internet connectivity to the firmwareresident Enterprise Fabric Connectivity Manager (EFCM) Basic Edition interface. • Management server running storage area network (SAN) management and Element Manager applications. • Product-attached open systems interconnection (OSI) host console.
Maintenence Analysis Procedures Are any amber LEDs illuminated? NO ↓ YES 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 10. 4 Is the product management interface (browser PC, management server, or OSI host console) powered on and operational? NO ↓ YES Go to step 7.
Maintenence Analysis Procedures • The icon representing the product displays a grey square with an exclamation mark (SAN management application). • A grey square at the alert panel, a No Link status and reason, and no visible product FRUs (Element Manager Hardware View). Was a failure indication observed? NO ↓ YES Communication between the product and management interface failed. Go to MAP 0300: Loss of Server Communication. Exit MAP.
Maintenence Analysis Procedures Is a failure indicated? NO ↓ YES 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 10. 8 A link incident may have occurred, but the LIN alerts option is not enabled and the yellow triangle (attention indicator) does not appear. Inspect the Link Incident Log: a.
Maintenence Analysis Procedures 9 If an incident occurs on the Fibre Channel link between the product and attached OSI server, a link incident record is generated and sent to the server console using the reporting procedure defined in T11/99-017v0. Was a link incident record generated and sent to the OSI server? NO ↓ YES A Fibre Channel link incident is indicated. Go to MAP 0500: Port Failure or Link Incident Analysis. Exit MAP.
Maintenence Analysis Procedures 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). 1 Ensure the product is connected to facility power.
Maintenence Analysis Procedures 3 As indicated by visual inspection or an event code, one or more power supplies failed and must be replaced (RRP: Power Supply on page 5-23). • The procedure is concurrent and performed while the product is operational. • Perform a data collection as part of FRU removal and replacement. NOTE: Do not remove a power supply unless a replacement FRU is available. To avoid product overheating, a removed power supply must be replaced within five minutes.
Maintenence Analysis Procedures c. Ensure AC power cords are not damaged. If damaged, replace the cords. Was the maintenance action successful? NO ↓ YES The product is operational. Exit MAP. 6 Verify power supply operation. a. Inspect each power supply to determine if the amber failure LED is illuminated. b. If an amber LED is illuminated, ensure the indicated power supply is correctly installed and seated. Partially remove and reseat the power supply (RRP: Power Supply on page 5-23).
Maintenence Analysis Procedures 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). 1 Table 3-5 lists event codes, explanations, and MAP steps. Table 3-5 Event Code MAP 200 Event Codes Explanation Action 400 Power-up diagnostic failure. Go to step 2. 411 Firmware fault. Go to step 9. 413 Backup CTP card POST failure.
Maintenence Analysis Procedures 3 The backplane failed POSTs (indicated by a FRU code 01) and must be replaced (RRP: Backplane on page 5-40). • This procedure is nonconcurrent and must be performed while director power is off. • Perform the data collection procedure as part of FRU removal and replacement. Did backplane replacement solve the problem? NO ↓ YES The director appears operational. Exit MAP. Contact the next level of support. Exit MAP.
Maintenence Analysis Procedures Did SBAR assembly replacement solve the problem? NO ↓ YES The director appears operational. Exit MAP. Contact the next level of support. Exit MAP. 6 A fan module failed POSTs (indicated by a FRU code 05) and must be replaced (RRP: Fan Module on page 5-30). • 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.
Maintenence Analysis Procedures 8 A port card failed POSTs (indicated by FRU codes 08 through 0F) and must be replaced (RRP: Port Module Card (UPM and XPM) on page 5-11). • This procedure is concurrent and can be performed while director power is on. • Perform the data collection procedure as part of FRU removal and replacement. Did port card replacement solve the problem? NO ↓ YES The director appears operational. Exit MAP. Contact the next level of support. Exit MAP.
Maintenence Analysis Procedures 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). • The icon representing the product displays a grey square with an exclamation mark (SAN management application).
Maintenence Analysis Procedures Is the product powered on? YES ↓ NO A power distribution problem is indicated. Go to MAP 0100: Power Distribution Analysis. Exit MAP. 4 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. b. At the Netsite field (Netscape Navigator) or Address field (Internet Explorer), type http://xxx.xxx.xxx.xxx, where xxx.xxx.xxx.
Maintenence Analysis Procedures • An illuminated PWR LED (green) or ERR LED (amber). • Illuminated LEDs adjacent to Fibre Channel ports. • Audio emanations and airflow from fans. Is the product powered on? YES ↓ NO A power distribution problem is indicated. Go to MAP 0100: Power Distribution Analysis. Exit MAP. 7 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.
Maintenence Analysis Procedures a. Ensure an RJ-45 Ethernet cable connects the product to a hub. If not, connect the cable as directed by the customer. b. Ensure an RJ-45 Ethernet cable connects the management server to a hub. If not, connect the cable as directed by the customer. c. Ensure Ethernet cables are not damaged. If damaged, replace the cables. Was the maintenance action successful? NO ↓ YES The management server connection is restored. Exit MAP.
Maintenence Analysis Procedures Figure 3-1 Daisy-Chained Ethernet Hubs Was the maintenance action successful? NO ↓ YES The management server connection is restored. Exit MAP. 11 Verify operation of Ethernet hubs. Inspect each hub for indications of being powered on, such as: • Green Power LED illuminated. • Green Status LEDs illuminated. Is a failure indicated? YES ↓ NO Go to step 13. 12 Remove and replace the Ethernet hub. Refer to supporting documentation for instructions.
Maintenence Analysis Procedures 13 A problem with LAN-attached device is indicated. • If the problem is associated with another fabric element or management server, go to MAP 0000: Start MAP to isolate the problem for that product. Exit MAP. • If the problem is associated with an unrelated device, inform the customer for problem resolution. Was the maintenance action successful? NO ↓ YES The management server connection is restored. Exit MAP.
Maintenence Analysis Procedures Was the maintenance action successful? NO ↓ YES The management server connection is restored. Exit MAP. Contact the next level of support. Exit MAP. 18 An instance of the SAN management application is open at another management server and communicating with the product (duplicate session). Inform the customer and either: • Power off the server running the second instance of the application.
Maintenence Analysis Procedures b. Type the user ID and password obtained in MAP 0000: Start MAP. c. Type the IP address of the management server running the first instance of the SAN management application in the Network Address field. d. Click Login. The application opens and the main window displays. Was the maintenance action successful? NO ↓ YES The management server connection is restored and the second management server is a client. Exit MAP. Contact the next level of support. Exit MAP.
Maintenence Analysis Procedures g. Configure Port Settings parameters: — Bits per second - 115200. — Data bits - 8. — Parity - None. — Stop bits - 1. — Flow control - Hardware or None. Click OK. The New Connection - HyperTerminal window displays. h. At the > prompt, type the user password (default is password) and press Enter. The password is case sensitive.
Maintenence Analysis Procedures d. Move the reconfigured product from the Available Addresses list to the Selected Individual Addresses list. e. Click OK to save the address, close the dialog box, and redefine the product to the SAN management application. f. Click OK to close the Discover Setup dialog box. Was the maintenance action successful? NO ↓ YES The management server connection is restored. Exit MAP. Contact the next level of support. Exit MAP.
Maintenence Analysis Procedures 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). 1 Table 3-8 lists event codes, explanations, and MAP steps. Table 3-8 3-30 MAP 400: Event Codes Event Code Explanation Action 300 Cooling fan propeller failed. Go to step 3. 301 Cooling fan propeller failed.
Maintenence Analysis Procedures MAP 400: Event Codes (Continued) Table 3-8 Event Code Explanation Action 806 Critically hot temperature warning (SBAR assembly thermal sensor). Go to step 8. 807 SBAR assembly shutdown due to thermal violation. Go to step 8. 810 High temperature warning (CTP card thermal sensor). Go to step 5. 811 Critically hot temperature warning (CTP card thermal sensor). Go to step 5. 812 CTP card shutdown due to thermal violation. Go to step 6.
Maintenence Analysis Procedures YES ↓ NO Contact the next level of support. Exit MAP. The product is operational. Exit MAP. 4 An intermittent synchronous dynamic random access memory (SDRAM) problem may indicate a CTP card failure. Is the event code a recurring problem? NO ↓ YES A CTP card failure is indicated. Go to step 6. Perform a data collection (Collecting Maintenance Data on page 4-32) and contact the next level of support. Exit MAP.
Maintenence Analysis Procedures 7 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 (Downloading Director Firmware and Software on page 4-41). Perform a data collection after the download (Collecting Maintenance Data on page 4-32).
Maintenence Analysis Procedures MAP 0500: Port Failure or Link Incident Analysis This MAP describes fault isolation for small form factor pluggable (SFP) 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). • Event codes observed at the console of an open systems interconnection (OSI) server attached to the product reporting the problem.
Maintenence Analysis Procedures MAP 500: Event Codes (Continued) Table 3-9 Event Code Explanation Action 586 Invalid primitive sequence received for current link state. Go to step 22. 800 High temperature warning (port card thermal sensor). Go to step 21. 801 Critically hot temperature warning (port card thermal sensor). Go to step 21. 802 Port card shutdown due to thermal violation. Go to step 21. 2 Table 3-10 lists link incident messages and MAP steps.
Maintenence Analysis Procedures c. The WWN must be entered in (XX:XX:XX:XX:XX:XX:XX:XX) format or must be a valid nickname. Ensure a valid WWN or nickname is entered. Was the maintenance action successful? NO YES ↓ The product port is operational. Exit MAP. Contact the next level of support. Exit MAP. 4 A port has an invalid attachment. a. At the Event Log, examine the first five bytes of event data. b. Byte 0 specifies the port reporting the problem.
Maintenence Analysis Procedures Table 3-11 Byte 4 Invalid Attachment Reasons and Actions (Continued) Invalid Attachment Reason Action 0F Unauthorized switch binding WWN. Go to step 11. 10 Authentication failure Go to step 13. 11 Fabric mode mismatch. Go to step 6. 5 A connection is not allowed because of a conflict with the configured port type. An expansion port (E_Port) is cabled to a Fibre Channel device or a fabric port (F_Port) is cabled to a director or fabric switch. a.
Maintenence Analysis Procedures • The product is configured to operate in Open Fabric 1.0 mode and is connected to a legacy McDATA 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-McDATA switch at the incorrect ELP revision level. • The product is configured to operate in McDATA Fabric 1.0 mode and is connected to a non-McDATA switch. Reconfigure the operating mode: a.
Maintenence Analysis Procedures • If the port is operational with no device attached, both LEDs adjacent to the port extinguish and the port state is No Light. • If the port is operational with a device attached, the blue/green LED illuminates, the amber LED extinguishes, and the port state is Online. Was the maintenance action successful? NO ↓ YES The product port is operational. Exit MAP. Contact the next level of support. Exit MAP.
Maintenence Analysis Procedures Contact the next level of support. Exit MAP. 11 A connection is not allowed because of a switch binding or exchange security attribute (ESA) feature mismatch. Switch binding parameters must be compatible for both fabric elements. At the EFCM Basic Edition interface or Element Manager, ensure switch binding is enabled, the connection policy is compatible, and switch membership lists are compatible for both elements.
Maintenence Analysis Procedures modify the IP address access control list, product-level authentication settings, port-level authentication settings, and challenge handshake authentication protocol (CHAP) sequence to ensure device access to the product. • EFCM Basic Edition - Refer to the McDATA EFCM Basic Edition User Manual (620-000240). • Element Manager - Refer to the McDATA Intrepid 6140 and 6064 Directors Element Manager User Manual (620-000153).
Maintenence Analysis Procedures • Optical transceiver does not support the configured port speed. Change the port speed to be compatible with the backplane or optical transceiver speed. a. For the product reporting the problem: — EFCM Basic Edition - Select Ports and Basic Info from the Configure menu at any view. The Basic Information View displays. — Element Manager - Select Ports from the Configure menu at any view. The Configure Ports dialog box displays. b.
Maintenence Analysis Procedures A port card failure is indicated. Go to step 21. 19 A port failed a loopback test. Reset the failed port. a. At the EFCM Basic Edition interface: 1. Select Ports and Reset from the Maintenance menu at any view. The Reset View displays. 2. If necessary, use the vertical scroll bar to display the information row for the port. 3. Select (click) the check box in the Reset column. 4. Click OK. The port resets. b. At the Element Manager: 1.
Maintenence Analysis Procedures Figure 3-2 UPM Card Diagram (Front) Figure 3-3 UPM Card Diagram (Rear) • Replace the transceiver with a transceiver of the same type (shortwave or longwave) and speed. • Perform an external loopback test (Performing Loopback Tests on page 4-21). NOTE: Event code 514 may generate a call-home event that incorrectly indicates a CTP card failure. Although the optical socket on the CTP card may have failed, replace the transceiver and verify operation.
Maintenence Analysis Procedures 21 A port card failed and the card must be replaced (RRP: Port Module Card (UPM and XPM) on page 5-11). • This procedure is concurrent and can be performed while director power is on. • Verify the location of the failed card. Figure 3-2 and Figure 3-3 show UPM card numbers (0 through 34), port numbers (00 through 139), and bolded logical port addresses. • Notify the customer that all ports on the defective card are to be blocked.
Maintenence Analysis Procedures ↓ The problem is transient and the product port is operational. Exit MAP. 23 Clean fiber-optic components. a. Inform the customer the port will be blocked. Ensure the system administrator quiesces Fibre Channel frame traffic and sets attached devices offline. b. Block the port (Blocking and Unblocking Ports on page 4-27). c. Clean fiber-optic connectors (Cleaning Fiber-Optic Components on page 4-40). d. Unblock the port (Blocking and Unblocking Ports on page 4-27). e.
Maintenence Analysis Procedures NO ↓ YES The product port is operational. Exit MAP. 26 The attached device is causing the recurrent link incident. Inform the customer of the problem and have the system administrator: a. Inspect and verify operation of the attached device. b. Repair the attached device if a failure is indicated. c. Monitor port operation for approximately five minutes. Was the maintenance action successful? NO ↓ YES The product port is operational. Exit MAP.
Maintenence Analysis Procedures 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). 1 Table 3-13 lists event codes, explanations, and MAP steps. Table 3-13 Event Code 3-48 MAP 600 Event Codes Explanation Action 010 Login Server unable to synchronize databases. Go to step 2.
Maintenence Analysis Procedures 2 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. • Event code 021 - The Name Server database failed CRC validation. Devices resume operation after fabric login.
Maintenence Analysis Procedures 6 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. Advise the customer of the problem and reconfigure the fabric so that no directors or switches have more than the proscribed number of ISLs.
Maintenence Analysis Procedures Table 3-14 Byte 4 E_Port Segmentation Reasons and Actions (Continued) Segmentation Reason Action 04 Build fabric protocol error. Go to step 11. 05 No principal switch. Go to step 13. 06 No response from attached switch (hello timeout). Go to step 14. 8 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. a.
Maintenence Analysis Procedures Was the maintenance action successful? NO ↓ YES The fabric, ISL, and product are operational. Exit MAP. Contact the next level of support. Exit MAP. 9 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. b. Inform the customer both products will be set offline. Ensure the system administrator quiesces Fibre Channel frame traffic and sets attached devices offline. c.
Maintenence Analysis Procedures 10 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. Zone names must conform to the following rules: — The name must be 64 characters or fewer in length. — The first character must be a letter (a through z), upper or lower case.
Maintenence Analysis Procedures 12 Reset the product (IML, IPL, or Reset the Director on page 4–38). Was the maintenance action successful? NO ↓ YES The fabric, ISL, and product are operational. Exit MAP. Perform a data collection and contact the next level of support. Exit MAP. 13 An E_Port segmented because no product in the fabric is capable of becoming the principal switch. a. Inform the customer the product will be set offline.
Maintenence Analysis Procedures Was the maintenance action successful? NO YES ↓ The fabric, ISL, and product are operational. Exit MAP. Contact the next level of support. Exit MAP. 14 An E_Port segmented (operational product) because a response (hello timeout) to a verification check indicates an attached switch is not operational. a. Perform a data collection at the operational product and send the CD to support personnel for analysis. This information may assist in fault isolating the failed switch.
Maintenence Analysis Procedures 17 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. Go to step 7. • The fiber-optic cable is disconnected, the cable failed or is degraded, or the port optical transceiver failed. The failure is accompanied by a primary event code indicating the failure type.
Maintenence Analysis Procedures — SAN management application - Refer to the SANavigator Software Release 4.2 User Manual (621-000013) or EFC Manager Software Release 8.7 User Manual (620-000170) for instructions. — Element Manager - Refer to the McDATA Intrepid 6140 and 6064 Directors Element Manager User Manual (620-000153) for instructions. b. Unblock the port (Blocking and Unblocking Ports on page 4–27). Was the maintenance action successful? NO ↓ YES The fabric, ISL, and product are operational.
Maintenence Analysis Procedures • Event code 142 - OpenTrunking firmware detected an ISL with no transmission BB_Credit for a period of time that exceeded the configured low BB_Credit threshold. This results in downstream fabric congestion. No action is required for an isolated event or if the reporting ISL approaches 100% throughput. If the event persists, perform one of the following: • Relieve the congestion by adding parallel ISLs between the fabric elements reporting the problem.
Maintenence Analysis Procedures Table 3-16 Fabric Merge Failure Reasons and Actions (Continued) Bytes 8 - 11 Merge Failure Reason Action F0 Retry limit reached. Go to step 23. F1 Invalid response length. Go to step 23. F2 Invalid response code. Go to step 23. 23 A zone merge process failed during ISL initialization. The following list explains the reason: • Reason 01 - An invalid data length condition caused an error in a zone merge frame.
Maintenence Analysis Procedures 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. Contact the next level of support and report the event code, associated failure reason, and supplementary error code. Exit MAP.
4 Repair Information This chapter describes repair-related procedures for the Intrepid 6140 Director. The procedures are performed at the director, through storage area network (SAN) management application (SANavigator or EFCM), Intrepid 6140 Element Manager application, or EFCM Basic Edition interface. The following procedures are described: • Obtaining log information. • Obtaining port diagnostic information. • Performing loopback tests. • Blocking or unblocking ports. • Swapping ports.
Repair Information 4 Factory Defaults Table 4-1 lists the defaults for the passwords, and IP, subnet, and gateway addresses. Table 4-1 Factory-Set Defaults Item Procedural Notes 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 NOTE: The screens in this manual may not match the screens on your server and workstation.
Repair Information 4 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 (SANavigator or EFCM). Fabric-log information: — Event Log. — Fabric Log. — Product Status Log. • Logs accessed through the Element Manager application. Director-log information. — Event Log. — Hardware Log.
Repair Information 4 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: • Date/Time - The date and time the event occurred. • Event - An event number and brief description of the event.
Repair Information 4 • Network Address - The IP address or configured name of the director. This address or name corresponds to the address or name displayed under the product icon at the physical map. • 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.
Repair Information 4 • Date/Time - The date and time the FRU was inserted or removed. • FRU - An acronym representing the FRU type. • Position - A number representing the FRU chassis position. The chassis (slot) position for a nonredundant FRU is 0. The chassis positions for redundant FRUs are 0 and 1. • Action - The action performed (Inserted or Removed). • Part Number - The part number of the inserted or removed FRU. • Serial Number - The serial number of the inserted or removed FRU.
Repair Information 4 • Port - The port number where the alert occurred. • Type - The type of alert: transmit (Tx) or receive (Rx). • Utilization % - The percent usage of traffic capacity. This setting constitutes the threshold value and is configured through the Configure Threshold Alerts dialog box. For example, a value of 25 means that threshold occurs when throughput reaches 25 percent of the port capacity.
Repair Information 4 • Direction - The Fibre Channel frame direction (In or Out). • Frame Header - 24-byte frame header (hexadecimal). • Length - The size of frame payload in bytes. • Payload - First 32 bytes of frame payload (hexadecimal). • SOF - The start of frame character (hexadecimal). • EOF - The end of frame character (hexadecimal). NOTE: Identical entries are recorded in the wrapping and non-wrapping logs. When the non-wrapping log fills, old records are overwritten.
Repair Information 4 • Error Code - The three-digit code that describes the event (Appendix A, Event Code Tables). • Severity - The severity of the event (Informational, Minor, Major, or Severe). • Event Data - Supplementary information (if available) in hexadecimal format (Appendix A, Event Code Tables). 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.
Repair Information 4 • Old Exit Port - The director port number (decimal) used for transmitting Fibre Channel traffic before the re-route action. • New Exit Port - The director port number (decimal) used for transmitting Fibre Channel traffic after the re-route action. 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.
Repair Information 4 • EOF - The end of frame character (hexadecimal). • Payload Size - The size of frame payload in bytes. • Header - 24-byte frame header (hexadecimal). • Payload - The first 32 bytes of frame payload (hexadecimal). 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.
Repair Information 4 Table 4-2 Port Operational States (continued) Port State Green LED Amber LED Alert Symbol Description Link Incident Off Off Yellow Triangle A link incident occurred on the port. The alert symbol appears at the Port Card View, Port List View, and Hardware View. Link Reset Off Off Yellow Triangle The director and attached device are performing a link reset operation to recover the link connection. This is a transient state that should not persist.
Repair Information 4 Port List View To open the Port List View, click the Port List tab at any view (Figure 4-1). A row of information for each port appears. Figure 4-1 Port List View The view provides the following information: • Port # - The director port number. • FC Addr - The director logical port address (hexadecimal format). • Name - The user-defined name or description for the port. • Block Config - Indicates if a port is blocked or unblocked.
Repair Information 4 level indicators corresponding to 5% of maximum port throughput. If any activity is detected, at least one green bar appears. A red indicator on each bar graph (high-water mark) remains at the highest level reached since the port was set online.
Repair Information 4 Port Properties Dialog Box To open the Port Properties dialog box (Figure 4-2), double-click a port graphic at the Hardware View or a port row at the Port List View. Figure 4-2 Port Properties Dialog Box 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. • Port Number - The director port number.
Repair Information 4 4-16 • Port WWN - The Fibre Channel WWN of the port. • Attached Port WWN - The Fibre Channel WWN of the device attached to the port. • Block Configuration - A user-configured state for the port (Blocked or Unblocked). • 10 - 100 km Configuration - The user-configured state for extended distance operation (On or Off). • Rx BB_Credits Configured - The user-defined number of receive BB_Credits allocated to the port.
Repair Information 4 • Zoning Enforcement - The zoning policy enforced (Hard Zoning, Soft Zoning, or N/A). Port Technology Dialog Box To open the Port Technology dialog box (Figure 4-3), right-click a port graphic at the Hardware View or a port row at the Port List View, then select Port Technology from the pop-up menu. Figure 4-3 Port Technology Dialog Box The dialog box provides the following information: • Port Number - The director port number.
Repair Information 4 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 4-4). Figure 4-4 Port List View A row of information for each port appears. Each row consists of the following columns: 4-18 • Port - The director port number. • Name - The user-defined name or description for the port. • Block Configuration - Indicates if a port is blocked or unblocked.
Repair Information 4 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: • Port Number - The director port number. • Port Name - The user-defined name or description for the port. • Port Type - The user-defined port type (G_Port, F_Port, or E_Port). • Operating Speed - The port operating speed (Not Established, 2 Gbps, or 10 Gbps).
Repair Information 4 • Transceiver Type - The installed transceiver type (SFP, XFP, 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. Inspect Port Transceiver Technology At the Port List View, click the entry for a port in the Transceiver column.
Repair Information 4 • Error Statistics - These statistics include the number of link failures; synchronization and signal losses; discarded frames; invalid transmission words; primitive sequence, cyclic redundancy check (CRC), delimiter, and address identification errors; and short frames. • 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.
Repair Information 4 NOTE: At the start of the loopback test, the port or port card can be online, offline, blocked, or unblocked. NOTE: An optical transceiver (SFP or XFP) must be installed in the port during the test. A device can remain connected during the test. 2. At the Element Manager application, select Port Diagnostics from the Maintenance menu. The Port Diagnostics dialog box displays (Figure 4-5). 3.
Repair Information 4 8. When finished, click Cancel to close the Port Diagnostics dialog box. 9. 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. 10. Notify the customer that the test is complete and the attached device can be set online.
Repair Information 4 c. A red progress bar (indicating percent completion) travels from left to right across the Completion Status field. 10. When the test completes, results appear as Port xx: Passed! or Port xx: Failed! in the message area of the dialog box. 11. When finished, click Cancel to close the Port Diagnostics dialog box. 12. Remove the loopback plug and reconnect the fiber-optic jumper cable from the device to the port. 13. Reset the port: a. At the Hardware View, right-click the port graphic.
Repair Information 4 Figure 4-6 Diagnostics View 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. The message Diagnostics Time Remaining: xx appears, where xx are the seconds remaining in the test. The test takes approximately 30 seconds. NOTE: Click Stop at any time to abort the loopback test. 6.
Repair Information 4 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. Notify the customer that a disruptive external loopback test will be performed and that the attached device must be disconnected. 2.
Repair Information 4 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. appears. 11. Notify the customer the test is complete and the device can be reconnected to the director and set online. Blocking and Unblocking Ports This section describes procedures to block or unblock director ports.
Repair Information 4 • 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. A Warning dialog box displays. Click OK. The dialog box closes and the following occur to indicate the port is unblocked and online: • At the director, the green port (or ports) LED illuminates.
Repair Information 4 Figure 4-7 Basic Information View 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. A blank box indicates the port is unblocked. 3. Click OK at the bottom of the page to save and activate the change.
Repair Information 4 Figure 4-8 Swap Ports Dialog Box 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. Click Next. The Instructions section of the dialog box indicates the ports will be blocked. 4. Notify the customer that a port swap will be performed.
Repair Information 4 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. The director port echoes the frames back to the host. To perform a channel wrap test for a director-attached host: 1.
Repair Information 4 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. The director then transfers (through the Ethernet connection) the captured dump file from FLASH memory to the management server hard drive.
Repair Information 4 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. 4. The Data Collection dialog box displays with a progress bar that shows percent completion of the data collection process.
Repair Information 4 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. 5. A Download dialog box displays, showing the estimated time remaining to complete the download process. When finished, the dialog box changes to a Download complete dialog box. 6.
Repair Information 4 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. — Green LED on each CTP card (active and backup) and each port card illuminate as the card is tested. — Green LEDs associated with Fibre Channel ports sequentially illuminate as the ports are tested. 3.
Repair Information 4 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. These operating states are described as: • Online - When the director is set online, an attached device can log in to the director if the port is not blocked.
Repair Information 4 Figure 4-11 Set Online State Dialog Box 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 4-12). 2. Perform one of the following: — If the director is offline, click the green Activate button adjacent to the Current Online State: field.
Repair Information 4 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. ATTENTION! A reset should only be performed if a CTP card failure is indicated. Do not reset the director unless directed to do so by a procedural step or the next level of support.
Repair Information 4 — The status bar at the bottom of the window displays a grey square, indicating director status is unknown. — Illustrated FRUs disappear, and appear again as the connection is re-established. IPL the Director (Element Manager Application) To IPL the director from the Element Manager application: 1. At the Element Manager application, select the IPL option from the Maintenance menu. An Information dialog box displays. 2. Click Yes to IPL the director.
Repair Information 4 — The director-to-management server Ethernet link drops momentarily and the following occur at the Hardware View: • As the network connection drops, the Intrepid 6140 Status table turns yellow, the Status field displays No Link, and the State field displays Link Timeout. • The status bar at the bottom of the window displays a grey square, indicating director status is unknown. • Illustrated FRUs disappear, and appear again as the connection is re-established.
Repair Information 4 — Hold the duster upright and keep the air nozzle approximately 50 millimeters (two inches) from the end of the component. — Blow compressed air or HFC-134a gas on the surfaces and end of the connector for approximately five seconds. Figure 4-13 Clean Fiber-Optic Components 3. Gently wipe the end-face and other surfaces of the connector with an alcohol pad (part B of Figure 4-13). Ensure the pad makes full contact with the surface to be cleaned.
Repair Information 4 • Downloading firmware and software versions to the director from the EFCM Basic Edition Application. Download Firmware and Software from Filecenter The firmware version shipped with the director is provided on the System Version XX.YY.ZZ CD-ROM. The SAN management application (software) shipped with the product is provided on the EFC Management Applications CD-ROM. Subsequent (upgrade) firmware and software versions are provided to customers through the McDATA Filecenter.
Repair Information 4 3. Type the user name and password (assigned and registered while performing Task 24: Register with the McDATA Filecenter on page 2-75) and click Login. The Welcome page displays. 4. Select (click) Documents at the top of the page. The Search / New Documents / By Category page displays. 5. Select (highlight) the desired option (firmware or software) from the list box and click Search. The Documents Match page displays with a list of firmware or software available for download. 6.
Repair Information 4 Download Firmware and Software to Director (Element Manger Application) To download a firmware and software 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. This information supplements information provided in this general procedure. 1.
Repair Information 4 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. Conditions that terminate the process include: — A redundant CTP card failure.
Repair Information 4 Download Firmware and Software to Director (EFCM Basic Edition) To download a firmware and software 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. This information supplements information provided in this general procedure. 1.
Repair Information 4 5. Click OK to download the firmware to the director. The download takes several minutes, during which the browser is unavailable. 6. When the process completes, the message "Firmware successfully received and verified. Your browser connection will be unavailable until unit restart is complete" displays. 7. After verification, the director performs an IPL that takes approximately 30 seconds.
Repair Information 4 — Ensure the desired software version is obtained from the Filecenter and resident on the server hard drive (Downloading Director Firmware and Software on page 4-41). 2. At the server Windows desktop, click Start at the left side of the task bar, then select the Run option. The Run dialog box displays. 3. In the Open field at the Run dialog box, type: — C:\mcdataServerInstall.exe to install from the server hard drive. — D:\mcdataServerInstall.
Repair Information 4 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. After the server reboots, click Login again. The VNC Authentication screen displays. d. Type the default password and click OK. The Welcome to Windows dialog box displays. NOTE: The default TightVNC viewer password is password. e.
Repair Information 4 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. Back Up Configuration (Element Manager Application) To back up the configuration file to the management server: 1.
Repair Information 4 2. Set the director offline (Setting the Director Online or Offline on page 4-36). 3. At the Element Manager application, select Backup & Restore Configuration from the Maintenance menu. The Backup and Restore Configuration dialog box displays (Figure 4-18). 4. Click Restore. A Warning dialog box displays, indicating the existing configuration file is to be overwritten. 5. Click Yes. A Restore dialog box displays, indicating the restore is in progress. 6.
Repair Information 4 5. Click Reset to start the reset and close the dialog box. 6. The IP address resets to the defaults of 10.1.1.10. — If the configured IP address (prior to reset) was the same as the default, the director-to-management server Ethernet link is not affected and the procedure is complete. — If the configured IP address (prior to reset) was not the same as the default, the director-to-management server Ethernet link drops and server communication is lost. Continue to the next step. 7.
Repair Information 4 Figure 4-21 Address Properties Dialog Box e. Type 10.1.1.10 in the IP Address field and click OK. Entries at the Discover Setup dialog box reflect the new IP address. f. At the Discover Setup dialog box, click OK. Director-tomanagement server communication is restored and the procedure is complete. 8. Change the director IP address and restart the management server session as follows: a.
Repair Information 4 Back Up Configuration (EFCM Basic Edition) To back up the director configuration file to the PC communicating with the EFCM Basic Edition interface: 1. Select Backup Configuration from the Maintenance menu at any view. The Backup Configuration View displays (Figure 4-22). Figure 4-22 Backup Configuration View 2. Right-click the Configuration file link to open a list of menu options. Select the Save Target As menu option. The Save As dialog box displays. 3.
Repair Information 4 3. Select Restore Configuration from the Maintenance menu at any view. The Restore Configuration View displays (Figure 4-23). Figure 4-23 Restore Configuration View 4. At the Download Configuration file from field, select the file from the PC hard drive using the Browse button or type the filename. 5. Click Send and Load Configuration. A message box displays, indicating any browser operation will terminate the configuration download. 6. Click OK to download the configuration.
Repair Information 4 5. Click OK to reset the configuration. The message "Your changes have been successfully activated." appears. 6. The IP address resets to the default of 10.1.1.10. — If the configured IP address (prior to reset) was the same as the default, the browser-to-director Internet connection is not affected and the procedure is complete.
5 Removal and Replacement Procedures (RRPs) This chapter describes removal and replacement procedures (RRPs) used by authorized service representatives for all Intrepid 6140 Director field-replaceable units (FRUs). Do not perform a procedure in this chapter until a failure is isolated to a FRU. If fault isolation was not performed, go to Chapter 3, Maintenance Analysis Procedures (MAPS). Factory Defaults Table 5-1 lists the defaults for the passwords, and IP, subnet, and gateway addresses.
Removal and Replacement Procedures (RRPs) 5 Procedural Notes NOTE: The screens in this manual may not match the screens on your server and workstation. The title bars have been removed and the fields may contain data that does not match the data seen on your system. The following procedural notes are referenced as applicable. The notes do not necessarily apply to all procedures in the chapter. 1.
Removal and Replacement Procedures (RRPs) 5 Removing and Replacing FRUs This section describes procedures to remove and replace director FRUs, along with a list of tools required to perform each procedure. In addition, the section provides: • ESD information • A list of concurrent FRUs. Concurrent FRUs can be removed and replaced while the director is powered on and operational. • A list of nonconcurrent FRUs. Nonconcurrent FRUs can only be removed and replaced after the director is powered off.
Removal and Replacement Procedures (RRPs) 5 Figure 5-1 5-4 ESD Grounding Points Intrepid® 6140 Director Installation and Service Manual
Removal and Replacement Procedures (RRPs) 5 Concurrent FRUs Table 5-2 Table 5-2 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.
Removal and Replacement Procedures (RRPs) 5 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. The director IP address, configuration data, and other operating parameters will be lost.
Removal and Replacement Procedures (RRPs) 5 5. The CTP card is secured to the director chassis with two captive Allen screws. The bottom screw is spring-loaded and locks the CTP card in place. The top screw cams the CTP card into and out of the backplane. ATTENTION! The torque tool supplied with the director is designed to tighten director logic cards and is set to release at a torque value of six inch-pounds. Do not use an Allen wrench or torque tool designed for use with another McDATA product.
Removal and Replacement Procedures (RRPs) 5 Figure 5-2 Replacement CTP Card Removal and 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. Hold the card by its stiffener and insert it in the chassis card track (Figure 5-2). The label identifying the card should be at the top.
Removal and Replacement Procedures (RRPs) 5 c. Verify the card stiffener is flush with the front of the card cage and even with other director logic cards. 5. After the replacement CTP card is installed, note the following: — When a CTP card with a different firmware version is installed in a director with an active CTP card, a synchronization process occurs. This process causes firmware from the active CTP card to be downloaded to the replacement CTP card.
Removal and Replacement Procedures (RRPs) 5 — 422 - CTP firmware synchronization complete (only if the firmware versions on the two CTP cards are different). If the event codes do not appear in the log, go to Chapter 3, Maintenance Analysis Procedures (MAPS) to isolate the problem. 11.
Removal and Replacement Procedures (RRPs) 5 RRP: Port Module Card (UPM and XPM) Use the following procedures to remove or replace a UPM or XPM card. A list of tools required is provided. Tools Required Removal The following tools are required to perform these procedures. • Door key with 5/16-inch socket (provided with the FC-512 Fabricenter equipment cabinet). • ESD grounding cable and wrist strap. • Torque tool and hex adapter (provided with the director).
Removal and Replacement Procedures (RRPs) 5 5. Identify the defective port card from the amber LED on the card or failure information at the management server Hardware View. 6. Block communication to the defective port card (Blocking and Unblocking Ports on page 4-27). 7. If necessary, remove the RFI shield. 8. Disconnect the fiber-optic jumper cable from each port on the defective card as follows. Repeat this step for all four ports. a. Pull the keyed LC connector free from the port optical transceiver.
Removal and Replacement Procedures (RRPs) 5 a. Insert the torque tool into the locking Allen screw (yellow). Turn the screw counter-clockwise until the spring releases and the tool turns freely. b. Insert the torque tool into the cam Allen screw (uncolored). To unseat the port card and cam it out of the backplane, turn the screw counterclockwise until the tool turns freely (Figure 5-3). 10. Pull the port card from its card track and remove it from the director chassis.
Removal and Replacement Procedures (RRPs) 5 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" symbol on the frame. Verify that the card is aligned in the card tracks (Figure 5-3), then slide it forward until it makes contact with the backplane. 3. Secure the port card: a. Insert the torque tool into the cam Allen screw (uncolored). Turn the torque tool clockwise until you feel it release and hear a clicking sound.
Removal and Replacement Procedures (RRPs) 5 9. 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: — 500 - Port card hot-insertion initiated. — 501 - Port card has been recognized. If an event code 501 does not appear in the log, go to Chapter 3, Maintenance Analysis Procedures (MAPS) to isolate the problem. 10.
Removal and Replacement Procedures (RRPs) 5 14. If necessary, close and lock the equipment cabinet door.
Removal and Replacement Procedures (RRPs) 5 RRP: Optical Transceiver (SFP and XFP) Use the following procedures to remove or replace an SFP or XFP optical transceiver from a UPM or XPM card. A list of tools required is provided. Tools Required Removal The following tools are required to perform these procedures. • Door key with 5/16-inch socket (provided with the FC-512 Fabricenter equipment cabinet). • ESD grounding cable and wrist strap. • Fiber-optic protective plug (provided with the director).
Removal and Replacement Procedures (RRPs) 5 7. Disconnect the fiber-optic jumper cable from the port: a. Pull the keyed LC free from the port optical transceiver. b. Place a protective cap over the cable connector. 8. Depending on the manufacturer, the optical transceiver may have a locking mechanism to secure the transceiver in the port receptacle, or the transceiver may have a pull tab to assist in removal. a.
Removal and Replacement Procedures (RRPs) 5 3. Perform an external loopback test for the port (Performing Loopback Tests on page 4-21). If the test fails, go to Chapter 3, Maintenance Analysis Procedures (MAPS) to isolate the problem. 4. Reconnect the fiber-optic jumper cable: a. Remove the protective cap from the cable connector and the protective plug from the port optical transceiver. Store the cap and plug in a suitable location for safekeeping. b.
Removal and Replacement Procedures (RRPs) 5 10. Restore communication to the port with the replacement transceiver as directed by the customer (Blocking and Unblocking Ports on page 4-27). Inform the customer the port is available for use. 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.
Removal and Replacement Procedures (RRPs) 5 RRP: Filler Panel (UPM and XPM) Use the following procedures to remove or replace a UPM or XPM filler panel. Filler panels cover and protect unused port card slots in the director chassis. A list of tools required is provided. Tools Required Removal The following tools are required to perform these procedures. • Door key with 5/16-inch socket (provided with the FC-512 Fabricenter equipment cabinet).
Removal and Replacement Procedures (RRPs) 5 Figure 5-5 Replacement Filler Panel Removal and Replacement To replace a filler panel: 1. Remove the filler panel from its packaging. 2. Hold the filler panel by its stiffener and insert it in the chassis card track (Figure 5-5). 3. To secure the filler panel, sequentially insert the torque tool into each locking Allen screw. Turn each screw clockwise until you feel the torque tool release and hear a clicking sound.
Removal and Replacement Procedures (RRPs) 5 RRP: Power Supply Use the following procedures to remove or replace a power supply. A list of tools required is provided. Tools Required Removal The following tools are required to perform these procedures. • Door key with 5/16-inch socket (provided with the FC-512 Fabricenter equipment cabinet). • Standard flat-tip screwdriver. • ESD grounding cable and wrist strap. To remove a power supply: 1.
Removal and Replacement Procedures (RRPs) 5 Figure 5-6 Power Supply Removal and Replacement 5. Pull the power supply from the director AC module (Figure 5-6). Support the power supply with one hand. 6. Place the power supply in an anti-static bag to provide ESD protection. Replacement To replace a power supply: 1. Remove the replacement power supply from its protective anti-static bag. 2. Inspect the rear of the power supply for bent or broken connector pins that may have been damaged during shipping.
Removal and Replacement Procedures (RRPs) 5 5. Inspect the power supply to ensure the green PWR OK LED is illuminated and all amber LEDs are extinguished. If a problem is indicated, go to Chapter 3, Maintenance Analysis Procedures (MAPS) to isolate the problem. 6. At the management server or at a web browser connected to the EFCM Basic Edition interface, inspect the Event Log. Ensure an event code 207 (power supply installed) appears in the log.
Removal and Replacement Procedures (RRPs) 5 RRP: AC Module Use the following procedures to remove or replace the AC module. A list of tools required is provided. Tools Required Removal The following tools are required to perform these procedures. • Door key with 5/16-inch socket (provided with the FC-512 Fabricenter equipment cabinet). • Standard cross-tip (Phillips) screwdriver. • ESD grounding cable and wrist strap. To remove the AC module: 1.
Removal and Replacement Procedures (RRPs) 5 4. Remove the power supply from the defective AC module (RRP: Power Supply on page 5-23). 5. Remove the two panhead Phillips screws that secure the AC module to the director chassis (Figure 5-7). Figure 5-7 AC Module Removal and Replacement 6. Pull the AC module out of the director chassis. Support the assembly with one hand. 7. Place the AC module in an anti-static bag to provide ESD protection. Replacement To replace the AC module: 1.
Removal and Replacement Procedures (RRPs) 5 3. Position the AC module at the rear of the director chassis (Figure 5-7). Push the module toward the backplane to engage the connector pins. 4. Insert and tighten the two panhead Phillips screws that secure the AC module. 5. Replace the power supply (RRP: Power Supply on page 5-23). 6. Disconnect the ESD wrist strap from the director chassis and your wrist. 7. Connect the power cord to the AC module. 8.
Removal and Replacement Procedures (RRPs) 5 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.
Removal and Replacement Procedures (RRPs) 5 RRP: Fan Module Use the following procedures to remove or replace a fan module. A list of tools required is provided. Tools Required Removal The following tools are required to perform these procedures. • Door key with 5/16-inch socket (provided with the FC-512 Fabricenter equipment cabinet). • Standard flat-tip screwdriver. • ESD grounding cable and wrist strap. To remove a fan module: 1.
Removal and Replacement Procedures (RRPs) 5 5. Two captive screws secure the fan module to the director chassis (Figure 5-8). Using a standard flat-tip screwdriver, loosen the captive screws. Figure 5-8 Fan Module Removal and Replacement 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. Remove the replacement fan module from its protective anti-static bag. 2.
Removal and Replacement Procedures (RRPs) 5 5. Disconnect the ESD wrist strap from the director chassis and your wrist. 6. Inspect the fan module to ensure the amber LED is extinguished. If the LED is illuminated, 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. Ensure an event code 321 (fan FRU inserted) appears in the log.
Removal and Replacement Procedures (RRPs) 5 c. Click Clear Light. 12. If necessary, close and lock the equipment cabinet door.
Removal and Replacement Procedures (RRPs) 5 RRP: Power/System Error LED Assembly Use the following procedures to remove or replace the Power/System Error LED assembly. A list of tools required is provided. Tools Required Removal The following tools are required to perform these procedures. • Door key with 5/16-inch socket (provided with the FC-512 Fabricenter equipment cabinet). • Standard flat-tip screwdriver. • ESD grounding cable and wrist strap.
Removal and Replacement Procedures (RRPs) 5 Figure 5-9 Replacement Power/System Error LED Assembly Removal and 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. Plug the Power/System LED assembly cable into the backplane. 4. Replace the center and upper left fan modules (viewed from the rear) (RRP: Fan Module on page 5-30). 5.
Removal and Replacement Procedures (RRPs) 5 RRP: SBAR Assembly Use the following procedures to remove or replace an SBAR assembly. A list of tools required is provided. Tools Required Removal The following tools are required to perform these procedures. • Door key with 5/16-inch socket (provided with the FC-512 Fabricenter equipment cabinet). • Standard flat-tip screwdriver. • ESD grounding cable and wrist strap. • Torque tool and hex adapter (provided with the director).
Removal and Replacement Procedures (RRPs) 5 Figure 5-10 SBAR Assembly Removal and Replacement 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. Replacement To replace an SBAR assembly: 1. Remove the replacement SBAR assembly from its protective anti-static bag. 2.
Removal and Replacement Procedures (RRPs) 5 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. Ensure the following event codes appear in the log: — 600 - SBAR card hot-insertion initiated. — 601 - SBAR card hot-insertion completed. If an event code 601 does not appear in the log, go to Chapter 3, Maintenance Analysis Procedures (MAPS) to isolate the problem. 9.
Removal and Replacement Procedures (RRPs) 5 b. Click the Sys Err Light tab. The Switch page displays with the Sys Err Light tab selected. A System Error Light is ON message displays on the page. c. Click Clear Light. 13. If necessary, close and lock the equipment cabinet door.
Removal and Replacement Procedures (RRPs) 5 RRP: Backplane Use the following procedures to remove or replace the backplane. A list of tools required is provided. Tools Required The following tools are required to perform these procedures. • Door key with 5/16-inch socket (provided with the FC-512 Fabricenter equipment cabinet). • Torque tool and hex adapter (provided with the director). • Standard flat-tip screwdriver. • Standard cross-tip (Phillips) screwdriver.
Removal and Replacement Procedures (RRPs) 5 — If the director is installed in a McDATA-supplied FC-512 Fabricenter equipment cabinet, insert the 5/16” door tool into the socket hole at the right top of the front door. Turn the tool counter-clockwise to unlock and open the door. Repeat this step to open the rear door. — If the director is installed in a customer-supplied equipment cabinet, unlock and open the cabinet front door as directed by the customer representative.
Removal and Replacement Procedures (RRPs) 5 15. The card cage and backplane are secured to the director chassis with 6 panhead Phillips screws. Use a standard Phillips screwdriver to remove these screws. 16. Remove the card cage and backplane assembly (Figure 5-11). Figure 5-11 Backplane Removal and Replacement 17. Disconnect the maintenance port cable from the backplane. 18. The backplane is secured to the card cage with 7 panhead Phillips screws.
Removal and Replacement Procedures (RRPs) 5 4. Insert and hand tighten the remaining six panhead Phillips screws. 5. Using a standard Phillips screwdriver, tighten the 7 panhead screws that secure the backplane to the card cage. Tighten the screws alternately from bottom to top and from side to side. 6. Connect the maintenance port cable. 7. Replace the card cage and backplane in the director chassis. with 6 panhead Phillips screws.
Removal and Replacement Procedures (RRPs) 5 c. Power on the maintenance terminal. Use the following settings. • Bits per second - 115200. • Data bits - 8. • Parity - None. • Stop bits - 1. • Flow control - Hardware. When the parameters are set, click OK. The HyperTerminal dialog box displays. d. At the > prompt, type the maintenance-level password (the default is level-2) and press Enter. The password is case sensitive. The HyperTerminal dialog box displays with a C> prompt at the top of the window. e.
Removal and Replacement Procedures (RRPs) 5 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. c. Click Clear Light. 24. If necessary, close and lock the equipment cabinet doors.
Removal and Replacement Procedures (RRPs) 5 5-46 Intrepid® 6140 Director Installation and Service Manual
6 Illustrated Parts Breakdown This chapter provides an illustrated parts breakdown for all Intrepid 6140 Director field-replaceable units (FRUs) and parts. Exploded-view assembly drawings are provided for: • Front-accessible FRUs. • Rear-accessible FRUs. • Miscellaneous parts. • Power cords and receptacles. Exploded-view illustrations portray the director disassembly sequence for clarity. Illustrated FRUs and parts are numerically keyed to associated parts lists.
Illustrated Parts Breakdown 6 Front-Accessible FRUs Figure 6-1 illustrates the front-accessible FRUs and Table 6-1 is the parts list. The table includes reference numbers to Figure 6-1, part numbers, descriptions, and quantities.
Illustrated Parts Breakdown 6 Table 6-1 Front-Accessible FRU Parts List Ref. Part Number 6-1-1 Reference Base assembly, Intrepid 6140 Director -2 reference Filler panel, CTP -3 Description Qty. 1 0 to 1 (*ESD*) Printed wiring assembly, 10 Gbps port module (XPM), 1-port, LC, (pluggable optics not included) -4 803-000100-850 (*ESD*) XFP transceiver, optical, shortwave (SW) laser, 10.625 Gbps, 850 nm, LC -4 803-000100-313 (*ESD*) XFP transceiver, optical, longwave (LW) laser, 10.
Illustrated Parts Breakdown 6 Rear-Accessible FRUs Figure 6-2 and Figure 6-3 illustrate the rear-accessible FRUs, and Table 6-2 and Table 6-3 are the parts lists. The table includes reference numbers to Figure 6-2, part numbers, descriptions, and quantities.
Illustrated Parts Breakdown 6 Table 6-2 Rear-Accessible FRU Parts List (Part 1) Ref. Part Number 6-2-1 Reference -2 Description Qty.
Illustrated Parts Breakdown 6 Figure 6-3 Table 6-3 6-6 Rear-Accessible FRUs (Part 2) Rear-Accessible FRU Parts List (Part 2) Ref. Part Number 6-2-1 Reference -2 476-000435-300 -3 -4 Description Qty.
Illustrated Parts Breakdown 6 Miscellaneous Parts Figure 6-4 illustrates the miscellaneous parts, and Table 6-4 is the parts list. The table includes reference numbers to Figure 6-4, part numbers, descriptions, and quantities.
Illustrated Parts Breakdown 6 Table 6-4 6-8 Miscellaneous Parts Ref. Part Number Description 6-1 002-002317-000 Torque driver with 5/32 in. bit 1 -2 803-000057-000 Loopback plug, LC, MM (50/125) (#1148) 1 -2 803-000057-001 Loopback plug, LC, SM (9/125) (blue) (#1149) 1 -3 801-000039-000 Null modem cable, DB9F-DB9F 1 -4 801-000035-010 Ethernet cable, 10 ft. 1 Intrepid® 6140 Director Installation and Service Manual Qty.
Illustrated Parts Breakdown 6 Power Cords and Receptacles Figure 6-5 illustrates the optional power cords and receptacles and Table 6-5 is the parts list. The table includes reference numbers to Figure 6-5, feature numbers, and descriptions.
Illustrated Parts Breakdown 6 Table 6-5 6-10 Power Cord and Receptacle List Ref. Part Number Description -1 806-000004-001 Power cord, AC, United Kingdom BS 1363 right angle, 250 volts, 10 amps, 2.8 meters Receptacle: BS 1363 1012 -2 806-000005-001 Power cord, AC, European Community CEE 7/7 straight, 250 volts, 10 amps, 2.5 meters Receptacle: CEE 7 1013 -3 806-000006-001 Power cord, AC, Australia AS 3112 straight, 250 volts, 10 amps, 2.
Illustrated Parts Breakdown 6 Table 6-5 Power Cord and Receptacle List (continued) Ref. Part Number Description Feature -12 806-000042-000 Power cord, AC, North America NEMA L6-15P straight, twist-lock, 250 volts, 10 amps, 2.8 meters Receptacle: NEMA L6-15R 1016 -13 806-000042-000 Power cord, AC, North America NEMA L6-15P straight, twist-lock, 250 volts, 10 amps, 2.8 meters Receptacle: NEMA L6-15R 1029 -14 806-000043-000 Power cord, AC, Japan NEMA 6-15P straight, 250 volts, 10 amps, 2.
Illustrated Parts Breakdown 6 6-12 Intrepid® 6140 Director Installation and Service Manual
A Event Code Tables An event is an occurrence (state change, problem detection, or problem correction) that requires user attention or that should be reported to a system administrator or service representative. An event usually indicates a director operational state transition, but may also indicate an impending state change (threshold violation). An event may also provide information only, and not indicate an operational state change. Events are reported as event codes.
Event Code Tables A 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. — Severe (not operational). A-2 • Explanation - An explanation of what caused the event. • Action - The recommended course of action (if any) to resolve the problem.
Event Code Tables A System Events (000 through 199) Event Code: 001 Message: System power-down. Severity: Informational. Explanation: The director was powered off or disconnected from the facility AC power source. The event code is distributed the next time the director powers on, but the date and time of the code reflect the power-off time. Action: No action required. Event Data: No supplementary data included with the event.
Event Code Tables A Event Code: 011 Message: Login Server database invalid. Severity: Minor. Explanation: Following a CTP card failover or replacement, initial machine load (IML), or firmware download, the Login Server database failed its cyclic redundancy check (CRC) validation. All fabric services databases are initialized to an empty state, resulting in an implicit fabric logout of all attached devices. Action: Perform the data collection procedure and return the CD to McDATA support personnel.
Event Code Tables A Event Code: 021 Message: Name Server database invalid. Severity: Minor. Explanation: Following a CTP card failover or replacement, IML, or firmware download, the Name Server database failed its CRC validation. All fabric services databases are initialized to an empty, state resulting in an implicit fabric logout of all attached devices. Action: Perform the data collection procedure and return the CD to McDATA support personnel.
Event Code Tables A Event Code: 050 Message: Management server unable to synchronize databases. Severity: Minor. Explanation: Following a CTP card reset or replacement, the management server attempted to acquire an up-to-date copy of its databases from the other CTP card, but failed. All management services databases are initialized to an empty state, resulting in an implicit logout of all devices logged in to the management server.
Event Code Tables A Event Code: 052 Message: Management server internal error. Severity: Informational. 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 McDATA support personnel. Event Data: Supplementary data consists of reporting tasks of type eMST_SB2, with component_id eMSCID_SB2_CHPGM.
Event Code Tables A Event Code: 061 Message: Fabric controller database invalid. Severity: Minor. Explanation: Following a CTP card failover or replacement, IML, or firmware download, the fabric controller database failed its CRC validation. 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 McDATA support personnel.
Event Code Tables A Event Code: 063 Message: Remote switch has too many ISLs. Severity: Major. Explanation: The fabric element (director or switch) whose domain ID is indicated in the event data has too many ISLs attached, and that element is unreachable from this director. Element Manager application Version 3.2 and earlier supports up to 32 ISLs. Element Manager application Version 3.3 and later supports up to 128 ISLs.
Event Code Tables A Event Code: 070 A-10 Message: E_Port is segmented. Severity: Informational. Explanation: A director E_Port recognized an incompatibility with an attached fabric element (director or switch), preventing the director from participating in the fabric. A segmented port does not transmit Class 2 or Class 3 traffic (data from attached devices), but transmits Class F traffic (management and control data from the attached director or switch).
Event Code Tables A Event Code: 070 (continued) Distribution: Director Nonvolatile System Event Log System Error LED Management Server Event Log E-Mail Host Call-Home Sense Info Link Incident Event Code: 071 Message: Switch is isolated. Severity: Informational. Explanation: The director is isolated from other fabric elements (directors or switches). This event code is accompanied by one or more 070 event codes. Refer to the event data for the segmentation reason.
Event Code Tables A Event Code: 072 Message: E_Port connected to unsupported switch. Severity: Informational. Explanation: The director is attached (through an ISL) to an incompatible fabric element (director or switch). Action: Disconnect the ISL. Event Data: No supplementary data included with this event.
Event Code Tables A Event Code: 074 Message: ILS frame delivery error threshold exceeded. Severity: Informational. Explanation: Fabric controller frame delivery errors exceeded an E_Port threshold and caused fabric initialization problems (073 event code). Most fabric initialization problems are caused by control frame delivery errors, as indicated by this code. Event data is intended for engineering evaluation.
Event Code Tables A Event Code: 075 Message: E_Port segmentation recovery. Severity: Informational. Explanation: A segmented E_Port has recovered. Event is not generated if port is manually recovered by blocking/unblocking, offline/online, or removing/inserting ISL. See the event data below for the segmentation reason. Action: Informational (see event 070). Event Data: The first byte of event data (byte 0) specifies the E_Port number.
Event Code Tables A Event Code: 080 Message: Unauthorized worldwide name. Severity: Informational. Explanation: The worldwide name of the device or director plugged in the indicated port is not authorized for that port. Action: Change the port binding definition or plug the correct device or director into this port. Event Data: Byte 0 = Port number reporting the unauthorized connection. Bytes 1 - 3 = reserved. Bytes 4 - 11 = WWN of the unauthorized device or fabric element.
Event Code Tables A Event Code: 081 A-16 Message: Invalid attachment. Severity: Informational. Explanation: A director port recognized an incompatibility with the attached fabric element or device and isolated the port. An isolated port does not transmit Class 2, Class 3, or Class F traffic. Refer to the event data for the reason. Action: Action depends on the reason specified in the event data.
Event Code Tables A Event Data: The first byte of event data (byte 0) specifies the port number. The fifth byte (byte 4) states the isolation reason: 1 = Unknown - Isolation reason is unknown, but probably caused by failure of a device attached to the director through an E_Port connection. Fault isolate the failed device or contact support personnel to report the problem. 2 = Non E_Port mode - Port on this director or other side of ISL is set to F_Port only mode. Change mode of port to G_Port or E_Port.
Event Code Tables A 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. Port fencing threshold settings can be changed to lesser values.
Event Code Tables A Event Code: 083 Message: Port inactive—port set to inactivate state (Release 8.0) Severity: Informational. Explanation: The port has been set to an inactive state because a hardware configuration or software issue is preventing the port from coming online. The inactive reason code is indicated in the event data. Action: Use the reason code to determine the action. Event Data: The first byte of event data (byte 0) specifies the port number.
Event Code Tables A Event Code: 090 Message: Database replication time out. Severity: Minor. Explanation: Replication of a fabric services database from master CTP to backup CTP has timed out. The backup CTP has been dumped and IPLed. After the backup CTP completes the IPL, its databases will be brought up to date and replication will resume. Action: Perform a data collection for this director using the SAN management application.
Event Code Tables A Event Code: 120 Message: Error detected while processing system management command. Severity: Informational. Explanation: This event occurs when the director receives an SAN management command that violates specified boundary conditions, typically as a result of a network error. The director rejects the command, drops the director-to-management server Ethernet link, and forces error recovery processing. When the link recovers, the command can be retried.
Event Code Tables A 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.
Event Code Tables A 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.
Event Code Tables A Event Code: 150 Message: Zone merge failure. Severity: Informational. Explanation: During ISL initialization, the zone merge process failed. Either an incompatible zone set was detected or a problem occurred during delivery of a zone merge frame. This event code always precedes a 070 ISL segmentation event code, and represents the reply of an adjacent fabric element in response to a zone merge frame. Refer to the event data for the failure reason.
Event Code Tables A Event Code: 151 Message: Fabric configuration failure. Severity: Informational. Explanation: A fabric-wide configuration activation failed. For example, a zone set activation. An event 151 is only logged by the managing switch. It is intended to detect and log errors that occur on the managing switch in the fabric when fabric configuration failures are detected. It is intended to help engineering personnel determine the cause of fabric-configuration failures.
Event Code Tables A Power Supply Events (200 through 299) Event Code: 200 Message: Power supply AC voltage failure. Severity: Major. Explanation: Alternating current (AC) input to the indicated power supply is disconnected or AC circuitry in the power supply failed. The second power supply assumes the full operating load for the director. Action: Ensure the power supply is connected to facility AC power, and verify operation of the facility power source.
Event Code Tables A Event Code: 202 Message: Power supply thermal failure. Severity: Major. Explanation: The thermal sensor associated with a power supply indicates an overheat condition that shut down the power supply. The second power supply assumes the full operating load for the director. Action: Replace the failed power supply. Perform the data collection procedure and return the CD and failed power supply to McDATA support personnel.
Event Code Tables A 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.
Event Code Tables A Event Code: 207 Message: Power supply installed. Severity: Informational. Explanation: A redundant power supply was installed with the director powered on and operational. Both power supplies adjust to share operating load for the director. Action: No action required. Event Data: No supplementary data included with the event.
Event Code Tables A 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 illuminates at the rear of the fan module associated with the failed fan. Action: Replace the indicated fan module. Event Data: The first byte of event data (byte 0) specifies the failed fan number.
Event Code Tables A 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 illuminates at the rear of the fan modules associated with the failed fans. Action: Replace the indicated fan modules. Event Data: The first byte of event data (byte 0) specifies the failed fan numbers.
Event Code Tables A 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 illuminates at the rear of the fan modules associated with the failed fans. Action: Replace the indicated fan modules. Event Data: The first byte of event data (byte 0) specifies the failed fan numbers.
Event Code Tables A 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.
Event Code Tables A 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.
Event Code Tables A 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.
Event Code Tables A 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 Nonvolatile System Event Log System Error LED Event Log E-Mail Host Call-Home Sense Info Link Incident Event Code: 321 Message: Fan module installed.
Event Code Tables A 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 Nonvolatile System Event Log System Error LED Event Log E-Mail Host Call-Home Sense Info Link Incident Event Code: 370 Message: Fan status polling temporarily disabled. Severity: Minor.
Event Code Tables A CTP Card Events (400 through 499) Event Code: 400 Message: Power-up diagnostics failure. Severity: Major. Explanation: Power-on self tests (POSTs) detected a faulty field-replaceable unit (FRU) as indicated by the event data. Action: Replace the failed FRU with a functional FRU. Perform the data collection procedure and return the CD and faulty FRU to McDATA support personnel.
Event Code Tables A Event Code: 411 Message: Firmware fault. Severity: Major. Explanation: Firmware executing on the indicated CTP card encountered an unexpected operating condition and dumped the operating state to FLASH memory for retrieval and analysis. The dump file is automatically transferred from the director to the management server, where it is stored for retrieval through the data collection procedure. A non-disruptive failover to the backup CTP card occurs.
Event Code Tables A Event Code: 413 Message: Backup CTP card POST failure. Severity: Major. Explanation: A backup CTP card was installed in the director and failed POSTs. Action: Replace the indicated CTP card with a functional card. Perform the data collection procedure and return the CD and faulty card to McDATA support personnel. Event Data: No supplementary data included with this event.
Event Code Tables A 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.
Event Code Tables A 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.
Event Code Tables A Event Code: 420 Message: Backup CTP card NVRAM failure. Severity: Major. Explanation: 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 McDATA support personnel. Event Data: Byte 0 = NVRAM area identifier.
Event Code Tables A 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 Nonvolatile System Event Log System Error LED Management Server Event Log E-Mail Host Call-Home Sense Info Link Incident Event Code: 423 Message: CTP firmware download initiated.
Event Code Tables A Event Code: 426 Message: Multiple ECC single-bit errors occurred. Severity: Minor. Explanation: When the SDRAM controller detects an error checking and correction (ECC) error, an interrupt occurs. If an interrupt occurs a certain number of times weekly, a 426 event code is recorded. The number of interrupts is indicated by the event data. Action: No action required. SDRAM is probably malfunctioning intermittently.
Event Code Tables A Event Code: 433 Message: Non-recoverable Ethernet fault. Severity: Major. Explanation: A non-recoverable error was detected on the CTP card Ethernet adapter and the LAN connection to the management server or Internet terminated. All Fibre Channel switching functions remain unaffected. This event only occurs on a director with a single CTP card. Because Ethernet communication is lost, no failure indication is externally reported.
Event Code Tables A 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. Byte 1 = engineering reason code. Bytes 4 - 7 = elapsed millisecond tick count. Bytes 8 and 9 = high-availability error callout #1.
Event Code Tables A 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. Event data indicates which feature or features are installed. Action: No action required.
Event Code Tables A Port Card (UPM and XPM) Events (500 through 599) Event Code: 500 Message: Port card hot-insertion initiated. Severity: Informational Explanation: Installation of a UPM was initiated with the director powered on and operational. The event indicates that operational firmware detected the presence of the UPM, but the card is not seated. When the card is seated in the director chassis and identified by firmware, an event code 501 is generated.
Event Code Tables A 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 four-port UPM. Action: No action required. An event code 504 is generated if the UPM fails. Event Data: Byte 0 = UPM slot position. Byte 1 = engineering reason code. Bytes 4 - 7 = elapsed millisecond tick count. Bytes 8 and 9 = high-availability error callout #1.
Event Code Tables A Event Code: 504 Message: Port module failure. Severity: Major. Explanation: The indicated UPM failed. Action: Replace the indicated UPM with a functional UPM of the same type. Perform the data collection procedure and return the CD and faulty card to McDATA support personnel. Event Data: Byte 0 = UPM slot position. Byte 1 = engineering reason code. Bytes 4 - 7 = elapsed millisecond tick count. Bytes 8 - 11 = reason code specific data.
Event Code Tables A Event Code: 506 Message: Fibre Channel port failure. Severity: Major. Explanation: A Fibre channel port on a UPM failed. The amber LED corresponding to the port illuminates to indicate the failure. Other ports remain operational if their LEDs are extinguished. Action: Replace the indicated UPM with a functional UPM of the same type. Perform the data collection procedure and return the CD and faulty card to McDATA support personnel. Event Data: Byte 0 = port number.
Event Code Tables A Event Code: 508 Message: Fibre Channel port anomaly detected. Severity: Informational. Explanation: The CTP card detected a deviation in the normal operating mode or status of the indicated Fibre Channel port. Action: No action required. An event code 506 is generated if this anomaly results in a hard port failure. Event Data: Byte 0 = port number. Byte 1 = anomaly reason code. Bytes 4 - 7 = elapsed millisecond tick count. Bytes 8 and 9 = high-availability error callout #1.
Event Code Tables A Distribution: Director Management Server Host Nonvolatile System Event Log System Error LED Event Log E-Mail Call-Home Sense Info Link Incident 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.
Event Code Tables A 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; Bit 2 = XFP. Bytes 4 - 7 = elapsed millisecond tick count.
Event Code Tables A 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 illuminates to indicate the failure. Other ports remain operational if their LEDs are extinguished. 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; Bit 2 = XFP.
Event Code Tables A Event Code: 516 Message: SFP/XFP optics digital diagnostics alarm threshold exceeded. Severity: Minor. Explanation: A digital diagnostics warning threshold is exceeded. If warning condition persists, additional 516 events are generated. 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; Bit 2 = XFP. Bytes 4 - 7 = elapsed millisecond tick count.
Event Code Tables A Event Code: 581 Message: Implicit incident. Severity: Major. Explanation: An attached open systems interconnection (OSI) or Fibre Connection (FICON) server recognized a condition caused by an event that occurred at the server. The event caused an implicit Fibre Channel link incident. Action: A link incident record (LIR) is generated and sent to the attached server using the reporting procedure defined in T11/99-017v0 (OSI) or the FICON architecture document (FICON).
Event Code Tables A Event Code: 583 Message: Loss of signal or loss of synchronization. Severity: Major. Explanation: An attached OSI or FICON server recognized a loss-of-signal condition or a loss-of-synchronization condition that persisted for more than the specified receiver-transmitter timeout value (R_T_TOV). Action: A LIR is generated and sent to the attached server using the reporting procedure defined in T11/99-017v0 (OSI) or the FICON architecture document (FICON).
Event Code Tables A Event Code: 585 Message: Primitive sequence timeout. Severity: Major. Explanation: An attached OSI or FICON server recognized either a link reset (LR) protocol timeout or a timeout while waiting for the appropriate response (while in a NOS receive state and after NOS was not longer recognized). Action: A LIR is generated and sent to the attached server using the reporting procedure defined in T11/99-017v0 (OSI) or the FICON architecture document (FICON).
Event Code Tables A 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.
Event Code Tables A 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. Byte 1 = anomaly reason code. Bytes 4 - 7 = elapsed millisecond tick count. Bytes 8 and 9 = high-availability error callout #1.
Event Code Tables A Event Code: 604 Message: SBAR failure. Severity: Major. Explanation: The indicated SBAR failed. If the active SBAR fails, the backup SBAR takes over operation. If the backup SBAR fails, the active 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 McDATA support personnel. Event Data: Byte 0 = SBAR slot position. Byte 1 = engineering failure reason code.
Event Code Tables A 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.
Event Code Tables A Event Code: 619 Message: SBAR module ASIC reset. Severity: Informational. Explanation: System software detected an abnormal event associated with the SBAR. Recovery of the SBAR required system software to perform a reset of the port module hardware. Action: 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.
Event Code Tables A 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. Bytes 10 and 11 = operational SBAR fan count. Byte 12 - 15 = reserved.
Event Code Tables A Thermal Events (800 through 899) Event Code: 800 Message: High temperature warning (port module thermal sensor). Severity: Major. Explanation: The thermal sensor associated with a UPM indicates the warm temperature threshold was reached or exceeded. Action: Replace the indicated UPM with a functional UPM of the same type. Perform the data collection procedure and return the CD and faulty card to McDATA support personnel.
Event Code Tables A Event Code: 802 Message: Port module shutdown due to thermal violation. Severity: Major. Explanation: A UPM failed and was powered off because of excessive heat. This event follows an indication that the hot temperature threshold was reached or exceeded (event code 801). Action: Replace the failed UPM with a functional UPM of the same type. Perform the data collection procedure and return the CD and faulty card to McDATA support personnel.
Event Code Tables A Event Code: 806 Message: Critically hot temperature warning (SBAR thermal sensor). Severity: Major. Explanation: 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 McDATA support personnel. Event Data: No supplementary data included with this event.
Event Code Tables A Event Code: 810 Message: High temperature warning (CTP card thermal sensor). Severity: Major. Explanation: The thermal sensor associated with a CTP card indicates the warm temperature threshold was reached or exceeded. Action: Replace the indicated CTP card with a functional card. Perform the data collection procedure and return the CD and faulty card to McDATA support personnel. Event Data: No supplementary data included with this event.
Event Code Tables A Event Code: 812 Message: CTP card shutdown due to thermal violation. Severity: Major. Explanation: A CTP card failed and was powered off because of excessive heat. This event follows an indication that the hot temperature threshold was reached or exceeded (event code 811). If the active CTP card fails, the backup card takes over operation. If the backup CTP card fails, the active card is not impacted. Action: Replace the failed CTP card with a functional card.
Event Code Tables A A-72 Intrepid® 6140 Director Installation and Service Manual
B Director Specifications This appendix lists physical characteristics, storage and shipping environment, and operating environment for the Intrepid 6140 Director. Physical Characteristics Dimensions: Height: 52.9 centimeters (20.8 inches) or 12 rack units Width: 44.5 centimeters (17.5 inches) Depth: 61.3 centimeters. (24.1 inches) Weight: 75.9 kilograms (167.0 pounds) Power requirements: Input voltage: 200 to 240 VAC Input current: 4.
Director Specifications B 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).
Director Specifications B Fabricenter Equipment Cabinet Service Clearances Front: 91.4 centimeters (36.0 inches) Rear: 91.4 centimeters (36.
Director Specifications B B-4 Intrepid® 6140 Director Installation and Service Manual
C Management Server and Ethernet Hub This appendix describes the management server and the optional, Ethernet hub. Management Server Description The management server with a liquid crystal display (LCD) panel (Figure C-1) is a one rack unit (1U) high, LAN-accessed, rack- mount unit that provides a central point of control for up to 48 connected directors, switches, or other McDATA managed products. Server applications are accessed through a LAN-attached PC or workstation with client software installed.
Management Server and Ethernet Hub C remote user workstations. The second adapter (LAN 2) attaches to a private LAN segment containing directors, switches, or other managed McDATA products. Management Server Specifications The following list summarizes the hardware specifications for the management server platform. Some platforms may ship with more enhanced hardware, such as a faster processor, additional randomaccess memory (RAM), or a higher-capacity hard drive.
Management Server and Ethernet Hub C . Figure C-2 24-Port Ethernet Hub Hubs can be daisy-chained to provide additional connections as more directors or switches (or other McDATA 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.
Management Server and Ethernet Hub C C-4 Intrepid® 6140 Director Installation and Service Manual
D Restore Management Server The procedure in this appendix provides information to restore the management server after a failure of the server hard drive. The procedure includes restoration of the: • Windows 2000 Professional operating system. • Windows 2000 configuration information. • Storage area network (SAN) management application (EFCM or SANavigator) and Intrepid 6140 Element Manager application. • SAN management application data directory.
Restore Management Server D • SAN management data directory backup on CD-ROM - The SAN management data directory is automatically backed up to a CD when the management server is rebooted or when the data directory contents change. The data directory includes: — All configuration data (product definitions, user names, passwords, user rights, nicknames, session options, SNMP trap recipients, E-mail recipients, and Ethernet event notifications).
Restore Management Server D 5. Power cycle the server. The server performs power-on self-tests (POSTs). After successful POST completion, the LCD panel displays a Welcome!! message, then cycles through and displays server operational information. 6. Configure the following parameters at the server LCD panel (Task 5: Configure Director Network Information (Optional) on page 2-30). • LCD panel password. • IP address for private and public LAN connections. • Subnet mask or private and public LAN connections.
Restore Management Server D 11. At the Run dialog box, type D:\mcdataServerInstall in the Open field. 12. Click OK. A series of message boxes appear as the InstallAnywhere third-party application prepares to install the SAN management software, followed by the McDATA EFC Management Applications dialog box. 13. Follow the online instructions for the InstallAnywhere program. Click Next, Install, or Done as appropriate. 14. Remove the EFC Management Applications CD-ROM from the CD-RW drive. 15.
Restore Management Server D Figure D-2 VNC Authentication Screen d. Type the default password and click OK. The Welcome to Windows dialog box displays (Figure D-3). NOTE: The default TightVNC viewer password is password. Figure D-3 Welcome to Windows Dialog Box e. 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 (Figure D-4). NOTE: Do not simultaneously press Ctrl, Alt, and Delete.
Restore Management Server D Figure D-4 Log On to Windows Dialog Box f. Type the default Windows 2000 user name and password and click OK. The server Windows 2000 desktop opens and the EFCM Log In or SANavigator Log In dialog box displays (Figure D-5). NOTE: The default Windows 2000 user name is Administrator and the default password is password. The user name and password are case-sensitive. Figure D-5 EFCM Log In or SANavigator Log In Log In Dialog Box g.
Restore Management Server D NOTE: The default SAN management application user name is Administrator and the default password is password. The user name and password are case-sensitive. h. Click Login. The application opens and the EFCM or SANavigator main window appears.
Restore Management Server D D-8 Intrepid® 6140 Director Installation and Service Manual
E Safety Notices (Multi-Lingual Translations) The DANGER and CAUTION safety notices in this publication are provided in the following languages: • English • Chinese, Simplified (PRC China) • Chinese, Traditional (ROC Taiwan) • French • German • Hebrew • Italian • Portuguese (Brazil) • Spanish • Spanish (Latin America) Safety Notices (Multi-Lingual Translations) E-1
Safety Notices (Multi-Lingual Translations) E DANGER Use the supplied power cords. Ensure the facility power receptacle is the correct type, supplies the required voltage, and is properly grounded. DANGER Disconnect the power cords. CAUTION Use safe lifting practices when moving the product.
Safety Notices (Multi-Lingual Translations) E E-3
Safety Notices (Multi-Lingual Translations) E DANGER Utiliser les câbles d’alimentation fournis. S’assurer que la prise de courant du local est du type correct, délivre la tension requise et est correctement raccordée à la terre. DANGER Débrancher les câbles d’alimentation. ATTENTION Utiliser des techniques de levage sûres pour déplacer le produit. GEFAHR Die mitgelieferten Netzkabel verwenden.
Safety Notices (Multi-Lingual Translations) E PERICOLO Usare il cavo di alimentazione in dotazione. Assicurarsi che la presa di corrente a disposizione sia del tipo corretto, eroghi la tensione richiesta e sia dotata di messa a terra idonea. PERICOLO Scollegare tutti i cavi di alimentazione. ATTENZIONE Sollevare il prodotto con prudenza per evitare di infortunarsi.
Safety Notices (Multi-Lingual Translations) E PERIGO Use os cordões elétricos fornecidos. Certifique-se de que o tipo de receptor de energia da facilidade é apropriado, fornece a voltagem necessária, e está corretamente aterrado. PERIGO Disconecte os cordões elétricos. CUIDADO Use práticas de levantamento seguras ao mover o produto. PELIGRO Utilice los cables de alimentación proporcionados.
Safety Notices (Multi-Lingual Translations) E PRECAUCIÓN Tenga mucho cuidado al levantar el producto para moverlo. PELIGRO Utilice los cables de alimentación proporcionados. Asegúrese que el receptáculo tomacorriente para la instalación sea el tipo correcto, suministre el voltaje necesario, y que esté apropiadamente puesto a tierra. PELIGRO Desconecte los cables de alimentación. PRECAUCIÓN Tenga mucho cuidado al levantar el producto para moverlo.
Safety Notices (Multi-Lingual Translations) E E-8 Intrepid® 6140 Director Installation and Service Manual
Glossary This glossary defines terms used in this manual or terms related to the product. It is not a comprehensive glossary of computer terms. The following cross-references are used in this glossary: Contrast with. This refers to a term that has an opposite or substantively different meaning. See. This refers the reader to another keyword or phrase for the same term. See also. This refers the reader to definite additional information contained in another entry.
Glossary 10 Gbps port module card A printed circuit board (Intrepid-series directors only) that provides port connections that support 10.625 Gbps Fibre Channel communication. Port connectivity is provided through XFP optical transceivers. Contrast with fibre port module card and universal port module card.
Glossary BB_Credit beaconing BER bidirectional bit bit error rate B_Port See buffer-to-buffer credit. The use of light-emitting diodes on ports, port cards, FRUs, directors, and switches to aid in the fault-isolation process. When enabled, beaconing causes amber LEDs to flash. See bit error rate. 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.
Glossary C call-home central memory module card A printed circuit board (ED-5000 Director only) that provides the storage area for director ports to deposit and retrieve Fibre Channel frames. Each port is allocated a portion of this memory, divided into a fixed number of frame buffers. Class 2 Fibre Channel service Provides connectionless multiplexed Fibre Channel service between fabric-attached node ports (N_Ports) with acknowledgement of frame delivery or nondelivery.
Glossary configuration data A collection of data that results from configuring director, switch, and system operating parameters. Configuration data includes product identification, port configurations, operating parameters, SNMP configuration, and zoning configuration. A backup file is required to restore configuration data if the CTP card in a nonredundant director is removed and replaced.
Glossary for use in enterprise computing environments. Contrast with fabric switch. DNS DNS server See domain name system. For Internet and TCP/IP applications, a DNS server supplies name-to-address translation by mapping domain names to Internet addresses. domain (1) A group of devices (nodes) on a network that form an entity with resources under common control. For example, a domain can be a group of servers connected and named to simplify network administration and security.
Glossary EFCM Lite application EFC Management Services application EFC Manager application electrostatic discharge Element Manager application enterprise Enterprise Fabric Connectivity Management Enterprise Systems Architecture The EFCM Lite application bundles the EFC Manager application, director or switch-specific Element Manager application, and Cluster Manager application on a CD-ROM for installation on a customersupplied server.
Glossary management and increase storage from 2 gigabyte to 6 terabytes. The architecture was enhanced with the introduction of ESA/390 in 1990. Enterprise Systems Connection E_Port error-detect time-out value ESA ESCON ESD g-8 An IBM architecture, technology, and set of products and services introduced in 1990 that provides a dynamically-connected computing environment using fiber-optic cables as the data transmission medium. See also Fibre Connection. See expansion port.
Glossary F Fabric Log fabric login A log recorded at the EFC Manager application that displays the time and nature of changes made to a managed fabric, such as a switch added or removed, ISL added or removed, fabric renamed or persisted, or zone set activated. The fabric login (FLOGI) command is initiated by a fabric-attached node port (N_Port) and establishes the operating parameters and topology required for fabric login. The command is accepted by a fabric port (F_Port).
Glossary FC-3 The Fibre Channel layer that provides a set of services common across multiple node ports (N_Ports) of a Fibre Channel node. The services are not commonly used and are essentially reserved for Fibre Channel architecture expansion. FC-4 The Fibre Channel layer that provides mapping of Fibre Channel capabilities to upper level protocols (ULPs), including IP and SCSI. FC-AL Acronym for Fibre Channel arbitrated loop. Synonymous with arbitrated loop.
Glossary 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. FICON is the successor to ESCON, but is designed to coexist with ESCON technology. See also Enterprise Systems Connection.
Glossary G gateway address Gb See gigabit. GB See gigabyte. GBIC See gigabit interface converter. Gbps Acronym for gigabits per second. Also written as Gb/sec. generic port generic port module card GHz gigabit gigabit interface converter g-12 For TCP/IP applications, the address of a router to which a device sends frames destined for addresses not on the same physical network as the sending device. The hexadecimal format for a gateway address is XXX.XXX.XXX.XXX.
Glossary GLS card GPM card G_Port graphical user interface GSM card GUI GXX card A G_Port, Longwave laser, Singlemode fiber variant of an ED-5000 Director GPM card. The card provides four longwave laser port connections. Contrast with GSM card and GXX card. See generic port module card. See generic port. A visually oriented interface where the user interacts with representations of real-world objects displayed on the computer screen.
Glossary high speed serial data connector A 20-pin serial connector type that provides connectivity to an ES-1000 Switch GBIC. Contrast with DB-9 connector. host bus adapter A logic card that provides a link between a server and storage subsystem, and that integrates the operating systems and I/O protocols of both devices to ensure interoperability. H_Port See hub port. HSSDC See high speed serial data connector.
Glossary IP address See Internet protocol address. IPL See initial program load. ISL See interswitch link. K Kb See kilobit. KB See kilobyte. kilobit kilobyte A unit of measure for data storage, equal to 1,024 bits. A kilobit is generally approximated as one thousand bits. A unit of measure for data storage, equal to 1,024 bytes. A kilobyte is generally approximated as one thousand bytes. L LAN laser latency LED light-emitting diode LIN See local area network.
Glossary link incident Link Incident Log LIP sequence local area network The interruption of traffic on a Fibre Channel link due to loss of light or other malfunction. A log recorded at the Element Manager application that displays a history of Fibre Channel link incidents (with associated port numbers) for a director or switch. See loop initialization primitive sequence. A communication system that links computers in a network through a wiring-based cable scheme.
Glossary management information base management server The related set of software objects (variables) that a gateway running the SNMP management protocol maintains. A MIB defines variables needed by the SNMP protocol to monitor and control components in the network. A rack-mounted processor shipped with a director or switch, and dedicated to running the EFC Manager application, Element Manager application, and Cluster Manager application. Formerly EFC Server. Mb See megabit. MB See megabyte.
Glossary multimode optical fiber A graded-index or step-index optical fiber that allows more than one mode (light path) to propagate. Contrast with singlemode optical fiber. N name server nickname NL_Port node node loop port node port nondisruptive maintenance N_Port In Fibre Channel protocol, a server that allows N_Ports to register information. This allows devices to obtain information about other fabric-attached devices by sending queries to the name server.
Glossary the implementation of a layer can be changed without affecting other layers. open-systems management server An optional feature that enables inband management and host control of a director or switch through an OSI server attached to a product port. Contrast with FICON management server. open-systems mode The management mode used to specify director or switch port connectivity when the product is attached to other McDATA products or OSI-compliant devices as part of an open fabric.
Glossary preferred domain ID The domain ID that a director or switch requests from a fabric principal switch. If the preferred value is in use, the principal switch assigns a different value. See also domain ID. principal switch In a multiswitch fabric, the switch that allocates domain IDs to itself and all other switches in the fabric. There is always one principal switch in a fabric. If a switch is not connected to any other switches, it acts as its own principal switch.
Glossary redundancy Performance characteristic of a system or product whose integral components are backed up by identical components to which operations automatically failover after component failure. Redundancy is a vital characteristic of high-availability computer systems and networks. remote notification The process by which a system informs remote users and workstations of certain classes of events that occur.
Glossary scalable The ability of a system to adapt to increased demands. A scalable network could start with a few nodes but easily expand to thousands of nodes. SC duplex connector An optical fiber connector that terminates jumper cables in one housing and provides physical attachment to a subscriber connector (SC) duplex receptacle. SC duplex connectors provide optical port connectivity for the ED-5000 Director and ES-1000 switch.
Glossary small form factor pluggable transceiver SMTP SNMP A laser-driven small form factor optical transceiver used for a wide range of networking applications requiring high data rates (usually 1 and 2 Gbps). SFP transceivers provide port connectivity for Intrepid-series directors and Sphereon-series switches. Contrast with gigabit interface converter and SC duplex connector. See simple mail transfer protocol. See simple network management protocol.
Glossary A low value indicates a high likelihood of becoming the principal switch. T TCP See transmission control protocol. TCP/IP See transmission control protocol/Internet protocol. Telnet The user command and underlying TCP/IP protocol for remote terminal access and connection over a network. Threshold Alert Log A log recorded at the Element Manager application that displays a history of threshold alert notifications for a director or switch, including the date and time an alert occurred.
Glossary uninterruptable power supply A buffer between public utility power or other power source, and a system that requires precise, uninterrupted power. universal port module card A printed circuit board (Intrepid-series directors only) that provides four port connections that support 1.0625 or 2.125 Gbps Fibre Channel communication. Port connectivity is provided through SFP optical transceivers. Contrast with fibre port module card and 10 Gbps port module card.
Glossary wide area network A network that covers a larger geographical area than a LAN and where telecommunications links are typically leased through a common carrier. Contrast with local area network, metropolitan area network, and storage area network. world-wide name An eight-byte string that uniquely identifies a Fibre Channel entity such as a port, node, director, switch, or fabric. WWN See world-wide name. X XFP transceiver XPM See 10 Gbps form factor pluggable transceiver.
Index Numerics 10 Gbps form factor pluggable optical transceiver See XFP optical transceiver 10/100 BaseT ethernet hub 1-1 10/100 Mbps ethernet port 1-6 A AC module 1-11 removing and replacing 5-26 AC system harness 1-11 access control list configure Element Manager 2-69 description 2-69 acoustical noise, director B-2 airflow clearances, director B-1 allen wrench, caution 1-15 altitude operating environment B-2 shipping and storage environment B-2 angular velocity, of fans 1-11 asynchronous RS-232 null mo
Index enable through EFCM Basic Edition 2-29 enable through Element Manager 2-61 switch configure through EFCM Basic Edition 2-29 configure through Element Manager 2-69 enable through EFCM Basic Edition 2-29 enable through Element Manager 2-69 blocking port 4-27 C call-home support configure at management server 2-46, 2-67 enable at management server 2-67 caution statements, list of -xxii CFR, laser compliance -xx, 1-7 channel wrap test, procedure 4-31 class 1 laser products -xx class 1 laser transceivers
Index EFCM Basic Edition 2-25 Element Manager 2-51 port BB_Credit EFCM Basic Edition 2-20 Element Manager 2-60 port binding EFCM Basic Edition 2-29 Element Manager 2-61 port fencing SAN management application 2-70 port NPIV EFCM Basic Edition 2-21 Element Manager 2-61 preferred path Element Manager 2-70 RADIUS server Element Manager 2-69 SANtegrity authentication Element Manager 2-68 SANtegrity binding Element Manager 2-68 SAN management application 2-68 security features Element Manager 2-68 SAN managemen
Index Windows 2000 user name D-6 Windows password 4-49 Windows user name 4-49 diagnostics port diagnostics 4-11 dimensions, director B-1 director AC module 1-11 acoustical noise B-2 airflow clearances B-1 CTP card 1-6 dimensions B-1 displaying information 4-21 event codes A-1 event log 4-5, A-1 fabric log 4-4 fan module 1-11 features error-detection 1-12 reporting 1-12 serviceability 1-12 general description 1-1 heat dissipation B-1 illustrated parts breakdown 6-1 IML 1-5, 4-38 installation 2-9 IPL 4-38, 4
Index switch fabric log 4-8 e-mail support configure at management server 2-65 enable at management server 2-65 embedded port frame log EFCM Basic Edition 4-10 embedded port log 4-7 embedded port subsystem 1-6 embedded web server interface See EFCM Basic Edition enable call-home support 2-67 CLI EFCM Basic Edition 2-23 EFCM Basic Edition 2-65 e-mail notification 2-65 Enterprise Fabric Mode SAN management application 2-69 Ethernet events 2-67 host control EFCM Basic Edition 2-23 Element Manager 2-53 port bi
Index fabric log 4-4 EFCM Basic Edition 4-10 fabric parameters configure EFCM Basic Edition 2-16 Element Manager 2-58 Fabricenter cabinet 1-1 door key 1-16 service clearances B-3 Fabricenter equipment cabinet Ethernet hub installation 2-8 management server installation 2-34 failover, SBAR assembly 1-11 fan module 1-11 removing and replacing 5-30 fan module events, event codes A-30 fault isolation logs 4-3 MAP 0000 - Start MAP 3-8 MAP 0100 - Power distribution analysis 3-13 MAP 0200 - POST failure analysis
Index G g_port UPM card 1-7 XPM card 1-8 gateway address change director address 2-18, 2-30 default 4-2, 5-1 director default 2-1, 3-1 management server default 2-49 grounding point front 5-4 H hardware log 4-5 hardware view displaying director information 4-21 heat dissipation, director B-1 hexagonal adapter 1-15 humidity operating environment B-2 shipping and storage environment B-2 HyperTerminal 1-18 I identification configure EFCM Basic Edition 2-13 Element Manager 2-56 illustrated parts breakdown 6-
Index preferred path 2-70 Intrepid 6140 Director See director IP address change director address 2-18, 2-30 default 4-2, 5-1 director default 2-1, 3-1 DNS server default 2-49 management server default 2-49 IPL 4-38, 4-39 L LAN connection connect management server 2-34 laser transceivers 1-7 lasers, compliance statement -xx LCD panel configure private server network addresses 2-37 configure public server network addresses 2-38 default password for management server 2-36 LEDs beaconing 1-5 CTP card 1-6 fan
Index Fibre Alliance MIB 1-14 firmware versions, storing 4-41 installation 2-34 LCD panel password 2-36 restore procedure D-2 restore requirements D-1 specifications C-2 managing configuration data 4-50 director 1-18 McDATA warranty -xx MIBs 1-14 multiswitch fabric e_port segmentation reasons for 4-16 EFCM Basic Edition 2-23 Element Manager 2-53 configure PFE key EFCM Basic Edition 2-26 OpenTrunking configure Element Manager 2-69 configure PFE key EFCM Basic Edition 2-26 Element Manager 2-52 description 2
Index traffic EFCM Basic Edition 4-20 Element Manager application 4-14 PFE keys configure EFCM Basic Edition 2-25 Element Manager 2-51 Element Manager application 2-25, 2-51 Flexport Technology 2-26 full-volatility 2-26, 2-52 N_Port ID virtualization 2-26, 2-52 open-systems management server 2-26 OpenTrunking 2-26, 2-52 preferred path 2-26 SANtegrity authentication 2-26, 2-52 SANtegrity binding 2-26, 2-52 physical characteristics, director B-1 port binding configure EFCM Basic Edition 2-29 Element Manager
Index managing firmware versions 4-41 power-off 4-35 power-on 4-34 reset 4-39 setting offline 4-34, 4-36 setting online 4-34, 4-36 upgrading software 4-47 ProComm Plus 1-18 Product Manager See element manager product status log 4-4 protective plug 1-16 publications related -xix R R_A_TOV 2-17, 2-58 rack-mount installation Ethernet hub 2-8 management server 2-34 radio frequency interference, compliance -xx RADIUS server configure Element Manager 2-69 description 2-69 rear-accessible FRUs, parts list 6-5, 6
Index default password 4-49, D-7 default user name 4-49, D-7 SANtegrity authentication access control list 2-69 configure Element Manager 2-68 configure PFE key EFCM Basic Edition 2-26 Element Manager 2-52 RADIUS server support 2-69 settings 2-68 SANtegrity binding configure Element Manager 2-68 SAN management application 2-68 configure PFE key EFCM Basic Edition 2-26 Element Manager 2-52 Enterprise Fabric Mode configure through SAN management application 2-69 fabric binding configure through SAN managemen
Index system events event codes A-3 system services processor 1-6 T TCP/IP MIB-II definition 1-14 technical support filecenter registration 2-75 Telnet access disable at management server 2-65 enable at management server 2-65 temperature operating environment B-2 shipping and storage environment B-2 test call-home support 2-67 e-mail notification 2-65 thermal events event codes A-67 threshold alert port properties dialog box 4-16 reasons for 4-16 threshold alerts configure 2-62 description 2-62 types 2-63
Index power supply 1-11 W warranty -xx weight, director B-1 wet-bulb temperature operating environment B-2 shipping and storage environment B-2 Windows configure users 2-42 default password 2-39, 2-72 user name 2-39, 2-72 default password 4-49 default user name 4-49 Windows 2000 default password D-6 default user name D-6 Windows operating systems, versions 1-18 world-wide name See WWN WWN port properties dialog box 4-16 X XFP optical transceiver 1-9 removing and replacing 5-17 XPM card description 1-8 ev
