Brocade Communications Systems PowerConnect B-RX Release Note
  1. Manuals
  2. Brands
  3. Brocade Communications Systems Manuals
  4. Software
  5. PowerConnect B-RX
  6. Release note
Brocade Communications Systems PowerConnect B-RX Release Note

Brocade Communications Systems PowerConnect B-RX Release Note

Multi-service ironware software r02.7.02a for brocade bigiron rx series switches
Hide thumbs Also See for PowerConnect B-RX:
Table of Contents

Advertisement

Quick Links

Download this manual
Multi-Service IronWare Software
R02.7.02a for Brocade BigIron RX

Series Switches

Release Notes v1.0
October 2, 2009
Document History
Document Title
Multi-Service IronWare Software R02.7.02a for
Brocade BigIron RX Series Switches Release
Notes v1.0
Summary of Changes
Release 02.7.02a
Publication Date
October 2009

Advertisement

Table of Contents
loading

Related Manuals for Brocade Communications Systems PowerConnect B-RX

Summary of Contents for Brocade Communications Systems PowerConnect B-RX

  • Page 1: Series Switches

    Multi-Service IronWare Software R02.7.02a for Brocade BigIron RX Series Switches Release Notes v1.0 October 2, 2009 Document History Document Title Summary of Changes Publication Date Multi-Service IronWare Software R02.7.02a for Release 02.7.02a October 2009 Brocade BigIron RX Series Switches Release Notes v1.0...
  • Page 2 Copyright © 2009 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, IronPoint, IronShield, IronView, IronWare, JetCore, NetIron, SecureIron, ServerIron, StorageX, and TurboIron are registered trademarks, and DCFM, Extraordinary Networks, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. All other brands, products, or service names are or may be trademarks or service marks of, and are used to identify, products or services of their respective owners.

  • Page 3: Table Of Contents

    Contents Supported devices for Multi-Service IronWare R02.7.02a ........5   Feature support ......................5   Supported features ........................ 5   Unsupported features ......................10   Software image files for Multi-Service IronWare R02.7.02a ......10     Software image files ......................10 Images and procedures required ..................
  • Page 4 Technical support ....................33   General Information ......................33   Getting Help or Reporting Errors ..................34   Web Access ..........................34  Email Access ..........................34  Telephone Access ........................34  Additional resources ....................35   Documentation Update ..................36   Defects ........................

  • Page 5: Supported Devices For Multi-Service Ironware R02.7.02A

    Supported devices for Multi-Service IronWare R02.7.02a This software release applies to the following Brocade products: BigIron RX-4 Switch • BigIron RX-8 Switch • BigIron RX-16 Switch • BigIron RX-32 Switch • Note: The software release described in these release notes can only be used on the devices specified above.
  • Page 6 Category Feature description  Serial and Telnet access to industry-standard Command Line Management Options Interface (CLI) SSHv2 TFTP Web-based GUI SNMP versions 1, 2, and 3 IronView Network Manager  AAA Authentication Security Local passwords RADIUS Secure Shell (SSH) version 2 Secure Copy (SCP) TACACS/TACACS+ User accounts...
  • Page 7 Category Feature description  Multiple Spanning Tree Protocol (MSTP) 802.1s  Rapid Spanning Tree Protocol (RSTP) 802.1w  Port Security 802.1x  Dynamic Link Aggregation on tagged and untagged trunks 802.3ad  Layer 2 jumbo packet support Jumbo packets  Layer 2 Hitless failover ...
  • Page 8 Category Feature description  802.1Q tagging VLANs Port-based VLANs Super Aggregated VLANs (SAV) Dual-mode VLAN ports Transparent Port Flooding VLAN ID to MSTP Instance Pre-assignment Private VLANs  Layer 2 Virtual Switch Redundancy Protocol (VSRP) VSRP Layer 3 Virtual Switch Redundancy Protocol (VSRP) VSRP and MRP Signaling ...
  • Page 9 Category Feature description  Routes IP Static entries ARPs Virtual interfaces Secondary addresses  Routes IS-IS BGP peers BGP dampening  Multicast cache Multicast Routing L2 IGMP table DVMRP routes PIM-DM PIM-SM PIM-SSM IGMP v1, v2, v3 snooping PIM-SM snooping (IPv4 only) ...

  • Page 10: Unsupported Features

    Unsupported features The following features are not supported in software release 02.7.02 on BigIron RX:  AppleTalk  Dynamic IP Routing   Mirroring across VLANs  MPLS   RARP  VLANs  VLAN translation  Subnet VLANs  Source IP Port Security Summary of Enhancements and Configuration Notes in Release 02.7.02a...

  • Page 11: Images And Procedures Required

    Module Image type Image name BigIron RX-32 mbridge32 Interface Module Boot and Monitor rlb02702a.bin IronWare rlp02702a.bin Images and procedures required The software images required and the procedures for upgrading have been changed as described in the following sections:  Upgrading Software Images as Required by Version – This sub-section describes the procedures required for your software upgrade depending upon the version you are upgrading from or to.

  • Page 12: Displaying Flash Memory And Version Information

    Displaying flash memory and version information Prior to upgrading the images on a BigIron RX Series switch, it is advisable to check the versions already installed. This allows you to determine which versions need to be upgraded. It is also useful to check the versions installed immediately after an upgrade has been done to make sure that you have installed the versions required in your installation.

  • Page 13: Displaying Flash Information

    Displaying flash information You can display information concerning the contents of a BigIron RX using the show flash command as shown in the following:   BigIron RX# show flash ==================================================================== Active Management Module (Right Slot) Code Flash - Type MT28F128J3, Size 32 MB o IronWare Image (Primary) Version 2.7.2aT143, Size 4461603 bytes, Check Sum de1d Compiled on Jul...
  • Page 14 Modified on 07:29:20 GMT+00 Thu Oct 04 1900 Boot Flash: Type AM29LV040B, Size 512 KB o Boot-Monitor Image Version 2.7.2aT145, Size 431766 bytes, Check Sum d035 Compiled on JUN 28 2009 at 01:08:52 labeled as rmb02702a ==================================================================== Line Card Slot 1 Code Flash: Type MT28F640J3, Size 16 MB o IronWare Image (Primary) Version 2.7.2aT157, Size 2308296 bytes, Check Sum 507c...

  • Page 15: Code Flash And Boot Flash Information

    Code flash and boot flash information This field... Displays… Management Modules <type> Management Module The management module for which flash information is displayed. (<location>) The <type> parameter indicates an active or standby management module. The <location> parameter indicates the top or bottom slot (M1 or M2, respectively).
  • Page 16 LP IronWare Image (Primary or Indicates the interface modules’ primary and/or secondary IronWare Secondary for Module Type 0) image stored in the management module’s code flash if you copied the primary and/or secondary IronWare image to all interface modules using the copy command with the all keyword.
  • Page 17 Boot-Monitor Image Indicates the boot image installed in the management module’s boot flash. The output displays the following information about the image:  Version – “2.2.1Txxy” indicates the image version number. The “Txxy” is used by Brocade for record keeping. The “xx” indicates the hardware type, while the “y”...
  • Page 18 Boot-Monitor Image Indicates the monitor image installed in the interface module’s code flash. The image must be imlb<xxxxx>. The output displays the following information about the image:  Version – “2.2.1Txxy” indicates the image version number. The “Txxy” is used by Brocade for record keeping. The “xx” indicates the hardware type, while the “y”...

  • Page 19: Displaying Version Information

    Displaying version information You can display version information for a BigIron RX using the show version command as shown in the following: BigIron RX# show version   ========================================================================== HW: BigIron RX Router BI-RX-4-S Backplane (Serial #: SA35085096, Part #: 35550-000B) RX-BI-SFM1 Switch Fabric Module 1 (Serial #: SA32080792, Part #: 35548-001B) FE 1: Type fe200,...
  • Page 20 FAP 1 version: 3 FAP 2 version: 3 FAP 3 version: 3 FAP 4 version: 3 660 MHz Power PC processor 440GP (version 8020/0020) 330 MHz bus 512 KB Boot Flash (AM29LV040B), 16 MB Code Flash (MT28F640J3) 512 MB DRAM, 8 KB SRAM, 0 Bytes BRAM LP Slot 1 uptime is 1 minutes 50 seconds ========================================================================== SL 2: RX-BI-24HF 24-port 1 GbE Hybrid Module (Serial #: SA46050295, Part #: 31593-...

  • Page 21: Backing Up The Current Software Images

    Backing up the current software images Before performing a software upgrade, Brocade recommends backing up the following current software images in the device’s flash memory. Syntax: cp <original-file-name> <backup-file-name> Upgrading the monitor and boot images You can upgrade the management module’s monitor and boot images simultaneously. Brocade highly recommends that the interface monitor and boot images be upgraded to the same software release version as the management module images to keep both code images synchronized on the same version.

  • Page 22: Unified Software Image Upgrade

    dir /<path-name>/ (if the destination is slot 1 or 2) • Check for the boot image, monitor image, and the date and time at which the new images were built. If you want to upgrade other software images, go to the appropriate upgrade section for information.

  • Page 23: Separation Of Boot And Monitor Images

    modules that you already own. They can work properly but must be installed as described in the following: Separation of boot and monitor images Beginning with version 02.5.00 and later of the Multi-Service IronWare software, the boot and monitor images no longer need to be upgraded with each release. ...

  • Page 24: Upgrading The Management Module Ironware Image

    BigIron RX#copy tftp flash 10.10.12.12 rmb02702a.bin monitor copy-boot Verify that the new monitor and boot images have been successfully copied to flash or slot 1 or 2 by entering one of the following commands at the Privileged EXEC level of the CLI: show flash •...

  • Page 25: Upgrading The Interface Module Monitor And Boot Images

    Upgrading the interface module monitor and boot images We recommend that you perform this upgrade procedure from a PC or terminal that is directly connected to the management module’s Console port. You can also perform this procedure via a Telnet or SSHv2 session.

  • Page 26: Upgrading Mbridge Fpga On The Management Module

    Copy the new IronWare image from the TFTP server or a flash card in slot 1 or 2 to all interface modules or an interface module in a specified chassis slot. To perform this step, enter one of the following commands at the Privileged EXEC level of the CLI (example: BigIron RX#): copy tftp lp <TFTP-server-ip-addr>...
  • Page 27 MBRIDGE versions required per software version Software Current MBRIDGE image Interface module image installed on BigIron RX 02.4.00 MP ( Management Module) 02.4.00a MP ( Management Module) 02.4.00b MP ( Management Module) 02.4.00c MP ( Management Module) 02.4.00d MP ( Management Module) 02.4.00e MP ( Management Module) 02.4.00f...
  • Page 28 Software image FPGA image Compatible FPGA installed on version BigIron RX 02.5.00 SBRIDGE 02.5.00a SBRIDGE 02.5.00b SBRIDGE 02.5.00c SBRIDGE 02.5.00d SBRIDGE 02.5.00e SBRIDGE 02.5.00f SBRIDGE 02.5.00g SBRIDGE 02.5.00h SBRIDGE 02.5.00i SBRIDGE 02.5.00j SBRIDGE 02.6.00 SBRIDGE 02.6.00a SBRIDGE 02.6.00b SBRIDGE 02.6.00c SBRIDGE 02.6.00d SBRIDGE...

  • Page 29: Rebooting The Management Module

    Rebooting the management module After upgrading one or more software images on the management or interface module, you must reboot the management module. After the management module reboots, it in turn reboots the interface modules. To reboot the management module, enter one of the following commands: ...

  • Page 30: Hitless Layer 2 Os Upgrade

    Hitless Layer 2 OS upgrade Hitless O/S upgrades are supported for Layer 2 switching and Layer 2 protocols only. See the Upgrading Software Images and Configuration Files chapter in the BigIron RX Installation Guide for additional information. The hitless O/S Layer 2 upgrade allows for upgrading the software in a system between two releases of the O/S, which support this functionality and have compatible data structures.

  • Page 31: Considerations When Using The Feature

    Considerations when using the feature Consider the following when using this feature:  You must have both active and standby management modules installed to use this feature.  To avoid any disruptions of Layer-3 traffic to OSPF or BGP routes, the switch must be configured with OSPF Graceful Restart and BGP Graceful Restart features.

  • Page 32: Performing A Hitless Layer 2 Os Software Upgrade

     Active console control is lost to the previously active management module as it becomes the standby management module.  The active management module initiates the upgrade process on all interface modules.  The switch is now operating on the new Multi-Service IronWare software. The management module that was initially configured as the standby management module is now the active management module and the management module that was initially configured as the active management module is now the standby.

  • Page 33: Technical Support

    Hitless Layer 2 OS upgrade loads from the primary and secondary images on the Management modules. The first step in performing a hitless Layer 2 OS upgrade is to copy the version 02.3.00 or later images into the flash memory of the active and standby management modules. For instructions for copying these files, see Upgrading the management module monitor and boot images and Upgrading the management module IronWare image.

  • Page 34: Getting Help Or Reporting Errors

    Getting Help or Reporting Errors Brocade is committed to ensuring that your investment in our products remains cost-effective. If you need assistance, or find errors in the manuals, contact Brocade using one of the following options: Web Access Go to kp.foundrynet.com and log in to the Knowledge Portal (KP) to obtain more information about a product, or to report documentation errors.

  • Page 35: Additional Resources

    Additional resources Below are some additional publications you can reference to find more information on the products supported in this software release. Additional publications Title Contents  Brocade BigIron RX Series Installation Product Overview Guide  Installation  Product Management ...

  • Page 36: Documentation Update

    Documentation Update The system monitoring service (SYSMON) feature was introduced in the 02.6.00c patch release. This feature monitors the hardware in the system to detect, report, and in some cases isolate and recover hardware errors in the system. When an error or event occurs, SYSMON generates Syslog messages, which must be reported to Brocade Technical Support.
  • Page 37 Syslog message examples Event Description 8 11:48:29:E:System: TM queue scanner Blocked traffic queues in the TM. ALARM:LP3/TM1 has shutdown (TM Q Stuck: LP3/TM1 (Queue 1024, Size 50331648, Credit 2047, RdPtr 0x0) (shutdown))] 8 11:48:19:E:System: ALARM:LP3/TM1 re-initialized (TM Q Stuck: LP3/TM1 (Queue 1024, Size 50331648, Credit 2047, RdPtr 0x0) (QDP...

  • Page 38: Defects

    Defects Closed with Code Change Defects in Multi-Service IronWare R02.7.02a This section lists defects closed in Multi-Service IronWare R02.7.02a. Note that when a workaround to an issue is available, it is provided. Reported release indicates the product and release that the defect was first identified. If the NOTE: problem also appeared in other Brocade IP Products, the issue was addressed using the same defect ID.
  • Page 39 Defect ID Technical Severity Summary of Software Fixes in R02.7.02a Summary: In some cases, a mcache prune failure may occur. The mcache entry displays the outgoing interface that should have been pruned out. Probability: Medium 99512 Medium Feature: PIM Function: PIM Sparse Reported in Release: BigIron RX R02.7.01 Summary: In some cases, the system does not correctly calculate the cost of summarized routes.
  • Page 40 Defect ID Technical Severity Summary of Software Fixes in R02.7.02a Summary: The system does not generate a syslog message indicating the speed and duplex setting if the configuration of a fiber SFP is changed to an unsupported setting. Probability: Medium 103402 Medium Feature: Optics and SFP Support...
  • Page 41 Defect ID Technical Severity Summary of Software Fixes in R02.7.02a Summary: Standard MIB in experimental tree needs unique name to prevent conflicts when using HPOV. Probability: Medium 104251 Medium Feature: SNMP Function: BFD STD MIB Reported in Release: BigIron RX R02.7.02 Summary: OSPFv3 retransmission timer should be per specific LSA for a specific neighbor instead of just per neighbor.
  • Page 42 Defect ID Technical Severity Summary of Software Fixes in R02.7.02a Summary: TCP initial sequence number generation does not fully conform to RFC 793. Probability: Medium 104389 High Feature: TCP Stack Function: IP Reported in Release: BigIron RX R02.7.02 Summary: Higher than normal CPU utilization on the management interface when attempting to ping a non-existent host in the OSPF network.
  • Page 43 Defect ID Technical Severity Summary of Software Fixes in R02.7.02a Summary: Router continues to send LACPDUs in slow timer mode after the far-end router reloads. Probability: High 104988 High Feature: Link Aggregation Function: LACP Reported in Release: BigIron RX R02.7.02 Summary: The ipv6 ospf network point-to-multipoint command can be configured on interfaces, but has no effect on OSPFv3 or the running configuration.
  • Page 44 Defect ID Technical Severity Summary of Software Fixes in R02.7.02a Summary: After hot swapping a module, unicast packets are not forwarded out the module. Probability: Medium 105221 High Feature: System Function: Forwarding Reported in Release: BigIron RX R02.7.02 Summary: A debug statistics message shows a large number of errors for 10G modules when installed in a 16 slot chassis.
  • Page 45 Defect ID Technical Severity Summary of Software Fixes in R02.7.02a Summary: When using SSH, ICMP requests to a resolved name with different ICMP sizes will use the size from the previous ICMP request issued. Probability: Medium 105635 Medium Feature: SSH Function: ICMP Reported in Release: BigIron RX R02.7.00f, and R02.7.01 Summary: Syslog packets sent to syslog server do not contain time...
  • Page 46 Defect ID Technical Severity Summary of Software Fixes in R02.7.02a Summary: The output of show ipv6 bgp <N>/<L> longer- prefixes displays incorrect routes. Probability: High 107639 Medium Feature: BGP4+ Function: BGP4+, CLI Reported in Release: BigIron RX R02.7.02 Summary: Last bit of second mll not set with odd mll entries and receiver of last mll leaves.

This manual is also suitable for:

Ironware

Table of Contents