McDATA® Sphereon™ 4500 Fabric Switch Installation and Service Manual P/N 620-000159-320 REV A
Record of Revisions and Updates Revision Date Description 620-000159-000 8/2002 Initial release of the manual to support early-ship products. 620-000159-100 10/2002 General availability (GA) release of the manual. Describes Release 6.3 of the Enterprise Fabric Connectivity Manager application. 620-000159-200 2/2003 Revision of the manual to describe additional features, Release 7.0, and Release 7.1 of the Enterprise Fabric Connectivity Manager application.
Contents Preface ...........................................................................................................................xix Chapter 1 General Information Switch Description............................................................................1-2 Field-Replaceable Units ............................................................1-3 SFP Transceiver ..........................................................................1-4 Power Supply Assembly ..................................
Contents Chapter 2 Installation Tasks Factory Defaults ................................................................................2-1 Installation Options ..........................................................................2-2 Summary of Installation Tasks........................................................2-3 Task 1: Verify Installation Requirements .......................................2-4 Task 2: Unpack, Inspect, and Install the Ethernet Hub (Optional).
Contents Change Default Administrator Password ........................... 2-64 Add a New User...................................................................... 2-65 Change User Properties ......................................................... 2-67 Task 10: Set Management Server Date and Time....................... 2-69 Task 11: Configure the Call-Home Feature (Optional) ............. 2-71 Task 12: Assign User Names and Passwords .............................
Contents MAP 0100: Power Distribution Analysis ....................................3-30 MAP 0200: POST Failure Analysis ...............................................3-38 MAP 0300: Server Application Problem Determination...........3-41 MAP 0400: Loss of Server Communication ................................3-51 MAP 0500: FRU Failure Analysis .................................................3-68 MAP 0600: Port Failure and Link Incident Analysis .................
Contents Block a Port (Management Server)....................................... 4-52 Unblock a Port (Management Server).................................. 4-53 Clean Fiber-Optic Components.................................................... 4-54 Power-On Procedure ..................................................................... 4-55 Power-Off Procedure ..................................................................... 4-56 IML, IPL, or Reset the Switch ..............................................
Contents N................................................................................................A-21 P.................................................................................................A-22 R ................................................................................................A-23 S.................................................................................................A-24 T..........................................................................................
January 26, 2005 2:24 pm serviceLOF.fm (Templates v3.0) 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 1-13 1-14 Sphereon 4500 Switch .................................................................................. 1-2 Sphereon 4500 Switch (Front View) ........................................................... 1-3 Sphereon 4500 Switch (Rear View) ............................................................ 1-4 Management Server ..............................................................
Figures 2-15 2-16 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 2-38 2-39 2-40 2-41 2-42 2-43 2-44 2-45 2-46 2-47 2-48 2-49 2-50 2-51 2-52 2-53 2-54 2-55 2-56 2-57 x Configure Panel (Management Page with SNMP Tab) ......................... 2-27 Configure Panel (Management Page with CLI Tab) .............................. 2-28 Configure Panel (Management Page with OSMS Tab) .........................
Figures 2-58 2-59 2-60 2-61 2-62 2-63 2-64 2-65 2-66 2-67 2-68 2-69 2-70 2-71 2-72 2-73 2-74 2-75 2-76 2-77 2-78 2-79 2-80 2-81 2-82 2-83 2-84 2-85 2-86 2-87 2-88 2-89 2-90 2-91 2-92 2-93 2-94 2-95 2-96 2-97 2-98 2-99 January 26, 2005 2:24 pm serviceLOF.fm Windows Security Dialog Box .................................................................. 2-64 Change Password Dialog Box .................................................................. 2-65 Add New User Wizard (First Window) ..................
Figures xii 2-100 2-101 2-102 2-103 2-104 2-105 2-106 2-107 2-108 2-109 2-110 2-111 2-112 2-113 2-114 2-115 Configure OpenTrunking Dialog Box .................................................... Email Event Notification Setup Dialog Box .......................................... Configure Ethernet Events Dialog Box .................................................. Call Home Event Notification Setup Dialog Box ................................. InCD Icon (Unformatted CD) ..................................
Figures January 26, 2005 2:24 pm serviceLOF.fm 3-27 3-28 3-29 3-30 3-31 3-32 3-33 3-34 3-35 3-36 3-37 3-38 3-39 3-40 3-41 3-42 3-43 3-44 3-45 3-46 3-47 3-48 3-49 Sphereon 4500 - HyperTerminal Dialog Box .......................................... 3-63 HyperTerminal Dialog Box ....................................................................... 3-64 HyperTerminal Dialog Box ....................................................................... 3-64 Discover Setup Dialog Box ............................
Figures 4-20 4-21 4-22 4-23 4-24 4-25 4-26 4-27 4-28 4-29 4-30 4-31 4-32 4-33 4-34 4-35 4-36 4-37 4-38 4-39 4-40 4-41 4-42 4-43 4-44 4-45 4-46 4-47 4-48 4-49 4-50 4-51 4-52 4-53 4-54 4-55 4-56 4-57 4-58 4-59 4-60 4-61 4-62 xiv View Panel (Port Properties Page) ............................................................ 4-29 Port List View .............................................................................................. 4-31 Performance View ..................................................
Figures January 26, 2005 2:24 pm serviceLOF.fm 4-63 4-64 4-65 4-66 4-67 4-68 4-69 4-70 4-71 4-72 4-73 4-74 4-75 4-76 4-77 4-78 4-79 4-80 4-81 4-82 4-83 4-84 4-85 4-86 4-87 4-88 4-89 New Firmware Version Dialog Box ......................................................... New Firmware Description Dialog Box .................................................. File Transfer Message Box ......................................................................... Firmware Library Dialog Box ......................
Figures D-1 D-2 D-3 D-4 D-5 D-6 D-7 D-8 D-9 D-10 D-11 D-12 D-13 D-14 D-15 D-16 D-17 D-18 D-19 D-20 D-21 D-22 D-23 D-24 D-25 D-26 D-27 D-28 xvi Servers Before Consolidation (Private LAN Connection Only) ............ D-2 Servers Before Consolidation (Private and Public LAN Connections) D-2 IP Addresses in a Multiswitch Environment (Before Consolidation) .. D-3 LCD Panel (Password Entry) ..................................................................... D-5 LCD Panel (LAN 2 IP Address) ..................
January 26, 2005 2:24 pm serviceLOT.fm (Templates v3.0) Tables 2-1 2-2 2-3 2-4 Factory-Set Defaults (Sphereon 4500 Switch) ........................................... 2-1 Factory-Set Defaults (Management Server) .............................................. 2-2 Installation Task Summary ......................................................................... 2-3 Switch Operational States and Symbols ..................................................
Tables 6-2 6-3 6-4 xviii Rear-Accessible FRU Parts List ................................................................... 6-3 Miscellaneous Parts List ............................................................................... 6-4 Power Cord and Receptacle List .................................................................
Preface This publication is part of a documentation suite that supports the McDATA® Sphereon 4500 Fabric Switch. Who Should Use this Manual Use this publication if you are a trained installation and service representative experienced with the switch, storage area network (SAN) technology, and Fibre Channel technology. The Sphereon 4500 Fabric Switch contains no customer-serviceable parts that require internal access to the product during normal operation or prescribed maintenance conditions.
Chapter 3, Diagnostics - This chapter describes maintenance analysis procedures (MAPs) to fault isolate a switch problem to an individual FRU. Chapter 4, Repair Information - This chapter describes supplementary diagnostic and repair procedures for a failed switch.
Ordering Printed Manuals Where to Get Help • McDATA Sphereon 4500 Fabric Switch Element Manager User Manual (620-000175). • SANavigator Software Release 4.0 User Manual (621-000013). • EFC Manager Software Release 8.0 User Manual (620-000170). • McDATA SANpilot User Manual (620-000160). • McDATA SNMP Support Manual (620-000131). • McDATA E/OS Command Line Interface User Manual (620-000134). • McDATA Sphereon 4300 and 4500 Switch Rack-Mount Kit Installation Instructions (958-000316).
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.
in a residential area is likely to cause interference in which case the user, at his or her own expense, will take whatever measures are required to correct the interference. Any modifications or changes made to the product 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.
• The product conforms with all protection requirements of EU directive 93/68/EEC (Machinery Directive) in accordance with of the laws of the member countries relating to safe electrical and mechanical operation of the equipment. McDATA does not accept responsibility for any failure to satisfy the protection requirements of any of these directives resulting from a non-recommended or non-authorized modification to a switch.
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. GEFAHR Die mitgelieferten Netzkabel verwenden. Sicherstellen, dass die verwendete Netzsteckdose dem vorgeschriebenen Typ entspricht, die erforderliche Spannung liefert und einwandfrei geerdet ist. PERICOLO Usare il cavo di alimentazione in dotazione.
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 Utilice los cables de alimentación proporcionados. Asegúrese que el receptáculo tomacorriente para la instalación sea del tipo correcto, suministre el voltaje necesario, y que esté apropiadamente conectado a tierra. DANGER Disconnect the power cords.
PERICOLO Scollegare tutti i cavi di alimentazione. PERIGO Disconecte os cordões elétricos. PELIGRO Desconecte los cables de alimentación. PELIGRO Desconecte los cables de alimentación. The following ATTENTION statements appear in this publication and describe practices that must be observed while installing or servicing the switch. An ATTENTION statement provides essential information or instructions for which disregard or noncompliance may result in equipment damage or loss of data.
ATTENTION ! Do not remove a power supply unless a replacement FRU is immediately available. To avoid product overheating, a removed power supply must be replaced within five minutes. ATTENTION ! A reset should only be performed if a CTP card failure is indicated. Do not reset a managed product unless directed to do so by a procedural step or the next level of support. ATTENTION ! This procedure deletes all data from the C: hard drive partition.
1 General Information The McDATA® Sphereon™ 4500 Fabric Switch provides up to 24 ports of low-cost and high-performance dynamic Fibre Channel connectivity for switched fabric devices or arbitrated loop devices. This function allows low-cost, low-bandwidth workgroup (edge) devices to communicate with mainframe servers, mass storage devices, or other peripherals, and ultimately be incorporated into an enterprise storage area network (SAN) environment.
General Information 1 Switch Description The Sphereon 4500 Switch provides Fibre Channel connectivity through 24 generic mixed ports (GX_Ports). Switch ports operate at either 1.0625 or 2.125 gigabits per second (Gbps), and can be configured as: • Fabric ports (F_Ports) to provide direct connectivity for up to 24 switched fabric devices. • Fabric loop ports (FL_Ports) to provide arbitrated loop connectivity and fabric attachment for FC-AL devices.
General Information 1 As an option, the switch can be managed through a one unit (1U) high, rack-mount management server running a Java™-based SAN management application (SANavigator® 4.0 or Enterprise Fabric Connectivity Manager (EFCM) 8.0) and the Sphereon 4500 Element Manager application. Multiple switches and the server communicate on a local area network (LAN) through one or more 10/100 Base-T Ethernet hubs. One or more 24-port Ethernet hubs are optional and can be ordered with the switch.
General Information 1 Maintenance Port Power Supplies with Internal Cooling Fans Figure 1-3 SFP Transceiver Sphereon 4500 Switch (Rear View) Singlemode or multimode fiber-optic cables attach to switch ports through SFP transceivers. The fiber-optic transceivers provide duplex LC® connectors, and can be detached from switch ports (through a 10-pin interface) for easy replacement. The following fiber-optic transceiver types are available: • Shortwave laser (1.
General Information 1 Power Supply Assembly • Longwave laser (2.125 Gbps) - Longwave laser transceivers provide connections for transferring 2.125 Gbps data up to 10 kilometers through 9-micron singlemode fiber. • Extended longwave laser (2.125 Gbps) - Two types of extended longwave laser transceivers provide connections for transferring 2.125 Gbps data up to 20 kilometers or 35 kilometers through 9-micron singlemode fiber. The switch contains two power supply assemblies with internal cooling fans.
General Information 1 IML/Reset Button When the IML/RESET button (Figure 1-2 on page 1-3) is pressed, held for three seconds, and released, the switch performs an IML that reloads the firmware from FLASH memory. This operation is not disruptive to Fibre Channel traffic. If the button is held for more than three seconds, the ERR LED blinks at twice the unit beaoning rate. When the IML/RESET button is pressed and held for ten seconds, the switch performs a reset.
General Information 1 The LED blinks if unit beaconing is enabled. An illuminated LED (indicating a failure) takes precedence over unit beaconing. The LED also blinks (at twice the beaconing rate) when the IML/RESET button is pressed and held for more than three seconds.
General Information 1 Input frequency: 47 to 63 Hz Plan for single phase or phase-to-phase connections and 5-ampere dedicated service Heat dissipation: 49 watts (167 BTUs/hr) Cooling airflow clearances (switch chassis): Right and left side: 1.3 centimeters (0.5 inches) Front and rear: 7.6 centimeters (3.
General Information 1 Operating Environment Temperature: 400 F to 1040 F (40 C to 400 C) Relative humidity: 8% to 80% Maximum wet-bulb temperature: 810 F (270 C) Altitude: 10,000 feet (3,048 meters) Maintenance Approach Whenever possible, the switch maintenance approach instructs service personnel to perform fault isolation and repair procedures without degrading or interrupting operation of the switch, attached devices, or associated applications.
General Information 1 Fault isolation and service procedures vary depending on the system event information provided. Fault isolation and related service information is provided through maintenance analysis procedures (MAPs) documented in Chapter 3. MAPs consist of step-by-step procedures that prompt service personnel for information or describe a specific action to be performed.
General Information 1 SANpilot Interface With switch firmware Version 4.0 (or later) installed, administrators or operators with a browser-capable PC and an Internet connection can monitor and manage the switch through the SANpilot interface. The application provides a GUI that supports switch configuration, operation, performance monitoring, maintenance and diagnostic functions. The SANpilot interface is opened from a standard web browser running Netscape Navigator® Version 4.
General Information 1 Ethernet Hub (Optional) • 1U rack-mount server running the Intel® Pentium® 4 processor with an 1,800 megahertz (MHz) or greater clock speed, Microsoft Windows® 2000 Professional operating system, and power cord. • TightVNC™ Viewer Version 1.2.7 client-server software control package that provides remote network access (through a standard web browser) to the management server desktop. • 1,024 megabyte (MB) or greater RAM. • 40 gigabyte (GB) or greater internal hard drive.
General Information 1 must have access to the LAN segment on which the management server is installed. Switch administrative functions are accessed through the LAN and server. The LAN interface can be: • Figure 1-6 Part of the dedicated 10/100 Mbps segment (LAN 2) that provides access to managed switches. This switch-to-server connection is part of the required equipment installation. Connection of client PCs and workstations can be through the McDATA Ethernet hub or through the customer intranet.
General Information 1 • Figure 1-7 Part of a second management server interface (LAN 1) that connects to a customer intranet and allows operation of the Sphereon 4500 Element Manager application from client PCs or workstations. Connection to this LAN segment is optional and depends on customer requirements. A network configuration using both Ethernet connections is shown in Figure 1-7.
General Information 1 • Unix workstation with color monitor, keyboard, and mouse, using a: — Linux-based system using an Intel Pentium III processor with a 1 gigahertz (GHz) or greater clock speed, using the Red Hat® 7.3 or higher operating system. — Hewlett-Packard® PA-RISC® processor with a 400 MHz or greater clock speed, using the HP-UX® 11 or higher operating system. — Sun® Microsystems UltraSPARC™ IIi or later processor, using Solaris™ Version 7.0 or higher operating system.
General Information 1 • System alerts and logs that display switch, Ethernet link, and Fibre Channel link status at the SANpilot interface, client communicating with the management server, or customersupplied server (running a SAN management application). • Diagnostic software that performs power-on self-tests (POSTs) and port diagnostics (loopback tests).
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 the switch. Up to six authorized management workstations can be configured through the SANpilot interface or Element Manager application to receive unsolicited SNMP trap messages. The trap messages indicate product operational state changes and failure conditions.
General Information 1 Figure 1-8 View Panel (SANpilot Interface) Task selection tabs appear at the top of the panel, a graphical representation of the switch hardware (front and rear) appears at the right side of the panel, and menu selections (View, Configure, Monitor, Operations, and Help) appear at the left side of the panel.
General Information 1 Management Server SAN Management Application Figure 1-9 Optional SAN management (SANavigator 4.0 or EFCM 8.0) and Element Manager applications provide a GUI to manage, monitor, and isolate problems for multiple switches and multiswitch fabrics. The server and client applications operate on the management server, and a user interface is provided through an Ethernet LAN-attached PC or workstation running client-only applications.
General Information 1 The main window provides a: • Menu bar - Commands at the top of the window provide drop-down menu selections to perform functions for SAN devices, including editing, viewing, planning, discovery, configuration, and monitoring.
General Information 1 A label below each icon identifies the managed product. Additional information associated with each icon includes: • Data transmission rate - 2.125 Gbps devices have a 2G label. • Attention indicator - A colored alert symbol adjacent to a product icon indicates the operational status of the product as follows: — Absence of an alert symbol indicates the product is fully operational. — A yellow triangle indicates a redundant component failure or degraded operational status.
General Information 1 Figure 1-11 Hardware View The graphical representation of the switch emulates the hardware configuration and operational status of the corresponding real switch. For example, if the switch is fully redundant and fully populated, this configuration is reflected in the Hardware View. When the mouse cursor is moved over a graphical FRU, the FRU border highlights in blue and a pop-up identification label appears.
General Information 1 SNMP Trap Message Support Unsolicited SNMP trap messages that indicate switch operational state changes or failure conditions can be customer-configured to be transmitted to up to 12 management workstations. If installed on a dedicated Ethernet LAN, the workstations communicate directly with each switch. If installed on a customer intranet, the workstations communicate with switches through the management server.
General Information 1 • Notified of a switch problem by E-mail message, either directly or through a system administrator at the customer site or call center. • Assigned a service call from call center personnel upon receipt and confirmation of a switch call-home event. NOTE: The call-home feature is not available through the SANpilot interface. The call-home feature may not be available if the EFCM 8.0 Lite application is installed on a customer-supplied platform.
General Information 1 • Figure 1-13 Fiber-Optic Protective Plug • Figure 1-14 Tools Supplied by Service Personnel Fiber-optic protective plug - For safety and port transceiver protection, fiber-optic protective plugs (Figure 1-13) must be inserted in all switch ports without fiber-optic cables attached. The switch is shipped with protective plugs installed in all ports.
General Information 1 • Cross-tip (#2 Phillips) screwdriver - The screwdriver is required to rack-mount the switch or to remove, replace, adjust or tighten various chassis or cabinet components. • T10 Torx® tool - The tool is required to rack-mount the switch or to remove, replace, adjust or tighten various chassis or cabinet components.
2 Installation Tasks This chapter describes tasks to install, configure, and verify operation of the Sphereon 4500 Fabric Switch, SANpilot interface, and rack-mount management server. The switch can be installed on a table top, mounted in a McDATA FC-512 Fabricenter equipment cabinet, or mounted in any standard 19-inch equipment rack. Factory Defaults Table 2-1 lists factory-set defaults for the Sphereon 4500 Switch.
Installation Tasks 2 Table 2-2 Factory-Set Defaults (Management Server) Item Default Liquid crystal display (LCD) front panel 9999 Windows 2000 operating system user name (case sensitive) Administrator Windows 2000 operating system password (case sensitive) password SAN management application user name (case sensitive) Administrator SAN management application password (case sensitive) password LAN 1 (public interface) IP address 192.168.0.1 Subnet mask 255.0.0.0 Gateway address 0.0.0.
Installation Tasks 2 • Customer-supplied equipment rack - One or more switches, an optional management server, and an optional Ethernet hub are delivered to the customer facility for installation in a customersupplied equipment rack. Rack mount flanges and hardware are provided in the shipping containers. Ethernet cabling, distance, and LAN addressing issues must be considered.
Installation Tasks 2 Table 2-3 Installation Task Summary (continued) Task Number and Description Required or Optional Page Task 13: Configure the Switch to the Management Application. Required if the management server is installed. 2-76 Task 14: Record or Verify Server Restore Information. Required if the management server is installed. 2-78 Task 15: Verify Switch-to-Server Communication. Required if the management server is installed. 2-80 Task 16: Configure PFE Key (Optional).
Installation Tasks 2 • Support is available for one of the following switch management methods: — A browser-capable PC and Internet connectivity to support switch management through the SANpilot interface, or — A browser-capable PC and LAN segment connectivity to the rack-mount management server to support switch management through the SAN management (SANavigator 4.0 or EFCM 8.0) and Element Manager applications. • Support equipment and technical personnel are available for the installation.
Installation Tasks 2 The following paragraphs provide instructions to unpack and inspect one or more Ethernet hubs, and install the hubs in a desktop or rack-mount configuration. If the customer’s existing Ethernet LAN segment is adequate for connectivity and the hub is not delivered, this task is not required. Go to Task 3: Unpack, Inspect, and Install the Switch on page 2-10.
Installation Tasks 2 1 4 5 8 9 12 13 MID 16 17 Baseline 10/100 MDIX 20 21 Hub Port Status 1 2 3 Collision 4 5 6 7 8 9 10 11 13 14 15 12 100M 16 17 18 19 20 21 Green - 100M, 22 23 24 Yellow - 10M, 10M Flash - Activity Power 24 3com 3C16411 SuperStack ® 3 ® 1 4 5 8 9 13 12 16 17 20 21 MID MDIX 24 Port Status 1 2 3 4 5 6 13 14 7 8 15 16 Collisio 9 10 n 17 Green 11 12 - 100M, 18 19 20 100M Yellow 21 22 - 10M, 23 24 Flash - Activity 10M 1 Baseline 13 8 Hub 3com 3C164 11 Super S
Installation Tasks 2 NOTE: To connect two hubs, use step b and step c (middle and bottom hub instructions only). 5. Connect the U. S. power cord to the receptacle at the rear of each hub and to an AC power strip. Use an 18-inch electrical extension cord if required. 6. Connect the AC power strip to a facility power outlet. Power for each hub switches on when the strip is connected to facility AC power. 7. Inspect the front panel of each hub. Ensure each green Power light-emitting diode (LED) illuminates.
Installation Tasks 2 3. Secure both sides of the hub to the rack-mount standards as shown in Figure 2-4. Use the 1/8-inch Allen wrench and four Allen-head mounting screws (10/32 x 0.5-inch) provided. Bas elin e 10/1 00 Hub 3C1 641 1 erS tack ® 3 Sup Figure 2-4 3co m ® Rack Installation (Ethernet Hub) 4. Repeat step 1 through step 3 for the second and third hubs. 5. To daisy-chain (connect) the hubs: a.
Installation Tasks 2 NOTE: Ensure each hub is connected to a separate rack power strip. 7. Inspect the front panel of each hub. Ensure each green Power LED illuminates. Task 3: Unpack, Inspect, and Install the Switch The following paragraphs provide instructions to unpack and inspect one or more Sphereon 4500 Switches, and install the switches in a desktop or rack-mount configuration.
Installation Tasks 2 — Grounded AC electrical outlets are available. — Adequate ventilation is present, and areas with excessive heat, dust, or moisture are avoided. — All planning considerations are met. Refer to McDATA Products in a SAN Environment - Planning Manual (620-000124) for information. 3. Verify all field-replaceable units (FRUs), including small form factor pluggable (SFP) optical transceivers and combined cooling fan and power supply assemblies are installed as ordered. 4.
Installation Tasks 2 7. After successful POST completion, the green power (PWR) LED remains illuminated and all other front panel LEDs extinguish. 8. If a POST error or other malfunction occurs, go to MAP 0000: Start MAP on page 3-6 to isolate the problem. 9. Perform one of the following steps: — If the switch is to be managed through the SANpilot interface, go to Task 4: Configure the Switch at the SANpilot Interface (Optional) on page 2-13.
Installation Tasks 2 a. The green power (PWR) LED on the front panel illuminates. b. The amber system error (ERR) LED on the front panel blinks momentarily while the switch is tested. c. The green LED associated with the Ethernet port blinks momentarily while the port is tested. d. The green/blue and amber LEDs associated with Fibre Channel ports blink momentarily while the ports are tested. 8.
Installation Tasks 2 Perform procedures under this task to configure the switch from the SANpilot interface. A PC platform with Internet access and standard web browser running Netscape Navigator 4.6 or higher or Microsoft Internet Explorer 4.0 or higher is required. 1. Connect the switch to the Internet or Ethernet LAN segment as follows: a. Connect one end of the Ethernet patch cable (supplied with the switch) to the RJ-45 connector (labelled 10/100) on the left front of the switch chassis. b.
Installation Tasks 2 c. Type the default user name and password. NOTE: The default SANpilot interface user name is Administrator and the default password is password. The user name and password are case-sensitive. d. Click OK. The SANpilot interface opens with the View panel open and the Director page displayed (Figure 2-7). Figure 2-7 Configure Switch Ports View Panel (Director Page) Perform procedures in this section to configure names and operating characteristics for Fibre Channel ports.
Installation Tasks 2 Figure 2-8 Configure Panel (Ports Page) 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. Click a check box in the Blocked column to block or unblock a port (default is unblocked). A check mark in the box indicates a port is blocked. Blocking a port prevents the attached device or fabric switch from communicating.
Installation Tasks 2 • Generic port (G_Port). A generic port setting allows F_Port and E_Port behavior only. • Generic mixed port (GX_Port). A generic mixed port setting allows F_Port, fabric loop port (FL_Port), and E_Port behavior. This is the default selection. • Fabric mixed port (FX_Port). A fabric mixed port setting allows F_Port and FL_Port behavior only. e. Select from the drop-down list in the Speed column to configure the port transmission rate.
Installation Tasks 2 Figure 2-9 Configure Panel (Switch Page with Identification Tab) b. Type a switch description of 255 alphanumeric characters or less in the Description field. c. Type the switch’s physical location (255 alphanumeric characters or less) in the Location field. d. Type the name of a contact person (255 alphanumeric characters or less) in the Contact field. 2. Click Activate to save and activate the changes.
Installation Tasks 2 Figure 2-10 Configure Panel (Switch Page with Date/Time Tab) a. Click the 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 the 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. Click Activate to save and activate the changes.
Installation Tasks 2 1. Set the switch offline as follows: a. At the Configure panel, select the Operations option at the left side of the panel. The Operations panel opens and the Switch page displays with the Beacon tab selected b. Click the Online State tab, then click Set Offline. The message Your operations changes have been successfully activated appears. 2. At the Operations panel, select the Configure option at the left side of the panel. The Configure panel opens with the Ports page displayed. 3.
Installation Tasks 2 b. At the Insistent Domain ID field, select Enabled or Disabled. When this parameter is enabled, the domain ID configured in the Preferred Domain ID field becomes the active domain identification when the fabric initializes. c. At the Rerouting Delay field, select Enabled or Disabled. When this parameter is enabled, traffic is delayed through the fabric by the specified error detect time out value (E_D_TOV).
Installation Tasks 2 2. At the Operations panel, select the Configure option at the left side of the panel. The Configure panel opens with the Ports page displayed. 3. At the Configure panel, click the Switch tab, then click the Fabric Parameters tab. The Switch page displays with the Fabric Parameters tab selected (Figure 2-12). Figure 2-12 Configure Panel (Switch Page with Fabric Parameters Tab) a. At the R_A_TOV field, type a value between 10 through 1200 tenths of a second (one through 120 seconds).
Installation Tasks 2 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. Select from the Switch Priority drop-down list to set the switch priority. Available selections are Default, Principal, and Never Principal. The default setting is Default.
Installation Tasks 2 4. Click Activate to save and activate the changes. The message Your changes to the fabric parameters configuration have been successfully activated appears. 5. Set the switch online as follows: a. At the Configure panel, select the Operations option at the left side of the panel. The Operations panel opens and the Switch page displays with the Beacon tab selected b. Click the Online State tab, then click Set Online.
Installation Tasks 2 Figure 2-13 Configure Panel (Switch Page with Network Tab) a. At the IP Address field, type the new value as specified by the customer’s network administrator (default is 10.1.1.10). b. At the Subnet Mask field, type the new value as specified by the customer’s network administrator (default is 255.0.0.0). c. At the Gateway Address field, type the new value as specified by the customer’s network administrator (default is 0.0.0.0). 3. Click Activate to save and activate the changes.
Installation Tasks 2 4. Update the address resolution protocol (ARP) table for the browser PC. a. Select the Exit option from the File menu to close the SANpilot interface and browser applications. The Windows desktop displays. 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.
Installation Tasks 2 2. At the Configure panel, click the Management tab. The Management page displays with the SNMP tab selected (Figure 2-15 on page 2-27). a. Click the Enable SNMP Agent check box to enable or disable the installed SNMP agent. b. Select the appropriate Fibre Alliance management information base (FA MIB) from the FA MIB Version drop-down list. Available selections are: • FA MIB Version 3.0. • FA MIB Version 3.1. c.
Installation Tasks 2 e. Click the check box in the Write Authorization column to enable or disable write authorization for the trap recipient (default is disabled). A check mark indicates write authorization is enabled. When the feature is enabled, a management workstation user can change sysContact, sysName, and sysLocation SNMP variables. f. Type the IP address or DNS host name of the trap recipient (SNMP management workstation) in the Trap Recipient field. It is recommended the IP address be used. g.
Installation Tasks 2 • Click Enable to activate the CLI. The message Your changes to the CLI enable state have been successfully activated appears. • Click Disable to deactivate the CLI. The message Your changes to the CLI enable state have been successfully activated appears. Enable or Disable Host Control Perform this procedure to toggle (enable or disable) host control of the switch through the OSMS. The OSMS feature must be installed to access this control.
Installation Tasks 2 Configure User Rights Perform this procedure to configure the administrator-level and operator-level passwords used to access the SANpilot interface through the Enter Network Password dialog box. To configure passwords: 1. At the Configure panel, click the Security tab. The Security page displays with the User Rights tab selected (Figure 2-18 on page 2-30). Figure 2-18 Configure Panel (Security Page with User Rights Tab) 2. For the Administrator set of data fields: a.
Installation Tasks 2 b. Type the operator password (as specified by the customer’s network administrator) in the New Password field. Use 16 alphanumeric characters or less. c. Type the operator password again in the Confirm New Password field. 4. Click Activate to save the information. The message Your changes to the user rights configuration have been successfully activated appears. Configure Port Binding Perform this procedure to configure Fibre Channel port binding by WWN.
Installation Tasks 2 c. The Attached WWN column contains read-only fields that list the world wide names of attached Fibre Channel devices. Click the check box in the Use Attached column to indicate the world wide name specified in the Attached WWN column is to be used for port binding. After activation, the attached WWN appears in the Bound WWN column. 2. Click Activate to save the information. The message Your changes to the port binding configuration have been successfully activated appears.
Installation Tasks 2 2. Select the connection policy from the Switch Binding State drop-down list. The switch binding state indicates the type of binding restrictions imposed on the switch. Switch binding is enabled by activating Enterprise Fabric Mode (refer to Enable or Disable Enterprise Fabric Mode on page 2-35), or by enforcing a connection policy at the Switch Binding State drop-down list.
Installation Tasks 2 Configure Fabric Binding Perform this procedure to configure fabric binding by attached fabric member (domain ID and WWN). The SANtegrity feature must be installed to access this control. Refer to Install PFE Keys (Optional) on page 2-38 for instructions. If the feature is not installed, the message This Feature Not Installed appears. To configure fabric binding: 1. At the Configure panel, click the Fabric Binding tab.
Installation Tasks 2 • Unsaved & Inactive - Information displayed may be different than the active configuration saved for the fabric. 3. Click Save and Activate to save and activate the displayed fabric binding configuration. A confirmation dialog box appears. Click OK to close the confirmation dialog box, activate the fabric binding configuration, and change the status to Saved & Active. 4. Click Deactivate to deactivate fabric binding while Enterprise Fabric Mode is also deactivated.
Installation Tasks 2 Figure 2-22 Configure Panel (Security Page with EFM Tab) 2. Perform one of the following steps as required: • Click Enable to activate EFM. The message Your changes to enterprise fabric mode have been successfully activated appears. • Click Disable to deactivate EFM. The message Your changes to enterprise fabric mode have been successfully activated appears. Configure OpenTrunking Perform this procedure to configure OpenTrunking parameters.
Installation Tasks 2 Figure 2-23 Configure Panel (Performance Page with OpenTrunking Tab) a. At the OpenTrunking State field, select Enabled or Disabled. When this parameter is enabled, the optional OpenTrunking feature is functional. b. At the Unresolved Congestion Event Notification field, select Enabled or Disabled. When this parameter is enabled, unresolved congestion events are recorded in the event log, and SNMP trap messages are generated and transmitted (if SNMP is configured).
Installation Tasks 2 d. The low BB_Credit threshold is the percent time an ISL is allowed to not transmit data because BB_Credit is unavailable. When the threshold is exceeded, data is rerouted to another ISL. In addition, traffic cannot be rerouted to another lowthreshold ISL. Use one of the following to set the low BB_Credit threshold: • Click the Default check box. A check mark appears in the box and a calculated default value appears (1% to 99%) in the Low BB_Credit Threshold field.
Installation Tasks 2 • OSMS - These feature allows open systems host control of the switch. • Flexport Technology - A Flexport Technology switch is delivered at a discount with only eight ports enabled. When additional port capacity is required, the remaining ports are enabled (in eightport increments) through purchase of this feature. • SANtegrity™ binding - This feature enhances security in SANs with a large and mixed group of fabrics and attached devices.
Installation Tasks 2 3. Click the Feature Installation tab. The Operations panel opens with the Feature Installation page displayed (Figure 2-24). Figure 2-24 Operations Panel (Feature Installation Tab) 4. Type the PFE key and click Activate. The interface displays a confirmation page with a warning, stating this action overrides the current set of switch features. 5. Click Activate to activate the new PFE key. The switch performs an IPL when the key is activated.
Installation Tasks 2 McDATA Solution Center (800-752-4572 or support@mcdata.com). Please have the serial numbers of the failed and replacement switches, and the old PFE key number or transaction code. 7. Go to Task 21: Cable Fibre Channel Ports on page 2-120.
Installation Tasks 2 switch or by installation or service personnel and are required to perform this task: • A maintenance terminal (desktop or notebook PC) with: — The Microsoft Windows 98, Windows 2000, Windows Millennium Edition, Windows XP, or Windows NT 4.0 operating system. — RS-232 serial communication software (such as ProComm Plus or HyperTerminal). HyperTerminal is provided with Windows operating systems. • An asynchronous RS-232 modem cable.
Installation Tasks 2 Figure 2-25 Connection Description Dialog Box 6. Type Sphereon 4500 in the Name field and click OK. The Connect To dialog box displays (Figure 2-26). Figure 2-26 Connect To Dialog Box 7. Ensure the Connect using field displays COM1 or COM2 (depending on the serial communication port connection to the switch), and click OK. The COMn Properties dialog box displays, where n is 1 or 2 (Figure 2-27 on page 2-44).
Installation Tasks 2 Figure 2-27 COMn Properties Dialog Box 8. Configure the Port Settings parameters as follows: — Bits per second - 115200. — Data bits - 8. — Parity - None. — Stop bits - 1. — Flow control - Hardware or None. When the parameters are set, click OK. The Sphereon 4500 HyperTerminal window displays. 9. At the > prompt, type the user-level password (the default is password) and press Enter. The password is case sensitive.
Installation Tasks 2 Figure 2-28 Sphereon 4500 - HyperTerminal Window 10. At the C > prompt, type the ipconfig command and press the Enter key. The Sphereon 4500 - HyperTerminal window displays with configuration information listed as follows: — MAC Address. — 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. 11.
Installation Tasks 2 The IP address is always xxx.xxx.xxx.xxx, the subnet mask is always yyy.yyy.yyy.yyy, and the gateway address is always zzz.zzz.zzz.zzz, where the octets xxx, yyy, and zzz are decimals from zero through 255. If a network address is to remain unchanged, type the current address in the respective field. When the new network addresses are configured at the switch, the message Request completed OK displays at the bottom of the Sphereon 4500 - HyperTerminal window. 12.
Installation Tasks 2 16. Disconnect the RS-232 modem cable from the switch and the maintenance terminal. Replace the protective cap over the maintenance port. 17. At the switch front panel, press and hold the IML/RESET button for ten seconds. The switch performs a POR. 18. Connect the switch to the customer-supplied Ethernet LAN segment, or McDATA Ethernet hub. To connect the desktop or rack-mounted (customer-supplied) switch to the Internet or Ethernet LAN segment: a.
Installation Tasks 2 NOTE: The management server and related applications provide a GUI to monitor and manage McDATA products, and are a dedicated hardware and software solution that should not be used for other tasks. McDATA tests applications installed on the management server, but does not compatibility test other third-party software. Modifications to the management server hardware or installation of additional software (including patches or service packs) may interfere with normal operation.
Installation Tasks 2 Figure 2-31 1U Management Server Connections b. Connect the remaining end of the Ethernet cable to the LAN as follows: • If the server is installed on a customer-supplied LAN segment, connect the cable to the LAN as directed by the customer’s network administrator. • If the server is installed on the McDATA- supplied Ethernet hub, connect the cable to any available hub port. 6. If required, connect the management server to the customer’s corporate intranet (public LAN interface).
Installation Tasks 2 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 the following message pertaining to boot sequence selection (Figure 2-32): Boot from LAN? Press Figure 2-32 LCD Panel During Boot Sequence d. Ignore the message.
Installation Tasks 2 Task 7: Configure Server Password and Network Addresses Verify the type of LAN installation with the customer’s network administrator. If the management server or Fabricenter equipment cabinet is installed on a dedicated LAN, network information does not require change. Change the default password for the server’s LCD panel (if required by the customer), then go to Task 8: Configure Management Server Information on page 2-55.
Installation Tasks 2 New Password: 0**** Figure 2-34 LCD Panel (New Password) 4. Use the arrow keys as described in step 2 to input a new 4-digit numeric password, then press ENTER. The following message appears (Figure 2-35): Save Change? Yes, Save !! Figure 2-35 LCD Panel (Save Change) 5. Press ENTER. A Wait a moment! message appears at the LCD panel, the LCD panel returns to the LAN 1 Setting?? message, and the password changes.
Installation Tasks 2 Input IP: 010.001.001.001 Figure 2-37 LCD Panel (LAN 2 IP Address) 4. Use the arrow keys as described in step 2 to input a new IP address, then press ENTER. The following message appears (Figure 2-38): Save Change? Yes, Save !! Figure 2-38 LCD Panel (Save Change) 5. Press ENTER. The LAN 2 IP address changes and the following message appears (Figure 2-39 on page 2-53) with the default subnet mask of 255.0.0.0. Input Netmask: 255.000.000.
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’s LCD panel, press ENTER. The Welcome!! or operational information message changes to the following (Figure 2-41): Input Password: 0**** Figure 2-41 LCD Panel (Password Entry) 2.
Installation Tasks 2 Input Netmask: 255.000.000.000 Figure 2-44 LCD Panel (LAN 1 Subnet Mask) 6. Use the arrow keys as described in step 2 to input a new subnet mask, then press ENTER. The following message appears (Figure 2-45): Save Change? Yes, Save !! Figure 2-45 LCD Panel (Save Change) 7. Press ENTER. A Wait a moment! message appears at the LCD panel, the LCD panel returns to the LAN 1 Setting?? message, and the LAN 1 subnet mask changes. 8.
Installation Tasks 2 2. At the PC browser, enter the LAN 2 IP address of the management server, followed by :5800, as the Internet uniform resource locator (URL). Enter the URL in 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-51. The VNC Authentication screen displays (Figure 2-46). Figure 2-46 VNC Authentication Screen 3.
Installation Tasks 2 4. Click the Send Ctrl-Alt-Del button at the top of the window to log on to the management server desktop. The Log On to Windows dialog box displays (Figure 2-48). NOTE: Do not simultaneously press the Ctrl, Alt, and Delete keys. This action logs the user on to the browser-capable PC, not the rack-mount management server. Figure 2-48 Log On to Windows Dialog Box 5. Type the default Windows 2000 user name and password and click OK.
Installation Tasks 2 NOTE: The default Windows 2000 user name is Administrator and the default password is password. The user name and password are case-sensitive. Configure Management Server Names Figure 2-50 To configure the management server name and workgroup name: 1. At the Windows 2000 desktop, click Start at the left side of the task bar (bottom of the desktop), then select Settings, then Control Panel. The Control Panel window displays (Figure 2-50). Control Panel Window 2.
Installation Tasks 2 Figure 2-51 System Properties Dialog Box (Network Identification Tab) 4. Click Properties. The Identification Changes dialog box displays (Figure 2-52).
Installation Tasks 2 5. At the Computer Name field, change the name to MGMTSERVER, at the Workgroup field, change the name to WORKGROUP, then click OK. The dialog box closes. 6. Record the computer and workgroup names for reference if the management server hard drive fails and must be restored. 7. At the System Properties dialog box, click OK to close the dialog box and return to the Control Panel window. 8.
Installation Tasks 2 Figure 2-54 Local Area Connection 2 Status Dialog Box 4. Click Properties. The Local Area Connection 2 Properties dialog box displays (Figure 2-55). Figure 2-55 Local Area Connection 2 Properties Dialog Box 5. Double-click the Internet Protocol (TCP/IP) entry. The Internet Protocol (TCP/IP) Properties dialog box displays (Figure 2-56 on page 2-62).
Installation Tasks 2 Figure 2-56 Internet Protocol (TCP/IP) Properties Dialog Box 6. 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-51. 7. At the Default gateway field, enter the gateway address obtained from the customer’s network administrator. 8. Select (enable) the Use the following DNS server addresses radio button.
Installation Tasks 2 13. Reboot the management server: a. At the Windows 2000 desktop, click Start at the left side of the task bar (bottom of the desktop), then select Shut down. The Shut Down Windows dialog box appears. b. At the Shut Down Windows dialog box, select the Restart option and click OK to reboot the server. c. Perform Access the Management Server Desktop on page 2-55.
Installation Tasks 2 3. The Guest user name is a built-in account in the Windows 2000 operating system and cannot be deleted. The srvacc account is for field service users and must not be modified or deleted. Change Default Administrator Password To change the administrator password from the default (password) to a customer-specified password: 1. Click the Send Ctrl-Alt-Del button at the top of the window surrounding the Users and Passwords dialog box.
Installation Tasks 2 Figure 2-59 Change Password Dialog Box 3. At the Old Password field, type the old password. At the New Password and Confirm New Password fields, type the new password. NOTE: The New Password and Confirm New Password fields are case-sensitive. 4. Click OK. The default administrator password changes and the Change Password dialog box closes. 5. Click Cancel at the Windows Security dialog box to return to the Users and Passwords dialog box.
Installation Tasks 2 Figure 2-60 Add New User Wizard (First Window) 2. Type the appropriate new user information in the User name, Full name, and Description fields, then click Next. The second window of the Add New User wizard displays (Figure 2-61).
Installation Tasks 2 3. Type the new user’s password in the Password and Confirm password fields, then click Next. The third window of the Add New User wizard displays (Figure 2-62). Figure 2-62 Add New User Wizard (Third Window) 4. Based on the level of access to be granted, 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.
Installation Tasks 2 Figure 2-63 MGMTSERVER\srvacc Properties Dialog Box (General Tab) 2. Type the appropriate new user information in the User name, Full name, and Description fields, then click the Group Membership tab. The MGMTSERVER\srvacc Properties dialog box displays with the Group Membership tab selected (Figure 2-64).
Installation Tasks 2 3. Based on the level of access to be changed, 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. 4. Click OK. The new user information is added and the MGMTSERVER\srvacc Properties dialog box closes. Record the user information for reference if the management server hard drive fails and must be restored. 5.
Installation Tasks 2 NOTE: The Time Zone field must be set before the Date & Time field. 3. Click the Time Zone tab. The Date/Time Properties dialog box displays with the Time Zone page open (Figure 2-66). Figure 2-66 Date/Time Properties Dialog Box (Time Zone Tab) 4. To change the time zone: a. Select the appropriate time zone from the drop-down list at the top of the dialog box. b.
Installation Tasks 2 d. Click in the time field and enter the desired time, then click the adjacent up or down arrow and select AM or PM. e. Click Apply. Record date and time information for reference if the management server hard drive fails and must be restored. 7. Click OK to close the Date/Time Properties dialog box. 8. Click close (X) at the upper right corner of the Control Panel window to return to the Windows 2000 desktop.
Installation Tasks 2 3. At the Call Center Phone Number field, enter the telephone number for the McDATA Solution Center (720-566-3912). Include necessary information, such as the country code, area code, or any prefix required to access a telephone line outside the facility. 4. At the Local Phone Number field, enter the telephone number for access to the local server. Include necessary information such as the country code or area code. 5.
Installation Tasks 2 Figure 2-68 Main Window (SANavigator or EFCM) 4. Select Users from the SAN menu. The SANavigator Server Users or EFCM 8 Server Users dialog box displays (Figure 2-69 on page 2-74).
Installation Tasks 2 Figure 2-69 SANavigator or EFCM 8 Server Users Dialog Box 5. Click Add. The Add User dialog box displays (Figure 2-70).
Installation Tasks 2 6. Enter information in fields as directed by the customer: • Name - click in this field and type a new user name up to 16 alphanumeric characters in length. Control characters and spaces are not valid. The user name is case-sensitive. • Email Address - click in this field and type one or more new user e-mail addresses. Separate multiple addresses with a semicolon. • User ID - click in this field and type a unique user ID for the new user.
Installation Tasks 2 Task 13: Configure the Switch to the Management Application To manage a new switch, it must be identified to and discovered by the SAN management application. To identify the new switch: 1. At the SAN management application (SANavigator or EFCM main window), select the Setup option from the Discover menu. The Discover Setup dialog box displays (Figure 2-71). Figure 2-71 Discover Setup Dialog Box 2. Click Add.
Installation Tasks 2 Figure 2-72 Domain Information Dialog Box (IP Address Page) 3. Type a switch description (Sphereon 4500, for example) in the Description field. 4. Type the switch IP address (determined by the customer’s network administrator) in the IP Address field. 5. Type the switch subnet mask (determined by the customer’s network administrator) in the Subnet Mask field. 6.
Installation Tasks 2 Task 14: Record or Verify Server Restore Information Windows 2000 operating system configuration information must be recorded to restore the management server in case of hard drive failure. Refer to Appendix C, Restore Management Server for instructions. Record or verify the following management server configuration information: 1. Verify network configuration information is recorded.
Installation Tasks 2 a. Verify the time zone is recorded. b. Verify if the management server is set to automatically adjust the clock for daylight savings time changes. 4. Record the Product ID number as follows: a. At the Windows 2000 desktop, click Start at the left side of the task bar, then select Settings, then Control Panel. The Control Panel window displays (Figure 2-50 on page 2-58). b. Double-click the System icon. The System Properties dialog box displays with the General page open (Figure 2-73).
Installation Tasks 2 Task 15: Verify Switch-to-Server Communication Communication must be verified between the switch and server (SAN management and Element Manager applications). To verify switch-to-server communication: 1. At the SAN management application’s main window (physical map or product list), inspect the shape and color of the status symbol associated with the Sphereon 4500 Switch product icon. Table 2-4 explains operational states and associated symbols.
Installation Tasks 2 3. Select the Element Manager option from the pop-up menu. When the Element Manager application opens, the last view (tab) accessed by a user opens by default. As an example, the Hardware View (Figure 2-75) is shown. Figure 2-75 Hardware View 4. Inspect switch status at the Hardware view and perform one of the following steps: • If the switch appears operational (no FRU alert symbols and a green circle at the status bar), go to Task 16: Configure PFE Key (Optional) on page 2-82.
Installation Tasks 2 Task 16: Configure PFE Key (Optional) Perform this task to display or install operating features that are available for the switch as customer-specified options. Available features include the: • OSMS - These feature allows open systems host control of the switch. • Flexport Technology - A Flexport Technology switch is delivered at a discount with only eight ports enabled.
Installation Tasks 2 Figure 2-76 No Feature Key Dialog Box In addition, the message Element Manager license key has not been installed - Please follow up instructions to update permanent key appears splashed across views, indicating the Element Manager PFE key must be installed. The Hardware View (Figure 2-77) is shown as an example.
Installation Tasks 2 Features are enabled through a PFE key that is encoded to work with the serial number of a unique switch. A key is a case- sensitive alphanumeric string with dashes every four characters. To configure the PFE key: 1. Ensure the switch is set offline. For instructions, refer to Set the Switch Online or Offline on page 4-48. 2. At the Hardware View, click Configure at top of the view and select Features from the pop-up menu. The Configure Feature Key dialog box displays (Figure 2-78).
Installation Tasks 2 Figure 2-80 Enable Feature Key Dialog Box 5. Click OK. If the switch is online, it performs an IPL when the PFE key is enabled and a Warning dialog box displays (Figure 2-81). Figure 2-81 Warning Dialog Box 6. Click Yes to enable the PFE key. When the key is enabled, the switch performs an IPL. 7. At the Configure Feature Key dialog box, click Close to close the dialog box.
Installation Tasks 2 NOTE: PFE keys are encoded to work with the serial number of the installed switch only. Record the key to re-install the feature if required. If the switch fails and must be replaced, obtain new PFE keys from the McDATA Solution Center (800-752-4572 or support@mcdata.com). Please have the serial numbers of the failed and replacement switches, and the old PFE key number or transaction code.
Installation Tasks 2 1. At the Hardware View, select Date/Time from the Configure menu. The Configure Date and Time dialog box displays (Figure 2-82). Figure 2-82 Configure Date and Time Dialog Box The switch date and time can be set manually, or set to be periodically updated by the SAN management application (the switch and application synchronize at least once daily). 2. To set the switch date and time manually: a.
Installation Tasks 2 3. To set the switch 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). The Date and Time fields are greyed out and not selectable. Perform one of the following options: • Click Activate to enable synchronization and close the Configure Date and Time dialog box.
Installation Tasks 2 Configure Switch Identification • Configure preferred paths. • Configure switch binding. • Configure switch ports. • Configure SNMP trap message recipients. • Configure threshold alerts. • Configure OpenTrunking. • Enable SANpilot interface and Telnet access. • Configure and enable e-mail notification. • Configure and enable Ethernet events. • Configure and enable call-home event notification.
Installation Tasks 2 a. Type a switch name of 24 alphanumeric characters or less in the Name field. Each switch should be configured with a unique name. If the switch is installed on a public LAN, the name should reflect the switch’s Ethernet network DNS host name. For example, if the DNS host name is sphereon4500.mcdata.com, the name entered in this dialog box should be Sphereon 4500. b. Type a switch description of 255 alphanumeric characters or less in the Description field. c.
Installation Tasks 2 Figure 2-85 Configure Switch Parameters Dialog Box a. At the Preferred Domain ID field, type a value between 1 through 31. The domain ID uniquely identifies each switch in a fabric. NOTE: If the switch is attached to a fabric element, the switch and element must have unique domain IDs. If the values are not unique, the E_Port connection to the element segments and the switch cannot communicate with the fabric. b.
Installation Tasks 2 e. Click the Suppress RSCNs on zone set activations check box to enable or disable this parameter. A check mark in the box indicates the parameter is enabled, and is the default. When the parameter is enabled (checked), attached devices do not receive notification following any change to the fabric’s active zone set.
Installation Tasks 2 NOTE: If the switch is attached to a fabric element, the switch and element must be set to the same R_A_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 R_A_TOV value must be greater than 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).
Installation Tasks 2 • Open Fabric 1.0 - Select this option (default) for managing heterogeneous fabrics and if the switch is fabric-attached to McDATA directors or switches and open-fabric compliant switches produced by other OEMs. 3. Click Activate to save the information and close the dialog box. 4. Set the switch online. For instructions, refer to Set the Switch Online or Offline on page 4-48.
Installation Tasks 2 Figure 2-87 Configure Preferred Paths Dialog Box 2. Click Add. The Add Preferred Path dialog box displays (Figure 2-88). Figure 2-88 Add Preferred Path Dialog Box 3. At the Source Port field, type a value between 0 through 23. For this switch, the value uniquely identifies the starting port for the preferred path. 4. At the Exit Port field, type a value between 0 through 23. For this switch, the value uniquely identifies the exit port for the preferred path. 5.
Installation Tasks 2 7. Repeat step 2 through step 6 to configure additional preferred paths. 8. At the Configure Preferred Paths dialog box, select (click) the Enable Preferred Path check box. 9. Click Activate to enable all configured preferred paths and close the dialog box. Configure Switch Binding Overview The switch binding (SANtegrity binding) feature specifies devices that can connect to Sphereon 4500 switch ports.
Installation Tasks 2 • Switch binding can be enabled or disabled when the switch is either offline or online. • If Enterprise Fabric Mode is enabled from the SAN management application: — Switch binding is automatically enabled. — Switch binding cannot be disabled if the switch is online. — Switch binding can be disabled if the switch is offline. However, if switch binding is disabled, Enterprise Fabric Mode is also disabled.
Installation Tasks 2 1. Ensure the SANtegrity binding PFE key is installed and configured. For instructions, refer to Task 16: Configure PFE Key (Optional) on page 2-82. 2. At the Hardware View, select Switch Binding, then Change State from the Configure menu. The Switch Binding - State Change dialog box displays (Figure 2-89). Figure 2-89 Switch Binding - State Change Dialog Box 3. Perform one of the following: • To enable switch binding, click the Enable Switch Binding check box to add a check mark.
Installation Tasks 2 • Restrict All Ports - Select this button to restrict connections from specific devices to switch F_Ports or FL_Ports and fabric elements to switch E_Ports. WWNs can be added to the membership list to allow connection and removed from the list to prohibit connection. 5. Click Activate to enable the changes and close the Switch Binding Change State dialog box. Edit Membership List Perform this procedure to edit the switch binding membership list: 1.
Installation Tasks 2 3. If nicknames are configured (through the SAN management application) and are to be displayed instead of WWNs, click Display Options. The Display Options dialog box displays (Figure 2-91). If nicknames are not configured, go to step 5. Figure 2-91 Display Options Dialog Box 4. Click the Nickname radio button, then click OK. The dialog box closes and nicknames appear in the Switch Binding - Membership List dialog box. 5.
Installation Tasks 2 Figure 2-92 Add Detached Node Dialog Box 7. Type the device WWN or nickname and click OK. The WWN or nickname appears in the Switch Membership List. 8. Click Activate to enable the changes and close the Switch Binding Membership List dialog box. Configure Switch Ports Figure 2-93 To configure switch Fibre Channel ports: 1. At the Hardware View, select Ports from the Configure menu. The Configure Ports dialog box displays (Figure 2-93).
Installation Tasks 2 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. Click a check box in the Blocked column to block or unblock a port (default is unblocked). A check mark in the box indicates a port is blocked. Blocking a port prevents the attached devices or fabric switch from communicating.
Installation Tasks 2 2. 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.125 Gbps operation (Negotiate). This is the default selection. • 1.0625 Gbps operation (1 Gig). • 2.125 Gbps operation(2 Gig). f. Click the check box in the Port Binding column to enable or disable port binding (default is disabled).
Installation Tasks 2 Figure 2-94 Configure SNMP Dialog Box a. For each trap recipient to be configured, type a community name of 32 alphanumeric characters or less in the associated Community Name field. The community name is incorporated in SNMP trap messages to ensure against unauthorized viewing or use. b. Click the check box in the Write Authorization column to enable or disable write authorization for the trap recipient (default is disabled).
Installation Tasks 2 Configure Threshold Alerts A threshold alert notifies users when an E_Port or F_Port transmit (Tx) or receive (Rx) throughput reaches or exceeds a specified value. Alerts are indicated by: • An attention indicator (yellow triangle) associated with a port at the Hardware View. • An attention indicator (yellow triangle) in the Alert column at the Port List View. • An attention indicator (yellow triangle) in the Threshold Alerts field at the Port Properties dialog box.
Installation Tasks 2 Figure 2-96 New Threshold Alert Dialog Box (Screen 1) 3. Type a name of 64 alphanumeric characters or less in the associated Threshold Alert Name field. 4. Select from the Threshold Alert drop-down list to configure the alert type. Available selections are: • Rx Throughput - An alert occurs if the threshold value for receive throughput is reached or exceeded. • Tx Throughput - An alert occurs if the threshold value for transmit throughput is reached or exceeded.
Installation Tasks 2 Figure 2-97 New Threshold Alert Dialog Box (Screen 2) 6. Type a percentage 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 Figure 2-98 New Threshold Alert Dialog Box (Screen 3) 10. Select the Port Type or Port List radio button. • Select Port Type radio button, then the E_Ports, F_Ports, or FL_Ports radio button to cause an alert to generate for all ports configured as either E_Ports, F_Ports, or FL_Ports. • Select Port List to configure individual ports by clicking the check box adjacent to each port number. Select Set All Ports to place a check mark adjacent to all port numbers.
Installation Tasks 2 Figure 2-99 New Threshold Alert Dialog Box (Screen 4) 12. Click Finish. The Configure Threshold Alerts dialog box reappears (Figure 2-95 on page 2-105) listing the name, type, and state of the alert configured. 13. To activate the alert, highlight (select) the alert and click Activate. Configure OpenTrunking Perform this procedure to configure OpenTrunking parameters. The OpenTrunking feature must be installed to access this control.
Installation Tasks 2 Figure 2-100 Configure OpenTrunking Dialog Box 3. Perform one of the following: • To enable OpenTrunking, click the Enable OpenTrunking check box to add a check mark. Go to step 4 to set the congestion threshold for each port. • To disable OpenTrunking, click the Enable OpenTrunking check box to remove the check mark, then click Activate to enable the change and close the dialog box. 4. For each switch port: a. Click the check box in the Use Algorithmic Threshold column.
Installation Tasks 2 NOTE: The default congestion threshold is calculated by the switch’s firmware. 5. Click the Unresolved Congestion check box to add a check mark and enable the parameter. When this parameter is enabled, unresolved congestion events are recorded in the event log, and SNMP trap messages are generated and transmitted (if SNMP is configured).
Installation Tasks 2 Enable SANpilot Interface and Telnet Access Perform this procedure to enable SANpilot interface and Telnet access through the maintenance port at the rear of the switch. To enable these functions: 1. To enable the SANpilot interface at the Hardware View, select Enable Web Server from the Configure menu. A check mark appears in the box when the interface is enabled, and the menu closes. 2. To enable Telnet access at the Hardware View, select Enable Telnet from the Configure menu.
Installation Tasks 2 NOTE: The enable function must also be activated for each switch through the Sphereon 4500 Element Manager application. E-mail notification can be active for some switches and inactive for others. 4. Type the IP address or DNS host name of the SMTP server in the E-mail Server field. It is recommended the IP address be used. 5. Type the e-mail address to which e-mail replies should be sent in the Reply field. 6.
Installation Tasks 2 Configure and Enable Ethernet Events Perform this procedure to configure and enable Ethernet events. An Ethernet event is recorded (after a user-specified time interval) when the switch-to-management server communication link drops. To configure and enable Ethernet events: 1. Minimize the Hardware View (Element Manager application) and return to the SAN management application. 2. At the SANavigator or EFCM main window, select the Ethernet Event option from the Monitor menu.
Installation Tasks 2 2. At the SANavigator or EFCM main window, select the Event Notification and Call Home options from the Monitor menu. The Call Home Event Notification Setup dialog box displays (Figure 2-103). Figure 2-103 Call Home Event Notification Setup Dialog Box 3. Click the Enable Call Home Event Notification check box. A check mark appears in the check box to indicate call-home event notification is enabled.
Installation Tasks 2 For the EFCM 8.0 application, critical configuration data is stored on the management server hard drive in the following directories: • C:\Program Files\EFCM 8.0\CallHome • C:\Program Files\EFCM 8.0\Client • C:\Program Files\EFCM 8.0\Server. The server is configured to automatically mirror the contents of these directories to the CD-RW drive anytime directory contents change or the server is rebooted.
Installation Tasks 2 Figure 2-104 InCD Icon (Unformatted CD) b. Right-click the icon and select Format (F). The first window of the InCD wizard displays (Figure 2-105). Figure 2-105 InCD Wizard (First Window) c. Click Next to proceed to the second window of the InCD wizard. Use the default parameters displayed at each window, and click Next and Finish as appropriate to complete the CD formatting task. d.
Installation Tasks 2 3. If the Hardware View is open, close the view and return to the SAN management application (SANavigator 4.0 or EFCM 8.0) by clicking close (X) at the upper right corner of the window. 4. Close the SAN management application by selecting Shutdown from the SAN menu. A SANavigator or EFCM Message dialog box displays (Figure 2-107). Figure 2-107 SANavigator or EFCM Message Dialog Box 5. Click Yes to close the SAN management application. 6.
Installation Tasks 2 b. Select the Restart option from the list box and click OK. The management server powers down and restarts. During the reboot process the LAN connection between the management server and browser-capable PC drops momentarily, and the TightVNC viewer displays a network error as shown in Figure 2-109 on page 2-119. Figure 2-109 TightVNC Network Error Message c. After the management server reboots, click Login again. The VNC Authentication screen displays. d.
Installation Tasks 2 g. Type the SAN management application default user ID and password and select a server or IP address from the Network Address drop-down list. NOTE: The default SAN management application user ID is Administrator and the default password is password. The user name and password are case-sensitive. h. Click Login. The application opens and the SANavigator or EFCM main window appears (Figure 2-68 on page 2-73). 7.
Installation Tasks 2 Task 22: Configure Zoning (Optional) Perform this procedure to: • Configure, change, add, or delete zones. A zone is a group of devices that can access each other through port- to-port connections. Devices in the same zone can recognize and communicate with each other; devices in different zones cannot. • Configure, change, enable, or disable zone sets.
Installation Tasks 2 Figure 2-110 Configure Panel (Zoning Page with Zones Tab) 3. Type the zone name and click Add New Zone. After the name is validated, the new zone name (Zone-1) and an associated Delete button appear at the bottom of the page. Note the following: • Save and activate the zone - Changes to a zone or zoning configuration are not saved and activated on the switch until saved as part of a zone set. Go to Configure Zone Sets (SANpilot Interface) on page 2-124 to perform this function.
Installation Tasks 2 4. To add devices (members) to the zone, click the zone name (Zone-1). The Zoning page displays with the Modify Zone tab selected (Figure 2-111). Figure 2-111 Configure Panel (Zoning Page with Modify Zone Tab) 5. To rename a configured zone, type the new name in the Zone field and click Rename Zone. After the name is validated, the zone name is changed. 6.
Installation Tasks 2 • Add member by domain ID and port number - Type the domain ID (1 through 31) of the switch in the Domain ID field, type the switch port number (0 through 23) to which a device is attached, and click the adjacent Add Member button. The device attached to that port is added to the zone. • Delete a member - To delete a zone member, click the Delete button adjacent to the configured zone member (WWN or domain ID and port number) at the bottom of the page.
Installation Tasks 2 2. To create a zone set that incorporates zones and zone members (configured under Configure Zones (SANpilot Interface) on page 2-121), type a new zone set name in the Zone Set Name field. 3. Click Save and Activate Zoning Configuration. After the zone set name is validated, a confirmation dialog box displays. 4. Click OK to save and activate the new zone set. The message Your changes to the Zoning configuration have been successfully activated appears.
Installation Tasks 2 — If the domain ID must be changed from the SANpilot interface, refer to Task 4: Configure the Switch at the SANpilot Interface (Optional) on page 2-13. — If the domain ID must be changed from the management server, refer to Task 19: Configure the Sphereon 4500 Element Manager Application on page 2-88. 3. Ensure the R_A_TOV and E_D_TOV values for the Sphereon 4500 Switch are identical to the values for all switches or directors participating in the fabric.
Installation Tasks 2 8. If required, click the Hardware tab. The Hardware View displays. 9. Double-click the graphical port connector used for the fabric ISL (connected in step 5). The Port Properties dialog box displays (Figure 2-113). Figure 2-113 Port Properties Dialog Box 10. Ensure the Link Incident field displays None and the Reason field is blank. If an ISL segmentation or other problem is indicated, go to MAP 0000: Start MAP on page 3-6 to isolate the problem.
Installation Tasks 2 To register with the McDATA File Center: 1. At a PC with Internet access, open the McDATA File Center home page (Figure 2-114). The uniform resource locator (URL) is http://central.mcdata.com. Figure 2-114 McDATA File Center Home Page 2. Select (click) the New User Registration option at the top of the home page. The File Center’s New User Registration page displays (Figure 2-115 on page 2-129). Use the registration page to input required and optional user information.
Installation Tasks 2 Figure 2-115 McDATA File Center (New User Registration Page) 4. At the browser PC, close the Internet session. If no switch problems are indicated, installation tasks are complete.
Installation Tasks 2 2-130 McDATA Sphereon 4500 Fabric Switch Installation and Service Manual
3 Diagnostics This chapter describes diagnostic procedures used by service representatives to fault isolate Sphereon 4500 Fabric Switch problems or failures to the field-replaceable unit (FRU) level. The chapter specifically describes how to perform maintenance analysis procedures (MAPs). Maintenance Analysis Procedures Fault isolation and related service procedures are provided through MAPs. The procedures vary depending on the diagnostic information provided.
Table 3-1 Quick Start Factory-Set Defaults Item Default Customer password password Maintenance password level-2 IP address 10.1.1.10 Subnet mask 255.0.0.0 Gateway address 0.0.0.0 Table 3-2 lists and summarizes the MAPs. Fault isolation normally begins at MAP 0000: Start MAP on page 3-6.
Table 3-3 Event Codes versus Maintenance Action Event Code Explanation Action 011 Login Server database invalid. Go to MAP 0700. 021 Name Server database invalid. Go to MAP 0700. 031 SNMP request received from unauthorized community. Add a community name through the Element Manager application. 051 Management Server database invalid. Go to MAP 0700. 052 Management Server internal error. Go to MAP 0700. 061 Fabric Controller database invalid. Go to MAP 0700.
Table 3-3 Event Codes versus Maintenance Action (Continued) Event Code 3-4 Explanation Action 151 Fabric configuration failure. Go to Collect Maintenance Data on page 4-44. 200 Power supply AC voltage failure. Go to MAP 0100. 201 Power supply DC voltage failure. Go to MAP 0100. 203 Power supply AC voltage recovery. No action required. 204 Power supply DC voltage recovery. No action required. 206 Power supply removed. Replace FRU. 207 Power supply installed. No action required.
Table 3-3 Event Codes versus Maintenance Action (Continued) Event Code Explanation Action 423 CTP firmware download initiated. No action required. 426 Multiple ECC single-bit errors occurred. Go to MAP 0500. 433 Non-recoverable Ethernet fault. Go to MAP 0500. 440 Embedded port hardware failed. Go to MAP 0500. 442 Embedded port anomaly detected. No action required. 445 ASIC detected a system anomaly. No action required. 453 New feature key installed. No action required.
MAP 0000: Start MAP This MAP describes initial fault isolation for the Sphereon 4500. Fault isolation begins at the Internet-connected PC accessing the SANpilot interface, rack-mount management server, customer-supplied server running the Enterprise Fabric Connectivity Manager (EFCM) Lite application, failed switch, or switch-attached host.
2 Are you at a PC with a web browser (such as Netscape Navigator or Microsoft Internet Explorer), an Internet connection to the switch reporting the problem, and communicating with the switch through the SANpilot interface? YES ↓ NO Go to step 19. 3 Is the web-browser PC powered on and communicating with the switch through the Internet connection and SANpilot interface? NO ↓ YES Go to step 5. 4 Boot the web-browser PC. a. Power on the PC in accordance with the instructions delivered with the PC.
d. Type the user name and password obtained in step 1, and click OK. The SANpilot interface opens with the View panel displayed (Figure 3-2 on page 3-8). Figure 3-2 View Panel (SANpilot Interface) Continue to the next step. 5 Does the SANpilot interface appear operational with the View panel displayed? NO ↓ YES Go to step 10. 6 A Page cannot be found, Unable to locate the server, HTTP 404 - file not found, or other similar message appears.
7 Ensure the switch is connected to facility AC power. Inspect the switch for indications of being powered on, such as: • At the front bezel, an illuminated PWR LED (green) or ERR LED (amber). • Illuminated LEDs adjacent to Fibre Channel ports. • Audio emanations and airflow from cooling fans. Does the switch appear powered on? YES ↓ NO A power distribution problem is indicated. Go to MAP 0100: Power Distribution Analysis on page 3-30. Exit MAP.
Does the SANpilot interface appear operational with the View panel displayed? YES ↓ NO Perform switch fault isolation at the management server or customer-supplied server running the EFCM Lite application. Go to step 20. 10 At the View panel, inspect the Status field. Does the switch status indicate Operational? NO ↓ YES The switch appears operational. Exit MAP. 11 Inspect Fibre Channel port operational states. a. At the View panel, click the Port Properties tab.
b. Inspect the Beaconing and Operational State fields. Does the Beaconing field display an On message? YES ↓ NO Go to step 13. 12 Port beaconing is enabled. a. Consult the customer and next level of support to determine the reason port beaconing is enabled. b. Disable port beaconing: 1. At the View panel, select Operations at the left side of the panel. The Operations panel opens with the Port Beaconing page displayed. 2. Click the Beaconing State check box for the port.
15 Repeat step 11 through step 14 for each remaining Fibre Channel port for which a problem is suspected (ports 0 through 23). Is a problem indicated for any of the ports? NO ↓ YES Go to step 18 to obtain event codes. If no event codes are found, go to MAP 0600: Port Failure and Link Incident Analysis on page 3-74. Exit MAP. 16 Inspect power supply operational states. a. At the View panel, click the FRU Properties tab. The View panel (FRU Properties tab) displays (Figure 3-4).
17 Inspect the Status fields for switch FRUs. Does the State field display a Failed message for any of the FRUs? YES ↓ NO The switch appears operational. Exit MAP. A FRU failure is indicated. Continue to the next step to obtain event codes. If no event codes are found, go to MAP 0500: FRU Failure Analysis on page 3-68. Exit MAP. 18 Obtain event codes from the SANpilot event log. NOTE: If multiple event codes are found, note all codes and associated severity levels.
c. Record the event code, date, time, and severity (Informational, Minor, Major, or Severe). d. Record all event codes that may relate to the reported problem. Were one or more event codes found? NO ↓ YES Go to Table 3-3 on page 3-3 to interpret event codes. Exit MAP. Return to step 1 and perform fault isolation again. If this is the second time at this step, contact the next level of support. Exit MAP.
22 Is the SAN management application (SANavigator 4.0 or EFCM 8.0) active? NO ↓ YES Go to step 24. 23 Reboot the management server or customer-supplied server. If the customer-supplied server does not use the Windows 2000 operating system, refer to the supporting documentation to reboot the server. a. At the Windows 2000 desktop, click Start at the left side of the task bar (bottom of the desktop), then select Shut Down. The Shut Down Windows dialog box displays (Figure 3-6).
1. The green LCD panel illuminates. 2. The green hard disk drive (HDD) LED blinks momentarily, and processor speed and random-access memory information display momentarily at the LCD panel. 3. After a few seconds, the LCD panel displays the following message pertaining to boot sequence selection (Figure 3-7): Boot from LAN? Press Figure 3-7 LCD Panel During Boot Sequence 4. Ignore the message. After ten seconds, the server performs the boot sequence from the basic input/output system (BIOS).
Figure 3-8 SANavigator Login or EFCM Login Dialog Box f. Type a user ID and password (obtained in step 1, and both are case sensitive), and click Login. The SAN management application opens and the SANavigator or EFCM main window displays (Figure 3-9).
Did the main window display and does the SAN management application appear operational? YES ↓ NO A management server or customer-supplied server hardware problem is indicated. Event codes are not recorded. Go to MAP 0800: Server Hardware Problem Determination on page 3-110. Exit MAP. 24 Inspect the status symbol associated with the Sphereon 4500 Switch at the main window’s physical map or product list.
25 Ensure the switch is connected to facility AC power. Inspect the switch for indications of being powered on, such as: • At the front bezel, an illuminated PWR LED (green) or ERR LED (amber). • Illuminated LEDs adjacent to Fibre Channel ports. • Audio emanations and airflow from cooling fans. Does the switch appear powered on? YES ↓ NO A power distribution problem is indicated. Go to step 38 to obtain event codes.
29 Right-click the icon representing the switch reporting the problem. A pop-up menu appears. Select the Element Manager option from the menu. The Element Manager application opens and the Hardware View displays (Figure 3-10). Figure 3-10 Hardware View At the Hardware View: • Observe that the Sphereon 4500 Status table is yellow and the switch status is NOT OPERATIONAL. • Inspect FRUs for a blinking red and yellow diamond (failed FRU indicator) that overlays the FRU graphic.
30 Is a yellow triangle (attention indicator) associated with the icon representing the switch reporting the problem? YES ↓ NO Go to step 33. 31 Right-click the icon representing the switch reporting the problem. A pop-up menu appears. Select the Element Manager option from the menu. The Element Manager application opens and the Hardware View displays (Figure 3-10 on page 3-20).
• Inspect the switch for a yellow triangle that overlays the FRU graphic and indicates FRU beaconing is enabled. • Inspect ports for a yellow triangle (attention indicator) that overlays the port graphic. Does a yellow triangle overlay the switch or FRU graphic? YES ↓ NO Go to step 35. 34 Beaconing is enabled for the FRU. a. Consult the customer and next level of support to determine the reason FRU beaconing is enabled. b. Disable FRU beaconing. 1.
Figure 3-11 Port Properties Dialog Box b. Inspect the Operational State field. Does the Operational State field display a Segmented E_Port message? NO ↓ YES Expansion port (E_Port) segmentation is indicated. Go to step 38 to obtain event codes. If no event codes are found, go to MAP 0700: Fabric, ISL, and Segmented Port Problem Determination on page 3-93. Exit MAP. A message displays indicating a link incident problem. Go to step 38 to obtain event codes.
Figure 3-12 Link Incident Log If a link incident occurred, the affected port number is listed with one of the following messages. Link interface incident - implicit incident. Link interface incident - bit-error threshold exceeded. Link failure - loss of signal or loss of synchronization. Link failure - not-operational primitive sequence (NOS) received. Link failure - primitive sequence timeout. Link failure - invalid primitive sequence received for the current link state.
38 Obtain event codes from the Sphereon 4500 Event Log. NOTE: If multiple event codes are found, note all codes and associated severity levels. Record the date, time, and listed sequence, and determine if the codes are related to the reported problem. Begin fault isolation with the most recent event code with the highest severity level. Other codes may accompany this event code, or may indicate a normal indication after a problem is recovered. a. At the Hardware View, click Logs and select Event Log.
39 Are you at the switch reporting the problem? YES ↓ NO Go to step 51. 40 Is the green PWR LED at the switch front bezel illuminated? NO ↓ YES Go to step 45. 41 Is the switch connected to facility AC power and powered on? NO ↓ YES Go to step 44. 42 Connect the switch to facility AC power. Inspect the switch for indications of being powered on, such as: • At the front bezel, an illuminated PWR LED (green) or ERR LED (amber). • Illuminated LEDs adjacent to Fibre Channel ports.
44 Inspect the switch for indications of being powered on, such as: • At the front bezel, an illuminated PWR LED (green) or ERR LED (amber). • Illuminated LEDs adjacent to Fibre Channel ports. • Audio emanations and airflow from cooling fans. Does the switch appear powered on? YES ↓ NO A power distribution problem is indicated. Go to step 38 to obtain event codes. If no event codes are found, go to MAP 0100: Power Distribution Analysis on page 3-30. Exit MAP.
Was unit beaconing enabled because switch failure or degradation was suspected? YES ↓ NO The switch appears operational. Exit MAP. Go to step 39 and perform fault isolation again (at the switch). 47 Is the amber ERR LED at the switch front bezel illuminated? YES ↓ NO The switch appears operational. Verify switch operation at the management server or customer-supplied server running the EFCM Lite application. Go to step 20. 48 Check FRUs for failure symptoms.
51 You are at the console of an open systems interconnection (OSI) server attached to the switch reporting the problem. If an incident occurs on the Fibre Channel link between the switch and server, a link incident record is generated and sent to the server using the reporting procedure defined in T11/99-017v0.
MAP 0100: Power Distribution Analysis This MAP describes fault isolation for the switch power distribution system, including defective AC power cords or redundant power supplies. 1 Was an event code 200 or 201 observed at the SANpilot event log or at the Sphereon 4500 Event Log (management server)? YES NO ↓ Go to step 9. 2 Table 3-4 lists event codes, brief explanations of the codes, and the associated steps that describe fault isolation procedures.
4 A redundant power supply is disconnected from facility power, not properly installed, or has failed. Verify the power supply is connected to facility power. a. Ensure the AC power cord associated with the power supply (PS0 or PS1) is connected to the rear of the switch and a facility power receptacle. If not, connect the cord as directed by the customer. b. Ensure the associated facility circuit breaker is on. If not, ask the customer set the circuit breaker on. c. Ensure the AC power cord is not damaged.
7 Verify redundant power supply operation. a. Inspect the power supply and ensure the amber LED is extinguished. b. At the management server’s Hardware View (Figure 3-10 on page 3-20), observe the graphic representing the power supply and ensure a failure symbol (blinking red and yellow diamond) does not appear. Is a failure indicated? YES ↓ NO The switch appears operational. Exit MAP. 8 Visual inspection or an event code 200 or 201 indicates one or both power supplies must be removed and replaced.
9 Is fault isolation being performed at the switch? YES ↓ NO Fault isolation is being performed at the SANpilot interface, management server, or customer-supplied server. Go to step 18. 10 Verify the switch is connected to facility power and is powered on. a. Ensure the AC power cord associated with the power supply (PS0 or PS1) is connected to the rear of the switch and a facility power receptacle. If not, connect the cord as directed by the customer. b.
13 The switch AC power distribution system failed. Possible causes include failure of: • Both power supplies. • The CTP card. Does inspection of both power supplies indicate a dual failure (amber LED illuminated on each power supply)? YES ↓ NO One or both power supplies appear operational, but a power distribution failure through the CTP card is indicated. Go to step 17. 14 Ensure both power supplies are correctly installed and seated in the switch.
16 Both power supplies failed and must be removed and replaced. Refer to RRP 2: Redundant Power Supply on page 5-6. • Perform the data collection procedure as part of FRU removal and replacement. • Connect the switch to facility AC power after both power supplies are replaced. Did dual power supply replacement solve the problem? NO ↓ YES The switch appears operational. Exit MAP. A dual power supply failure is not confirmed.
20 A Page cannot be found, Unable to locate the server, HTTP 404 - file not found, or other similar message appears. The message indicates the PC cannot communicate with the switch because: • The switch-to-PC Internet link could not be established. • AC power distribution in the switch failed, or AC power was disconnected. • The switch CTP card failed. Continue to the next step. 21 Ensure the switch reporting the problem is connected to facility AC power.
23 At the management server’s Hardware View (Figure 3-10 on page 3-20), does a yellow triangle appear at the alert panel and a blinking red and yellow diamond (failed FRU indicator) appear to overlay a power supply graphic? NO ↓ YES A redundant power supply failed. Go to step 8.
MAP 0200: POST Failure Analysis When the switch is powered on, it performs a series of power-on self-tests (POSTs). When POSTs complete, the switch performs an initial program load (IPL) that loads firmware and brings the unit online. This MAP describes fault isolation for problems that may occur during the POST/IPL process. If an error occurs, the POST/IPL process continues in an attempt to initialize the switch and bring it online. An event code 400 displays when the switch completes the POST/IPL process.
Table 3-5 Event Code MAP 200 Event Codes Explanation Action 400 Power-up diagnostic failure. Go to step 4. 411 Firmware fault. Go to step 8. 4 POST/IPL diagnostics detected a FRU failure as indicated by event code 400 with supplementary event data. a. At the SANpilot event log or the Sphereon 4500 Event Log, examine the first two bytes (0 and 1) of event data associated with event code 400. b. Byte 0 is a FRU code that indicates the failed component.
• This procedure is concurrent and can be performed while switch power is on. • Perform the data collection procedure as part of FRU removal and replacement. • If multiple power supply failures occurred, connect the switch to facility AC power after both power supplies are replaced. ATTENTION ! Do not remove a power supply unless a replacement FRU is immediately available. To avoid product overheating, a removed power supply must be replaced within five minutes.
8 POST/IPL diagnostics detected a firmware failure (as indicated by event code 411) and performed an online dump. All Fibre Channel ports reset after the failure and devices momentarily logout, login, and resume operation. Perform the data collection procedure and return the CD to McDATA for analysis. Exit MAP.
Figure 3-14 Windows Security Dialog Box b. Click Task Manager. The Windows Task Manager dialog box displays with the Applications page open by default (Figure 3-15).
c. Select (highlight) the SAnavigator or EFCM entry and click End Task. The SAN management application closes. Continue to the next step. 3 Attempt to clear the problem by rebooting the management server or customer-supplied server PC. If the customer-supplied server does not use the Windows 2000 operating system, refer to the supporting documentation to reboot the server. a. At the Windows 2000 desktop, click Start at the left side of the task bar (bottom of the desktop), then select Shut Down.
Boot from LAN? Press Figure 3-17 LCD Panel During Boot Sequence 4. Ignore the message. After ten seconds, the server performs the boot sequence from the BIOS. During the boot sequence, the server performs additional POSTs and displays the following operational information at the LCD panel: • Host name. • System date and time. • LAN 1 and LAN 2 IP addresses. • Fan 1, fan 2, fan 3, and fan 4 rotational speed. • CPU temperature. • Hard disk capacity.
Figure 3-18 SANavigator Login or EFCM Login Dialog Box f. Type a user ID and password (obtained in MAP 0000: Start MAP, and both are case sensitive), and click Login. The SAN management application opens and the SANavigator or EFCM main window displays (Figure 3-9 on page 3-17). Did the main window display and does the SAN management application appear operational? NO ↓ YES The problem is transient and the management server or customer-supplied server appears operational. Exit MAP.
6 The SAN management applications running on the management server and client workstation are not at compatible release levels. Recommend to the customer that the downlevel version be upgraded. Does the customer want the SAN management application upgraded? YES ↓ NO Power off the client workstation. Exit MAP. 7 Upgrade the downlevel SAN management application. Refer to Install or Upgrade Software on page 4-87.
Did the firmware version download to the switch? NO ↓ YES The management server or customer-supplied server appears operational. Exit MAP. A CTP card failure is suspected. Go to MAP 0000: Start MAP on page 3-6 to isolate the problem. Exit MAP. 11 Did the Element Manager application display a window with the message The data collection process failed? YES ↓ NO Go to step 13. 12 The data collection process failed. Retry the process using a new CD. Refer to Collect Maintenance Data on page 4-44.
Figure 3-19 Dr. Watson for Windows 2000 Dialog Box YES ↓ NO Go to step 14. A SAN management application error occurred and transmitted a handling exception event to the operating system. a. Click Cancel to close the Dr. Watson for Windows 2000 dialog box and SAN management application. b. Using the My Computer function at the Windows 2000 desktop, copy the crash dump file (user.dmp) from the local disk (C:) to the CD-RW drive (D:). c.
14 Did the management server or customer-supplied server crash and display a blue screen with the system dump file in hexadecimal format (blue screen of death)? YES ↓ NO The management server or customer-supplied server appears operational. Exit MAP. 15 Attempt to clear the problem by power cycling the management server or customer-supplied server PC. If the customer-supplied server does not use the Windows 2000 operating system, refer to the supporting documentation to reboot the server. a.
• Fan 1, fan 2, fan 3, and fan 4 rotational speed. • CPU temperature. • Hard disk capacity. • Virtual and physical memory capacity. c. After successful POST completion, the LCD panel displays a Welcome!! message, then continuously cycles through and displays server operational information. d. After rebooting the server at the LCD panel, log on to the management server’s Windows 2000 desktop through a LAN connection to a browser-capable PC.
MAP 0400: Loss of Server Communication This MAP describes fault isolation of the Ethernet communication link between a switch and the management server or customersupplied server, or between a switch and a web browser PC running the SANpilot interface. Failure indicators include: • Event codes recorded at the SANpilot event log or Sphereon 4500 Event Log. • At the web browser PC, A Page cannot be found, Unable to locate the server, HTTP 404 - file not found, or other similar message.
3 A Page cannot be found, Unable to locate the server, HTTP 404 - file not found, or other similar message appears. The message indicates the PC cannot communicate with the switch because: • The switch-to-PC Internet (Ethernet) link could not be established. • AC power distribution in the switch failed, or AC power was disconnected. • The switch CTP card failed. Continue to the next step. 4 Ensure the switch is connected to facility AC power.
a. Wait approximately five minutes, then attempt to login to the switch again. b. At the Netsite field (Netscape Navigator) or Address field (Internet Explorer), type http://xxx.xxx.xxx.xxx, where xxx.xxx.xxx.xxx is the IP address of the switch (obtained in MAP 0000: Start MAP). The Username and Password Required dialog box appears. c. Type the user name and password obtained in MAP 0000: Start MAP and click OK. If the View panel does not display, wait five minutes and perform this step again.
8 Ensure the switch reporting the problem is connected to facility AC power. Inspect the switch for indications of being powered on, such as: • At the front bezel, an illuminated PWR LED (green) or ERR LED (amber). • Illuminated LEDs adjacent to Fibre Channel ports. • Audio emanations and airflow from cooling fans. Does the switch appear powered on? YES ↓ NO A power distribution problem is indicated. Go to MAP 0100: Power Distribution Analysis on page 3-30. Exit MAP.
Table 3-7 MAP 400 Error Messages Error Message Action Never connected. Go to step 11. Link timeout. Go to step 11. Protocol mismatch. Go to step 18. Duplicate session. Go to step 21. Unknown network address. Go to step 24. Incorrect product type. Go to step 26. 11 Transmit or receive errors for a switch’s Ethernet adapter exceeded a threshold, the switch-to-server link was not connected, or the switch-to-server link timed out.
13 Verify the hubs are correctly daisy-chained (Figure 3-22). 1 4 5 8 9 12 13 16 17 MID 20 21 MDIX 24 1 1 1 4 5 8 13 9 12 16 17 20 21 MID 1 MDIX 24 4 5 13 1 8 9 16 17 12 20 21 MID 24 MDIX 1 Figure 3-22 Daisy-Chained Ethernet Hubs a. At the first (top) Ethernet hub, ensure an RJ-45 Ethernet patch cable connects to port 24 and the medium-dependent interface (MDI) switch is set to MDI (in). b.
14 Verify operation of the Ethernet hub or hubs. Inspect each hub for indications of being powered on, such as: • Green Power LED illuminated. • Green Status LEDs illuminated. Is a hub failure indicated? YES ↓ NO Go to step 16. 15 Remove and replace the Ethernet hub. Refer to the supporting documentation shipped with the hub for instructions. Did hub replacement solve the problem? NO ↓ YES The switch-to-server connection is restored and appears operational. Exit MAP.
17 The Ethernet adapter on the switch CTP card reset in response to an error. The connection to the management server or customersupplied server terminated briefly, then recovered upon reset. Perform the data collection procedure and return the CD to McDATA for analysis. Exit MAP. 18 A protocol mismatch occurred because the SAN management application and the switch firmware are not at compatible release levels. Recommend to the customer that the downlevel version (software or firmware) be upgraded.
21 An instance of the SAN management application is open at another management server or customer-supplied server and is communicating with the switch (duplicate session). Notify the customer and either: • Power off the management server or customer-supplied server running the second instance of the application, or • Configure the management server or customer-supplied server running the second instance of the application as a client workstation.
b. After a few seconds, the LCD panel displays the following (Figure 3-23): LAN 2: 010.001.001.001 Figure 3-23 LCD Panel (LAN 2 IP Address) c. Depending on switch-to-server LAN connectivity, record the appropriate IP address (LAN 1 or LAN 2). Continue to the next step. 23 Configure the management server or customer-supplied server reporting the Duplicate Session communication problem as a client. a. At the SANavigator or EFCM main window, select Logout from the SAN menu.
24 The IP address defining the switch to the SAN management application is incorrect or unknown and must be verified. A maintenance terminal (PC) and asynchronous RS-232 null modem cable are required to verify the switch IP address. The tools are provided with the switch or by service personnel. To verify the IP address: a. Remove the protective cap from the 9-pin maintenance port at the rear of the switch (a phillips screwdriver may be required). Connect one end of the RS-232 null modem cable to the port.
f. Type Sphereon 4500 in the Name field and click OK. The Connect To dialog box displays (Figure 3-25). Figure 3-25 Connect To Dialog Box g. Ensure the Connect using field displays COM1 or COM2 (depending on the serial communication port connection to the switch), and click OK. The COMn dialog box displays, where n is 1 or 2 (Figure 3-26).
h. Configure the Port Settings parameters as follows: — Bits per second - 115200. — Data bits - 8. — Parity - None. — Stop bits - 1. — Flow control - Hardware or None. When the parameters are set, click OK. The Sphereon 4500 HyperTerminal dialog box displays. i. At the > prompt, type the user-level password (default is password) and press Enter. The password is case sensitive. The Sphereon 4500 - HyperTerminal dialog box displays with a C> prompt at the bottom of the window. j.
Figure 3-28 HyperTerminal Dialog Box m. Click Yes. A second HyperTerminal dialog box displays (Figure 3-29). Figure 3-29 HyperTerminal Dialog Box n. Click No to exit and close the HyperTerminal application. o. Power off the maintenance terminal. p. Disconnect the RS-232 null modem cable from the switch and the maintenance terminal. Replace the protective cap over the maintenance port. Continue to the next step.
Figure 3-30 Discover Setup Dialog Box b. At the Available Addresses field, select (highlight) the switch to be reconfigured and click Change. The Editing Domain Information dialog box displays (Figure 3-31). Figure 3-31 Editing Domain Information Dialog Box c. Click Yes. The Domain Information dialog box displays with the IP Address page open by default (Figure 3-32 on page 3-66).
Figure 3-32 Domain Information Dialog Box (IP Address Page) d. Type the correct switch IP address in the IP Address field. e. Click OK to save the new IP address, close the dialog box, and redefine the switch to the SAN management application. f. Click OK to close the Discover Setup dialog box and return to the SAN management application.
b. Select the Delete option from the pop-up menu. The SANavigator or EFCM Message dialog box displays (Figure 3-33). Figure 3-33 SANavigator or EFCM Message Dialog Box c. Click Yes to delete the switch. d. At the SAN management application main window, select the Setup option from the Discover menu. The Discover Setup dialog box displays (Figure 3-30 on page 3-65). e. Click Add. The Domain Information dialog box displays with the IP Address page open by default (Figure 3-34).
f. Type a switch description in the Description field. g. Type the switch IP address (determined by the customer’s network administrator) in the IP Address field. h. Type the switch subnet mask (determined by the customer’s network administrator) in the Subnet Mask field. i. At the Data Source for Domain area of the dialog box, select the Use auto detection, Use the server, or Use a specific RDC radio button (determined by the customer’s network administrator). j.
1 Was an event code 300, 301, 302, 303, 304, 305, 426, 433, 440, 810, or 811 observed at the SANpilot event log or at the Sphereon 4500 Event Log? YES ↓ NO Go to step 3. 2 Table 3-8 lists event codes, brief explanations of the codes, and associated steps that describe fault isolation procedures. MAP 500 Event Codes Table 3-8 Event Code Explanation Action 300 Cooling fan propeller failed. Go to step 6. 301 Cooling fan propeller failed. Go to step 6. 302 Cooling fan propeller failed.
4 Ensure the switch reporting the problem is connected to facility AC power. Inspect the switch for indications of being powered on, such as: • At the front bezel, an illuminated PWR LED (green) or ERR LED (amber). • Illuminated LEDs adjacent to Fibre Channel ports. • Audio emanations and airflow from cooling fans. Does the switch appear powered on? YES ↓ NO Both power supply modules failed or the CTP card failed. Go to MAP 0000: Start MAP on page 3-6.
• Perform the data collection procedure as part of FRU removal and replacement. ATTENTION ! Do not remove a power supply unless a replacement FRU is immediately available. To avoid product overheating, a removed power supply must be replaced within five minutes. Do the fan and power supply module(s) appear to function? NO ↓ YES The switch appears operational. Exit MAP. Contact the next level of support. Exit MAP. 7 Inspect the switch front panel.
8 Is the green PWR LED illuminated, the amber ERR LED illuminated, and all Fibre Channel traffic disrupted (not operational)? NO ↓ YES A CTP card failure is indicated. Replace the switch. Exit MAP. Analysis for this failure is not described in this MAP. Go to MAP 0000: Start MAP on page 3-6. If this is the second time at this step, contact the next level of support. Exit MAP.
13 A Page cannot be found, Unable to locate the server, HTTP 404 - file not found, or other similar message appears. The message indicates the PC cannot communicate with the switch because: • The switch-to-PC Internet link could not be established. • AC power distribution in the switch failed, or AC power was disconnected. • The switch CTP card failed. The SANpilot interface is not operational and fault isolation must be performed at the switch or management server. Go to step 1.
NO YES ↓ A fan module failure is indicated. Go to step 6. 17 At the Hardware View, does a grey square appear at the alert panel, a No Link status appear at the Sphereon 4500 Status table, and graphical FRUs appear uninstalled? YES ↓ NO A green circle appears at the alert panel and the switch appears operational. Exit MAP. The grey square indicates the management server or customersupplied server cannot communicate with the switch because: • The switch-to-server Ethernet link failed.
• A blinking red and yellow diamond (failed FRU indicator) appears over a port graphic or a yellow triangle (attention indicator) appears at the alert panel of the Hardware View. • A link incident message recorded in the Link Incident Log or Port Properties dialog box. 1 Was an event code 080, 081, 506, 507, 512, or 514 observed at the SANpilot event log or at the Sphereon 4500 Event Log (management server)? NO ↓ YES Go to step 3.
MAP 600 Event Codes (Continued) Table 3-9 Event Code Explanation Action 583 Loss of signal or loss of synchronization. Go to step 34. 584 Not operational primitive sequence received. Go to step 34. 585 Primitive sequence timeout. Go to step 34. 586 Invalid primitive sequence received for current link state. Go to step 34. 4 Is fault isolation being performed at the switch? YES ↓ NO Fault isolation is being performed at the SANpilot interface, management server, or customer-supplied server.
• Perform an external loopback test for the port as part of FRU removal and replacement. Refer to Perform Port Diagnostic Loopback Tests on page 4-38. NOTE: An event code 514 may generate a call-home event that incorrectly indicates a CTP card failure. Although the optical socket may have failed, first replace the optical transceiver and verify operation. If a failure is still indicated, replace the switch.
• At the front bezel, an illuminated PWR LED (green) or ERR LED (amber). • Illuminated LEDs adjacent to Fibre Channel ports. • Audio emanations and airflow from cooling fans. Does the switch appear powered on? YES ↓ NO Analysis for an Ethernet link, AC power distribution, or CTP failure is not described in this MAP. Go to MAP 0000: Start MAP on page 3-6. If this is the second time at this step, contact the next level of support. Exit MAP.
12 Install an SFP optical transceiver in the port receptacle. Refer to RRP 1: SFP Optical Transceiver on page 5-2. • This procedure is concurrent and can be performed while the switch is powered on and operational. • Verify location of the failed port. • Perform an external loopback test for the port as part of FRU removal and replacement. Refer to Perform Port Diagnostic Loopback Tests on page 4-38. Exit MAP.
c. Table 3-11 lists LED and port operational state combinations and associated MAP 0600 (or other) steps that describe fault isolation procedures. Table 3-11 Port Operational and LED States (Management Server) Operational State Green LED Amber LED Action Offline Off Off Go to step 19. Not Operational Off Off Go to step 19. Testing Off Blinking Internal loopback test in process. Exit MAP. Testing On Blinking External loopback test in process. Exit MAP.
Did one of the listed messages appear in the Link Incident Log? YES ↓ NO The switch appears operational. Exit MAP. Go to step 34. 18 As indicated by a message or event code 507, a Fibre Channel port failed an internal or external loopback test. a. Reset each port that failed the loopback test. 1. At the Hardware View (Figure 3-10 on page 3-20), right-click the port. A pop-up menu appears. 2. Select Reset Port. A This operation will cause a link reset to be sent to the attached device message displays. 3.
Was port beaconing enabled because port failure or degradation was suspected? YES NO ↓ The switch appears operational. Exit MAP. Go to step 1. 21 As indicated by a message or event code 080, the eight-byte (16-digit) worldwide name (WWN) entered to configure port binding is not valid or a nickname was used that is not configured for the attached device in the Element Manager application. From the Hardware View (Figure 3-10 on page 3-20), click Node List. Note the Port WWN column.
Table 3-12 Invalid Attachment Reasons and Actions (Continued) Reason Action External loopback plug connected. Go to step 25. N-Port connection not allowed. Go to step 23. Non-McDATA switch at other end. Go to step 24. Unauthorized port binding WWN. Go to step 21. Unresponsive node. Go to step 27. ESA security mismatch. Go to step 29. Fabric binding mismatch. Go to step 30. Authorization failure reject. Go to step 27. Unauthorized switch binding WWN. Go to step 31. Fabric mode mismatch.
Did reconfiguring the port type solve the problem? NO ↓ YES The switch appears operational. Exit MAP. Contact the next level of support. Exit MAP. 24 One of the following mode-mismatch conditions was detected and an ISL connection is not allowed: • The switch is configured for operation in Open Fabric 1.0 mode and is connected to a fabric element not configured to Open Fabric 1.0 mode. • The switch is configured for operation in Open Fabric 1.
Figure 3-35 Configure Fabric Parameters Dialog Box c. Select McDATA Fabric 1.0 or Open Fabric 1.0 from the Interop Mode list box. — Select the McDATA Fabric 1.0 option if the switch is fabric-attached only to other McDATA directors or switches that are also operating in McDATA Fabric 1.0 mode. — Select the Open Fabric 1.0 option if the switch is fabric-attached to directors or switches produced by other original equipment manufacturers (OEMs) that are open-fabric compliant. d.
26 Remove the loopback plug from the port receptacle. If directed by the customer, connect a fiber-optic jumper cable attaching a device to the switch. • If the port is operational and a device is not attached, both LEDs adjacent to the port extinguish and the port state is No Light. • If the port is operational and a device is attached, the blue or green LED illuminates, the amber LED extinguishes, and the port state is Online.
Did service of the HBAs solve the problem? NO ↓ YES Exit MAP. Contact the next level of support. Exit MAP. 29 A port connection is not allowed because of an Exchange Security Attribute (ESA) feature mismatch. Switch binding parameters must be compatible for both fabric elements. a. At the Hardware View (Figure 3-10 on page 3-20) for each switch, click Configure and select Switch Binding and Change State. The Switch Binding - State Change dialog box displays (Figure 3-36).
c. Ensure the Connection Policy radio buttons are compatible for both switches. d. Click Activate for each switch. The switch binding feature is consistently enabled for both switches. Did configuring the switch binding parameters solve the problem? NO ↓ YES The switch appears operational. Exit MAP. Contact the next level of support. Exit MAP. 30 A port connection is not allowed because of a fabric binding mismatch. Fabric membership lists must be compatible for both fabric elements. a.
b. At the Fabric List section, ensure the Enable/Disable checkbox is enabled (checked) for the fabric containing both switches. c. At the Membership List of section, update the membership list for both elements to ensure interswitch compatibility, then click OK. The fabric binding feature is consistently enabled for both switches. Did updating the fabric membership lists solve the problem? NO ↓ YES The switch appears operational. Exit MAP. Contact the next level of support. Exit MAP.
b. At the Switch Binding - Membership List dialog box ensure the Switch Membership List is updated and correct for each switch, then click Activate for each switch. The switch binding feature is consistently enabled for both switches. Did updating the switch membership lists solve the problem? NO ↓ YES The switch appears operational. Exit MAP. Contact the next level of support. Exit MAP.
Clear the link incident for the port. a. At the Hardware View (Figure 3-10 on page 3-20), right-click the port. A pop-up menu appears. b. Select Clear Link Incident Alert(s). The Clear Link Incident Alert(s) dialog box displays (Figure 3-39). Figure 3-39 Clear Link Incident Alert(s) Dialog Box c. Select the This port (n) only radio button (where n is the port number) and click OK. The link incident clears. d. Monitor port operation for approximately five minutes.
36 Monitor port operation for approximately five minutes. Did the link incident recur? YES ↓ NO The Fibre Channel link and switch appear operational. Exit MAP. 37 Clean fiber-optic connectors on the jumper cable. a. Notify the customer the port will be blocked. Ensure the customer’s system administrator quiesces Fibre Channel frame traffic through the port and sets the attached device offline. b. Block the port. Refer to Block or Unblock a Port on page 4-51. c.
39 The attached device is causing the recurrent link incident. Notify 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. Did the link incident recur? YES ↓ NO The attached device, Fibre Channel link, and switch appear operational. Exit MAP. Contact the next level of support. Exit MAP.
1 Was an event code 011, 021, 051, 052, 061, 062, 063, 070, 071, 072, 140, 142, or 150 observed at the SANpilot event log or at the Sphereon 4500 Event Log (management server)? YES ↓ NO Go to step 3. 2 Table 3-13 lists event codes, brief explanations of the codes, and associated steps that describe fault isolation procedures. Table 3-13 Event Code 3-94 MAP 700 Event Codes Explanation Action 011 Login Server database invalid. Go to step 9. 021 Name Server database invalid. Go to step 9.
3 Is fault isolation being performed through the SANpilot interface? YES ↓ NO Fault isolation is being performed at the management server or customer-supplied server. Go to step 6. 4 Does the SANpilot interface appear operational? YES ↓ NO Analysis for an Ethernet link, AC power distribution, or CTP failure is not described in this MAP. Go to MAP 0000: Start MAP on page 3-6. If this is the second time at this step, contact the next level of support. Exit MAP.
Table 3-14 Port Segmentation Reasons and Actions (SANpilot) Segmentation Reason Action Build fabric protocol error. Go to step 18. No principal switch. Go to step 20. No response from attached switch (hello timeout). Go to step 21. 6 At the management server, does a yellow triangle (attention indicator) appear adjacent to a Fibre Channel port graphic at the Hardware View (Figure 3-10 on page 3-20)? YES ↓ NO The problem is transient and the switch-to-fabric element connection appears operational.
Table 3-15 Port Segmentation Reasons and Actions (Management Server) Segmentation Reason Action Incompatible operating parameters. Go to step 15. Duplicate domain ID. Go to step 16. Incompatible zoning configurations. Go to step 17. Build fabric protocol error. Go to step 18. No principal switch. Go to step 20. No response from attached switch (hello timeout). Go to step 21. 9 A minor error occurred that caused the Fabric Services database to be re-initialized to an empty state.
11 As indicated by an event code 061, a minor error occurred that caused the Fabric Controller database to be re-initialized to an empty state and fail CRC validation. As a result, the switch briefly lost interswitch link capability. All interswitch links resume operation after CTP reset. Perform the data collection procedure and return the CD to McDATA for analysis. Exit MAP.
Did fabric reconfiguration solve the problem? NO YES ↓ The switch and multiswitch fabric appear operational. Exit MAP. Contact the next level of support. Exit MAP. 14 A 070 event code indicates an E_Port detected an incompatibility with an attached switch and prevented the switches from forming a multiswitch fabric. A segmented E_port cannot transmit Class 2 or Class 3 Fibre Channel traffic.
15 A switch 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. Contact McDATA customer support or engineering personnel to determine the recommended E_D_TOV and R_A_TOV values for both switches. b. Notify the customer both switches will be set offline. Ensure the system administrator quiesces Fibre Channel frame traffic through the switches and sets attached devices offline. c.
g. Set both switches online. Refer to Set the Switch Online or Offline on page 4-48. Did the operating parameter change solve the problem and did both switches join through the ISL to form a fabric? NO ↓ YES The switch, associated ISL, and multiswitch fabric appear operational. Exit MAP. Contact the next level of support. Exit MAP. 16 A switch E_Port segmented because two fabric elements had duplicate domain IDs. a.
e. Type the customer-determined preferred domain ID value, then click Activate. f. Repeat steps d and e at the Hardware View for the switch attached to the segmented E_Port (second switch). Use a different preferred domain ID value. g. Set both switches online. Refer to Set the Switch Online or Offline on page 4-48. Did the domain ID change solve the problem and did both switches join through the ISL to form a fabric? NO ↓ YES The switch, associated ISL, and multiswitch fabric appear operational. Exit MAP.
Figure 3-42 Zoning Dialog Box (Zone Library Tab) e. Click the Active Zone Set tab. The Zoning dialog box displays with the Active Zone Set page open (Figure 3-43).
Figure 3-43 Zoning Dialog Box (Active Zone Set Tab) f. Inspect zone names in the active zone set to determine the incompatible name. g. Modify the incompatible zone name as directed by the customer: 1. At the Zoning dialog box, click the Zone Library tab. The dialog box returns to the Zone Library page (Figure 3-42 on page 3-103). 2. At the Zones field, right-click the zone name to be changed. A pop-up menu appears. 3. Select the Rename option from the menu.
Did the zone name change solve the problem and did both switches join through the ISL to form a fabric? NO ↓ YES The switch, associated ISL, and multiswitch fabric appear operational. Exit MAP. Contact the next level of support. Exit MAP. 18 A switch E_Port segmented because a build fabric protocol error was detected. a. Disconnect the fiber-optic jumper cable from the segmented E_Port. b. Reconnect the cable to the same port.
b. Set the switch offline. Refer to Set the Switch Online or Offline on page 4-48. c. At the Hardware View (Figure 3-10 on page 3-20) for the switch reporting the problem, click Configure and select Operating Parameters and Fabric Parameters. The Configure Fabric Parameters dialog box displays (Figure 3-40 on page 3-100). d. At the Switch Priority field, select Principal, Never Principal, or Default (the default setting is Default). The switch priority value designates the fabric’s principal switch.
Exit MAP. 22 As indicated by an event code 072, a switch E_Port is connected to an unsupported switch or fabric element. Advise the customer of the problem and disconnect the interswitch link to the unsupported switch. Exit MAP. 23 A 140 event code occurs only if the optional OpenTrunking feature is enabled. The event code indicates OpenTrunking firmware detected an ISL with Fibre Channel traffic that exceeds the configured congestion threshold. No action is required for an isolated event.
• Increase the ISL link speed between the switches reporting the problem (from 1 Gbps to 2 Gbps). • Reroute Fibre Channel traffic by moving device connections to a less-congested region of the fabric. Did the corrective action solve the problem and relieve the reported low BB_Credit condition? NO YES ↓ The ISL appears operational. Exit MAP. Contact the next level of support. Exit MAP. 25 A 150 event code indicates a zone merge process failed during ISL initialization.
26 A zone merge process failed during ISL initialization. The following list explains the reason: • Failure reason 01 - An invalid data length condition caused an error in a zone merge frame. • Failure reason 08 - An invalid zone set format caused an error in a zone merge frame. • Failure reason F0 - A retry limit reached condition caused an error in a zone merge frame. • Failure reason F1 - An invalid response length condition caused an error in a zone merge frame.
Perform the data collection procedure and return the CD to McDATA for analysis. Contact the next level of support, and report the 150 event code, the associated failure reason, and the associated error code. Exit MAP. MAP 0800: Server Hardware Problem Determination This MAP describes isolation of hardware-related problems with the customer-supplied server communicating with the switch through the SANpilot interface, management server, or customer-supplied server running the SAN management application.
3 Are you performing fault isolation at one of the following servers? • The rack-mount management server running the Windows 2000 Professional operating system. • A customer-supplied server running the client SAN management application and a Windows-based operating system (Windows 95, Windows 98, Windows 2000, Windows XP, or Windows NT 4.0). • A customer-supplied server running the EFCM Lite application and a Windows-based operating system.
a. Right-click anywhere on the Windows task bar at the bottom of the desktop. A pop-up menu appears. b. Select Task Manager. The Windows Task Manager dialog box displays with the Applications page open by default. Click the Performance tab to open the Performance page (Figure 3-45). Figure 3-45 Windows Task Manager Dialog Box (Performance Page) c. At the Physical Memory (K) portion of the dialog box, inspect the total amount of physical memory. d.
6 Reboot the server and perform system diagnostics. a. At the Windows 2000 desktop, click Start at the left side of the task bar (bottom of the desktop), then select Shut Down. The Shut Down Windows dialog box displays (Figure 3-46). Figure 3-46 Shut Down Windows Dialog Box b. Select the Shut Down option from the list box and click OK. The management server powers down. c. Wait approximately 30 seconds and press the power ( ) button on the LCD panel to power on the server and perform POSTs.
4. Ignore the message. After ten seconds, the server performs the boot sequence from BIOS. During the boot sequence, the server performs additional POSTs and displays the following operational information at the LCD panel: • Host name. • System date and time. • LAN 1 and LAN 2 IP addresses. • Fan 1, fan 2, fan 3, and fan 4 rotational speed. • CPU temperature. • Hard disk capacity. • Virtual and physical memory capacity. d.
Figure 3-48 SANavigator Login or EFCM Login Dialog Box Did the SANavigator Log In or EFCM Log In dialog box display? YES ↓ NO Go to step 9. 8 At the SANavigator Log In or EFCM Log In dialog box, type a user ID and password (obtained in MAP 0000: Start MAP, and both are case sensitive), and click Login. The SAN management application opens and the SANavigator or EFCM main window displays (Figure 3-9 on page 3-17).
Did diagnostic test programs detect a problem? NO ↓ YES Refer to the supporting documentation shipped with the server for instructions to resolve the problem. Exit MAP. 10 Reboot the server. a. At the Windows 2000 desktop, click Start at the left side of the task bar (bottom of the desktop), then select Shut Down. The Shut Down Windows dialog box displays (Figure 3-46 on page 3-113). b. Select the Shut Down option from the list box and click OK. The management server powers down. c.
• CPU temperature. • Hard disk capacity. • Virtual and physical memory capacity. d. After successful POST completion, the LCD panel displays a Welcome!! message, then continuously cycles through and displays server operational information. e. After rebooting the server at the LCD panel, log on to the management server’s Windows 2000 desktop through a LAN connection to a browser-capable PC. Refer to Access the Management Server Desktop on page 2-55 for instructions.
12 Advise the customer and next level of support that the server hard drive should be restored to its original factory configuration. If the customer and support personnel do not concur, go to step 13. a. Format the server hard drive. Refer to supporting documentation shipped with the server for instructions. b. Install the Windows 2000 operating system and SAN management application. Refer to Appendix C, Restore Management Server for instructions.
4 Repair Information This chapter describes repair-related procedures for the Sphereon 4500 Fabric Switch and associated field-replaceable units (FRUs). The procedures are performed through the SANpilot interface, storage area network (SAN) management application (SANavigator 4.0 or EFCM 8.0), or Sphereon 4500 Element Manager application. The following procedures are described: • Obtain log information. • Obtain port diagnostic information. • Perform port diagnostic loopback tests.
Procedural Notes The following procedural notes are referenced in applicable repair procedures. The notes do not necessarily apply to all procedures in the chapter. 1. Before performing a procedure, read the procedure carefully and thoroughly to familiarize yourself with the information and reduce the possibility of problems or customer down time. 2. When performing procedures described in this chapter, follow all WARNING statements, and statements listed in the preface of this manual. 3.
— Audit Log — Fabric Log — Embedded Port Frame Log • The SAN management application (SANavigator 4.0 or EFCM 8.0) provides access to the following: — Audit Log. — Event Log. — Session Log. — Product Status Log. — Fabric Log. • The Element Manager application provides access to the following: — Sphereon 4500 Audit Log. — Sphereon 4500 Event Log. — Hardware Log. — Link Incident Log. — Threshold Alert Log. — Open Trunking Log. SANpilot Logs To open a SANpilot log, click the Logs tab at the Monitor panel.
Figure 4-1 Monitor Panel (Logs Page) At the Logs page: • Select (double-click) a log title to open and view the contents of the associated log, or • Select (double-click) the All Logs title to open and simultaneously view the contents of all logs. The Logs page provides a Clear Log button for each log. Click the button to delete all entries for the associated log. The Logs page also provides a Clear All Logs button. Click the button to delete all entries in all logs.
Figure 4-2 Event Log The log consists of the following columns: Open Trunking Re-Route Log • Date/Time - Date and time the event occurred. • Error Code - Three-digit code that describes the event. Event codes are listed and described in Appendix B, Event Code Tables. • Severity - Severity of the event (Informational, Minor, Major, or Severe). • Event Data - Up to 32 bytes of supplementary information (if available) in hexadecimal format. Event data is described in Appendix B, Event Code Tables.
Figure 4-3 Open Trunking Re-Route Log The log consists of the following columns: Link Incident Log 4-6 • Date/Time - Date and time the re-route action occurred. • Receive Port - The switch port number (decimal) used for receiving Fibre Channel traffic after the re-route action. • Target Domain - The domain ID (decimal) of the target device to which Fibre Channel traffic from the switch was rerouted.
Figure 4-4 Link Incident Log The log consists of the following columns: • Date/Time - Date and time the link incident occurred. • Port - Port number (0 through 23) that reported the link incident. • Event - Brief description of the link incident. Problem descriptions include: — Implicit incident. — Bit-error threshold exceeded. — Loss of signal or loss of synchronization. — Not-operational primitive sequence received. — Primitive sequence timeout.
Figure 4-5 Clearing the Security Log • Date/Time: The date/time when the event occurred. • Trigger Level: The trigger level of the event. Possible values include: Informational, Security Change, or Error • Count: A cumulative count of events within a known period. • Category: The event category message with possible values may be: Successful Connection, Disconnection, Configuration Change, Authorization Failure, Authentication Failure, or Reserved • Description: Description of the event.
Figure 4-6 Clearing the Audit Log • Date/Time: The date and time of the log entry. • Source: The source of Audit Log event. • User ID: Identifier of the user that issued the command. The identifier is usually an IP Address. • Action: The type of Audit Log event. Viewing the Audit Log ATTENTION! Before clearing logs, make sure the logs are not needed for troubleshooting. Once a log is cleared, the data cannot be retrieved. To clear the Audit Log, select Monitor and select the Logs tab.
TIP: The same entries will go into both logs until the non-wrap log gets full. Once the non-wrap log gets full, the entries go into the wrap log. Once the wrap log is full, it will start to overwrite entries. If you need to look at a history of log entries, you should review both logs. The Fabric Log provides: Figure 4-7 Clearing the Fabric Log • Count: A cumulative count of entries within a known period. • Date/Time: The date and time of the log entry.
TIP: The same entries will go into both logs until the non-wrap log gets full. Once the non-wrap log gets full, the entries go into the wrap log. Once the wrap log is full, it will start to overwrite entries. If you need to look at a history of log entries, you should review both logs. The Embedded Port Frame Log provides: Figure 4-8 Defining Filtering Settings • Count: A cumulative count of entries within a known period. • Date/- Time: Time of the frame. • Port #: The port number.
Figure 4-9 Clearing Embedded Port Frame Log Entries Setting Embedded Port Frame Filtering ATTENTION! Before clearing logs, make sure the logs are not needed for troubleshooting. Once a log is cleared, the data cannot be retrieved. To clear the Embedded Frame Log, select Monitor and select the Logs tab and then select the Clear Log button. A message displays stating that the operation has been performed successfully. Viewing All Logs 4-12 Select Monitor on the navigation panel.
Figure 4-10 All Logs View The All Logs listing provides the ability to view (display) all of the content of the logs. Clearing All Log Entries ATTENTION! Before clearing information in all of the logs, make sure the logs are not needed for troubleshooting. Once the logs are cleared, the data cannot be retrieved. To clear all logs’ entries, select Monitor and select the Logs tab. Select the Clear All Logs button, next to the All Logs link.
Figure 4-11 Event Log The log displays 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 consists of the following columns: Session Log Product Status Log 4-14 • Date/Time - Date and time the event occurred. • Event - Event number and brief description of the event.
Figure 4-12 Product Status Log The log reflects the previous and current status of the switch, and indicates the instance of a Sphereon 4500 Element Manager application that should be opened to investigate a problem. The information is useful to maintenance personnel for fault isolation and repair verification. The log consists of the following columns: • Date/Time - Date and time the switch status change occurred. • Network Address - IP address or configured name of the switch.
Fabric Log Element Manager Logs To open the Fabric Log, select the option from the Monitor and Logs menus. The log reflects the time and nature of changes made to a managed fabric. This information is useful for system administrators and users. For a log description, refer to the SANavigator Software Release 4.0 User Manual (621-000013). To open a log from the Element Manager application, select the Logs menu at any view, then click (select) the desired log option.
The log consists of the following columns: • Date/Time - Date and time the event occurred. • Event - Three-digit code that describes the event. Event codes are listed and described in Appendix B: Event Code Tables on page B-1. • Description - Brief description of the event. • Severity - Severity of the event (Informational, Minor, Major, or Fatal). • FRU-Position - Acronym representing the FRU type, followed by a number representing the FRU chassis position.
The log displays a history of FRU removals and replacements (insertions) for the switch. The information is useful to maintenance personnel for fault isolation and repair verification. The log consists of the following columns: • Date/Time - Date and time the FRU was inserted or removed. • FRU - Acronym representing the FRU type. FRU acronyms are: — CTP - Control processor card. The CTP card is not a FRU. A failed CTP card requires replacement of the switch. — PWR - Power supply.
• Date/Time - Date and time the link incident occurred. • Port - Port number (0 through 23) that reported the link incident. • Link Incident - Brief description of the link incident. Problem descriptions include: — Implicit incident. — Bit-error threshold exceeded. — Link failure - loss of signal or loss of synchronization. — Link failure - not-operational primitive sequence (NOS) received. — Link failure - primitive sequence timeout.
Open Trunking Log Figure 4-17 • Date/Time - Date and time the alert occurred. • Name - Name for the alert as configured through the Configure Threshold Alerts dialog box. • Port - Port number where the alert occurred. • Type - Type of alert: transmit (Tx) or receive (Rx). • Utilization % - Percent usage of traffic capacity. This setting constitutes the threshold value and is configured through the Configure Threshold Alerts dialog box.
• Old Exit Port - The switch port number (decimal) used for transmitting Fibre Channel traffic before the re-route action. • New Exit Port - The switch port number (decimal) used for transmitting Fibre Channel traffic after the re-route action. Obtain Port Diagnostic Information Fibre Channel port diagnostic information can be obtained by: Port LEDs Table 4-1 Port State Online • Inspecting port LEDs at the switch front panel or emulated port LEDs at the management server’s Hardware View.
Table 4-1 Port State Port Operational States (continued) Blue/Green LED Alert Symbol Description Beaconing Off, On, or Blinking Blinking Yellow Triangle The port is beaconing. The amber port LED blinks once every two seconds to enable users to locate the port. Invalid Attachment On Off Yellow Triangle The port has an invalid attachment. The reason appears in the Reason field at the Port Properties dialog box. Link Incident Off Off Yellow Triangle A link incident occurred.
Port List Page Figure 4-18 When the SANpilot interface opens, the View panel appears as the default panel. At the View panel, select the Monitor option at the left side of the panel. The Monitor panel opens with the Port List page displayed (Figure 4-18). Monitor Panel (Port List Page) A row of information for each port (0 through 23 inclusive) appears. Each row consists of the following columns: • Port # - Switch port number. • Name - Port name of 24 alphanumeric characters or less.
• Type - Configured port type. Settings are: — Generic mixed port (GX_Port). This setting also configures a port as a generic loop port (GL_Port). — Fabric mixed port (FX_Port). This setting also configures a port as a fabric loop port (FL_Port). — Generic port (G_Port). — Fabric port (F_Port). — Expansion port (E_Port). Port Stats Page Figure 4-19 4-24 When the SANpilot interface opens, the View panel appears as the default panel.
Troubleshooting Tip for Port Statistics Parts of Statistics Tables Traffic Transmit and Receive Statistics As a general rule, you should clear all the counters by selecting Clear Port Stats or Clear All Port Stats after you have resolved a problem. When troubleshooting, keep track of the time interval when errors accumulate to judge the presence and severity of a problem. (There is a link recovery hierarchy implemented in Fibre Channel to handle some level of “expected anomalies”.
• Link utilization % Rx - The current link utilization for the port expressed as a percentage. On 1 Gbps links, ports can transmit or receive data at 100 MB per second. On 2 Gbps links, ports can transmit or receive data at 200 MB per second. Link utilization is calculated over one-second intervals. • Link utilization % Tx - The current link utilization for the port expressed as a percentage. On 1 Gbps links, ports can transmit or receive data at 100 MB per second.
Class 2 Statistics • CRC errors - A received frame failed a cyclic redundancy check (CRC) validation, indicating the frame arrived at the port corrupted. Frame corruption may be caused by device disconnection, an optical transceiver failure, a bad fiber-optic cable, or a poor cable connection. • Delimiter errors - The number of times that the switch detected an unrecognized start-of-frame (SOF), an unrecognized end-of-frame (EOF) delimiter, or an invalid class of service.
Class 3 Statistics Open Trunking Statistics Port Properties Page 4-28 The Class 3 Statistics include these transmit and receive values: • Received Frames - The number of Class 3 frames received by the F_Port from its attached N_Port. • Transmitted Frames - The number of Class 3 frames transmitted by this F_Port to its attached N_Port. • Discarded Frames - The number of Class 3 frames discarded (including multicast frames with bad Domain IDs).
Figure 4-20 View Panel (Port Properties Page) The Port Properties page displays information for one port. Values update only when the page opens for a selected port or the user selects Get Port Properties. The page defaults to port 0. Increment or decrement the port number displayed (0 through 23 inclusive) by clicking Fwd>> or <
Management Server Port List View 4-30 • Block Configuration - User-configured state for the port (Blocked or Unblocked). • Beaconing - User-specified for the port (On or Off). • FAN Configuration - User-configured state for fabric address notification (FAN) configuration (Enabled or Disabled). • Operational State - Port state (Online, Offline, Not Installed, Inactive, Invalid Attachment, Link Reset, No Light, Not Operational, Port Failure, Segmented E_Port, or Testing).
Figure 4-21 Port List View • Type - Port type (GX_Port, FX_Port, G_Port, F_Port, or E_Port). • Operating Speed - Operating speed (Not Established, 1 Gbps, or 2 Gbps). • Alert - If link incident (LIN) alerts are configured for the port through the Configure Ports dialog box, a yellow triangle appears in the column when a link incident occurs. A yellow triangle also appears if beaconing is enabled for the port. A red and yellow diamond appears if the port fails.
Performance View Figure 4-22 4-32 • Block or unblock the port. • Enable or disable port beaconing. • Perform port diagnostics. • Clear link incident alerts. • Reset the port. • Enable or disable port binding. • Clear threshold alerts. At the management server, click the Performance tab. The Performance View displays (Figure 4-22). The view provides statistical information about port performance that is useful to maintenance personnel for isolating port problems.
Each port bar graph in the upper portion of the view displays the instantaneous transmit or receive activity level for the port, and is updated every five seconds. The relative value displayed is the greater of either the transmit or receive activity (whichever value is greatest when sampled). Each port graph has 20 green-bar level indicators corresponding to 5% of the maximum throughput for the port (either transmit or receive). If any activity is detected for a port, at least one green bar appears.
• Class 3 statistics - These entries provide information about Class 3 traffic, including: — Class 3 frames received and transmitted. — Four-byte words received and transmitted. — Discarded frames. • Error statistics - The Performance View displays the following error statistics for the port: — Link failures - Link failures are recorded in response to an NOS, protocol timeout, or port failure.
— Delimiter errors - Received frames had frame delimiter errors, indicating the frame arrived at the switch port corrupted. Frame corruption may be caused by device disconnection, an optical transceiver failure at the device, a bad fiber-optic cable, or a poor cable connection. — Address ID errors - Received frames had unavailable or invalid Fibre Channel destination addresses, or invalid Fibre Channel source addresses. This typically indicates the destination device is unavailable.
Figure 4-23 Port Properties Dialog Box • Port WWN - Fibre Channel WWN for the port. • Block Configuration - User-configured state for the port (Blocked or Unblocked). • LIN Alerts Configuration - User-configured state for LIN alerts configuration (On or Off). • FAN Configuration - User-configured state for FAN configuration (Enabled or Disabled). • Beaconing - User-specified for the port (On or Off). When beaconing is enabled, a yellow triangle appears adjacent to the status field.
— Link failure - not-operational primitive sequence received. — Link failure - primitive sequence timeout. — Link failure - invalid primitive sequence received for current link state. Port Technology Dialog Box Figure 4-24 • Operational State - Port state (Online, Offline, Not Installed, Inactive, Invalid Attachment, Link Reset, No Light, Not Operational, Port Failure, Segmented E_Port, or Testing).
• Transceiver - Type of port transceiver (Shortwave Laser, Longwave Laser, Long Distance Laser, Unknown, or None). • Distance - Port transmission distance (Short, Intermediate, Long, Very Long, or Unknown). • Media - Type of optical cable used (Singlemode, multimode 50-micron, multimode 62.5-micron, or Unknown). • Speed - Operating speed (Not Established, 1 Gbps, or 2 Gbps). Perform Port Diagnostic Loopback Tests Port diagnostics consist of internal and external loopback tests.
3. Click the Port and Diagnostics tabs. The Port page displays with the Diagnostics tab selected (Figure 4-25). Figure 4-25 Operations Panel (Port Page with Diagnostics Tab) 4. Type the port number to be tested in the Targeted Port Number field. 5. At the Diagnostics Test list box, select the Internal Loopback option. 6. Click Start Port Diagnostics. The test begins and: a. The Start Port Diagnostics button changes to a Terminate Port Diagnostics button. b.
8. Reset the tested port: a. Click the Reset tab. The Port page displays with the Reset tab selected. b. For the tested port, click (enable) the check box in the Port Reset column. A check mark in the box indicates the port reset option is enabled. c. Click Activate at the bottom of the page. The port resets and the message Your changes have been successfully activated appears. 9. Notify the customer the test is complete and the attached device can be set online.
NOTE: Click Terminate Port Diagnostics at any time to abort the loopback test. 9. When the test completes, results appear as Passed or Failed in the message area of the dialog box. 10. Remove the loopback plug and reconnect the fiber-optic jumper cable from the device to the port (disconnected in step 2). 11. Reset the tested port: a. Click the Reset tab. The Port page displays with the Reset tab selected. b. For the tested port, click (enable) the check box in the Port Reset column.
Figure 4-26 Port Diagnostics Dialog Box 5. Type the port number to be tested or select all ports at the Port Select area of the dialog box. 6. At the Diagnostics Test list box, select the Internal Loop option. 7. Click Next. The message Press START TEST to begin diagnostics appears, and the Next button changes to a Start Test button. 8. Click Start Test. The test begins and: a. The Start Test button changes to a Stop Test button. b. The message Port xx: TEST RUNNING appears. c.
11. Reset the port: a. At the Hardware View, right-click the port graphic. A pop-up menu appears. b. Select the Reset Port option. A Message message box displays, indicating a link reset operation will occur. c. Click OK. The port resets. 12. Notify the customer the test is complete and the attached device can be set online. External Loopback Test (Management Server) To perform an external loopback at the management server (Sphereon 4500 Element Manager application): 1.
11. Click Start Test. The test begins and: a. The Start Test button changes to a Stop Test button. b. The message Port xx: TEST RUNNING appears. c. A red progress bar (indicating percent completion) travels from left to right across the Completion Status field. NOTE: Click Stop Test at any time to abort the loopback test. 12. When the test completes, results appear as Port xx: Passed! or Port xx: Failed! in the message area of the dialog box. 13.
Perform the maintenance data collection procedure after a firmware fault is corrected or a failed FRU is replaced to capture the data for analysis by support personnel. Maintenance data includes the dump file, hardware log, audit log, and an engineering log viewable only by support personnel. SANpilot Interface To collect maintenance data (retrieve the dump file from the CTP card) at the SANpilot interface: 1. When the SANpilot interface opens, the View panel and Switch page appear as the default.
Figure 4-28 Save As Dialog Box 5. Insert a blank diskette in the floppy drive of the browser PC. 6. At the Save As dialog box, select the floppy drive (A:\) from the Save in drop-down menu, type a descriptive name for the dump file in the File name field, and click Save. 7. A Download dialog box displays, showing the estimated time remaining to complete the download process. When the process finishes, the dialog box changes to a Download complete dialog box (Figure 4-29).
8. Click Close to close the dialog box. 9. Remove the diskette with the newly-collected maintenance data from the browser PC floppy drive. Return the diskette with the failed FRU to McDATA for failure analysis. Management Server To collect maintenance data (retrieve the dump file from the management server hard drive) from the Sphereon 4500 Element Manager application: 1. At the management server, open the SAN management application (SANavigator 4.0 or EFCM 8.0). 2.
5. 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. 6. The Data Collection dialog box (Figure 4-31) displays with a progress bar that shows percent completion of the data collection process. When the process reaches 100%, the Cancel button changes to a Close Button. Figure 4-31 Data Collection Dialog Box 7. Click Close to close the dialog box. 8.
NOTE: When the switch is set offline, the operation of attached Fibre Channel devices is disrupted. Do not set the switch offline unless directed to do so by a procedural step or the next level of support. Set Online State (SANpilot Interface) To set the switch online from the SANpilot interface: 1. When the SANpilot interface opens, the View panel and Switch page appear as the default. At the View panel, select the Operations option at the left side of the panel.
2. Click the Online State tab. The Switch page displays with the Online State tab selected (Figure 4-32 on page 4-49). 3. Click Set Offline. The switch goes offline and the message Your changes have been successfully activated appears. Set Online State (Management Server) To set the switch online from the management server (Sphereon 4500 Element Manager application): 1. At the management server, open the SAN management application (SANavigator 4.0 or EFCM 8.0). 2.
3. Select the Set Online State option from the Maintenance menu. The Set Online State dialog box displays (Figure 4-33 on page 4-50). 4. Click Set Offline. A warning dialog box displays the message Performing this operation will change the current state to Offline. 5. Click OK. As the switch goes offline, inspect the Hardware View. The State field of the Sphereon 4500 Status table displays Offline. Block or Unblock a Port This section describes procedures to block or unblock a switch Fibre Channel port.
2. Click the check box for the selected port in the Blocked column to block the port (default is unblocked). A check mark in the box indicates the port is blocked. 3. Click Activate at the bottom of the page to save and activate the blocked configuration. The message Your changes to the port configuration have been successfully activated appears. Unblock a Port (SANpilot Interface) To unblock a switch port from the SANpilot interface: 1.
6. Select the Block Port menu option. A Warning dialog box displays (Figure 4-35). Figure 4-35 Warning Dialog Box 7. Click OK. The dialog box closes and the following occur to indicate the port is blocked and offline: — The emulated green LED associated with the port extinguishes at the Hardware View. — The green LED associated with the port extinguishes at the switch. — A check mark displays in the check box adjacent to the Block Port menu option.
Figure 4-36 Warning Dialog Box 6. Click OK. The dialog box closes and the following occur to indicate the port is unblocked (and online): — The emulated green LED associated with the port illuminates at the Hardware View. — The green LED associated with the port illuminates at the switch. — The check box adjacent to the Block Port menu option becomes blank.
— Keep the air nozzle approximately 50 millimeters (two inches) from the end of the connector and hold the can upright. — Blow compressed air on the surfaces and end of the connector continuously for approximately five seconds. 3. Gently wipe the end-face and other surfaces of the connector with an alcohol pad as shown in part B of Figure 4-37 on page 4-54. Ensure the pad makes full contact with the surface to be cleaned. Wait approximately five seconds for cleaned surfaces to dry. 4.
— The green LED associated with the Ethernet port blinks momentarily while the port is tested. — The blue/green and amber LEDs associated with the ports blink momentarily while the ports are tested. 4. After successful POST completion, the green power (PWR) LED remains illuminated and all amber LEDs extinguish. 5. If a POST error or other malfunction occurs, go to MAP 0000: Start MAP on page 3-6 to isolate the problem. Power-Off Procedure To power off the switch: 1.
An IML and IPL are functionally equivalent. The operations do not cause power-on diagnostics to execute and are not disruptive to Fibre Channel traffic. Both operations: • Reload switch firmware from FLASH memory. • Reset the Ethernet LAN interface, causing the connection to the management server to drop momentarily until the connection automatically recovers.
Switch IPL To IPL the switch from the management server (Sphereon 4500 Element Manager application): 1. At the management server, open the SAN management application (SANavigator 4.0 or EFCM 8.0). 2. At the SAN management application’s physical map, right-click the product icon representing the switch requiring an IPL, then select Element Manager from the pop-up menu. The application opens. 3. Select the IPL option from the Maintenance menu. An Information dialog box displays (Figure 4-38).
— After holding the button for ten seconds, the ERR LED stops blinking, and all front panel LEDs illuminate. 2. Release the button to reset the switch. During the reset: — The green power (PWR) LED on the switch front panel illuminates. — The amber system error (ERR) LED on the switch front panel blinks momentarily while the switch is tested. — The green LED associated with the Ethernet port blinks momentarily while the port is tested.
Determine Switch Firmware Version Figure 4-39 To determine a switch firmware version from the SANpilot interface: 1. When the SANpilot interface opens, the View panel and Switch page appear as the default. At the View panel, click the Unit Properties tab. The Unit Properties page displays (Figure 4-39). View Panel (Unit Properties Page) 2. At the bottom of the page, record the firmware version listed in the Firmware Level field.
To add a switch firmware version to the browser PC hard drive (PC running the SANpilot interface): 1. Obtain the new firmware version from the McDATA File Center. At a PC with Internet access, open the File Center home page (Figure 4-40). The uniform resource locator (URL) is http://central.mcdata.com. Figure 4-40 McDATA File Center Home Page 2. Select (click) the Login option at the top of the home page. The Login page displays (Figure 4-41).
3. Type the user name and password (assigned and registered while performing Task 24: Register with the McDATA File Center on page 2-127) and click Login. The Welcome page displays. 4. Select (click) the Documents option at the top of the page. The Find Documents page displays (Figure 4-42). Figure 4-42 McDATA File Center (Find Documents Page) 5. Select (highlight) the ES 4500 Firmware option at the list box and click Search.
Figure 4-43 McDATA File Center (Documents Match Page) 6. Authorization to download a firmware version requires approval from the McDATA Solution Center. In the Action column adjacent to the desired firmware version, click Add to Request. The Current Request page displays (Figure 4-44). Figure 4-44 McDATA File Center (Current Request Page) 7. Click Submit Request. The Request Submitted page displays and the request for approval is e-mailed to the McDATA Solution Center.
Figure 4-45 McDATA File Center (Request History Page) 8. In the Action column adjacent to the approved request for the firmware version, click Download. The File Download dialog box displays (Figure 4-46). Figure 4-46 File Download Dialog Box 9. Select the Save this file to disk radio button and click OK. The Save As dialog box appears (Figure 4-47 on page 4-65).
Figure 4-47 Save As Dialog Box 10. At the Save As dialog box, ensure the correct directory path is specified at the Save in field, the correct file is specified in the File name field, and click Save. 11. A Download dialog box displays, showing the estimated time remaining to complete the download process. When the process finishes, the dialog box changes to a Download complete dialog box (Figure 4-48).
12. Click Close to close the dialog box. The new firmware version is downloaded and saved to the browser PC hard drive. 13. At the browser PC, close the Internet session. Download a Firmware Version to the Switch To download a firmware version to the switch from the SANpilot interface: NOTE: When downloading a firmware version, follow all procedural information contained in release notes or EC instructions that accompany the firmware version.
3. At the Download Firmware file from field: — Select the desired firmware file from the PC hard drive using the Browse button, or — Type the desired firmware filename in the Download Firmware file from field. 4. Click Send and Load Firmware. A browser-specific message box displays (Figure 4-50). Figure 4-50 Browser-Specific Message Box 5. Click OK to download the firmware version to the switch. The download process takes several minutes to complete, during which the browser is unavailable. 6.
8. After the switch IPL and SANpilot session logout, the following message box displays (Figure 4-52). Figure 4-52 Firmware Upgrade Complete Message Box 9. Click here to login to the switch and start a new SANpilot session. The Enter Network Password dialog box displays. 10. Type the default user name and password. NOTE: The default user name is Administrator and the default password is password. The user name and password are case-sensitive. 11. Click OK.
3. Select the Firmware Library option from the Maintenance menu. The Firmware Library dialog box displays (Figure 4-53). Figure 4-53 Firmware Library Dialog Box 4. The active firmware version displays at the lower left corner of the dialog box in XX.YY.ZZ format, where XX is the version level, YY is the release level, and ZZ is the patch level. 5. Click Close to close the dialog box.
Figure 4-54 McDATA File Center Home Page b. Select (click) the Login option at the top of the home page. The Login page displays (Figure 4-41 on page 4-61). c. Type the user name and password (assigned and registered while performing Task 24: Register with the McDATA File Center on page 2-127) and click Login. The Welcome page displays. d. Select (click) the Documents option at the top of the page. The Find Documents page displays (Figure 4-55).
e. Select (highlight) the ES 4500 Firmware option at the list box and click Search. The Documents Match page displays (Figure 4-56) with a list of firmware available for download. Figure 4-56 McDATA File Center (Documents Match Page) f. Authorization to download a firmware version requires approval from the McDATA Solution Center. In the Action column adjacent to the desired firmware version, click Add to Request. The Current Request page displays (Figure 4-57).
g. Click Submit Request. The Request Submitted page displays and the request for approval is e-mailed to the McDATA Solution Center. Wait five to ten minutes for a response from McDATA, then select (click) the My Requests option at the top of the page. The Request History page displays (Figure 4-58) with the approved request. Figure 4-58 McDATA File Center (Request History Page) h. In the Action column adjacent to the approved request for the firmware version, click Download.
i. Select the Save this file to disk radio button and click OK. The Save As dialog box appears (Figure 4-60). Figure 4-60 Save As Dialog Box j. At the Save As dialog box, ensure the correct directory path is specified at the Save in field, the correct file is specified in the File name field, and click Save. k. A Download dialog box displays, showing the estimated time remaining to complete the download process.
l. Click Close to close the dialog box. The new firmware version is downloaded and saved to the PC hard drive. m. At the PC, close the Internet session. n. Transfer the firmware version file from the PC to the rackmount management server by diskette, CD-ROM, or other electronic means. 2. At the management server, open the SAN management application (SANavigator 4.0 or EFCM 8.0). 3.
Figure 4-63 New Firmware Version Dialog Box 6. Select the desired firmware version file (downloaded in step 1) from the management server diskette drive or hard drive. Ensure the correct filename appears in the File name field and click Save. The New Firmware Description dialog box displays (Figure 4-64). Figure 4-64 New Firmware Description Dialog Box 7. Enter a description (up to 24 characters) for the new firmware version.
8. The File Transfer message box converts to a Transfer Complete message box, indicating the new firmware version is stored on the management server hard drive. Click Close to close the message box. 9. The new firmware version and associated description appear in the Firmware Library dialog box. Click Close to close the dialog box. 10. To send the firmware version to a switch, refer to Download a Firmware Version to a Switch below.
Figure 4-66 Firmware Library Dialog Box 6. Select (highlight) the firmware version to be downloaded and click Send. The send function verifies existence of certain switch conditions before the download process begins. If an error occurs, a message displays indicating the problem must be fixed before the firmware download. Conditions that terminate the process include: — The firmware version is being installed to the switch by another user. — The switch-to-management server link fails or times out.
7. Click Yes to download the firmware version. The Send Firmware dialog box displays (Figure 4-68). Figure 4-68 Send Firmware Dialog Box 8. The following occur during the download process: a. As the download begins, a Writing data to FLASH message displays at the top of the dialog box for a few moments. b. As the download progresses, a Sending Files message displays. This message remains as a progress bar travels across the dialog box to show percent completion of the download.
Manage Configuration Data The Sphereon 4500 Element Manager application provides options to back up and restore the configuration file stored in nonvolatile random-access memory (NV-RAM) on the switch CTP card. The switch must be set offline prior to restoring the configuration file. Configuration data in the file include: • Switch identification data. • Port configuration data. • Switch and fabric operating parameters. • Simple network management protocol (SNMP) configuration information.
Figure 4-69 Backup and Restore Configuration Dialog Box 4. Click Backup. An Information dialog box displays, indicating the backup operation was initiated (Figure 4-70). Figure 4-70 Information Dialog Box 5. Click OK to complete the backup operation and close the dialog box. Restore the Configuration To restore the switch configuration file from the management server using the Sphereon 4500 Element Manager application: 1. Notify the customer the switch is to be set offline.
5. Select the Backup & Restore Configuration option from the Maintenance menu. The Backup and Restore Configuration dialog box displays (Figure 4-71). Figure 4-71 Backup and Restore Configuration Dialog Box 6. Click Restore. A Warning dialog box displays, indicating the existing configuration file is to be overwritten (Figure 4-72). Figure 4-72 Warning Dialog Box 7. Click Yes. A Restore dialog box displays, indicating the restore operation is in progress (Figure 4-73).
Reset Configuration Data (SANpilot Interface) To reset switch data to the factory default settings from the SANpilot interface: NOTE: When switch configuration data is reset to factory default values, all optional features are disabled. 1. Notify the customer the switch is to be set offline. Ensure the customer’s system administrator quiesces Fibre Channel frame traffic through the switch and sets attached FC-AL devices offline. 2. Set the switch offline.
5. Click Reset Configuration. A browser-specific message box displays (Figure 4-75). Figure 4-75 Browser-Specific Message Box 6. Click OK to reset the configuration. The message Your changes have been successfully activated appears. 7. The switch IP address resets to the default address of 10.1.1.10. — If the configured IP address (prior to reset) was the same as the default address, the browser-to-switch Internet connection is not affected and the procedure is complete.
Reset Configuration Data (Management Server) To reset switch data to the factory default settings from the management server (Sphereon 4500 Element Manager application): NOTE: When switch configuration data is reset to factory default values, all optional features are disabled. 1. Notify the customer the switch is to be set offline. Ensure the customer’s system administrator quiesces Fibre Channel frame traffic through the switch and sets attached FC-AL devices offline. 2.
— If the configured IP address (prior to reset) was not the same as the default address, the switch-to-management server Ethernet link drops and server communication is lost. Continue to the next step. 8. To change the switch IP address and restart the management server session, go to step 10. 9. To restart a management server session using the default IP address of 10.1.1.10: a. Close the Sphereon 4500 Element Manager application and return to the SAN management application. b.
d. Select (highlight) the entry representing the reset switch in the Available Addresses window and click Change. The Domain Information dialog box displays (Figure 4-78). Figure 4-78 Domain Information 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. Switch-tomanagement server communication is restored and the procedure is complete. 10.
e. Identify the switch to the SAN management application. For instructions, refer to Task 13: Configure the Switch to the Management Application on page 2-76. f. Switch-to-management server communication is restored and the procedure is complete. Install or Upgrade Software This section describes the procedure to install or upgrade the SAN management application at the management server. The application includes the Sphereon 4500 Element Manager application.
Figure 4-79 McDATA File Center Home Page b. Select (click) the Login option at the top of the home page. The Login page displays (Figure 4-41 on page 4-61). c. Type the user name and password (assigned and registered while performing Task 24: Register with the McDATA File Center on page 2-127) and click Login. The Welcome page displays. d. Select (click) the Documents option at the top of the page. The Find Documents page displays (Figure 4-80).
e. Select (highlight) the EFCM Software option at the list box and click Search. The Documents Match page displays (Figure 4-81) with a list of software available for download. Figure 4-81 McDATA File Center (Documents Match Page) f. Authorization to download a software version requires approval from the McDATA Solution Center. In the Action column adjacent to the desired software version, click Add to Request. The Current Request page displays (Figure 4-82).
g. Click Submit Request. The Request Submitted page displays and the request for approval is e-mailed to the McDATA Solution Center. Wait five to ten minutes for a response from McDATA, then select (click) the My Requests option at the top of the page. The Request History page displays (Figure 4-83) with the approved request. Figure 4-83 McDATA File Center (Request History Page) h. In the Action column adjacent to the approved request for the software version, click Download.
i. Select the Save this file to disk radio button and click OK. The Save As dialog box appears (Figure 4-85). Figure 4-85 Save As Dialog Box j. At the Save As dialog box, ensure the correct directory path is specified at the Save in field, the correct file is specified in the File name field, and click Save. k. A Download dialog box displays, showing the estimated time remaining to complete the download process.
l. Click Close to close the dialog box. The new firmware version is downloaded and saved to the PC hard drive. m. At the PC, close the Internet session. n. Transfer the firmware version file from the PC to the rackmount management server by diskette, CD-ROM, or other electronic means. o. Go to step 5. 4. Insert the EFC Management Applications CD-ROM into the CD-ROM drive of the management server. 5.
Figure 4-88 McDATA EFC Management Applications Dialog Box 8. Follow the online instructions for the InstallAnywhere program. Click Next, Install, or Done as appropriate. 9. Power off and reboot the rack-mount management server. a. At the Windows 2000 desktop, click Start at the left side of the task bar (bottom of the desktop), then select Shut Down. The Shut Down Windows dialog box displays. b. Select the Restart option from the list box and click OK. The management server powers down and restarts.
e. Click the Send Ctrl-Alt-Del button at the top of the window to log on to the management server desktop. The Log On to Windows dialog box displays. NOTE: Do not simultaneously press the Ctrl, Alt, and Delete keys. This action logs the user on to the browser-capable PC, not the rack-mount management server. f. Type the default Windows 2000 user name and password and click OK. The management server’s Windows 2000 desktop opens and the SANavigator Log In or EFCM Log In dialog box displays (Figure 4-89).
5 FRU Removal and Replacement This chapter describes removal and replacement procedures (RRPs) used by authorized service representatives for all Sphereon 4500 Fabric Switch field-replaceable units (FRUs). Do not remove a switch FRU until a failure is isolated to that FRU. If fault isolation was not performed, refer to MAP 0000: Start MAP on page 3-6. Procedural Notes The following procedural notes are referenced in applicable removal and replacement procedures.
Remove and Replace FRUs This section describes procedures to remove and replace concurrent switch FRUs, along with tools required to perform each procedure. Concurrent FRUs are removed and replaced while the switch is powered on and operational. Refer to Chapter 6, Illustrated Parts Breakdown for FRU locations and part numbers. Table 5-1 lists concurrent FRUs that are removed and replaced while the switch is powered on and operational.
— If the switch is installed in a McDATA FC-512 Fabricenter equipment cabinet, insert the 5/16-inch 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. — If the switch is installed in a customer-supplied equipment cabinet, unlock and open the cabinet front door as directed by the customer representative. 3. Identify the defective port transceiver from: — The illuminated amber LED adjacent to the port.
Figure 5-1 SFP Optical Transceiver Removal and Replacement 7. Perform one of the following to inspect the Event Log: — If at a web browser connected to the SANpilot interface, click the Log tab at the Monitor panel. The Event Log displays. An event code 513 (SFP optics hot-removal completed) appears. — If at the management server, open the Hardware View, click Logs, and select Event Log. The Event Log displays. An event code 513 (SFP optics hot-removal completed) appears.
c. Insert the keyed LC cable connector into the port’s optical transceiver. 5. Ensure the amber LED adjacent to the port transceiver is extinguished. If the amber LED is illuminated, go to MAP 0000: Start MAP on page 3-6 to isolate the problem. 6. Perform one of the following to inspect the Event Log: — If at a web browser connected to the SANpilot interface, click the Log tab at the Monitor panel. The Event Log displays. Ensure an event code 510 (SFP optics hot-insertion initiated) appears.
d. If a problem is indicated, go to MAP 0000: Start MAP on page 3-6 to isolate the problem. 8. Restore communication to the port with the replacement transceiver as directed by the customer. Refer to Block or Unblock a Port on page 4-51 for instructions. Inform the customer the port is available. 9. Perform one of the following to clear the system error (ERR) LED on the switch front bezel: — If at a web browser connected to the SANpilot interface: a. Click the Switch tab at the Operations panel.
— If the switch is installed in a customer-supplied equipment cabinet, unlock and open the cabinet front door as directed by the customer representative. 2. Identify the defective power supply from: — The illuminated amber LED on the FRU. — At the SANpilot interface, failure information associated with the power supply at the FRU Properties page of the View panel.
b. Use the finger handles to pull the power supply out of the switch chassis as shown in part (B) of Figure 5-2 on page 5-7. Support the power supply as it is pulled from the chassis. 5. Perform one of the following to inspect the Event Log. Note that multiple events appear because the power supply contains three internal cooling fans. — If at a web browser connected to the SANpilot interface, click the Log tab at the Monitor panel. The Event Log displays.
a. While supporting the power supply with one hand, insert it into the switch chassis. b. Firmly push the power supply into the chassis. Rotate the finger handles 90 degrees inward to seat the power supply and engage the connector pins. Ensure the faceplate is flush with the chassis cutout. 4. Connect the AC power cord to the power supply and to a facility power source. 5. Wait several seconds, then inspect the power supply to ensure the amber LED is extinguished.
7. Perform one of the following to verify power supply operation: — If at a web browser connected to the SANpilot interface, open the Switch tab at the View panel and ensure no amber LEDs illuminate that indicate a power supply failure. If a problem is indicated, go to MAP 0000: Start MAP on page 3-6 to isolate the problem. — If at the management server, open the Hardware View and observe the power supply graphic to ensure no alert symbols appear that indicate a failure (yellow triangle or red diamond).
6 Illustrated Parts Breakdown This chapter provides an illustrated parts breakdown for Sphereon 4500 Fabric Switch field-replaceable units (FRUs). Exploded-view assembly drawings are provided for: • Front-accessible FRUs. • Rear-accessible FRUs. • Miscellaneous parts. • Power cords and receptacles. Exploded-view illustrations portray the switch disassembly sequence for clarity. Illustrated FRUs are numerically keyed to associated tabular parts lists.
Front-Accessible FRUs Figure 6-1 illustrates front-accessible FRUs. Table 6-1 is the associated FRU parts list. The table includes reference numbers to Figure 6-1, FRU part numbers, descriptions, and quantities. Figure 6-1 Table 6-1 Ref. 6-2 Front-Accessible FRUs Front-Accessible FRU Parts List Part Number Description Qty. 6-1 002-002579-002 Switch, Sphereon 4500, base assembly -1 803-000054-395 Transceiver, optical, SFP, shortwave laser, LC connector, 1.
Rear-Accessible FRUs Figure 6-2 illustrates rear-accessible FRUs. Table 6-2 is the associated FRU parts list. The table includes reference numbers to Figure 6-2, FRU part numbers, descriptions, and quantities. Figure 6-2 Table 6-2 Ref. Rear-Accessible FRUs Rear-Accessible FRU Parts List Part Number Description Qty. 6-1 002-002579-002 Switch, Sphereon 4500, base assembly Reference -1 721-000072-201 Power supply assembly, 70-watt rated, 3.
Miscellaneous Parts Figure 6-3 illustrates miscellaneous parts. Table 6-3 is the associated parts list. The table includes reference numbers to Figure 6-3, part numbers, descriptions, and quantities. 2 1 Figure 6-3 Table 6-3 Ref. 6-4 3 Miscellaneous Parts Miscellaneous Parts List Part Number Description Qty.
Power Cords and Receptacles Figure 6-4 illustrates optional power cords and receptacles. Table 6-4 on page 6-6 is the associated parts list. The table includes reference numbers to Figure 6-4, feature numbers, and descriptions.
Table 6-4 Ref. 6-6 Power Cord and Receptacle List Part Number Description Feature -1 806-000001-000 Power cord, AC, North America NEMA 5-15P straight, 125 volts, 10 amps, 3.0 meters Receptacle: NEMA 5-15R 1010 -2 806-000004-001 Power cord, AC, United Kingdom BS 1363 right angle, 250 volts, 10 amps, 2.8 meters Receptacle: BS 1363 1012 -3 806-000005-001 Power cord, AC, European Community CEE 7/7 straight, 250 volts, 10 amps, 2.
Table 6-4 Ref. Power Cord and Receptacle List (Continued) Part Number Description Feature -12 806-000040-000 Power cord, AC, United States (Chicago) NEMA L6-15P straight, twist-lock, 250 volts, 10 amps, 1.8 meters Receptacle: NEMA L6-15R 1028 -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 1016 -14 806-000042-000 Power cord, AC, North America NEMA L6-15P straight, twist-lock, 250 volts, 10 amps, 2.
6-8 McDATA Sphereon 4500 Fabric Switch Installation and Service Manual
A Messages This appendix lists information and error messages that appear in pop-up message boxes at the Sphereon 4500 Element Manager application. Sphereon 4500 Element Manager Messages This section lists Sphereon 4500 Element Manager information and error messages in alphabetical order. A Message Description Action Message Description Action A preferred path already exists between this Source Port and this Destination Domain ID. Please reconfigure the desired path.
Message Description Action Message Description Action Message Description Action Message Description All address configurations must be saved with unique names. Save the configuration with a different name that is unique to all saved configurations. All port names must be unique. A duplicate port name was entered. Every configured port name must be unique. Reconfigure the port with a unique name. Another Element Manager is currently performing a firmware install.
C Message Descripton Action Message Description Action Message Description Action Cannot change port type while Management Style if FICON, without SANtegrity Feature. Please contact your sales representative. Firmware level is below 6.0 and user attempted to change a port type in the Configure Ports dialog box while FICON management style is enabled, but the optional SANtegrity Binding feature is not installed. Informational message. If the firmware is below 6.
Message Description Action Message Description Message occurs when selecting Enable Beaconing for a failed FRU. Replace the FRU and enable beaconing or enable beaconing on an operating FRU. Cannot enable beaconing while the system error light is on. Beaconing cannot be enabled while the system error LED is illuminated. Action Select Clear System Error Light from the Products menu to clear the error light, then enable beaconing.
Message Description Action Message Description Action Message Cannot have spaces in field. Spaces are not allowed as part of the entry for this field. Delete spaces from the field entry. Cannot install firmware to a switch with a failed CTP card. Firmware cannot be installed on a switch with a failed CTP card. The CTP card failed and is not a FRU. Replace the switch. Cannot perform this operation while the switch is offline.
Action Message Description Action Message Description Action Message Description Action Message Cannot retrieve port configuration. The port configuration cannot be retrieved. The link is down or busy. Retry the operation later. If the condition persists, contact support personnel and report the problem. Cannot retrieve port information. Port information cannot be retrieved. The link is down or busy. Retry the operation later. If the condition persists, contact support personnel and report the problem.
Message Description Cannot run diagnostics on a port that is failed. Port diagnostics cannot be performed on a failed port. Action Run diagnostics only on an operational port. Message Cannot run diagnostics on an active E_Port. Description Action Message Description Action Message Port diagnostics cannot be performed on a configured and active expansion port (E_Port). Run diagnostics only on an inactive E-port. Cannot run diagnostics. The port is not installed.
Action Ensure all port transceivers support 1.0625 Gigabit per second (Gbps) data transmission. Message Cannot set all ports to 2 Gbps due to port speed restriction on some ports. Description This message displays if all ports are set to 2 Gb/sec through the Configure Ports dialog box and some port transceivers do not support this transceiver speed. Action Ensure all port transceivers support 2.125 Gbps data transmission.
Message Description Action Message Description Action Message Description Action Message Description Action Message Cannot set write authorization without defining a community name. A community name was not defined in the Configure SNMP dialog box for the write authorization selected. Enter a community name in the name field where write authorization is checked. Cannot start data collection. Data collection cannot be started. The link is down or busy. Retry the operation later.
Message Description Action Message Description Action Message Description Action Message Description Action Message Description Action A-10 Could not export log to file. A log file I/O error occurred and the file could not be saved to the specified destination. The disk may be full or write protected. If the disk is full, use another disk. If the disk is write protected, change the write-protect properties or use another disk. Could not find firmware file.
D Message Description Action Message Description Action Message Description Action Date entered is invalid. The date is entered incorrectly. Verify the number of days in the month entry is valid. Device applications should be terminated before starting diagnostics. Press NEXT to continue. A device application is not terminated. Terminate the device application before running port diagnostics. [device WWN] cannot be removed from the switch membership list while participating in switch binding.
Action Message Description Action Message Description Action Message Description Action Disable Enterprise Fabric Mode at the Enterprise Fabric Mode dialog box before disabling switch binding. Do you want to continue with IPL? Message requesting confirmation to proceed with an IPL. Click Yes to confirm the IPL or Cancel to end the operation. Duplicate community names require identical write authorizations. Duplicate community names exist that have conflicting or different write authorizations.
Message Description Action Message Description Action Message Description Action Message Description Action Message Description Action Element Manager instance is currently open. An instance of the Element Manager application is already open. Information message - no action required. Enterprise Fabric Mode will be disabled if any of the following parameters are disabled: Insistent Domain ID, Rerouting Delay, Domain RSCN’s.
Message Description Action Error transferring files < message >. An error occurred while transferring files from the PC hard drive to the Element Manager application. The message varies, depending on the problem. Retry the operation. If the condition persists, contact support personnel and report the problem. F Message Description Action Message Description Action Message Description Action Message Description Action Message Description Action A-14 Feature not supported.
Message Description Action Message Description Action Message Description Action Firmware download timed out. The switch did not respond in the time allowed, causing the firmware download to time out. Retry the operation. If the condition persists, contact support personnel and report the problem. Firmware file I/O error. A firmware file I/O error occurred. Retry the operation. If the condition persists, contact support personnel and report the problem. Firmware file not found.
Message Internal file transfer error received from switch. Description The switch detected an internal file transfer error. Action Message Description Action Message Invalid character in field. An invalid character was entered in the data field. Remove invalid characters from the entry. Invalid configuration name. Description A user attempted to save an invalid address configuration name.
Message Description Action Message Description Action Message Description Action Message Description Action Message Description Action Message Description Invalid port number. Valid ports are (0-< nn >). You have specified an invalid port number. Specify a valid port number, in the range 0 to the maximum number of ports on the product minus one. For example, for a switch with 24 ports, the valid port range is 0 to 23. Invalid response received from switch.
Action Enter a value from 1 to 99 into the Low BB Credit Threshold of the Configure Open Trunking dialog box. Message Description Action Message Description Action Message Description Action Message The Day value must be an integer from 1 through 31. Enter a Day value from 1 through 31. Invalid value for E_D_TOV. The value for E_D_TOV must be an integer from 2 through 600 milliseconds. Enter an E_D_TOV value from 2 through 600. Invalid value for hour (0 - 23).
Message Description Action Message Description Action Message Description Action Message Description Action Message Invalid value for R_A_TOV. The value for R_A_TOV must be an integer from 10 through 1200 milliseconds. Enter an R_A_TOV value from 10 through 1200. Invalid value for second (0 - 59). The Second value must be an integer from 0 through 59. Enter a Second value from 0 through 59. Invalid value for Threshold (1 - 99%).
L Message Description Action Message Description Action Message Link dropped. The switch-to-management server link was dropped. Wait approximately 30 seconds for the link to establish and retry the operation. If the condition persists, contact support personnel. Log is currently in use. The selected log is in use by another Element Manager instance. Retry the operation. If the condition persists, contact support personnel and report the problem.
N Message Description Action Message Description Action Message Description Action Message Description Action Message Description Action Message Description Action Nickname already exists. Please use a different nickname. The entered nickname already exists. Specify a unique nickname. No backup configuration available to restore. A backup of the configuration is not on the management server hard drive. A configuration restore cannot be completed.
Message Not all of the optical transceivers are installed for this range of ports. Description One or more ports in the specified port range do not have optical transceivers installed. Action Specify a port range valid for ports installed. P Message Description Action Message Description Action Message Description Action Message Description Action Message A-22 Performing this operation will change the current state to offline. This operation causes the switch to go offline.
Description Action Message Description Action Message Description A user disabled port binding for attached devices, but one or more of the devices is controlled by fabric binding. Review the switch binding membership list to determine if devices should or should not be included. Port diagnostics cannot be performed on an inactive port. This message displays when port diagnostics are performed on an inactive port. Perform diagnostics on an active port.
Message Description Action Resource is unavailable. The specified operation cannot be performed because the switch is unavailable. Verify the switch-to-management server link is operational. If the link is up, the management server may be busy. Try the operation later. S Message Description Action Message Description Action Message Description Action Message Description Action Message A-24 Send firmware failed. A send firmware operation failed. Retry the operation.
Description Action Message Description Action Device WWNs were removed from the switch membership list (SANtegrity binding feature), but one or more of the devices still has security controlled by port binding. Verify the security level for each device is specified as required by reviewing the Bound WWN list at the Configure Ports dialog box. System diagnostics cannot run. The operational status is invalid. System diagnostics cannot run on a switch with failed ports. Replace failed port transceivers.
Message The management server is busy processing a request from another Element Manager. Description The management server could not process the current request because it is busy handling a request from another Element Manager instance. Action Message Description Action Message Description Action Message Description Action Message Description Action Message Description A-26 Retry the operation later. If the condition persists, contact support personnel and report the problem.
Action Check the Ethernet connection. If the condition persists, contact support personnel and report the problem. Message The maximum number of address configurations has been reached. Description The maximum number of address configurations that can be saved to the management server was reached.
Message Description Action Message Description Action Message A configuration change was attempted that requires the switch to be set offline. Set the switch offline and retry the configuration change. This feature has not been installed. Please contact your sales representative. A user selected an option that is unavailable because a necessary feature is not installed. Contact your sales representative to obtain and install the desired optional feature.
U Message Description Action Message Description Action Unable to change incompatible firmware release. The firmware you are trying to download cannot be used for this Element Manager application release. Download compatible firmware for this Element Manager application release. Unable to save data collection file to destination. Could not save data collection file to the specified drive. Retry the operation later. If the condition persists, contact support personnel and report the problem.
A-30 McDATA Sphereon 4500 Fabric Switch Installation and Service Manual
B Event Code Tables An event is an occurrence (state change, problem detection, or problem correction) that requires user attention or that should be reported to a system administrator or service representative. An event usually indicates a switch operational state transition, but may also indicate an impending state change (threshold violation). An event may also provide information only, and not indicate an operational state change. Events are reported as event codes.
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: — 0 - informational. — 2 - minor. — 3 - major. — 4 - severe (not operational). • Explanation - a complete explanation of what caused the event. • Action - the recommended course of action (if any) to resolve the problem.
Event Code: 021 Message: Name Server database invalid. Severity: Minor. Explanation: Following an IML or firmware download, the Name Server database failed its CRC validation. All fabric services databases initialize 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 Data: No supplementary data included with the event.
Event Code: 051 Message: Management Server database invalid. Severity: Minor. Explanation: Following an IML or firmware download, the Management Server database failed its CRC validation. All management services databases initialize to an empty state, resulting in an implicit logout of all devices logged in to the Management Server. Action: Perform the data collection procedure and return the CD to McDATA support personnel. Event Data: No supplementary data included with the event.
Event Code: 052 Message: Management Server internal error, asynchronous status report activation, or mode register update occurred. Severity: Informational. Explanation: An internal operating error was detected by the Management Server subsystem, an asynchronous status was reported to an attached host, or a mode register update occurred. Action: Management Server internal error: Perform the data collection procedure and return the CD to McDATA support personnel.
Event Code: 061 Message: Fabric Controller database invalid. Severity: Minor. Explanation: Following an IML or firmware download, the fabric controller database failed its CRC validation. All fabric controller databases initialize to an empty state, resulting in a momentary loss of interswitch communication. Action: Perform the data collection procedure and return the CD to McDATA support personnel. Event Data: No supplementary data included with the event.
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 switch. SAN management application Version 3.2 and earlier supports up to 32 ISLs. SAN management application Version 3.3 and later supports up to 128 ISLs. Action: Reduce the ISLs on the indicated fabric element to a number within the limits specified.
Event Code: 070 Message: E_Port is segmented. Severity: Informational. Explanation: A switch E_Port recognized an incompatibility with the attached fabric director or switch, preventing the switch from participating in the fabric. A segmented port does not transmit Class 2 or Class 3 traffic, but transmits Class F traffic. Refer to the event data for the segmentation reason. Action: Action depends on the segmentation reason specified in the event data.
Event Code: 071 Message: Switch is isolated. Severity: Informational. Explanation: The switch 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. Action: Action depends on the segmentation reason specified in the event data. Event Data: The first byte of event data (byte 0) specifies the E_Port number.
Event Code: 072 Message: E_Port connected to unsupported switch. Severity: Informational. Explanation: The switch is attached (through an ISL) to an incompatible fabric element (director or switch). Action: Disconnect the ISL. Event Data: No supplementary data included with the event. Distribution: Switch SANpilot Event Log System Error LED ✔ Management Server Event Log E-Mail Host Call-Home Sense Info Link Incident ✔ Event Code: 073 Message: Fabric initialization error.
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. Action: Perform the data collection procedure and return the CD to McDATA support personnel.
Event Code: 081 Message: Invalid attachment. Severity: Informational. Explanation: A switch port recognized an incompatibility with the attached fabric element or device and isolated the port. An isolated port does not transmit Class 2, Class 3, or Class F traffic. Refer to the event data for the reason. Action: Action depends on the reason specified in the event data. Event Data: The first byte of event data (byte 0) specifies the port number.
Event Code: 081 (continued) Event Data (continued): C = ESA security mismatch - Processing of the Exchange Security Attribute (ESA) frame detected a security feature mismatch. The switch binding parameters for this switch and the attached fabric element must agree. At the Switch Binding - State Change dialog boxes, ensure the parameters for both fabric elements are compatible, or disable the fabric and switch binding features.
Event Code: 120 Message: Error detected while processing system management command. Severity: Informational. Explanation: This event occurs when the switch receives a management command that violates specified boundary conditions, typically as a result of a network error. The switch rejects the command, drops the switch-to-server Ethernet link, and forces error recovery processing. When the link recovers, the command can be retried. Action: No action is required for an isolated event.
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 Data: Byte 0 = Port number reporting congestion.
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: 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: 150 (continued) Event Data (continued): Bytes 12 - 15 of the event data specify error codes as follows: 01 = Completion fail. 03 = Zone merge error - too many zones. 04 = Zone merge error - incompatible zones. 05 = Zone merge error - too long if reason = 0A. 06 = Zone set definition too long. 07 = Zone set name too short or not authorized. 08 = Invalid number of zones. 09 = Zone merge error - default zone states incompatible if reason = 0A. 0A = Invalid protocol.
Event Code: 151 Message: Fabric configuration failure. Severity: Informational. Explanation: A fabric-wide configuration activation process failed. An event code 151 is recorded only by the managing switch in the fabric. The event code is intended to help engineering support personnel fault isolate a fabric-wide configuration failures. Action: Perform the data collection procedure and return the CD to McDATA support personnel.
Power Supply Events (200 through 299) Event Code: 200 Message: Power supply AC voltage failure. Severity: Major. Explanation: AC input to the power supply is disconnected or AC circuitry in the power supply failed. The event only occurs when two power supplies are installed. The second power supply assumes the full operating load for the switch. Action: Ensure the power supply is connected to facility AC power and verify operation of the facility power source.
Event Code: 203 Message: Power supply AC voltage recovery. Severity: Informational. Explanation: AC voltage recovered for the power supply. Both power supplies adjust to share operating load for the switch. Action: No action required. Event Data: No supplementary data included with the event. Distribution: Switch SANpilot Event Log System Error LED Management Server Event Log ✔ E-Mail Host Call-Home Sense Info Link Incident ✔ Event Code: 204 Message: Power supply DC voltage recovery.
Event Code: 206 Message: Power supply removed. Severity: Informational. Explanation: A power supply was removed while the switch was powered on and operational. The second power supply assumes the full operating load for the switch. Action: No action required or install an operational power supply. Event Data: No supplementary data included with the event.
Fan Events (300 through 399) Event Code: 300 Message: Cooling fan propeller failed. Severity: Major. Explanation: One cooling fan (out of six) failed or is rotating at insufficient angular velocity. The remaining fans are operational. The amber LED illuminates at the rear of the power supply assembly associated with the failed fan. Action: Replace the power supply assembly containing the indicated fan module.
Event Code: 302 Message: Cooling fan propeller failed. Severity: Major. Explanation: Three cooling fans (out of six) failed or are rotating at insufficient angular velocity. The remaining fans are operational. The amber LED illuminates at the rear of the power supply assembly (or assemblies) associated with the failed fans. Action: Replace the power supply assembly (or assemblies) containing the indicated fan modules.
Event Code: 304 Message: Cooling fan propeller failed. Severity: Major. Explanation: Five cooling fans (out of six) failed or are rotating at insufficient angular velocity. The remaining fan is operational. The amber LED illuminates at the rear of both power supply assemblies. Action: Replace both power supply assemblies. Event Data: The first byte of event data (byte 0) specifies the failed fan numbers (0 through 5 inclusive).
Event Code: 310 Message: Cooling fan propeller recovered. Severity: Informational. Explanation: One cooling fan (out of six) recovered or the associated power supply assembly was replaced. All fans are operational. Action: No action required. Event Data: The first byte of event data (byte 0) specifies the recovered fan number (0 through 5 inclusive).
Event Code: 312 Message: Cooling fan propeller recovered. Severity: Informational. Explanation: Three cooling fans (out of six) recovered or the associated power supply assembly (or assemblies) were replaced. All fans are operational. Action: No action required. Event Data: The first byte of event data (byte 0) specifies the recovered fan numbers (0 through 5 inclusive).
Event Code: 314 Message: Cooling fan propeller recovered. Severity: Informational. Explanation: Five cooling fans (out of six) recovered or both power supply assemblies were replaced. All fans are operational. Action: No action required. Event Data: The first byte of event data (byte 0) specifies the recovered fan numbers (0 through 5 inclusive).
CTP Card Events (400 through 499) Event Code: 400 Message: Power-up diagnostics failure. Severity: Major. Explanation: Power-on self tests (POSTs) detected a failed FRU as indicated by the event data. Action: If a CTP card failure is indicated, replace the switch. If a fan or power supply failure is indicated, replace the power supply assembly. Perform the data collection procedure and return the CD and faulty FRU to McDATA support personnel.
Event Code: 411 Message: Firmware fault. Severity: Major. Explanation: Switch firmware encountered an unexpected condition and dumped operating state information to FLASH memory for retrieval and analysis. The dump file automatically transfers from the switch to the management server, where it is stored for later retrieval through the data collection procedure. The switch performs a software reset, during which all attached Fibre Channel devices are momentarily disrupted, log out, and log back in.
Event Code: 421 Message: Firmware download complete. Severity: Informational. Explanation: A new firmware version was downloaded to the switch from the management server or SANpilot interface. Event data contains the ASCII firmware version in hexadecimal format xx.yy.zz.bbbb. Action: No action required. Event Data: Bytes 0 and 1 = release level (xx). Byte 2 = always a period. Bytes 3 and 4 = maintenance level (yy). Byte 5 = always a period.
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 Data: Byte 0 of the event data (equal to 5, 10, 15, or 20) is recorded.
Event Code: 440 Message: Embedded port hardware failed. Severity: Major. Explanation: The embedded port hardware detected a fatal error. Action: Replace the switch. Event Data: Byte 0 = CTP slot position (00). Byte 1 = engineering reason code Bytes 4 - 7 = elapsed millisecond tick count.
Event Code: 445 Message: ASIC detected a system anomaly. Severity: Informational. Explanation: The application-specific integrated chip (ASIC) detected a deviation in the normal operating mode or operating status of the switch. Action: No action required. An additional event code is generated if this incident exceeds an error threshold that results in a system event. Event Data: Byte 0 = embedded port number. Byte 1 = anomaly reason code. Bytes 4 - 7 = elapsed millisecond tick count.
Port Events (500 through 599) Event Code: 506 Message: Fibre Channel port failure. Severity: Major. Explanation: A Fibre channel port failed. The amber LED corresponding to the port illuminates to indicate the failure. Other ports remain operational if their LEDs are extinguished. Action: Perform the data collection procedure and return the CD to McDATA support personnel. Perform a switch reset. If the problem persists, replace the switch. Event Data: Byte 0 = port number (00 - 23).
Event Code: 508 Message: Fibre Channel port anomaly detected. Severity: Informational. Explanation: The switch detected a deviation in the normal operating mode or status of the indicated Fibre Channel port. Action: No action required. An event code 506 is generated if this anomaly results in a hard port failure. Event Data: Byte 0 = port number (00 - 23). Byte 1 = anomaly reason code. Bytes 4 - 7 = elapsed millisecond tick count. Bytes 8 and 9 = high-availability error callout #1.
Event Code: 512 Message: SFP optical transceiver nonfatal error. Severity: Minor. Explanation: Switch firmware detected an SFP optical transceiver non-fatal error. Action: Replace the failed transceiver with a functional transceiver of the same type. Event Data: Byte 0 = port number (00 - 23). Byte 1 = engineering reason code. Bytes 4 - 7 = elapsed millisecond tick count.
Event Code: 514 Message: SFP optical transceiver failure. Severity: Major. Explanation: An SFP 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 (00 - 23). Byte 1 = engineering reason code. Bytes 4 - 7 = elapsed millisecond tick count.
Event Code: 524 Message: No AL_PA acquired. Severity: Informational. Explanation: Switch cannot allocate an AL_PA of 0 (loop master) for an FC-AL device during loop initialization. The device cannot participate in loop operation. Action: Disconnect the FC-AL device that is loop master. Event Data: Byte 0 = port number (00 - 23).
Event Code: 581 Message: Implicit incident. Severity: Major. Explanation: An attached open systems interconnection (OSI) 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). If fault isolation at the server does not detect a failure, the problem may be due to a port failure.
Event Code: 583 Message: Loss of signal or loss of synchronization. Severity: Major. Explanation: An attached OSI 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).
Event Code: 585 Message: Primitive sequence timeout. Severity: Major. Explanation: An attached OSI 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).
Thermal Sensor Events (800 through 899) Event Code: 810 Message: High temperature warning (CTP card thermal sensor). Severity: Major. Explanation: The thermal sensor associated with the CTP2 card indicates the warm temperature threshold was reached or exceeded. Action: Perform the data collection procedure and return the CD to McDATA support personnel. Perform a switch reset. If the problem persists, replace the switch. Event Data: No supplementary data included with the event.
B-44 McDATA Sphereon 4500 Fabric Switch Installation and Service Manual
C Restore Management Server The procedure in this appendix provides information to restore the rack-mount 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 (SANavigator 4.0 or EFCM 8.0) and Sphereon 4500 Element Manager application. • SAN management data directory.
• 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, simple network management protocol (SNMP) trap recipients, E-mail recipients, and Ethernet event notifications).
4. After the restore process completes, the server makes an audible series of beeps. Remove the Management Server Restore CD-ROM from the CD-RW drive. 5. Power cycle the management server. The server performs power-on self-tests (POSTs). After successful POST completion, the LCD panel displays a Welcome!! message, then continuously cycles through and displays server operational information. 6. Configure the following parameters at the server’s LCD panel.
Figure C-1 Run Dialog Box 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.
17. Power off and reboot the management server. a. At the Windows 2000 desktop, click Start at the left side of the task bar (bottom of the desktop), then select Shut Down. The Shut Down Windows dialog box displays. b. Select the Restart option from the list box and click OK. The server powers down and restarts. 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.
e. Click the Send Ctrl-Alt-Del button at the top of the window to log on to the management server desktop. The Log On to Windows dialog box displays (Figure C-4). NOTE: Do not simultaneously press the Ctrl, Alt, and Delete keys. This action logs the user on to the browser-capable PC, not the rack-mount management server. Figure C-4 Log On to Windows Dialog Box f. Type the default Windows 2000 user name and password and click OK.
Figure C-5 SANavigator Log In or EFCM Log In Dialog Box g. Type the SAN management application default user ID and password and select a server or IP address from the Network Address drop-down list. 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 SANavigator or EFCM main window appears.
C-8 McDATA Sphereon 4500 Fabric Switch Installation and Service Manual
D Consolidating Management Servers This appendix provides instructions to consolidate multiple rackmount management servers by configuring one unit as the server and configuring the remaining units as clients backups. The appendix provides the following sections: • Overview. • Consolidating management servers. • Reconfiguring a client after an management server failure. Overview For control and efficiency, directors and switches in a multiswitch fabric should be managed by a single management server.
Figure D-1 Servers Before Consolidation (Private LAN Connection Only) • Figure D-2 D-2 Multiple management servers (Figure D-2), each with one Ethernet media adapter connected to the private director and switch network (LAN 2), and a second Ethernet media adapter connected to the customer’s corporate intranet (LAN 1).
Required SAN Management Application Version Before consolidating management servers, ensure each rack-mount server is running Version 4.0 (or later) of the SANavigator application or Version 8.0 (or later) of the EFCM application, and each switch is running firmware Version 6.0 (or later). If the SAN management application requires upgrade, refer to Install or Upgrade Software on page 4-87 for instructions.
IP addresses are structured to represent a location and product type. The address format is 010.rrr.ppp.xxx, where: • rrr is the cabinet number (001, 002, or 003), which specifies the location of a stand-alone product or McDATA FC-512 Fabricenter equipment cabinet. The numbers have no hierarchical significance and do not have to reflect physical order along a LAN. However, you must assign a different number to each stand-alone product or cabinet.
Consolidating Management Servers This procedure provides instructions to consolidate multiple management servers into a single environment. The procedure is divided into steps that are: Common Steps for All Configurations • Common for all configurations. • Unique to the private LAN configuration. • Unique to the public LAN and corporate intranet configuration. Perform the following steps for the switch configurations shown in Figure D-1 on page D-2 and Figure D-2 on page D-2: 1.
Input IP: 010.001.001.001 Figure D-5 LCD Panel (LAN 2 IP Address) d. Use the arrow keys as described in step b to input a unique IP address for each rack-mount server. For example: • Management server: 10.1.1.1 • First client backup server: 10.2.1.1 • Second client backup server: 10.3.1.1 • Third client backup server: 10.4.1.1 e. Press ENTER. The following message appears (Figure D-6): Save Change? Yes, Save !! Figure D-6 LCD Panel (Save Change) f. Press ENTER.
h. Press ENTER. A Wait a moment! message appears at the LCD panel, the LCD panel returns to the LAN 1 Setting?? message, and the LAN 2 subnet mask changes. 3. Ensure each server has a unique computer name. Repeat this step for the management server and all client servers. a. Log on to the server’s Windows 2000 desktop through a LAN connection to a browser-capable PC. Refer to Access the Management Server Desktop on page 2-55 for instructions. b.
e. Click Properties. The Identification Changes dialog box displays (Figure D-10). Figure D-10 Identification Changes Dialog Box f. At the Computer Name field, input a unique name for each rack-mount server. For example: • Management server: MGMTSERVER • First client backup server: CLIENT1 • Second client backup server: CLIENT2 • Third client backup server: CLIENT3 g. For each server, change the workgroup name to WORKGROUP, then click OK. The dialog box closes. h.
4. Ensure each Sphereon 4500 Switch has a unique IP address. a. Change the IP address of a switch through the maintenance port at the rear of the switch chassis (Task 5: Configure Switch Network Information (Optional) on page 2-41). b. If the IP address is changed at a switch, the IP address must also be changed at the SAN management application (management server) (Task 13: Configure the Switch to the Management Application on page 2-76).
Figure D-12 Discover Setup Dialog Box b. Click Add. The Domain Information dialog box displays with the IP Address page open by default (Figure D-13 on page D-11). c. Type a switch description (Sphereon 4500, for example) in the Description field. d. Type the switch IP address (determined by the customer’s network administrator) in the IP Address field. e. Type the switch subnet mask (determined by the customer’s network administrator) in the Subnet Mask field. f.
Figure D-13 Domain Information Dialog Box (IP Address Page) h. Click OK to close the Discover Setup dialog box and return to the SAN management application. 6. At all client backup PCs, delete all consolidated switches from the physical map (SANavigator or EFCM main window) as follows: a. Right-click the Sphereon 4500 product icon (Figure D-14) representing a switch to be deleted at the SAN management application’s physical map. A pop-up menu appears. Figure D-14 Sphereon 4500 Product Icon b.
Figure D-15 SANavigator or EFCM Message Dialog Box c. Click Yes to delete the switch. 7. Daisy-chain (connect) the Ethernet hubs. a. To connect the top and middle hubs in the stack, 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 hubs in the stack, 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.
NOTE: To connect two hubs, use step b and step c (middle and bottom hub instructions only). 8. Wait approximately five minutes for the Ethernet link to establish, then inspect the product list or physical map at the SANavigator or EFCM main window. Ensure all switch icons appear without a yellow triangle, red diamond, or grey square with a yellow exclamation mark, indicating the switches are defined and communicating with the SAN management application.
Figure D-17 Network and Dial-up Connections Window 3. Double-click the Local Area Connection icon. The Local Area Connection Status dialog box displays (Figure D-18). Figure D-18 Local Area Connection Status Dialog Box 4. Click Disable. The LAN 1 connection is disabled and the dialog box closes. After performing the preceding steps, Figure D-19 on page D-15 shows consolidation of management servers and switches in a private LAN environment.
Figure D-19 Servers After Consolidation (Private LAN Connection Only) Private and Public LAN Connection After completing the common steps to consolidate management server operation, ensure each client backup server can login to the management server. Perform this procedure at each client backup server. 1. Reboot the client backup server at the Windows 2000 desktop (accessed through a LAN connection to a browser-capable PC): a.
b. Select the Restart option from the list box and click OK. The backup server powers down and restarts. During the reboot process the LAN connection between the backup server and browser-capable PC drops momentarily, and the TightVNC viewer displays a network error (Figure D-21). Figure D-21 TightVNC Network Error Message c. After the backup server reboots, click Login again. The VNC Authentication screen displays (Figure D-22). Figure D-22 VNC Authentication Screen 2.
Figure D-23 Welcome to Windows Dialog Box 3. Click the Send Ctrl-Alt-Del button at the top of the window to log on to the backup server desktop. The Log On to Windows dialog box displays (Figure D-24). NOTE: Do not simultaneously press the Ctrl, Alt, and Delete keys. This action logs the user on to the browser-capable PC, not the backup server. Figure D-24 Log On to Windows Dialog Box 4. Type the default Windows 2000 user name and password and click OK.
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-25 SANavigator Log In or EFCM Log In Dialog Box 5. Type the SAN management application default user ID and password and select a server or IP address from the Network Address drop-down list. NOTE: The default SAN management application user name is Administrator and the default password is password. The user name and password are case-sensitive. 6.
Figure D-26 Servers After Consolidation (Private and Public LAN Connections) Reconfiguring a Client PC After a Management Server Failure If the rack-mount management server fails, backup configuration data from the server hard drive (saved to a removable CD-ROM) is installed to any client backup server, and the client is reconfigured as the new management server. To reconfigure a client backup server as the management server: 1. At the management server, press the power ( off the unit.
Figure D-27 My Computer Window 5. Double-click the Local Disk (C:) icon. The Local Disk (C:) window displays (Figure D-28). Figure D-28 Local Disk (C:) Window 6.
• For the Sanavigator 4.0 application, copy the backup CD-ROM contents to the following directories: — C:\Program Files\SANavigator4.0\CallHome — C:\Program Files\SANavigator4.0\Client — C:\Program Files\SANavigator4.0\Server. • For the EFCM 8.0 application, copy the backup CD-ROM contents to the following directories: — C:\Program Files\EFCM 8.0\CallHome — C:\Program Files\EFCM 8.0\Client — C:\Program Files\EFCM 8.0\Server. 7.
10. Type the default password and click OK. The Welcome to Windows dialog box displays (Figure D-23 on page D-17). NOTE: The default TightVNC viewer password is password. 11. Click the Send Ctrl-Alt-Del button at the top of the window to log on to the backup server desktop. The Log On to Windows dialog box displays (Figure D-24 on page D-17). NOTE: Do not simultaneously press the Ctrl, Alt, and Delete keys. This action logs the user on to the browser-capable PC, not the backup server. 12.
Index A C applications Element Manager 1-21 SAN management 1-19 SANpilot interface 1-17 attention statements xxiv audit log Element Manager application 4-16 SAN management application 4-13 call-home support configure at management server 2-71, 2-114 description 1-23 enable at management server 2-114 clean fiber-optic components 4-54 clear event log entries 4-8, 4-9, 4-10, 4-12, 4-13 port statistics 4-25 clearances 1-8 client PC description 1-12 specifications 1-14 client workstation description 1-12 spe
Index call-home feature 2-71 call-home support 2-114 e-mail notification 2-112 Ethernet events 2-114 fabric binding 2-34 fabric parameters 2-21, 2-92 management server date and time 2-69 management server DNS domain name 2-55 management server IP address 2-51 management server name 2-55 management server password 2-51 management server subnet mask 2-51 OpenTrunking 2-36, 2-109 OSMS 2-29 passwords 2-30, 2-51, 2-72 PFE key 2-38, 2-82 port binding 2-31, 2-103 ports 2-15, 2-101 preferred path 2-94 SNMP 2-26, 2
Index configuring 2-15, 2-101 description 1-2 segmented 3-93 Element Manager application audit log 4-16 configuring 2-88 description 1-21 error messages A-1 event log 4-16 hardware log 4-17 Hardware View 1-22 information messages A-1 link incident log 4-18 PFE key 2-82 threshold alert log 4-19 e-mail support configure at management server 2-112 description 1-23 enable at management server 2-112 enable call-home support 2-114 CLI 2-28 EFM 2-35, 2-97 e-mail notification 2-112 Ethernet events 2-114 fabric bin
Index configure at management server 2-92 configure at SANpilot interface 2-21 Fabricenter equipment cabinet description 1-2 Ethernet hub installation 2-8 management server installation 2-48 switch installation 2-12 fault isolation MAP 0000 - Start MAP 3-6 MAP 0100 - Power distribution analysis 3-30 MAP 0200 - POST failure analysis 3-38 MAP 0300 - Server application problem determination 3-41 MAP 0400 - Loss of server communication 3-51 MAP 0500 - FRU failure analysis 3-68 MAP 0600 - Port failure and link
Index Element Manager application A-1 insistent domain ID 2-21, 2-91 installation options customer-supplied rack 2-3 desktop 2-2 Fabricenter cabinet 2-2 installation tasks summary 2-3 Task 1 - Verify installation requirements 2-4 Task 10 - Set management server date and time 2-69 Task 11 - Configure the call-home feature (optional) 2-71 Task 12 - Assign user names and passwords 2-72 Task 13 - Configure the switch to the management application 2-76 Task 14 - Record or verify server restore information 2-78
Index clearing 4-8, 4-9, 4-10, 4-12, 4-13 events 4-7, 4-8, 4-9, 4-10, 4-12 Log tab view 4-7, 4-8, 4-9, 4-10, 4-12 logs Element Manager link incident 4-18 fabric 4-16 hardware 4-17 product status 4-14 SAN management application audit 4-13 SAN management application event 4-13 SANpilot event 4-4 SANpilot link incident 4-6 SANpilot open trunking 4-5 session 4-14 Sphereon 4500 audit 4-16 Sphereon 4500 event 4-16 threshold alert 4-19 loopback plug description 1-24 illustration 1-24 loopback test description 4-3
Index configure at SANpilot interface 2-29 PFE key 2-39, 2-82 OpenTrunking configure at management server 2-109 configure at SANpilot interface 2-36 OpenTrunking PFE key 2-39, 2-82 operating environment 1-9 operating parameters configure at management server 2-90 configure at SANpilot interface 2-19 P password configure at management server 2-72 configure at SANpilot interface 2-30 customer-level switch 2-1, 3-1 default management server LCD panel 2-51 default maintenance port 2-44 default SAN management
Index PWR LED description 1-6 location 1-3 R R_A_TOV 2-22, 2-92 rack-mount installation Ethernet hub 2-8 management server 2-48 Sphereon 4500 Switch 2-12 reconfigure client PC D-19 remove and replace procedures 5-2 repair procedures block or unblock a port 4-51 clean fiber-optic components 4-54 collect maintenance data 4-44 IML, IPL, or reset the switch 4-56 install or upgrade software 4-87 manage configuration data 4-79 manage firmware versions 4-59 obtain log information 4-2 obtain port diagnostic infor
Index upgrade 4-87 Solution Center e-mail address xxi fax number xxi phone number xxi specifications client PC 1-14 client workstation 1-14 management server 1-11 management server consolidation D-3 switch clearances 1-8 switch dimensions 1-7 switch power requirements 1-7 Sphereon 4500 Switch description 1-2 firmware 4-59 FRU removal and replacement 5-1 FRUs 1-3 illustrated parts breakdown 6-1 illustration 1-2 installation 2-10 installation options 2-2 maintenance analysis procedures 3-1 maintenance approa
Index V verify management server restore information 2-78 power supply replacement 5-10 SFP transceiver replacement 5-5 switch-to-server communication 2-80 W Windows 2000 configure users 2-63 default password 2-58, 2-119, 4-94, C-6, D-18, D-22 default user name 2-58, 2-119, 4-94, C-6, D-18, D-22 wraps, definition 4-25 Z zone sets configure at SANpilot interface 2-124 description 2-121 zones add or delete members 2-123 configure at SANpilot interface 2-121 description 2-121 I-10 McDATA Sphereon 4500 Fab
