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

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

Advertisement

Quick Links

Download this manual See also: Release Note
Multi-Service IronWare Software
R02.7.03a for Brocade BigIron RX

Series Switches

Release Notes v1.0
January 14, 2011
Document History
Document Title
Multi-Service IronWare Software
R02.7.03 for Brocade BigIron RX Series
Switches Release Notes v1.0
Summary of Changes
Release 02.7.03a
Publication Date
January 2011

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.03a for Brocade BigIron RX Series Switches Release Notes v1.0 January 14, 2011 Document History Document Title Summary of Changes Publication Date Multi-Service IronWare Software Release 02.7.03a January 2011 R02.7.03 for Brocade BigIron RX Series Switches Release Notes v1.0...
  • Page 2 Copyright © 2011 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, BigIron, DCFM, DCX, Fabric OS, FastIron, IronView, NetIron, SAN Health, ServerIron, TurboIron, and Wingspan are registered trademarks, and Brocade Assurance, Brocade NET Health, Brocade One, Extraordinary Networks, MyBrocade, VCS, and VDX are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.

  • Page 3: Table Of Contents

    Contents Supported devices for Multi-Service IronWare R02.7.03a ........5 Enhancements ......................5 R02.7.03a ..........................5 R02.7.03 ..........................5 Feature support ......................6 Supported features ........................6 Unsupported features ......................11 Software image files for Multi-Service IronWare R02.7.03 ......11 Software image files ......................11 Images and procedures required ...................
  • Page 4 Technical support ....................28 General Information ......................28 Getting Help or Reporting Errors ................28 Web access ..........................28 E-mail and telephone access ....................29 Additional resources ....................29 Defects ........................30 Closed defects with code change in Multi-Service IronWare R02.7.03a......30 Closed defects with code change in Multi-Service IronWare R02.7.03....... 32 IronWare Software Release 02.7.03a for Brocade BigIron RX Series Swtches Release Notes v 1.0 Page 4 of 40...

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

    Supported devices for Multi-Service IronWare R02.7.03a 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: Feature Support

    Enhancement Descriptions Described in… Syslog update The System Log has been updated as follows: Book: BigIron RX Configuration Giuide • Chapter: Using Syslog Separate buffers for static and dynamic logs • Entries in the static log buffer are cleared at reset or reload, while entries in the dynamic log are preserved •...
  • Page 7 Category Feature description • Serial and Telnet access to industry-standard Command Line Interface (CLI) Management Options 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 8 Category Feature description • see VLANs, below 802.1q • 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 •...
  • Page 9 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 10 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 11: 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 Software image files for Multi-Service IronWare R02.7.03 The following Software Image Files are available for Multi-Service IronWare R02.7.03 for the BigIron...

  • Page 12: Images And Procedures Required

    Module Image type Image name IronWare rlp02703a.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 13 make sure that you have installed the versions required in your installation. The following sections describe how to use the show version commands to display this information. You can display version information for a BigIron RX using the show version command as shown in the following: BigIron RX Router#show version ========================================================================== HW: BigIron RX Router...
  • Page 14 IronWare : Version 2.7.3T143 Copyright (c) 1996-2010 Brocade Communications Systems, Inc. Compiled on Aug 27 2010 at 01:39:36 labeled as rmpr02703 (4538957 bytes) from Primary Board ID : 00 MBRIDGE Revision : 21 916 MHz Power PC processor (version 8003/0101) 166 MHz bus 512 KB Boot Flash (AM29LV040B), 32 MB Code Flash (MT28F128J3) 2048 MB DRAM Standby Management uptime is 12 minutes 0 seconds...

  • Page 15: Different Image Information

    Different image information Management Modules This field Displays Boot Image Indicates the boot image running in the management module. 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.

  • Page 16: Interface Modules

    Interface Modules This field Displays Boot Image Indicates the boot image running in the interface module. 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 17: Unified Software Image Upgrade

    Syntax: cp <original-file-name> <backup-file-name> Unified software image upgrade You can use the Unified Software Image Upgrade procedure to upgrade the Monitor and the Multiservice Ironware image of both the management module and also the interface modules. You can use the command shown below to upgrade the Images.

  • Page 18: Upgrading The Images Independently

    Upgrading the images Independently Note: Using the unified approach is the easier single step process and also the preferred one. If you don’t want to use the unified software upgrade procedure to upgrade your modules boot, monitor and system images, you can do them one by one separately, as described in the sections below. Upgrading the management module Monitor boot images To upgrade the management module monitor and boot image, perform the following steps: 1.

  • Page 19: Upgrading The Management Module Ironware Image

    Upgrading the management module IronWare image To upgrade the management module IronWare image (primary or secondary), you must perform the following steps: Place the new IronWare image on a TFTP server to which the BigIron RX system has access or on a PCMCIA flash card inserted in slot 1 or 2.

  • Page 20: Upgrading The Ironware Image On The Interface Module

    Command syntax for upgrading the monitor and boot images on the interface module Command syntax Description copy tftp lp <TFTP-server-ip-addr> <image- Copies the latest monitor image from the TFTP server name>mon all | <slot-number> to all interface modules or to the specified interface module (slot-number).

  • Page 21: Upgrading Mbridge Fpga On The Management Module

    NOTE: If you copy the new IronWare image to all interface modules using the all keyword, the management module makes a copy of the image (called lp-primary-0 or lp-secondary-0) and stores it in its code flash, thereby synchronizing the new IronWare image on both the interface and management modules.
  • Page 22 Software Current MBRIDGE image Interface module image installed on BigIron RX 02.5.00f 02.6.00a BigIron RX-16/8/4 MP ( Management Module) through BigIron RX-32 (mbridge32) 02.6.00c 02.7.00 BigIron RX-16/8/4 (mbridge) MP ( Management Module) BigIron RX-32 (mbridge32) 02.7.01 BigIron RX-16/8/4 (mbridge) MP ( Management Module) BigIron RX-32 (mbridge32) 02.7.01a BigIron RX-16/8/4 (mbridge)

  • Page 23: Rebooting The Management Module

    1. Determine the versions of the images currently installed on the BigIron RX management module using the show version command. 2. Place the new MBRIDGE FPGA image on a TFTP server to which the BigIron RX system has access or on a PCMCIA flash card inserted in slot 1 or 2. 3.

  • Page 24: Regenerating Ssh V2 Crypto Key

    • Enter the show module command at any CLI level, and verify that the status of all interface modules is CARD_STATE_UP. • Enter the show version command at any CLI level, and verify that all management and interface modules are running the new software image version. If you find that an interface module is in a waiting state or is running an older software image, then you may have forgotten to enter the lp cont-boot sync <slot-number>...

  • Page 25: Considerations When Using The Hitless Layer 2 Os Upgrade Feature

    • Due to Internal changes introduced in patch release version 02.4.00d ,hitless upgrade is not supported onto 02.4.00b and hitless downgrade is not supported from 02.4.00d. • The Hitless upgrade feature is not supported on release 02.5.00b to 02.5.00c for the BigIron RX-32 only.

  • Page 26: The Hitless Os Layer 2 Software Process

    • If there are protocol dependencies between neighboring nodes, it’s recommended that only each node is upgraded: one node at a time. • After hitless upgrade, the BigIron RX switch will still have the same running configuration as it does before the upgrade.

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

    Figure 1 Management module (MP) and Interface Module (LP) Hitless Upgrade Process Performing a Hitless Layer 2 OS software upgrade To perform a hitless Layer 2 OS software upgrade, you must perform the following tasks: • Copy version 02.3.00 or later of the Multi-Service IronWare software to the primary and secondary image on both the active and standby management modules and interface modules.

  • Page 28: Technical Support

    fail-over control to it. Executing the Hitless upgrade command To begin the process of a hitless upgrade, use the following command: BigIron RX(config)# hitless-reload mp primary lp primary Syntax: hitless-reload mp [primary | secondary ] lp [primary | secondary] The mp parameter specifies that the management module will be reloaded with either the primary or secondary image as directed.

  • Page 29: E-Mail And Telephone Access

    E-mail and telephone access http://www.brocade.com/services-support/index.page Go to for the latest e-mail and telephone contact information. 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 •...

  • Page 30: Defects

    Defects NOTE: In the tables below, "Reported In Release" indicates the product and release that the defect was first identified. If the problem also appeared in other Brocade IP Products, the issue was addressed using the same defect ID. Closed defects with code change in Multi-Service IronWare R02.7.03a.

  • Page 31: Ironware Software Release 02.7.03A For Brocade Bigiron Rx Series Swtches

    Defect ID: DEFECT000321390 Technical Severity: Medium Summary: ARP packets transiting through the router, tagged with VLAN ID 0 (Priority tag) are being dropped. Probability: High Feature: IPv4 Forwarding Function: ARP Reported In Release: RX 02.7.03 Defect ID: DEFECT000322582 Technical Severity: Medium Summary: When a fan power supply write error occurs, an incorrect value of 31 may be displayed on the screen.

  • Page 32: Closed Defects With Code Change In Multi-Service Ironware R02.7.03

    Defect ID: DEFECT000326324 Technical Severity: Medium Summary: Output from ‘tag-type’ command is truncated to 200 characters. Probability: High Feature: CLI Infrastructure Function: Parser Engine Reported In Release: RX 02.7.03 Service Request ID: 267672 Closed defects with code change in Multi-Service IronWare R02.7.03.

  • Page 33: Ironware Software Release 02.7.03A For Brocade Bigiron Rx Series Swtches

    Defect ID: DEFECT000271931 Technical Severity: High Summary: VRRP/STP flap when BGP session is reset (full Internet route table is withdrawn and updated) Symptom: VRRP flap is seen. Probability: Medium Feature: L2 Protocol Function: VSRP1 Reported In Release: RX 02.4.00 Service Request ID: 178709 Defect ID: DEFECT000272063 Technical Severity: Medium Summary: Broadcast traffic is CPU forwarded when enabling IP multicast active.

  • Page 34: Ironware Software Release 02.7.03A For Brocade Bigiron Rx Series Swtches

    Defect ID: DEFECT000273769 Technical Severity: Medium Summary: Modifying an ACL may cause a reload. Symptom: System may reload Probability: Low Feature: ACL Function: IPv4 Reported In Release: RX 02.7.02 Service Request ID: 237740 Defect ID: DEFECT000274156 Technical Severity: Medium Summary: Command "show interface slot 0" may cause a system reset. Symptom: System may reload Probability: Medium Feature: CLI Infrastructure...

  • Page 35: Ironware Software Release 02.7.03A For Brocade Bigiron Rx Series Swtches

    Defect ID: DEFECT000279523 Technical Severity: Medium Summary: The LED status on the Web-GUI LED for the 16x10GE module is transposed between the odd and even ports. Feature: Web Management Function: FRONT PANEL Reported In Release: RX 02.7.03 Defect ID: DEFECT000279728 Technical Severity: Medium Summary: Multicast traffic is flooded on all ports when IGMPv3 snooping enabled.

  • Page 36: Ironware Software Release 02.7.03A For Brocade Bigiron Rx Series Swtches

    Defect ID: DEFECT000284653 Technical Severity: Medium Summary: Not able to set Extended IP ACL Protocol field to ESP(50) from SNMP Symptom: Customer was trying to implement ACL to RX from INM but failed. Using CLI command the access list is added without any problem access-list 105 permit esp host 1.1.1.1 host 2.2.2.2 Probability: High Feature: SNMP Management...

  • Page 37: Ironware Software Release 02.7.03A For Brocade Bigiron Rx Series Swtches

    Defect ID: DEFECT000290430 Technical Severity: Medium Summary: When a port is removed from a LAG it gets stuck in blocking state. Symptom: If an up interface is added to a LAG, but the LAG is not deployed and then the interface is removed from the LAG.

  • Page 38: Ironware Software Release 02.7.03A For Brocade Bigiron Rx Series Swtches

    Defect ID: DEFECT000301863 Technical Severity: High Summary: An OSPF route with metric of 65535 is not installed in the routing table. Symptom: Using the configuration 'auto-cost reference-bandwidth 100000' will prevent routes from a GRE tunnel interface from being installed. Workaround: Remove the auto-cost reference-bandwidth 100000 or set the cost on the GRE tunnel interface. Probability: High Feature: OSPF Function: PROTOCOL...

  • Page 39: Ironware Software Release 02.7.03A For Brocade Bigiron Rx Series Swtches

    Defect ID: DEFECT000305721 Technical Severity: Medium Summary: OSPF interface cannot be established between a VE interface on 16x10G linecard. This was seen when the 16x10G card is in an RX-4 system. Symptom: Unable to for a OSPF adjacency. Probability: High Feature: OSPF Function: PROTOCOL Reported In Release: RX 02.7.02...
  • Page 40 Defect ID: DEFECT000310404 Technical Severity: Critical Summary: The management module may reload when issuing the command 'sh stat brief lag' from telnet session. Symptom: Reload Probability: Low Feature: LAG Function: LACP Reported In Release: RX 02.7.02 Service Request ID: 255300 Defect ID: DEFECT000310529 Technical Severity: High Summary: An Interface module may reload when a new L2 multicast stream is received.

This manual is also suitable for:

Ironware

Table of Contents