Specifications

ManualsBrandsMcDATA ManualsNetwork RouterULTRANETTM EDGE STORAGE ROUTER 3000

UltraNet™ Edge Storage Router

3000

Release 3.1.5

Release Notes

P/N 958-000502-315 REV A

Summary of content (56 pages)

PAGE 1
UltraNet™ Edge Storage Router 3000 Release 3.1.
PAGE 2
Record of Revisions and Updates Revision Date Description 958-000502-000 8/2005 Release notes for release 3.1.2 under the McDATA brand. 958-000502-313 11/2005 Release notes for release 3.1.3. 958-000502-314 4/2006 Release notes for release 3.1.4. 958-000502-315 7/2006 Release notes for release 3.1.5. Copyright © 2005 - 2006 McDATA Corporation. All rights reserved.
PAGE 3
Contents Chapter 1 Introduction What’s New With the Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Minimum Software Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Minimum Hardware Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 4
Supported McDATA Sphereon and Intrepid Models . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Connector Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Required McDATA Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Cascaded Switches and Preferred Path . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Required Switch Settings for Edge Configurations . . . . . . . . . . . . . . . . . .
PAGE 5
Chapter 3 UltraNet ConfigManager New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Licensing Highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 6
McDATA i10k, 6140, 6064, and 3232 Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3 McDATA UMD Switch (Firmware Revision 1.5 or above) . . . . . . . . . . . . . . . . . . . . B-5 Cisco MDS 9000 Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5 FICON Emulation Requirements for Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 7
Tables Table 1-1 Differences between Old and New ATM cards . . . . . . . . . . . . . . . . . . 1-1 Table 1-2 Minimum Hardware Levels for the Release . . . . . . . . . . . . . . . . . . . . . 1-2 Table 1-3 Compatible Operating System (OS) Versions . . . . . . . . . . . . . . . . . . . 1-4 Table 1-4 Fibre Channel Card Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Table 2-1 Supported Edge Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 8
viii UltraNet Edge Storage Router - 3000 Series 3.1.
PAGE 9
Chapter 1 Introduction This chapter provides a brief description of new features, minimum hardware and software levels, and the compatibility requirements for the release of the UltraNet Edge Storage Router - 3000 Series (“UltraNet Edge 3000”). What’s New With the Release Environmental concerns and the desire to protect human health, has led the EU (European Union) to issue the Restriction of Hazardous Substances (RoHS) directive.
PAGE 10
Introduction Overview Overview The UltraNet Edge 3000 interconnects Fibre Channel fabrics over extended distances, using a new or existing IP or ATM network. The UltraNet Edge 3000 can be customized and configured as 1x1 and 2x2 configurations in an IP, or ATM WAN implementation. Note: 1x2, 2x1, and 3x1 configurations are possible, but not supported as a standard implementation. The UltraNet Edge 3000 has been designed to be user installable, configurable, and maintainable.
PAGE 11
Introduction Minimum Hardware Levels Table 1-2 Minimum Hardware Levels for the Release (continued) Part Number Description Revision Note: Revision D of the FCBB card (part number 20501792) ships with the v3.1.1.4 or greater release. If you are upgrading from v3.1.1.3, Revision D is required only if you are running the Edge v3.1.1.4 or greater with the FC/9000 or if you are enabling Disk Streaming.
PAGE 12
Introduction Compatibility Requirements Hardware Requirements for Disk Streaming Disk Streaming requires revision D of the FCBB card (part number 20501792) and revision 16 of the FPGA, which resides on the FCBB card. To determine the FPGA revision level for E_Port configurations, use the following commands: • For E_Port configurations, use the fccnt dump backbone command. • For F_Port configurations, use the fccnt dump switchport command.
PAGE 13
Introduction Fibre Channel Card Dependencies Fibre Channel Card Dependencies The UltraNet Edge 3000 supports two types of Fibre Channel cards; FCBB or FCXL2. The FCBB card is standard, the FCXL2 card is only used for FC/SCSI Tape Pipelining (Device Extension) implementations. Table 1-4 explains the configurations that can be run with each card.
PAGE 14
Introduction Fibre Channel Card Dependencies FC/SCSI E_Port to E_Port When an UltraNet Edge 3000 is configured for E_port, its peer UltraNet Edge 3000 must also be configured as E_port. FC/SCSI F_port Configurations F_port is a port in the fabric where an N_port can attach. F_ports are frame routing ports, which are insensitive to higher level protocols. A port configured for F_port can only connect to another N_port via a point-to-point connection.
PAGE 15
Introduction Fibre Channel Card Dependencies FC/SCSI N_Port to N_Port When an UltraNet Edge 3000 is configured for N_port, its peer UltraNet Edge 3000 must also be configured as N_port.
PAGE 16
Introduction FC/SCSI Tape Pipelining (Device Extension) Requirements FICON N_Port to N_Port In this configuration, the Edge 3000 FICON port on one side is directly connected to a Channel Interface and the remote side is directly connected to a Control Unit interface. This configuration is defined the same as the F_port to N_port configuration described in the prior section.
PAGE 17
Chapter 2 Fibre Channel Switch Requirements This chapter provides configuration information for the internal Fibre Channel Switch (FCSW) application for the UltraNet Edge 3000, the certified models of McDATA, Cisco, and Brocade Fibre Channel switches, and the supported configurations and configuration requirements for the Brocade Multiprotocol Router.
PAGE 18
Fibre Channel Switch Requirements FCSW - Internal Fibre Channel Switch Application FCSW - Internal Fibre Channel Switch Application The UltraNet Edge 3000 contains an application (FCSW) which acts as a Fibre Channel switch and eliminates the need for an external switch. Note: FICON connections cannot be defined through an UltraNet Edge 3000 F_Port interface.
PAGE 19
Fibre Channel Switch Requirements Supported McDATA Sphereon and Intrepid Models Supported McDATA Sphereon and Intrepid Models The following McDATA models are supported with the UltraNet Edge 3000 for FC/SCSI E_port, N_port, NL_port, and FICON configurations, as appropriate.
PAGE 20
Fibre Channel Switch Requirements Supported McDATA Sphereon and Intrepid Models Table 2-2 Required Connector Types for McDATA Switches (continued) McDATA Model McDATA Media McDATA Connector Type Edge Connector Type 6140 SFP LC LC 10000 SFP LC LC Required McDATA Firmware This section provides the required firmware version for use with the supported McDATA models.The UltraNet Edge 3000 supports 1x1 and 2x2 configurations with all McDATA firmware releases.
PAGE 21
Fibre Channel Switch Requirements Supported McDATA Sphereon and Intrepid Models Required Switch Settings for Edge Configurations Use the following settings for Edge E_port and FICON ISL configurations: • • • • Port – E-Port – 2 Gb Switch Parameters – Preferred Domain ID: 3 (any unique domain) – Rerouting Delay: Disabled Switch Fabric Parameters – R_A_TOV: 100 – E_D_TOV: 50 – Interop Mode: Open Fabric 1.0 Device connection: any port Note: Only WWN Zoning will be allowed.
PAGE 22
Fibre Channel Switch Requirements Supported McDATA FC/9000 and UMD Models Supported McDATA FC/9000 and UMD Models Table 2-4 lists the models certified with the UltraNet Edge 3000 for FC/SCSI E_port, N_port, NL_port, and FICON configurations, and shows the supported firmware versions. Table 2-4 Supported Models and Required Firmware Model Supported Firmware FC9000 5.0.0.0 5.0.4.0 (recommended) UMD 1.5.0.0 (recommended) Note: Recommended Enterprise Manager code level: 9.
PAGE 23
Fibre Channel Switch Requirements Supported Cisco Models Supported Cisco Models Table 2-5 lists the Cisco switch models certified with the UltraNet Edge 3000 for FC/SCSI E_port, N_port, and NL_port, configurations (no FICON support at this time). Table 2-5 Supported Cisco Models and Required Firmware Cisco Model Required Firmware 9216, 9509 2.0.2b 2.1.2b 2.1.
PAGE 24
Fibre Channel Switch Requirements Supported Brocade Models Supported Brocade Models Table 2-6 lists the Brocade switch models that McDATA has certified with the UltraNet Edge 3000 for FC/SCSI E_port, N_port, or NL_port configurations (no FICON support at this time).
PAGE 25
Fibre Channel Switch Requirements Requirements for Brocade Switches Requirements for Brocade Switches The settings for Brocade switches vary depending upon which UltraNet Edge 3000 configuration is implemented (E-port Extension or Device Extension [Tape Pipelining]). Use the Brocade settings shown in the following sections.
PAGE 26
Fibre Channel Switch Requirements Requirements for Brocade Switches Table 2-8 Required Brocade Firmware (continued) Brocade Model Compatible Applications Brocade 7420 Xpath OS 7.3.0 (recommended) for most applications Note: E_port mode must be turned on when using the Xpath OS. Follow the procedure found in the section “Configuring the Port Settings for Brocade Switch AP7420” on page 2-15.
PAGE 27
Fibre Channel Switch Requirements Requirements for Brocade Switches Switch:admin> portcfgshow Ports 0 1 2 3 4 5 6 7 -------------------+--+--+--+--+----+--+--+-Speed 2G AN AN AN AN AN AN AN Locked L_Port .. .. .. .. .. .. .. .. Locked G_Port .. .. .. .. .. .. .. .. Disabled E_Port .. .. .. .. .. .. .. .. Persistent Disable .. .. .. .. .. .. .. .. ISL R_RDY Mode .. .. .. .. .. .. .. .. where AN:AutoNegotiate, ..:OFF, ??:INVALID. The speed for port 0 (zero) is changed to 2Gig (2G). 3.
PAGE 28
Fibre Channel Switch Requirements Requirements for Brocade Switches switchId: switchWwn: switchBeacon: Zoning: port 0: id 2G port 1: id N2 port 2: id N2 port 3: id N2 port 4: id N2 port 5: -- N2 port 6: -- N2 port 7: -- N2 Switch:admin> fffc02 10:00:00:60:69:c0:0b:1b OFF ON (Active) Online E_port 20:00:00:00:88:19:71:ca (upstream) No_Light No_Light No_Light No_Light No_Module No_Module No_Module In the preceding output, 2G Online.....
PAGE 29
Fibre Channel Switch Requirements Requirements for Brocade Switches 2. To configure the port speed, use the applicable command syntax: • For a Brocade 3250, 3850, 3900, or 4100, enter the portcfgspeed 0 2 command: Switch:admin> portcfgspeed 0 2 Example of the portcfgspeed 0 2 command screen display: Success: configuration allowed. Committing configuration...done. Switch:admin> portcfgshow Ports 0 1 2 3 4 5 6 7 -------------------+--+--+--+--+----+--+--+-Speed 2G AN AN AN AN AN AN AN Locked L_Port .. ..
PAGE 30
Fibre Channel Switch Requirements Requirements for Brocade Switches fabric: Subordinate switch fabric: Domain 2,1 • For a Brocade 12000 or 24000, use the following syntax: Usage: portCfgISLMode [SlotNumber/]PortNumber Mode Example of the portcfgISLMode command screen display: Ports 0 1 2 3 4 5 6 7 -------------------+--+--+--+--+----+--+--+-Speed 2G AN AN AN AN AN AN AN Locked L_Port .. .. .. .. .. .. .. .. Locked G_Port .. .. .. .. .. .. .. .. Disabled E_Port .. .. .. .. .. .. .. ..
PAGE 31
Fibre Channel Switch Requirements Requirements for Brocade Switches switchDomain: switchId: switchWwn: switchBeacon: Zoning: port 0: id 2G port 1: id N2 port 2: id N2 port 3: id N2 port 4: id N2 port 5: -- N2 port 6: -- N2 port 7: -- N2 Switch:admin> 2 fffc02 10:00:00:60:69:c0:0b:1b OFF ON (Active) Online E_port 20:00:00:00:88:19:71:ca (upstream) No_Light No_Light No_Light No_Light No_Module No_Module No_Module In the preceding output, 2G Online.....
PAGE 32
Fibre Channel Switch Requirements Requirements for Brocade Switches 3. Enter the portdisable command to disable the port before a configuration change can be made: Switch:admin>portdisable 0 Example of the portdisable command screen display: port 0 disabled 4. To configure the port speed, use the following command syntax: Switch:admin>portcfgspeed 0 2 Example of the portcfgspeed command screen display: port 0 speed is set to: 2G 5.
PAGE 33
Fibre Channel Switch Requirements Requirements for Brocade Switches Viewing the E_Port Mode To view the E_Port mode, use the following command syntax: Switch:admin>portcfgeport 0 Example of the portcfgeport command screen display: port 0 eport mode is: ENABLED 2-17
PAGE 34
Fibre Channel Switch Requirements Configuring a Brocade for Use with a UltraNet Edge 3000 Configuring a Brocade for Use with a UltraNet Edge 3000 In addition to configuring the Brocade switch settings for use with the UltraNet Edge 3000, you may need to configure the Flow Control Mode in UCM if the Remote Switch License is installed. It is recommended for Brocade Series 3000 switches, the Brocade port connected to the UltraNet Edge 3000 is configured to 2Gbps.
PAGE 35
Fibre Channel Switch Requirements Configuring a Brocade for Use with a UltraNet Edge 3000 Switch Settings Without the RSL for Use with the UltraNet Edge 3000 Use the following Brocade switch settings with the UltraNet Edge 3000 when you are not using the Remote Switch License (RSL) and the UltraNet Edge 3000 is configured as E-port Extension. The BBCredits are not a required configuration on the Brocade switch when configuring the UltraNet Edge 3000 for E-port Extension (16 is the default).
PAGE 36
Fibre Channel Switch Requirements Configuring a Brocade for Use with a UltraNet Edge 3000 Configuring the UltraNet Edge 3000 for Brocade Remote Switch License When using the Brocade Remote Switch License (RSL) with a UltraNet Edge 3000, use UltraNet ConfigManager to configure the UltraNet Edge 3000 Fibre Channel interface to run with RSL. The No Remote Switch License (Flow Control Mode 2) option in (UCM) is the default.
PAGE 37
Fibre Channel Switch Requirements PID Format Settings PID Format Settings The required PID format settings for the Brocade Fibre Channel switches are determined by the series/model of the Brocade switch and the firmware level used. Note: The PID format settings should be consistent throughout the fabric. Table 2-9 provides the required PID format settings for Brocade 2000 series/models.
PAGE 38
Fibre Channel Switch Requirements Brocade Switch Settings Matrix for all Edge Series Brocade Switch Settings Matrix for all Edge Series Table 2-10 shows Brocade switch settings for all Edge models. Table 2-10 Brocade Switch Settings for all Edge Models Brocade Switch Settings Edge 3000 Series (FCXL2) Tape Pipelining (N or NL_port) Edge 3000 Series (FCBB) E_port or F_port • fabric.domain: N/A 3 (any unique domain) • fabric.ops.BBCredit: 7 Not required (16 default) • fabric.ops.
PAGE 39
Fibre Channel Switch Requirements Mapping a Device to a Specific E_port Connection Mapping a Device to a Specific E_port Connection The uRouteConfig command can be used to map connections to a specific E_port connection on the Edge. The following section provides the applicable configuration settings. The uRoute information is specific to each Brocade switch. Each Brocade switch in the fabric must be configured with the applicable uRoute information.
PAGE 40
Fibre Channel Switch Requirements Supported Compatibility with the Brocade Multiprotocol Router Supported Compatibility with the Brocade Multiprotocol Router The UltraNet Edge 3000 3.1.4 release provides compatibility with the Brocade Multiprotocol Router. When the Brocade Multiprotocol Router is used in combination with the UltraNet Edge 3000, it allows disk and tape applications to be extended across multiple SANs, regardless of location.
PAGE 41
Chapter 3 UltraNet ConfigManager This chapter provides the supported UltraNet Edge 3000 versions for the UltraNet ConfigManager software. UltraNet ConfigManager (UCM) is a graphical configuration tool that provides a point-and-click process for designing and configuring UltraNet Edge Storage Router nodes. This tool allows the user to self-configure and manage configuration modifications. This appendix provides the following information about the UCM 5.6.
PAGE 42
UltraNet ConfigManager Application Licensing Application Licensing UCM 5.6.1 includes application licensing for USD and USD-X series nodes. However, an application license is not required for Edge 3000 series node. Edge 1000 and Edge 3000 series nodes are automatically enabled. When installing UCM 5.6.1, the following Enter License Information (OPTIONAL) screen is displayed. The Product I.D. and Install Key are not required for UltraNet Edge-only installations.
PAGE 43
UltraNet ConfigManager Supported Operating Systems Application Licensing Highlights • When you install UCM, you are prompted to enter a product ID and installation key. If you do not enter a product ID and installation key, UCM is installed but only Edge nodes are enabled. • Product ID and Installation Key are obtained from Technical Support. • Provides support for an expiration date. If you do not enter a product ID and installation key, there is no expiration date.
PAGE 44
UltraNet ConfigManager Procedures for Changing the Default Software Version Procedures for Changing the Default Software Version The default Edge 3000 software version can be changed for the entire network or for the existing nodes on the Network Map. Changing the Default Version for the Entire Network Use the following procedure to change the default Edge 3000 software version for the entire network. Note: This change takes effect for the next node that is added to the Network Map.
PAGE 45
Chapter 4 UltraNet WebView UltraNet WebView This chapter provides the supported platforms, internet browsers, and minimum system requirements for the UltraNet WebView software. UltraNet WebView is an optional software tool that is browser-based and allows the user to monitor the network and the UltraNet Edge Storage Router 3000 remotely from any global location. WebView 3.4.
PAGE 46
UltraNet WebView Compatibility Requirements Java Plug-In The supported browser, Internet Explorer requires a plug-in for the Java applets to function properly in WebView. The required plug-in is Java(TM) 2 Runtime Environment, Standard Edition, version 1.4.2_06. Note: If you do not have external web access, download the plug-in (j2re-1_4_2_06-windows-i586-p.exe) from the WebView CD-ROM.Internet Explorer requires that you download an executable file and install the plug-in.
PAGE 47
Appendix A Resolved Defects and Known Issues This appendix provides the resolved Product Defects and Service Requests and a list of Known Issues at the time of the UltraNet Edge 3000 3.1.5 release. Resolved Service Requests and Product Defects Table A-1 provides a brief description of the problem and the customer impact prior to the fix. Table A-1 Resolved SRs and PDs in the Edge 3.1.
PAGE 48
Resolved Defects and Known Issues Resolved Service Requests and Product Defects A-2 UltraNet Edge Storage Router - 3000 Series 3.1.
PAGE 49
Appendix B Feature and Compatibility Matrix Edge Features, UCM, and Webview Compatibility Table B-1 lists the Edge 3000 releases and shows the compatible versions of UltraNet ConfigManager and WebView, related features, and release notes versions.
PAGE 50
Feature and Compatibility Matrix Edge Features, UCM, and Webview Compatibility Release Version 3.1.2 Tape Pipelining Table B-1 Edge 3000 Releases by Application and Feature UCM WebView Version Version Features Released Release Notes X 5.2.
PAGE 51
Appendix C Switch Considerations for FICON This appendix describes fibre channel switch considerations for Edge 3000 FICON extension. FICON Director (Switch) Considerations There are 3 key things to consider when working in FICON configurations with switches. • Whether or not an ISL is involved, and if so, ensuring that ISL paths are properly configured. • What the Fibre Channel bb-credits value should be. • What the Fibre Channel ports speeds should be set to.
PAGE 52
Switch Considerations for FICON Customer Impact Customer Impact Fibre Channel links may fail to properly initialize if these guidelines are not followed. In addition, having the bb_credits too low will result in device paths not coming online or Fibre Channel aborts (MVS interface control checks). FICON emulation will fail if all the frames associated with a device do not cross the same ISL.
PAGE 53
Switch Considerations for FICON McDATA i10k, 6140, 6064, and 3232 Switches Setting the Fibre Channel Port Speed All Fibre Channel switches allow a port to be set to auto negotiation , 1 Gbps or 2 Gbps. Ultranet Fibre Channel link startup is more efficient and more reliable when the Fibre Channel ports are set to a specific speed, when available. Most devices and IBM host channels are not configurable.
PAGE 54
Switch Considerations for FICON McDATA i10k, 6140, 6064, and 3232 Switches A McDATA switch port defined as FICON (S/390 mode) automatically behaves as a G-Port (generic port). You are not able to set the port type as you can for open systems. G-Ports first attempt to bring up a link as an ISL (E-Port). If attached to a non-ISL device, the port automatically switches to an F-Port. In general the Firmware Revision should be 08.00.00 or above.
PAGE 55
Switch Considerations for FICON McDATA UMD Switch (Firmware Revision 1.5 or above) McDATA UMD Switch (Firmware Revision 1.5 or above) The McDATA UMD has a feature called "flow groups" that must be enabled in cascaded configurations in order for Ultranet FICON emulation support to operate correctly. In the case of XRC operations in UMD cascaded configurations that have multiple extended ISLs, channel detected errors will occur when the "flow groups" feature is not enabled or defined correctly.
PAGE 56
Switch Considerations for FICON FICON Emulation Requirements for Switches There are features in all the McDATA switch products that can be used to define rules for ISL usage. The switch specific rules are used to select the ISL that is used for a combination of inbound ports referencing a remote switch domain. Rules can be defined within the Switch Configuration to at least encourage the switch to route the traffic over a specific ISL.