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 Publication Date Release 02.7.
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.
Contents Supported devices for Multi-Service IronWare R02.7.03a..................................5 Enhancements...........................................................................................................5 R02.7.03a ................................................................................................................................ 5 R02.7.03 ..................................................................................................................................
Technical support...................................................................................................28 General Information .............................................................................................................. 28 Getting Help or Reporting Errors ........................................................................28 Web access ............................................................................................................................
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. All information required to operate the BigIron RX Series Switch is described in the BigIron RX Series Configuration Guide or the Brocade BigIron RX Series Installation Guide.
Enhancement Syslog update Descriptions Described in… The System Log has been updated as follows: Book: BigIron RX Configuration Giuide • Separate buffers for static and dynamic logs Chapter: Using Syslog • Entries in the static log buffer are cleared at reset or reload, while entries in the dynamic log are preserved • Log buffer size cannot be changed.
Category Feature description • Management Options Serial and Telnet access to industry-standard Command Line Interface (CLI) SSHv2 TFTP Web-based GUI SNMP versions 1, 2, and 3 IronView Network Manager • Security AAA Authentication Local passwords RADIUS Secure Shell (SSH) version 2 Secure Copy (SCP) TACACS/TACACS+ User accounts 802.
Category Feature description • 802.1q see VLANs, below • 802.1s Multiple Spanning Tree Protocol (MSTP) • 802.1w Rapid Spanning Tree Protocol (RSTP) • 802.1x Port Security • 802.
Category Feature description • VLANs 802.
Category Feature description • IP Static entries Routes ARPs Virtual interfaces Secondary addresses • IS-IS Routes BGP peers BGP dampening • Multicast Routing Multicast cache L2 IGMP table DVMRP routes PIM-DM PIM-SM PIM-SSM IGMP v1, v2, v3 snooping PIM-SM snooping (IPv4 only) • OSPF OSPF routes OSPF adjacencies – Dynamic OFPF LSAs OSPF filtering of advertised routes • PBR Policy Based Routing (Release 02.2.
Unsupported features The following features are not supported in software release 02.7.02 on BigIron RX: • AppleTalk • Dynamic IP Routing • IPX • Mirroring across VLANs • MPLS • NAT • 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 RX Series Switches.
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. Links are provided to the required procedures as required.
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.
IronWare : Version 2.7.3T143 Copyright (c) 1996-2010 Brocade Communications Systems, Inc.
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: Monitor Image IronWare 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” indicates the image type. • Size – The size, in bytes, of the image.
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: Monitor Image IronWare Image FPGA Version Information • 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” indicates the image type. • Size – The size, in bytes, of the image.
Syntax: cp 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. You can set parameters to limit images being copied and to direct images to be copied to the secondary image location to a later release. 1. Copy the unified software image (rx02703a.
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.
Upgrading the management module IronWare image To upgrade the management module IronWare image (primary or secondary), you must perform the following steps: 1. 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. 2. Copy the new IronWare image from the TFTP server or a flash card in slot 1 or 2 to the management module’s code flash or a flash card in slot 1 or 2.
Command syntax for upgrading the monitor and boot images on the interface module Command syntax Description copy tftp lp mon all | Copies the latest monitor image from the TFTP server to all interface modules or to the specified interface module (slot-number).
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. If you copy the new IronWare image to a specified chassis slot, the management module does not make a copy of the image or store it.
Software image installed on BigIron RX Current MBRIDGE image Interface module 02.5.00f 02.6.00a through 02.6.00c 02.7.00 02.7.01 02.7.01a through 02.7.01b 02.7.02 02.7.02a through 02.7.02h 02.7.03 through 02.7.
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. Copy the MBRIDGE FPGA image from the TFTP server or a flash card in slot 1 or 2 to all management modules or a management module in a specified chassis slot.
• 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 command at the Privileged EXEC prompt.
• 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. It is supported on all other BigIron RX devices.
• 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. A configuration that is not saved before hitless reload is not removed and the existing startup configuration does not take effect. This behavior is the same as displayed by the management module switchover feature.
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. • Setup a console connection to both the active and standby management modules.
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.
E-mail and telephone access Go to http://www.brocade.com/services-support/index.page 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.
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. Defect ID: DEFECT000316902 Technical Severity: High Summary: An LSA with a higher metric can prevent the route installation of an LSA which has a lower metric and broadcast address LS ID.
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. Probability: Low Feature: SYSTEM Function: Fan Reported In Release: RX 02.7.
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. Defect ID: DEFECT000271667 Technical Severity: Medium Summary: Line Modules may reload during multicast memory request because of memory corruption. Cannot reproduce.
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 RX 02.4.00 Reported In Release: Service Request ID: 178709 Defect ID: DEFECT000272063 Technical Severity: Medium Summary: Broadcast traffic is CPU forwarded when enabling IP multicast active.
Defect ID: DEFECT000273769 Summary: Modifying an ACL may cause a reload. Symptom: System may reload Probability: Low Feature: ACL Reported In Release: RX 02.7.02 Technical Severity: Medium Function: IPv4 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 Function: Parser Engine Reported In Release: RX 02.7.
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. Symptom: Multicast traffic is flooded on all ports.
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 Function: IP Mib Reported In Release: RX 02.7.
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. The interface could be left in blocking state. Probability: Low Feature: LAG Function: LACP Reported In Release: RX 02.7.
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 Reported In Release: RX 02.7.
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 Service Request ID: 251533 Defect ID: DEFECT000306096 Technical Severity: High Summary: With Multicast enabled, traffic may stop forwarding due to buffer depletion.
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 RX 02.7.02 Reported In Release: Service Request ID: 255300 Defect ID: DEFECT000310529 Technical Severity: High Summary: An Interface module may reload when a new L2 multicast stream is received.
