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 Publication Date Release 02.7.
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.
Contents Supported devices for Multi-Service IronWare R02.7.02a..................................5 Feature support ........................................................................................................5 Supported features ................................................................................................................ 5 Unsupported features .........................................................................................................
Technical support ...................................................................................................33 General Information ........................................................................................................... 33 Getting Help or Reporting Errors ..................................................................................... 34 Web Access ...............................................................................................................................
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. 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.
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.1s Multiple Spanning Tree Protocol (MSTP) 802.1w Rapid Spanning Tree Protocol (RSTP) 802.1x Port Security 802.3ad Dynamic Link Aggregation on tagged and untagged trunks Jumbo packets Layer 2 jumbo packet support Layer 2 Hitless failover Layer 2 IGMP Snooping L2 ACL Filtering based on MAC layer-2 parameters.
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 Summary of Enhancements and Configuration Notes in Release 02.7.02a This release contains new Syslog messages for Traffic Manager and software defects that have been closed. Software image files for Multi-Service IronWare R02.7.
Module Image type BigIron RX-32 Interface Module Image name mbridge32 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.
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.
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 4 2009 at 01:25:04 labeled as rmpr02702a o IronWare Image (Secondary) Version 2.7.
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.
Code flash and boot flash information This field... Displays… Management Modules Management Module () The management module for which flash information is displayed. The parameter indicates an active or standby management module. The parameter indicates the top or bottom slot (M1 or M2, respectively). Code Flash The model number and size of the management module’s code flash.
LP IronWare Image (Primary or Secondary for Module Type 0) Boot-Monitor Image Startup Configuration Boot Flash Indicates the interface modules’ primary and/or secondary IronWare 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. The management module stores these images only; it does not run the images.
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” indicates the image type. Size – The size, in bytes, of the image. Check sum – A unique ID for the image. If the contents of the image change, the check sum changes also.
Boot-Monitor Image Indicates the monitor image installed in the interface module’s code flash. The image must be imlb. 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” indicates the image type. Size – The size, in bytes, of the image. Check sum – A unique ID for the image.
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, Version 2 RX-BI-SFM1 Switch Fabric Module 2 (Serial #: SA32080829, Part #: 35548-001B) FE
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 #: 31593002B) Boot : Version 2.7.2aT155 Copyright (c) 1996-2007 Foundry Networks, Inc.
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 Upgrading the monitor and boot images You can upgrade the management module’s monitor and boot images simultaneously.
• dir // (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. 4. If you want to upgrade other software images, go to the appropriate upgrade section for information. If you have completed upgrading the software images, you must reboot the management module to complete the upgrade process. Unified software image upgrade BigIron RX software release 02.6.
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. The Boot images no longer need to be upgraded with each release and in fact will almost never need to be changed.
BigIron RX#copy tftp flash 10.10.12.12 rmb02702a.bin monitor copy-boot 3. 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 • dir // (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. 4.
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. To upgrade monitor and boot images simultaneously for an interface, perform the following steps: 1.
2. 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.
MBRIDGE versions required per software version Software image installed on BigIron RX 02.4.00 02.4.00a 02.4.00b 02.4.00c 02.4.00d 02.4.00e 02.4.00f 02.4.00g 02.5.00 02.5.00a 02.5.00b 02.5.00c 02.5.00d 02.5.00e 02.5.00f 02.6.00a 02.6.00b 02.6.00c 02.7.00 02.7.01 02.7.01a 02.7.01b 02.7.02 02.7.
Software image installed on FPGA image Compatible FPGA version BigIron RX 02.5.00 02.5.00a 02.5.00b 02.5.00c 02.5.00d 02.5.00e 02.5.00f 02.5.00g 02.5.00h 02.5.00i 02.5.00j 02.6.00 02.6.00a 02.6.00b 02.6.00c 02.6.00d 02.6.00e 02.7.00 02.7.01 02.7.01a 02.7.01b 02.7.02 02.7.
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.
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.
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. In addition, the device’s OSFP neighbors must have OSPF Graceful Restart Helper enabled.
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.
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.
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. To report errors, click on Cases > Create a New Ticket. Make sure you specify the document title in the ticket description.
Additional resources Below are some additional publications you can reference to find more information on the products supported in this software release.
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. In the 02.7.02a patch release, the following enhancements were added: 1.
Syslog message examples Event Description Jan 8 11:48:29:E:System: ALARM:LP3/TM1 has shutdown (TM Q Stuck: LP3/TM1 (Queue 1024, Size 50331648, Credit 2047, RdPtr 0x0) (shutdown))] TM queue scanner Blocked traffic queues in the TM. Dec 31 13:51:42:E:System: ALARM:LP1/TM1 has shutdown (LP1/NP1 TCAM failure (shutdown)) TCAM scan Corruption on the TCAM.
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. NOTE: Reported 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. Defect ID Technical Severity Summary of Software Fixes in R02.7.
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. 99512 Medium Probability: 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.
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. 103402 Medium Probability: Medium Feature: Optics and SFP Support Function: System Reported in Release: BigIron RX R02.7.
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. Probability: Medium 104261 High Feature: OSPFv3 Function: OSPFv3 Reported in Release: BigIron RX R02.7.
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. 104610 Medium Probability: High Feature: ARP Function: IP Stack Reported in Release: BigIron RX R02.7.
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.
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. Probability: Medium 105367 Medium Feature: System Function: System Reported in Release: BigIron RX R02.6.
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. 105635 Medium Probability: 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 stamp. Probability: High 106120 Low Feature: Syslog Function: Syslog Reported in Release: BigIron RX R02.7.
Defect ID Technical Severity Summary of Software Fixes in R02.7.02a Summary: The output of show ipv6 bgp / longerprefixes 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. Probability: Low 107719 High Feature: PIM Function: PIM Sparse Reported in Release: BigIron RX R02.6.
