McDATA® Sphereon™ 4300 Fabric Switch Installation and Service Manual P/N 620-000171-010 REV A
Record of Revisions and Updates Revision Date Description 620-000171-000 8/2003 General availability (GA) release of the manual. 620-000171-010 12/2003 Revision of the manual to describe Release 6.1 of the Enterprise Operating System. 620-000171-020 1/2005 Revision of the manual to describe Release EOS 7.0. Copyright © 2003-2005 McDATA Corporation. All rights reserved.
Contents Preface .......................................................................................................................... xiii Chapter 1 General Information Switch Description............................................................................1-1 Field-Replaceable Units ............................................................1-3 Power Supply .............................................................................1-4 Controls, Connectors, and Indicators ..................
Contents Task 2: Unpack, Inspect, and Install the Switch ...........................2-3 Unpack and Inspect the Switch ...............................................2-4 Desktop Installation ..................................................................2-4 Rack-Mount Installation ...........................................................2-5 Task 3: Configure the Switch at the SANpilot Interface..............2-6 Configure Switch Ports.............................................................
Contents Determination................................................................................. 3-54 Chapter 4 Repair Information Procedural Notes.............................................................................. 4-2 Obtain Log Information .................................................................. 4-2 Event Log ................................................................................... 4-3 Open Trunking Re-Route Log .................................................
Contents Chapter 6 Illustrated Parts Breakdown Front-Accessible FRUs .....................................................................6-2 Miscellaneous Parts ..........................................................................6-3 Power Cords and Receptacles.........................................................6-4 Appendix A Event Code Tables System Events (000 through 199) .................................................A-2 Fan Events (300 through 399) .....................................
Figures 1-1 1-2 1-3 1-4 1-5 1-6 1-7 2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 2-10 2-11 2-12 2-13 2-14 2-15 2-16 2-17 2-18 2-19 2-20 2-21 2-22 2-23 Sphereon 4300 Switch .................................................................................. 1-2 Sphereon 4300 Switch (Front View) ........................................................... 1-3 Sphereon 4300 Switch (Rear View) ............................................................ 1-3 View Panel (SANpilot Interface) ................................
Figures 2-24 2-25 2-26 2-27 2-28 2-29 2-30 2-31 2-32 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 3-10 3-11 3-12 3-13 4-1 4-2 4-3 4-4 4-5 4-6 4-7 4-8 4-9 4-10 4-11 4-12 4-13 4-14 4-15 4-16 4-17 4-18 4-19 4-20 4-21 viii COMn Properties Dialog Box .................................................................... 2-42 Sphereon 4300 - HyperTerminal Window .............................................. 2-43 HyperTerminal Dialog Box (1) ..................................................................
Figures 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 5-1 6-1 6-2 6-3 McDATA File Center Home Page ............................................................ 4-33 McDATA File Center (Login Page) .......................................................... 4-34 McDATA File Center (Find Documents Page) ....................................... 4-34 McDATA File Center (Documents Match Page) .................................... 4-35 McDATA File Center (Current Request Page) ........
Figures x McDATA Sphereon 4300 Fabric Switch Installation and Service Manual
Tables 2-1 2-2 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 3-10 3-11 3-12 3-13 4-1 6-1 6-2 6-3 Factory-Set Defaults (Sphereon 4300 Switch) ........................................... 2-1 Installation Task Summary ......................................................................... 2-2 Factory-Set Defaults ..................................................................................... 3-2 MAP Summary .............................................................................................
Tables xii McDATA Sphereon 4300 Fabric Switch Installation and Service Manual
Preface This publication is part of a documentation suite that supports the McDATA® Sphereon 4300 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 4300 Fabric Switch contains no customer-serviceable parts that require internal access to the product during normal operation or prescribed maintenance conditions.
Chapter 4, Repair Information - This chapter describes supplementary diagnostic and repair procedures for a failed switch. The chapter includes procedures to display and use log information, perform port diagnostics, manage configuration data, collect maintenance data, power-on, power-off, and reset the switch, set the switch online or offline, block ports, manage switch firmware, and clean fiber optics.
below. Please have the product serial number (printed on the service label attached to the switch) available. Phone: (800) 752-4572 or (720) 566-3910 Fax: (720) 566-3851 E-mail: support@mcdata.com 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.
Laser Compliance Statement Laser transceivers for the switch are tested and certified in the United States to conform to Title 21 of the Code of Federal Regulations (CFR), Subchapter J, Parts 1040.10 and 1040.11 for Class 1 laser products. Elsewhere, the transceivers are tested and certified to be compliant with International Electrotechnical Commission IEC825-1 and European Norm EN60825-1 and EN60825-2 regulations for Class 1 laser products. Class 1 laser products are not considered hazardous.
European Union Conformity Declarations for Information Technology Equipment European Union Directives The switch meets the following regulatory requirements as set forth by European Norms (ENs) and relevant International Electrotechnical Commission (IEC) standards for commercial and light industrial information technology equipment (ITE). • EN55022: 1998; EN55024: 1997, +A1: 1998: ITE-generic radio frequency interference (RFI) emission standard for domestic, commercial, and light industrial environments.
• Hebrew. • Italian. • Portuguese. • Spanish (European). • Spanish (Latin American). DANGER Use the supplied power cords. Ensure the facility power receptacle is the correct type, supplies the required voltage, and is properly grounded. 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.
PERICOLO Usare il cavo di alimentazione in dotazione. Assicurarsi che la presa di corrente a disposizione sia del tipo corretto, eroghi la tensione richiesta e sia dotata di messa a terra idonea. PERIGO Use os cordões elétricos fornecidos. Certifique-se de que o tipo de receptor de energia da facilidade é apropriado, fornece a voltagem necessária, e está corretamente aterrado. PELIGRO Utilice los cables de alimentación proporcionados.
ATTENTION ! Prior to servicing a product, determine the Ethernet LAN configuration. Installation of products on a public customer intranet can complicate problem determination and fault isolation. 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.
1 General Information The McDATA® Sphereon™ 4300 Fabric Switch provides up to 12 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 • Fabric ports (F_Ports) to provide direct connectivity for up to 12 switched fabric devices. • Fabric loop ports (FL_Ports) to provide arbitrated loop connectivity and fabric attachment for FC-AL devices. Each FL_Port can theoretically support the connection of 126 FC-AL devices. • Expansion ports (E_Ports) to provide interswitch link (ISL) connectivity to fabric directors and switches.
General Information 1 Field-Replaceable Units Figure 1-2 The switch provides a modular design that enables quick removal and replacement of small form factor pluggable (SFP) optical transceivers. Figure 1-2 illustrates the front of the switch. SFP optical transceivers are the only FRUs. The figure also shows front-panel controls, connectors, and indicators. Sphereon 4300 Switch (Front View) Figure 1-3 illustrates the rear of the switch. The figure shows the power connector and maintenance port.
General Information 1 SFP Transceiver 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.0625 Gbps) - Shortwave laser transceivers provide connections for transferring 1.
General Information 1 Controls, Connectors, and Indicators Controls, connectors, and indicators for the switch include the: IML/Reset Button • Combined initial machine load and reset (IML/RESET) button. • Ethernet LAN connector. • Green power (PWR) and amber system error (ERR) light-emitting diodes (LEDs). • Green, blue, and amber status LEDs associated with Fibre Channel ports. • RS-232 maintenance port.
General Information 1 Ethernet LAN Connector The front panel provides a 10/100 megabit per second (Mbps) RJ-45 twisted-pair connector (Figure 1-2 on page 1-3) that attaches to an Ethernet LAN to provide communication with a PC accessing the SANpilot interface or a simple network management protocol (SNMP) management workstation. The connector provides two green LEDs. The left LED illuminates to indicate LAN operation at 10 Mbps, while the right LED illuminates to indicate LAN operation at 100 Mbps.
General Information 1 Switch Specifications This section lists physical characteristics, storage and shipping environment, operating environment, and service clearances for the Sphereon 4300 Switch. Physical Characteristics Dimensions: Height: 4.1 centimeters (1.6 inches) or 1 rack unit Width: 43.7 centimeters (17.2 inches) Depth: 47.3 centimeters (18.6 inches) Weight: 6.
General Information 1 Storage and Shipping Environment Protective packaging must be provided to protect the switch under all shipping methods (domestic and international).
General Information 1 • System event information displays at the SANpilot interface. • LEDs on the switch front panel or adjacent to Fibre Channel ports illuminate to indicate a hardware malfunction. • An unsolicited SNMP trap message is received at a management workstation, indicating an operational state change or failure. System events can be related to a: • Switch failure (hardware or software). • Ethernet LAN communication failure between the switch and a PC accessing the SANpilot interface.
General Information 1 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 • Beaconing to assist service personnel in locating a specific port or switch. When port beaconing is enabled, the amber LED associated with the port flashes. When unit beaconing is enabled, the system error indicator on the front panel flashes. Beaconing does not affect port or switch operation. • SNMP management using the Fibre Channel Fabric Element MIB (Version 1.
General Information 1 Figure 1-4 View Panel (SANpilot Interface) The task selection tabs allow personnel to perform switch-specific tasks, and are a function of the menu selected as follows: 1-12 • View - At the View panel, the Switch (default), Port Properties, FRU Properties, Unit Properties, Operating Parameters, and Fabric task selection tabs appear. • Configure - At the Configure panel, the Ports (default), Switch, Management, Zoning, Security, and Performance task selection tabs appear.
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 browser-capable PC.
General Information 1 Tools Supplied with the Switch The following tools are supplied with the switch. Use of the tools may be required to perform one or more installation, test, service, or verification tasks. • Figure 1-5 Loopback Plug • Figure 1-6 Fiber-optic protective plug - For safety and port transceiver protection, fiber-optic protective plugs (Figure 1-6) must be inserted in all switch ports without fiber-optic cables attached.
General Information 1 Figure 1-7 Tools Supplied by Service Personnel Null Modem Cable The following tools are expected to be supplied by service personnel performing switch installation or maintenance actions. Use of the tools may be required to perform one or more test, service, or verification tasks. • Scissors or pocket knife - A sharp cutting edge (scissors or knife blade) may be required to cut the protective strapping when unpacking replacement FRUs.
General Information 1 1-16 McDATA Sphereon 4300 Fabric Switch Installation and Service Manual
2 Installation Tasks This chapter describes tasks to install, configure, and verify operation of the Sphereon 4300 Switch and SANpilot interface. 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 4300 Switch.
Installation Tasks 2 Installation Options The switch is installed in one of three configurations. The options are: • Table or desktop - One or more switches are delivered and installed at the customer facility on a table or desktop. Ethernet cabling, distance, and local area network (LAN) addressing issues must be considered. • Fabricenter equipment cabinet - One or more switches are delivered (cabled and installed) in a McDATA equipment cabinet.
Installation Tasks 2 Task 1: Verify Installation Requirements Verify the following requirements are met prior to switch and SANpilot interface installation. Ensure: • A site plan is prepared, configuration planning tasks are complete, planning considerations are evaluated, and related planning checklists are complete. Refer to McDATA Products in a SAN Environment - Planning Manual (626-000124) for information.
Installation Tasks 2 Unpack and Inspect the Switch Unpack and inspect the switch(es) as follows: 1. Inspect shipping container(s) for damage caused during transit. If a container is damaged, ensure a representative from the freight carrier is present when the container is opened. 2. Unpack shipping container(s) and inspect each item for damage. Ensure the packaged items correspond to the items listed on the enclosed bill of materials. 3.
Installation Tasks 2 Figure 2-1 AC Power Connection 6. When the power cord is connected, the switch powers on and performs power-on self-tests (POSTs). During POSTs: 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.
Installation Tasks 2 3. Open the rack-mount kit and inspect the contents. Refer to the enclosed bill of materials and verify all parts are delivered. 4. Using a T10 Torx tool and #2 Phillips screwdriver, install the switch in the equipment cabinet. Refer to the Sphereon 4300 Switch Rack-Mount Kit Installation Instructions (958-000316) for guidance. 5. Connect the AC power cord to the receptacle at the rear of the chassis as shown in Figure 2-1 on page 2-5. 6.
Installation Tasks 2 • Configure administrator and operator passwords. • Install switch product feature enablement (PFE) keys. 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.
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 Switch page displayed (Figure 2-3). Figure 2-3 Configure Switch Ports View Panel (Switch Page) Perform procedures in this section to configure names and operating characteristics for Fibre Channel ports.
Installation Tasks 2 Figure 2-4 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 d. Select from the drop-down list in the Type column to configure the port type. Available selections are: • Fabric port (F_Port). • Expansion port (E_Port). This selection is available only if enabled through an optional PFE key. • Generic port (G_Port). A generic port setting allows F_Port and E_Port behavior only. This selection is available only if enabled through an optional PFE key. • Generic mixed port (GX_Port).
Installation Tasks 2 1. At the View panel, select the Configure option at the left side of the panel. The Configure panel opens with the Ports page displayed (Figure 2-4). Select the BB Credits tab is selected. Use the vertical scroll bar to display additional port information rows. 2. It is recommended you select the Default values. If not, you can enter values in the RX BB Credit field. 3. Select Activate to save the changes. 4. Place the port back online.
Installation Tasks 2 Figure 2-6 Configure Panel (Switch Page with Identification Tab) 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 domain name system (DNS) host name. For example, if the DNS host name is sphereon4300.mcdata.com, the name entered in this dialog box should be sphereon4300. b.
Installation Tasks 2 Configure Date and Time Perform this procedure to configure the effective date and time for the switch. To set the date and time: 1. At the Configure panel, click the Date/Time tab. The Switch page displays with the Date/Time tab selected (Figure 2-7). Figure 2-7 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.
Installation Tasks 2 Configure Operating Parameters Perform this procedure to configure the switch’s preferred domain ID, insistent domain ID, rerouting delay, and domain registered state change notifications (RSCNs). The switch must be set offline to configure the preferred domain ID. To configure parameters: 1. Set the switch offline as follows: a. At the Configure panel, select the Operations option at the left side of the panel.
Installation Tasks 2 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. 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.
Installation Tasks 2 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. The message Your operations changes have been successfully activated appears.
Installation Tasks 2 Figure 2-9 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). Ten seconds (100) is the recommended value. 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.
Installation Tasks 2 This value designates the fabric’s principal switch. The principal switch is assigned a priority of 1 and controls the allocation and distribution of domain IDs for all fabric elements (including itself). Principal is the highest priority setting, Default is the next highest, and Never Principal is the lowest priority setting. The setting Never Principal means the switch is incapable of becoming a principal switch.
Installation Tasks 2 b. Click the Online State tab, then click Set Online. The message Your operations changes have been successfully activated appears. Configure Network Information Verify the type of LAN installation with the customer’s network administrator. If one switch is installed on a dedicated LAN, network information (IP address, subnet mask, and gateway address) does not require change. Go to Configure SNMP on page 2-21.
Installation Tasks 2 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. The following message box displays (Figure 2-11). Figure 2-11 Network Information Message Box 4. Update the address resolution protocol (ARP) table for the browser PC. a.
Installation Tasks 2 6. At the PC, launch the browser application (Netscape Navigator or Internet Explorer). 7. At the browser, enter the switch’s new IP address as the Internet URL. The Enter Network Password dialog box displays. 8. 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. 9. Click OK. The SANpilot interface opens with the View panel open and the Switch page displayed.
Installation Tasks 2 Figure 2-12 Configure Panel (Management Page with SNMP Tab) a. Click the Enable SNMP Agent check box to enable or disable the installed SNMP agent. b. Select the Fibre Alliance management information base (FA MIB) from the FA MIB Version drop-down list. This should be set to match the level of FA MIB used by the SNMP management stations that access the product. 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.
Installation Tasks 2 Figure 2-13 Configure Panel (Management Page with CLI Tab) 2. Perform one of the following steps as required: • 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. 3. To enable SSH, from the Protocol drop down box, select SSH. 4. Select Activate to enable SSH for Telnet.
Installation Tasks 2 Figure 2-14 Configure Panel (Management Page with OSMS Tab) 2. Select eithe Enable or Disable from the drop-down box: • Select Enable to activate the OSMS. The message Your changes to the host control enable state have been successfully activated appears. • Select Disable to deactivate the OSMS. The message Your changes to the host control enable state have been successfully activated appears. 3. To change the host control state, select enable or disable from the drop-down box.
Installation Tasks 2 Figure 2-15 Configure Panel (Security Page with User Rights Tab) 2. Under the Currer User Records, enter the new password. 3. Click Activate to save the information. The message Your changes to the user rights configuration have been successfully activated appears. NOTE: If you want to create a user account, review the SANpilot User’s Guide for more information.
Installation Tasks 2 Figure 2-16 Configure Panel (Security Page with Port Binding Tab) a. Click the check box in the Port Binding column to enable or disable port binding for a specified port (default is disabled). b. In the Bound WWN column, type the world wide name of the device to which the port is to be bound. If port binding is enabled, only the specified device can connect to the port.
Installation Tasks 2 Perform this procedure to configure switch binding by attached devices (nodes). The SANtegrity feature must be installed to access this control (Install PFE Keys (Optional) on page 2-38). If the feature is not installed, the message This Feature Not Installed appears. Switch Binding functionality enables you to identify the devices with which the switch or director can communicate. Switch Binding is available only if the SANtegrity Binding feature is installed.
Installation Tasks 2 To configure switch binding: 1. At the Configure panel, click the Switch Binding tab. The Security page displays with the Switch Binding tab selected (Figure 2-17 on page 2-30). 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.
Installation Tasks 2 Figure 2-17 Configure Panel (Security Page with Switch Binding Tab) 3. Click Submit. A confirmation dialog box appears. Click OK to close the confirmation dialog box, activate the selected connection policy, and change the switch binding state. NOTE: The Disable Switch Binding selection cannot be activated while Enterprise Fabric Mode is enabled and the switch is online. 4. The Attached Nodes drop-down list contains the world wide names of attached Fibre Channel devices.
Installation Tasks 2 Configuring the Switch Binding Membership List The SBML contains the WWNs of devices that are allowed to communicate with the switch when Switch Binding is enabled. This list is configured using the Switch Binding tab. The contents of the SBML are shown at the bottom of the tab, listed by WWN. The tab can show up to 64 list members. If the list contains more than 64 members, the other list members are shown on subsequent pages.
Installation Tasks 2 • The switch or device with the WWN is connected to a port that is blocked. To delete a member or all members from the SBML, perform the following procedure: 1. Select Configure from the navigation panel. 2. Select the Security tab and the Switch Binding tab. 3. Select the Delete button next to the listing for the member. 4. At the Are you sure you want to delete this member? prompt, click OK. The SBML redisplays without the deleted member. 5.
Installation Tasks 2 Figure 2-18 Configure Panel (Security Page with Fabric Binding Tab) 2. The Fabric Binding tab is divided into sections by the following headings. Configure fabric binding from the following: • Fabric Binding Status—Identifies whether Fabric Binding is active or inactive on the product.
Installation Tasks 2 — Delete All: By selecting this button, you can delete all members from the pending FBML that are not attached to the current fabric. Members that are attached must remain in the list, because the membership list must contain all attached members to be activated. — Load Active: By selecting this button, you can copy the contents of the active FBML to the pending FBML. The added members may include unattached members of the active FBML.
Installation Tasks 2 Figure 2-19 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. NOTE: For detailed information on configuring Enterprise Fabric Mode, review the SANpilot User Manual.
Installation Tasks 2 Figure 2-20 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 A backpressure event occurs when the percent time an ISL has low BB_Credit exceeds the low BB_Credit threshold. 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.
Installation Tasks 2 Install PFE Keys (Optional) Perform this procedure to install optional features. After purchasing a feature, obtain the required product feature enablement (PFE) key by following the enclosed instructions. A PFE key is an alphanumeric string consisting of both uppercase and lowercase characters. The total number of characters may vary. The key is case sensitive and must be entered exactly, including dashes. The following is an example of a PFE key format: XxXx-XXxX-xxXX-xX.
Installation Tasks 2 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. NOTE: When Activate is selected, all current features are replaced with new features. Features not included in the new feature key are no longer available on the system.
Installation Tasks 2 NOTE: If multiple switches are delivered in a McDATA Fabricenter equipment cabinet, all devices are configured with unique IP addresses that do not require change. The addresses require change only if multiple equipment cabinets are LAN-connected. • Subnet mask - The default subnet mask is 255.0.0.0. If the switch is installed on a complex public LAN with one or more routers, the address may require change. • Gateway address - The default gateway address is 0.0.0.0.
Installation Tasks 2 4. At the Windows desktop, click Start at the left side of the task bar. The Windows Workstation menu displays. NOTE: The following steps describe changing network addresses using HyperTerminal serial communication software. 5. At the Windows Workstation menu, sequentially select the Programs option, Accessories option, Hyperterminal option, and HyperTerminal option. The Connection Description dialog box displays (Figure 2-22 on page 2-41).
Installation Tasks 2 Figure 2-23 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-24 on page 2-42).
Installation Tasks 2 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 4300 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 — 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. Change the IP address, subnet mask, and gateway address as directed by the customer’s network administrator. To change the switch network addresses, type the following at the C > prompt and press the Enter key. ipconfig xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy zzz.zzz.zzz.
Installation Tasks 2 Figure 2-27 HyperTerminal Dialog Box (2) 14. Click No to exit and close the HyperTerminal application. 15. Power off the maintenance terminal: a. Click Start at the left side of the task bar and select the Shut Down option. The Shut Down Windows dialog box appears. b. At the Shut Down Windows dialog box, select the Shut down option from the list box and click OK to power off the PC. 16. Disconnect the RS-232 modem cable from the switch and the maintenance terminal.
Installation Tasks 2 2. Connect device cables to SFP optical port transceivers. Start with port 0 (far right) and continue sequentially to the left through port 11. 3. Perform one of the following: • If the switch is installed on a table or desk top, bundle and secure the Fibre Channel cables as directed by the customer.
Installation Tasks 2 Figure 2-28 Configure Panel (Zoning Page with Zones Tab) 2. To configure a zone, first add the zone name to the zoning library. The following naming conventions apply to zones and zone sets: • All names must be unique and may not differ by case only. For example, zone-1 and Zone-1 are both valid individually, but are not considered unique. • The first character of a zone set name must be a letter (A through Z or a through z). • A zone set name cannot contain spaces.
Installation Tasks 2 • Delete all zones - To delete all configured zones and zone members, click Delete All Zones. A confirmation dialog box displays. Click OK to delete all zones. • Delete a single zone - To delete a single zone and its zone members, click the Delete button adjacent to the zone name. A confirmation dialog box displays. Click OK to delete the zone. • Go to zones- If a zone set contains more than 64 zones, the Go to zones link activates to display subsequent pages.
Installation Tasks 2 • Add member by attached node WWN - Select the WWN of an attached device (node) from the Attached Node World Wide Name drop-down list and click the adjacent Add Member button. The device is added to the zone. • Add member by WWN - Type the WWN of an attached device in the World Wide Name field and click the adjacent Add Member button. The device is added to the zone.
Installation Tasks 2 Figure 2-30 Configure Panel (Zoning Page with Zone Set Tab) 2. To create a zone set that incorporates zones and zone members (configured under Configure Zones on page 2-46), 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.
Installation Tasks 2 • Disable zone set - To disable the active zone set and place all attached devices in the default zone, click Disable Zone Set. A confirmation dialog box displays. Click OK to disable the active zone set. • Discard changes - To discard unsaved changes made to a zone set configuration and revert to a saved zoning configuration, click Discard Changes. A confirmation dialog box displays. Click OK to discard the changes.
Installation Tasks 2 9. Ensure the Operational State field displays Online and the Reason field displays N/A or is blank. If an ISL segmentation or other problem is indicated, go to MAP 0000: Start MAP on page 3-6 to isolate the problem. Task 8: Register with the McDATA File Center To complete the installation, register with the McDATA File Center web site to receive e-mail updates and access the following: • Technical publications. • Firmware and software upgrades. • Technical newsletters.
Installation Tasks 2 The following information is required: • Password. • Verify password. • First name. • Last name. • E-mail address. • Company. • Title. 3. Complete the information fields as required and click Register. The registration is complete and File Center login information is transmitted to the e-mail address specified on the 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 Figure 2-32 2-54 McDATA File Center (New User Registration Page) McDATA Sphereon 4300 Fabric Switch Installation and Service Manual
3 Diagnostics This chapter describes diagnostic procedures used by service representatives to fault isolate Sphereon 4300 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 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 on page 3-3 lists event codes and the corresponding MAP references. The table provides a quick start guide if an event code is readily available. Table 3-3 Event Codes versus Maintenance Action Event Code Explanation Action 011 Login Server database invalid. Go to MAP 0600. 021 Name Server database invalid. Go to MAP 0600. 031 SNMP request received from unauthorized community. Add a community name through the SANpilot interface. 051 Management Server database invalid.
Table 3-3 Event Codes versus Maintenance Action (Continued) Event Code 3-4 Explanation Action 143 Low BB_Credit relieved on an ISL. No action required. 150 Zone merge failure. Go to MAP 0600. 151 Fabric configuration failure. Go to Collect Maintenance Data on page 4-22. 300 Cooling fan propeller failed. Go to MAP 0400. 301 Cooling fan propeller failed. Go to MAP 0400. 302 Cooling fan propeller failed. Go to MAP 0400. 310 Cooling fan propeller recovered. No action required.
Table 3-3 Event Codes versus Maintenance Action (Continued) Event Code Explanation Action 510 SFP optical transceiver hot-insertion initiated. No action required. 512 SFP optical transceiver nonfatal error. Go to MAP 0500. 513 SFP optical transceiver hot-removal completed. No action required. 514 SFP optical transceiver failure. Go to MAP 0500. 523 FL_Port open request failed. No action required. 524 No AL_PA acquired. No action required. 525 FL_Port arbitration timeout.
MAP 0000: Start MAP This MAP describes initial fault isolation for the Sphereon 4300 Switch. Fault isolation begins at the Internet-connected PC accessing the SANpilot interface, failed switch, or switch-attached host. 1 Prior to fault isolation, acquire the following from the customer: • A system configuration drawing or planning worksheet that includes the customer-supplied web browser PC accessing the SANpilot interface, switch, other McDATA products, and device connections.
4 Boot the web-browser PC. a. Power on the PC in accordance with the instructions delivered with the PC. The Windows desktop appears. b. Launch the PC browser application by double-clicking the Netscape Navigator or Internet Explorer icon at the Windows desktop. c. 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 step 1).
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. 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.
7 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-18. Exit MAP.
Does the SANpilot interface appear operational with the View panel displayed? YES ↓ NO Perform fault isolation at the switch. Go to step 20. 10 At the View panel and Switch page, inspect the Status field at the top of the page. 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. The Port Properties page displays with port 0 highlighted (Figure 3-3).
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 at the SANpilot interface: 1. At the View panel, select Operations at the left side of the panel. The Operations panel opens with the Switch and Beacon pages displayed. 2. Click the Port tab. The Operations panel opens with the Port and Beacon pages displayed. 3.
15 Repeat step 11 through step 14 for each remaining Fibre Channel port for which a problem is suspected (ports 0 through 11). 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 0500: Port Failure and Link Incident Analysis on page 3-35. Exit MAP. 16 Inspect the power supply operational state. a. At the View panel, click the FRU Properties tab. The FRU Properties page 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 0400: FRU Failure Analysis on page 3-30. 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. Click the Event Log entry. The Event Log (Figure 3-6) displays. Figure 3-6 Event Log d. Record the event code, date, time, and severity (Informational, Minor, Major, or Severe). e. 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.
21 Is the switch connected to facility AC power? NO ↓ YES Go to step 24. 22 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. • Audio emanations and airflow from cooling fans. Does the switch appear powered on? YES ↓ NO A power distribution problem is indicated. Go to step 18 to obtain event codes.
Does the switch appear powered on? YES ↓ NO A power distribution problem is indicated. Go to step 18 to obtain event codes. If no event codes are found, go to MAP 0100: Power Distribution Analysis on page 3-18. Exit MAP. A faulty PWR LED is indicated, but switch and Fibre Channel port operation is not disrupted. The LED is connected to CTP card circuitry, and if this problem is a concern to the customer, the switch must be replaced. Exit MAP.
28 Check FRUs for failure symptoms. Are any amber LEDs associated with Fibre Channel ports illuminated? NO ↓ YES A Fibre Channel port failure is indicated. Go to step 18 to obtain event codes. If no event codes are found, go to MAP 0500: Port Failure and Link Incident Analysis on page 3-35. Exit MAP. A link incident is indicated. Go to step 18 to obtain event codes. If no event codes are found, go to MAP 0500: Port Failure and Link Incident Analysis on page 3-35. Exit MAP.
Were one or more event codes found? YES ↓ NO Perform fault isolation at the switch. Go to step 20. Go to Table 3-3 on page 3-3 to interpret event codes. Exit MAP. MAP 0100: Power Distribution Analysis This MAP describes fault isolation for the switch power distribution system, including a defective AC power cord or power supply. 1 Is fault isolation being performed at the switch? YES ↓ NO Fault isolation is being performed at the SANpilot interface. Go to step 8.
Is a power supply or power distribution system failure indicated? YES ↓ NO The switch appears operational. Exit MAP. 4 Have the customer inspect and verify that facility power is within specifications. These specifications are: • One single-phase connection for the power supply. • Input power between 100 and 240 VAC, and at least 5 amps. • Input frequency between 47 and 63 Hz. Is facility power within specifications? YES ↓ NO Ask the customer to correct the facility power problem.
7 Visual inspection indicates a power supply, power distribution system, or CTP card failure. Replace the switch. Exit MAP. 8 Does the SANpilot interface appear operational? NO ↓ YES Go to step 11. 9 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.
11 Inspect the power supply operational state at the SANpilot interface. a. At the View panel, click the FRU Properties tab. The View panel (FRU Properties tab) displays. b. Inspect the Status field for the power supply. Does the Status field display a Failed message for the power supply? NO ↓ YES The power supply failed. Replace the switch. Exit MAP. The switch appears operational. Exit MAP.
2 Was an event code 400 or 411 observed at the SANpilot Event Log? YES ↓ NO Analysis for the failure is not described in this MAP. Go to MAP 0000: Start MAP on page 3-6. Exit MAP. 3 Table 3-4 on page 3-22 lists event codes, brief explanations of the codes, and the associated steps that describe fault isolation procedures. Table 3-4 Event Code MAP 200 Event Codes Explanation Action 400 Power-up diagnostic failure. Go to step 4. 411 Firmware fault. Go to step 8.
5 The CTP card failed POSTs as indicated by FRU code 02. Replace the switch. Exit MAP. 6 A cooling fan failed POSTs as indicated by FRU code 05. Replace the switch. Exit MAP. 7 The power supply failed POSTs as indicated by FRU code 06. Replace the switch. Exit MAP. 8 POST/IML 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.
If this intermittent problem continues, perform the data collection procedure and return the diskette to McDATA for analysis. Exit MAP. 2 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.
5 Either a switch-to-PC Internet link problem (Internet too busy or IP address typed incorrectly) or a switch Ethernet port failure is indicated. 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 on page 3-6). The Username and Password Required dialog box appears. c.
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-tip screwdriver may be required). Connect the RS-232 null modem cable to the port. b. Connect the other cable end to a 9-pin communication port (COM1 or COM2) at the rear of the maintenance terminal PC. c. Power on the maintenance terminal. After the PC powers on, the Windows desktop displays. d.
Figure 3-8 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-9).
Figure 3-9 COMn Properties Dialog Box 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 4300 HyperTerminal dialog box displays. i. At the > prompt, type the user-level password (default is password) and press Enter. The password is case sensitive.
Figure 3-10 Sphereon 4300 - HyperTerminal Dialog Box k. Record the switch IP address. l. Select Exit from the File pull-down menu to close the HyperTerminal application. A HyperTerminal dialog box displays (Figure 3-11). Figure 3-11 HyperTerminal Dialog Box m. Click Yes. A second HyperTerminal dialog box displays (Figure 3-12).
Figure 3-12 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. Did changing the IP address of the switch solve the problem? NO YES ↓ The switch-to-SANpilot PC connection is restored and appears operational. Exit MAP. Failure of the switch Ethernet port is indicated. Replace the switch.
2 Table 3-6 lists event codes, brief explanations of the codes, and associated steps that describe fault isolation procedures. MAP 400 Event Codes Table 3-6 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. Go to step 6. 426 Multiple ECC single-bit errors occurred. Go to step 10. 433 Non-recoverable Ethernet fault. Go to step 11. 440 Embedded port hardware failed.
Does the switch appear powered on? YES ↓ NO An AC power distribution or CTP card failure is indicated. Go to MAP 0000: Start MAP on page 3-6. If this is the second time at this step, replace the switch. Exit MAP. 5 Inspect cooling fans at the rear of the switch to ensure all fan blades are rotating. Does cooling fan inspection indicate a failure (one or more cooling fans not rotating)? YES ↓ NO Go to step 7. 6 Visual inspection or an event code 300, 301, or 302 indicates one or more cooling fans failed.
NO ↓ YES Go to step 1. The switch appears operational. Exit MAP. 9 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.
• 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. Go to step 4. 14 Inspect the power supply (includes fan modules) operational state at the SANpilot interface. a. At the View panel, click the FRU Properties tab. The View panel (FRU Properties tab) displays. b.
MAP 0500: Port Failure and Link Incident Analysis This MAP describes fault isolation for shortwave laser small form factor pluggable (SFP) optical transceivers, longwave laser SFP optical transceivers, and Fibre Channel link incidents. Failure indicators include: • An event code recorded at the SANpilot Event Log. • A link incident event code recorded at the console of an OSI server attached to the switch reporting the problem. • One or more amber LEDs on the ports illuminate.
MAP 500 Event Codes Table 3-7 Event Code Explanation Action 507 Loopback diagnostics port failure. Go to step 14. 512 SFP optical transceiver nonfatal error. Go to step 6. 514 SFP optical transceiver failure. Go to step 6. 581 Implicit incident. Go to step 17. 582 Bit error threshold exceeded. Go to step 17. 583 Loss of signal or loss of synchronization. Go to step 17. 584 Not operational primitive sequence received. Go to step 17. 585 Primitive sequence timeout. Go to step 17.
• This procedure is concurrent and can be performed while the switch is powered on and operational. • Verify location of the failed port. • Replace the optical transceiver with a transceiver of the same type (shortwave or longwave). • 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-19. NOTE: An event code 514 may generate a call-home event that incorrectly indicates a CTP card failure.
9 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 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.
Table 3-8 Port Operational States and Actions (Continued) Operational State Action Not Installed Go to step 12. Invalid Attachment Go to step 24. Link Reset Go to step 35. Inactive Go to step 36. No light Go to step 40. Segmented E_Port Go to MAP 0600. 11 A switch port is unblocked and receiving the offline sequence (OLS) or not operational sequence (NOS) from an attached device.
b. Click the Security tab, then click the Port Binding tab. The Port Binding page displays. c. Inspect entries the Port WWN column. These are WWNs assigned to the port or Fibre Channel interface installed on the attached device. — If a nickname is not assigned to the WWN, the WWN is prefixed by the device manufacturer’s name. — If a nickname is assigned to the WWN, the nickname appears in place of the WWN. d.
15 Port beaconing may be enabled. a. Consult the customer and next level of support to determine the reason port beaconing is enabled. b. Disable port beaconing at the SANpilot interface: 1. At the View panel, select Operations at the left side of the panel. The Operations panel opens with the Switch and Beacon pages displayed. 2. Click the Port tab. The Operations panel opens with the Port and Beacon pages displayed. 3.
Figure 3-13 Link Incident Log c. 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.
c. Click OK. The message Your changes have been successfully activated appears. After clearing the log, did the link incident recur? YES ↓ NO The problem is transient and the Fibre Channel link and switch appear operational. Exit MAP. 18 Inspect the fiber-optic jumper cable attached to the port and ensure the cable is not bent and connectors are not damaged. If the cable is bent or connectors are damaged: a. Notify the customer the port will be blocked.
d. Clean the fiber-optic connectors. Refer to Clean Fiber-Optic Components on page 4-28. e. Reconnect the fiber-optic cable. f. Unblock the port. Refer to Block or Unblock a Port on page 4-26. g. Monitor port operation for approximately five minutes. Did a link incident or No Light message recur? YES ↓ NO The Fibre Channel link and switch appear operational. Exit MAP. 21 Disconnect the fiber-optic jumper cable from the switch port and connect the cable to a spare port.
24 As indicated by a message or event code 081, a port has an invalid attachment. The information in the Port Properties dialog box specifies the reason as listed in Table 3-9. Table 3-9 Invalid Attachment Reasons and Actions Reason Action Unknown Contact the next level of support. ISL connection not allowed. Go to step 25. Incompatible switch. Go to step 26. External loopback plug connected. Go to step 27. N-Port connection not allowed. Go to step 25. Non-McDATA switch at other end.
• Select fabric port (F_Port) if the port is cabled to a device (node). • Select expansion port (E_Port) if the port is cabled to a fabric element (director or switch) to form an ISL. c. Click Activate to save the change. The message Your changes to the port configuration have been successfully activated appears. Did reconfiguring the port type solve the problem? NO ↓ YES The switch appears operational. Exit MAP. Contact the next level of support. Exit MAP.
— 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. e. Click Activate to save the change. The message Your changes to the fabric parameters configuration have been successfully activated appears.
29 A port connection timed out because of an unresponsive device (node) or an ISL connection was not allowed because of a security violation (authorization failure reject). Check the port status and clean the fiber-optic connectors on the cable. 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-26. c.
b. Click the Security tab, then click the Switch Binding tab. The Switch Binding page displays. c. Ensure the switch binding state is enabled (noted at the top of the page) for both switches. d. Ensure the Connection Policy (Enable & Restrict E_Ports, Enable & Restrict F_Ports, Enable & Restrict All Ports, or Disable Switch Binding) is compatible for both switches. e. The Attached Nodes drop-down list contains the world wide names of attached Fibre Channel devices.
Did configuring the fabric and switch binding parameters solve the problem? NO ↓ YES The switch appears operational. Exit MAP. Contact the next level of support. Exit MAP. 32 A port connection is not allowed because of a fabric binding mismatch between fabric elements. Fabric binding membership lists must be compatible for both switches. At the SANpilot interface for both switches: a. At the View panel, select Configure at the left side of the panel.
compatible for both switches. At the SANpilot interface for both switches: a. At the View panel, select Configure at the left side of the panel. The Configure panel opens with the Ports page displayed. b. Click the Security tab, then click the Switch Binding tab. The Switch Binding page displays. c. The Attached Nodes drop-down list contains the world wide names of attached Fibre Channel devices.
35 The switch and attached device are performing a Fibre Channel link reset. This is a transient state. Wait approximately 30 seconds and inspect port state and LED behavior. Did the link recover and resume operation? NO ↓ YES The Fibre Channel link and switch appear operational. Exit MAP. Go to step 1.
39 A transmission speed conflict between the port configuration and the SFP optical transceiver is indicated. a. At the SANpilot interface View panel, select Configure at the left side of the panel. The Configure panel opens with the Ports page displayed. b. At the Speed column, click the arrow adjacent to the list box for the port and select a port speed as follows: • Select 1 Gb/sec if a one gigabit per second (Gbps) optical transceiver is installed in the port.
42 Connect a Fibre Channel device to the port as directed by the customer. Did connection of a device to the port solve the problem? NO YES ↓ The switch appears operational. Exit MAP. 43 A problem exists with the fiber-optic cable, attached device, or SFP optical transceiver. Go to step 18. MAP 0600: Fabric, ISL, and Segmented Port Problem Determination This MAP describes fault isolation of fabric logout, interswitch link (ISL), and E_Port segmentation problems.
3 Was an event code 011, 021, 051, 052, 061, 062, 063, 070, 071, 072, 140, 142, or 150 observed at the SANpilot Event Log? YES ↓ NO Go to step 5. 4 Table 3-10 on page 3-55 lists event codes, brief explanations of the codes, and associated steps that describe fault isolation procedures. Table 3-10 Event Code MAP 600 Event Codes Explanation Action 011 Login Server database invalid. Go to step 7. 021 Name Server database invalid. Go to step 7. 051 Management Server database invalid.
5 Go to the web server PC accessing the switch’s SANpilot interface. 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. 6 Inspect the Fibre Channel port segmentation reason at the SANpilot interface. a. At the View panel, click the Port Properties tab.
7 A minor error occurred that caused the Fabric Services database to be re-initialized to an empty state. As a result, a disruptive fabric logout and login occurred for all attached devices. The following list explains the error: • Event code 011 - The Login Server database failed cyclic redundancy check (CRC) validation. • Event code 021 - The Name Server database failed CRC validation. All attached devices resume operation after fabric login.
(hops). Fibre Channel frames may persist in the fabric longer than timeout values allow. Advise the customer of the problem and work with the system administrator to reconfigure the fabric so the path between any two fabric elements does not traverse more than three hops. 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.
A 071 event code indicates the switch is isolated from all switches in a multiswitch fabric, and is accompanied by a 070 event code for each segmented E_Port. The 071 event code is resolved when all 070 events are corrected. Obtain supplementary event data for each 070 event code. a. At the SANpilot Event Log, examine the first five bytes (0 through 4) of event data. b. Byte 0 specifies the switch port number (00 through 11) of the segmented E_port.
e. Click the Switch tab, then click the Fabric Parameters tab. The Fabric Parameters page displays. f. Type the recommended E_D_TOV and R_A_TOV values, then click Activate to save the change. The message Your changes to the fabric parameters configuration have been successfully activated appears. g. Repeat steps d through f for the switch attached to the segmented E_Port (second switch). Use the same E_D_TOV and R_A_TOV values. h. Set both switches online.
g. Repeat steps d through f for the switch attached to the segmented E_Port (second switch). Use a different preferred domain ID value. h. Set both switches online. Refer to Set the Switch Online or Offline on page 4-25. 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. Contact the next level of support. Exit MAP.
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. 16 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-25. c. At the View panel, select Configure at the left side of the panel. The Configure panel opens with the Ports page displayed. d. Click the Switch tab, then click the Fabric Parameters tab. The Fabric Parameters page displays. The switch priority value designates the fabric’s principal switch.
a. Perform the data collection procedure at the operational switch and return the diskette to McDATA for analysis. This information may assist in fault isolating the failed switch. b. Go to MAP 0000: Start MAP on page 3-6 and perform fault isolation for the failed switch. Exit MAP. 20 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.
No action is required for an isolated event or if the reporting ISL approaches 100% throughput. However, if this event persists, perform one of the following: • Relieve the congestion by adding parallel ISLs between the switches reporting the problem. • 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.
Table 3-13 Bytes 8 through 11 Failure Reasons and Actions Bytes 8 - 11 Failure Reason Action 01 Invalid data length. Go to step 24. 08 Invalid zone set format. Go to step 24. 09 Invalid data. Go to step 25. 0A Cannot merge. Go to step 25. F0 Retry limit reached. Go to step 24. F1 Invalid response length. Go to step 24. F2 Invalid response code. Go to step 24. 24 A zone merge process failed during ISL initialization.
25 A zone merge process failed during ISL initialization. The following list explains the reason: • Failure reason 09 - Invalid data caused a zone merge failure. • Failure reason 0A - A Cannot Merge condition caused a zone merge failure. Obtain supplementary error code data for the 150 event code. At the SANpilot Event Log, examine bytes 12 through 15 of event data that specify the error code. Record the error code and supplementary error code data.
3-68 McDATA Sphereon 4300 Fabric Switch Installation and Service Manual
4 Repair Information This chapter describes repair-related procedures for the Sphereon 4300 Switch and associated field-replaceable units (FRUs). The procedures are performed through the SANpilot interface. The following procedures are described: • Obtain log information. • Obtain port diagnostic information. • Perform port diagnostic loopback tests. • Collect maintenance data. • Set the switch online or offline. • Block or unblock Fibre Channel ports. • Clean fiber-optic components.
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.
provides a Clear All Logs button. Click the button to delete all entries in all logs. Figure 4-1 Event Log Monitor Panel (Logs Page) The Event Log (Figure 4-2) displays events or errors recorded at the SANpilot interface. Entries reflect the status of the interface and managed switch. The log stores up to 200 entries, and the most recent entry appears at the top of the log.
The log consists of the following columns: Open Trunking Re-Route Log Figure 4-3 • 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 A, 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 A, Event Code Tables.
Link Incident Log Figure 4-4 • 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. The Link Incident Log (Figure 4-4) displays Fibre Channel link incident events recorded at the SANpilot interface. Entries reflect the cause of the link incident.
Viewing the Security Log Select Monitor on the navigation panel. Select the Logs tab; the Logs tab view displays. Select the Security Log link. The Security Log displays in text format, as shown in Figure 4-5. The log displays in a separate browser window. Close the browser window to close the log. The security log provides: Figure 4-5 Clearing the Security Log • Reason: The reason code for the security Event • Date/Time: The date/time when the event occurred.
Viewing the Audit Log Select Monitor on the navigation panel. Select the Logs tab; the Logs tab view displays. Select the Audit Log link. The Audit Log displays in text format, as shown in Figure 4-6. The log displays in a separate browser window. Close the browser window to close the log. The audit lot provides: 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.
Viewing the Fabric Log Select Monitor on the navigation panel. Select the Logs tab; the Logs tab view displays. Select the Fabric Log, either a wrapped or non-wrapped view. TheFabric Log displays in text format, as shown in Figure 4-7. The log displays in a separate browser window. Close the browser window to close the log. 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.
Viewing the Embedded Port Frame Log Select Monitor on the navigation panel. Select the Logs tab; the Logs tab view displays. Select the Embedded Port Frame Log link either a wrapped or non-wrapped view. The Frame Logs listing displays in text format, as shown in Figure 4-10. The log displays in a separate browser window. Close the browser window to close the log. 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.
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-10 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.
Table 4-1 Port State Port Operational States Blue/Green LED Amber LED Alert Symbol Description Inactive On Off Yellow Triangle The port is inactive. The reason appears in the Reason field at the Port Properties dialog box. Not Installed Off Off None An optical transceiver is not installed in the switch port. Not Operational Off Off Yellow Triangle The port is receiving the not operational sequence (NOS) from an attached device.
Table 4-1 Port State Port Operational States (Continued) Blue/Green LED Amber LED Alert Symbol Description Segmented E_Port On Off Yellow Triangle The E_Port is segmented, preventing two connected switches from joining and forming a multiswitch fabric.The reason appears in the Reason field of the Port Properties dialog box. Testing Off Blinking Yellow Triangle The port is performing an internal loopback test. On Blinking Yellow Triangle The port is performing an external loopback test.
Figure 4-11 Monitor Panel (Port List Page) A row of information for each port (0 through 11 inclusive) appears. Each row consists of the following columns: • Port # - Switch port number. • Name - Port name of 24 alphanumeric characters or less. The name typically characterizes the device or fabric element to which the port is attached. • Block Configuration - Indicates if a port is blocked or unblocked. Blocking a port prevents the attached devices or fabric element from communicating.
— Fabric mixed port (FX_Port). This setting also configures a port as a fabric loop port (FL_Port). — Generic port (G_Port). This selection is available only if enabled through an optional PFE key. — Fabric port (F_Port). — Expansion port (E_Port). This selection is available only if enabled through an optional PFE key. Port Stats Page Figure 4-12 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 Port Stats page displays traffic and error statistics for one port. Values update only when the page opens for a selected port or the user selects Get Port Statistics. The page defaults to port 0. Increment or decrement the port number displayed (0 through 11 inclusive) by clicking Fwd>> or <
— CRC errors - Received frames failed cyclic redundancy check (CRC) validation, indicating the frames 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. — Delimiter errors - Received frames had frame delimiter errors, indicating the frame arrived at the switch port corrupted.
Figure 4-13 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 11 inclusive) by clicking Fwd>> or <
• 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).
NOTE: A small form factor pluggable (SFP) optical transceiver must be installed in the port during the test. A device can remain connected during the test. 2. 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. The Operations panel opens with the Switch page displayed. 3. Click the Port and Diagnostics tabs. The Port page displays with the Diagnostics tab selected (Figure 4-14).
b. The message Diagnostics Time Remaining: xx appears, where xx are the seconds remaining in the test. The test takes approximately 30 seconds. NOTE: Click Terminate Port Diagnostics at any time to abort the loopback test. 7. When the test completes, results appear as Passed or Failed in the message area of the dialog box. 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.
8. Click Start Port Diagnostics. The test begins and: a. The Start Port Diagnostics button changes to a Terminate Port Diagnostics button. b. The message Diagnostics Time Remaining: xx appears, where xx are the seconds remaining in the test. The test takes approximately 30 seconds. NOTE: Click 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.
NOTE: An optional full-volatility feature is often required at military sites that process classified data. If the feature is enabled through the switch’s maintenance port, a memory dump file (that possibly includes classified Fibre Channel frames) is not included as part of the data collection procedure. 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-16 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-17).
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. Set the Switch Online or Offline This section describes procedures to set the switch online or offline. These operating states are described as follows: • Online - When the switch is set online, an attached device can log in to the switch if the port is not blocked.
Figure 4-18 Operations Panel (Switch Page with Online State Tab) 3. Click Set Online. The switch comes online and the message Your changes have been successfully activated appears. Set Offline State To set the switch offline 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. The Operations panel opens with the Switch page displayed. 2.
1. When the SANpilot interface opens, the View panel and Switch page appear as the default. At the View panel, select the Configure option at the left side of the panel. The Configure panel opens with the Ports page displayed (Figure 4-19). Figure 4-19 Configure Panel (Ports Page) 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.
Unblock a Port To unblock a switch port 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 Configure option at the left side of the panel. The Configure panel opens with the Ports page displayed (Figure 4-19 on page 4-27). 2. Click the check box for the selected port in the Blocked column to remove the check mark and unblock the port. A blank box indicates the port is unblocked. 3.
3. Gently wipe the end-face and other surfaces of the connector with an alcohol pad as shown in part B of Figure 4-20 on page 4-28. Ensure the pad makes full contact with the surface to be cleaned. Wait approximately five seconds for cleaned surfaces to dry. 4. Repeat step 2 and step 3 of this procedure (second cleaning). 5. Repeat step 2 and step 3 of this procedure again (third cleaning), then reconnect the fiber-optic cable to the port. Power-On Procedure To power on the switch: 1.
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. Notify the customer the switch is to be powered off. 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.
• Ports, causing all Fibre Channel connections to drop momentarily until the connections automatically recover. This causes attached devices to log out and log back in, therefore data frames lost during switch reset must be retransmitted. 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. Switch IML To IML the switch from the front panel: 1.
Manage Firmware Versions Firmware is the switch operating code stored in FLASH memory on the CTP card. Multiple firmware versions can be stored on a browser PC hard drive and made available for download to the switch from the SANpilot interface. Service personnel can perform the following firmware management tasks from the SANpilot interface: Determine Switch Firmware Version Figure 4-21 4-32 • Determine the firmware version actively running on the switch.
2. At the bottom of the page, record the firmware version listed in the Firmware Level field. Add a Firmware Version to the Browser PC Hard Drive The firmware version shipped with the switch is provided on the System Version XX.YY.ZZ CD-ROM. Subsequent firmware versions for upgrading the switch are provided to customers through McDATA’s Internet home page.
Figure 4-23 McDATA File Center (Login Page) 3. Type the user name and password (assigned and registered while performing Task 8: Register with the McDATA File Center on page 2-52) 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-24).
5. Select (highlight) the ES 4300 Firmware option at the list box and click Search. The Documents Match page displays (Figure 4-25) with a list of firmware available for download. Figure 4-25 McDATA File Center (Documents Match Page) 6. Authorization to download a firmware version typically 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-26).
7. 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-27) with the approved request. Figure 4-27 McDATA File Center (Request History Page) 8. In the Action column adjacent to the approved request for the firmware version, click Download.
9. Select the Save this file to disk radio button and click OK. The Save As dialog box appears (Figure 4-29). Figure 4-29 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.
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 hard drive of the browser PC accessing 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-32). Figure 4-32 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.
Figure 4-34 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. The SANpilot interface opens with the View panel open and the Switch page displayed.
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. For instructions, refer to Set the Switch Online or Offline on page 4-25. 3. 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.
Figure 4-36 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.
5 FRU Removal and Replacement This chapter describes removal and replacement procedures (RRPs) used by authorized service representatives for all Sphereon 4300 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. 1.
RRP 1: SFP Optical Transceiver Small form factor pluggable (SFP) optical transceivers are the only concurrent FRUs removed and replaced while the switch is powered on and operational. The FRU has no ESD precaution requirements. Use the following procedures to remove or replace an SFP optical transceiver from the front of the switch chassis. A list of tools required is provided. Refer to Chapter 6, Illustrated Parts Breakdown for FRU locations and part numbers.
4. Block communication to the port. Refer to Block or Unblock a Port on page 4-26 for instructions. 5. Disconnect the fiber-optic jumper cable from the port: a. Pull the keyed LC connector free from the port’s optical transceiver. b. Place a protective cap over the jumper cable connector. 6. The optical transceiver has a wire locking bale to secure the transceiver in the port receptacle and to assist in removal.
b. Grasp the wire locking bale and pull the transceiver from the port receptacle as shown in part (B) of Figure 5-1 on page 5-3. c. At the 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 in the log. Replacement To replace an SFP optical transceiver: 1. Remove the replacement transceiver from its packaging. 2.
7. Open the Switch tab at the View panel and: a. Ensure no amber LEDs illuminate that indicate a port failure. b. Click the graphic representing the port with the replacement transceiver to open the Port Properties tab. Verify port and port technology information is correct. c. 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.
5-6 McDATA Sphereon 4300 Fabric Switch Installation and Service Manual
6 Illustrated Parts Breakdown This chapter provides an illustrated parts breakdown for Sphereon 4300 Switch field-replaceable units (FRUs). Exploded-view assembly drawings are provided for: • Front-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. The parts lists also include McDATA part numbers, descriptions, and quantities.
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 6-2 Front-Accessible FRUs Front-Accessible FRU Parts List Ref. Part Number Description 6-1 002-002688-100 Switch, Sphereon 4300, base assembly -1 803-000054-395 Transceiver, optical, SFP, shortwave laser, LC connector, 1.
Miscellaneous Parts Figure 6-2 illustrates miscellaneous parts. Table 6-2 is the associated parts list. The table includes reference numbers to Figure 6-2, part numbers, descriptions, and quantities. 2 1 Figure 6-2 Table 6-2 3 Miscellaneous Parts Miscellaneous Parts List Ref. Part Number Description Qty.
Power Cords and Receptacles Figure 6-3 illustrates optional power cords and receptacles. Table 6-3 on page 6-5 is the associated parts list. The table includes reference numbers to Figure 6-3, feature numbers, and descriptions.
Table 6-3 Power Cord and Receptacle List Ref. 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-3 6-6 Power Cord and Receptacle List (Continued) Ref. Part Number Description -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.
A Event Code Tables An event is an occurrence (state change, problem detection, or problem correction) that requires user attention or that should be reported to a system administrator or service representative. An event usually indicates a 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 diskette 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 diskette 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 diskette 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 diskette 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. Action: Reduce the ISLs on the indicated fabric element to a number within the limits specified. Event Data: Byte 0 = domain ID of the fabric element (director or switch) with too many ISLs.
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 diskette 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 fabric binding and switch binding parameters for this switch and the attached fabric element must agree. At the Fabric Binding and 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 an 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 diskette to McDATA support personnel.
Fan Events (300 through 399) Event Code: 300 Message: Cooling fan propeller failed. Severity: Major. Explanation: One cooling fan (out of three) 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 switch. Event Data: The first byte of event data (byte 0) specifies the failed fan number (0 through 2 inclusive).
Event Code: 302 Message: Cooling fan propeller failed. Severity: Major. Explanation: Three cooling fans (out of three) 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 switch. Event Data: The first byte of event data (byte 0) specifies the failed fan numbers (0 through 2 inclusive).
Event Code: 311 Message: Cooling fan propeller recovered. Severity: Informational. Explanation: Two cooling fans (out of three) 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 2 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 diskette 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 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 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. Distribution: Bytes 6 and 7 = interim release level (zz).
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. Distribution: Switch Management Server SANpilot Event Log System Error LED ✔ ✔ Event Log E-Mail Host Call-Home Sense Info Link Incident ✔ Event Code: 442 Message: Embedded port anomaly detected.
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 diskette to McDATA support personnel. Perform a switch reset. If the problem persists, replace the switch. Event Data: Byte 0 = port number (00 - 11).
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 - 11). 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 - 11). 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 - 11). 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 - 11).
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 diskette to McDATA support personnel. Perform a switch reset. If the problem persists, replace the switch. Event Data: No supplementary data included with the event.
A-38 McDATA Sphereon 4300 Fabric Switch Installation and Service Manual
Index A AC power receptacle, location 1-3 applications diagnostic features 1-11 SANpilot interface 1-11 attention statements xvii B binding fabric configure 2-32 description 2-32 port configure 2-26 description 2-26 switch configure 2-27 description 2-27 block ports 4-26 C clean fiber-optic components 4-28 clear event log entries 4-6, 4-7, 4-8, 4-10, 4-11 clearances 1-7 command line interface disable 2-23 enable 2-23 compliance statements Class 1 laser transceiver xvi CNS mark xvi European Union conform
Index default maintenance port password 2-43 SANpilot interface password 2-8 SANpilot interface user name 2-8 switch gateway address 2-1, 3-1 switch IP address 2-1, 3-1 switch passwords 2-1, 3-1 switch subnet mask 2-1, 3-1 dimensions 1-7 disable EFM 2-34 OSMS 2-24 download firmware 4-38 E E_D_TOV 2-17 E_Port configuring 2-8 description 1-2 PFE key requirement 1-2 segmented 3-54 enable EFM 2-34 OSMS 2-24 enterprise fabric mode disable 2-34 enable 2-34 environment operating 1-8 shipping 1-8 storage 1-8 ERR
Index add version to browser PC 4-33 determine version 4-32 download 4-38 FL_Port configuring 2-8 description 1-2 FRU removal SFP transceiver 5-2 tools required 5-2 FRU replacement SFP transceiver 5-4 tools required 5-2 FRUs description 1-3 illustrated parts breakdown 6-1 SFP transceiver 1-4 status LEDs 1-6 full-volatility feature 4-23 G gateway address change switch address 2-19, 2-40 switch default 2-1, 3-1 H heat dissipation 1-7 I illustrated parts breakdown front-accessible FRUs 6-2 miscellaneous pa
Index Event Log 4-3 Link Incident Log 4-5 Open Trunking Re-Route Log 4-4 loopback plug description 1-14 illustration 1-14 loopback test description 4-19 external 4-21 internal 4-19 M MAC address, switch 2-39 maintenance analysis procedures MAP 0000 - Start MAP 3-6 MAP 0100 - Power distribution analysis 3-18 MAP 0200 - POST failure analysis 3-21 MAP 0300 - Loss of web browser PC communication 3-23 MAP 0400 - FRU failure analysis 3-30 MAP 0500 - Port failure and link incident analysis 3-35 MAP 0600 - Fabric
Index connecting 2-5 illustrated parts breakdown 6-4 power requirements 1-7 power supply description 1-4 fault isolation 3-18 power-off procedure 4-30 power-on procedure 4-29 precautions ESD xx general xx preferred domain ID 2-14 procedural notes 4-2, 5-1 procedures data collection 4-22 fault isolation 3-1 FRU remove and replace 5-2 installation 2-2 power-off 4-30 power-on 4-29 repair 4-1 publications, related xiv PWR LED description 1-6 location 1-3 R R_A_TOV 2-17 related publications xiv remove and repl
Index firmware 4-32 FRU removal and replacement 5-1 FRUs 1-3 illustrated parts breakdown 6-1 illustration 1-2 installation 2-3 installation options 2-2 maintenance analysis procedures 3-1 maintenance approach 1-8 management 1-9 repair procedures 4-1 specifications 1-7 storage environment 1-8 subnet mask change switch value 2-19, 2-40 switch default 2-1, 3-1 switch binding configure 2-27 description 2-27 switch binding membership list configuring 2-31 overview 2-28 switch identification, configure 2-11 swit
