Multi-Service IronWare Software R02.8.00 for Brocade BigIron RX Series Switches Release Notes v1.0 May 19, 2011 Document History Document Title Multi-Service IronWare Software R02.8.00 for Brocade BigIron RX Series Switches Release Notes v1.0 Summary of Changes Publication Date Release 02.8.
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.8.00....................................5 Enhancements for R02.8.00 ....................................................................................5 Feature support ........................................................................................................6 Supported features .................................................................................................................. 6 Unsupported features .....................
Getting Help or Reporting Errors ........................................................................28 Additional resources ..............................................................................................28 Defects .....................................................................................................................29 Closed defects with code change in Multi-Service IronWare R02.8.00 ............................... 30 IronWare Software Release 02.8.
Supported devices for Multi-Service IronWare R02.8.00 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 this 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 Descriptions Described in Protocol (MSTP) 802.1s Section: Displaying MSTP information for the specified Ethernet interface Copy software image from a flash card to the flash memory In Release 02.8.00 of the Multi-Service IronWare software, a new copy command have been added to copy the software image from a flash card to the flash memory.
Table 2: Supported features for R02.8.00 Category Feature description System level features • Cisco Discovery Protocol (CDP) Allows you to configure a Brocade device to intercept and display the contents of CDP packets. This feature is useful for learning device and interface information for Cisco devices in the network. • CLI Logging Allows the logging of all valid CLI commands from each user session into the system log.
Category Feature description • Logging Multiple SysLogD server logging • sFlow sFLow version 5 • Uni-directional Link Detection (UDLD) Monitors a link between two devices and brings the ports on both ends of the link down if the link goes down at any point between the two devices. Layer 2 features • 802.1d Spanning Tree Protocol (STP) and Single Spanning Tree Protocol (SSTP) • 802.1p Quality of Service (QoS) queue mapping • 802.1q see VLANs, below • 802.
Category Feature description • Foundry MRP Metro Ring Protocol (MRP) Phase 1 and Phase 2 • PVST / PVST+ Per-VLAN Spanning Tree (PVST) • Rate Limiting Port-based, port-and priority-based, port-and vlan-based, and port-and-ACLbased rate limiting on inbound ports are supported. • SuperSpan A Brocade STP enhancement that allows Service Providers (SPs) to use STP in both SP networks and customer networks. • Topology Groups A named set of VLANs that share a Layer 2 topology.
Layer 3 features • ACLs Standard, Extended, and Super Inbound ACL logging ACL editing • BGP BGP routes BGP peers BGP dampening Graceful Restart • FDR Foundry Direct Routing • IP Forwarding IPv4 Routing IPv6 Routing • 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 ad
• PBR Policy Based Routing (Release 02.2.01 and later) • RIP versions 1 and 2 RIP routes • VRRP and VRRPE Virtual Router Redundancy Protocol (VRRP) and VRRP Extended (VRRPE) IPv6 features • IPv6 ACLs Extended ACLs • IPv6 Routing Protocols RIPng OSPFv3 BGP4+ Unsupported features The following features are not supported in software release 02.7.
Software image files for Multi-Service IronWare R02.8.00 The following software image files are available for Multi-Service IronWare R02.8.00 for the BigIron RX Series switches. Table 3: Software image files Module Image type Image name Unified Image N/A rx02800.bin Management Module Boot and Monitor rmb02800.bin IronWare rmpr02800.bin FPGA mbridge.xsvf BigIron RX-4, BigIron RX-8, and BigIron RX-16 BigIron RX-32 Interface Module mbridge32.xsvf Boot and Monitor rlb02800.
• Rebooting the device – This sub-section describes the procedures required for rebooting the device after upgrading the software images. Upgrading the Multi-Service IronWare software When performing this upgrade, you will usually need to upgrade Unified Multi-Service IronWare image. The boot image will need to be upgraded only if it is specifically mentioned in the relevant release notes. The steps for this upgrade include the following: 1.
(439602 bytes) from boot flash Monitor : Version 2.8.0T145 Copyright (c) 1996-2010 Brocade Communications Systems, Inc. Compiled on Apr 20 2011 at 01:07:14 labeled as rmb02800 (439633 bytes) from code flash IronWare : Version 2.8.0T143 Copyright (c) 1996-2010 Brocade Communications Systems, Inc.
Different image information The following sections describe the various software images for the management module and interface module. Management Modules The following table describes the various software images for the management module. Table 4: Software image files for management modules Field Description 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.
Interface Modules The following table describes the various software images for the interface module. Table 5: Software image files for interface module Field Description 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.
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 Unified software image upgrade You can use the unified software image upgrade procedure to upgrade the monitor and the Multi-Service IronWare image of both management and interface modules. You can use the following command to upgrade the images.
Upgrading the images independently Note: Using the unified approach is the easier single step process and also the preferred one. If you do not 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 monitor and boot images on the management module To upgrade the monitor and boot images on the management module, perform the following steps: 1.
Upgrading the IronWare image on the management module To upgrade the IronWare image (primary or secondary) on the management module, 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 slot 2. 2. Copy the new IronWare image from the TFTP server or a flash card in slot 1 or slot 2 to the management module’s code flash or a flash card in slot 1 or slot 2.
To upgrade monitor and boot images simultaneously on an interface module, perform the following steps: 1. Place the new monitor and boot images on a TFTP server to which the BigIron RX system has access or on a PCMCIA flash card inserted in slot 1 or slot 2. 2. Copy the new monitor and boot images to the BigIron RX.
Table 9: Command syntax for upgrading IronWare image on the interface module Command syntax Description copy tftp lp primary | secondary all Copies the images from the TFTP server to the interface module. copy tftp lp primary | secondary Copies the images from the TFTP server to the interface module in the specified chassis slot.
Upgrading MBRIDGE FPGA on the management module BigIron RX management modules contain an upgradable FPGA images called MBRIDGE and SBRIDGE. The MBRIDGE and SBRIDGE image installed must be compatible with the software version you are running on the BigIron RX. The following table describes the MBRIDGE FPGA versions required for the 02.8.00 version. Table 10: MBRIDGE versions required per software version Software image installed on BigIron RX Current MBRIDGE image Version Interface module 02.4.
Software image installed on BigIron RX 02.6.00a through 02.6.00e 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.03a 02.8.00 FPGA image Compatible FPGA version SBRIDGE SBRIDGE SBRIDGE SBRIDGE SBRIDGE SBRIDGE SBRIDGE SBRIDGE 6 6 6 6 6 6 6 6 To upgrade the MBRIDGE FPGA image on the BigIron RX management module, perform the following general steps: 1.
• 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 made a copy of the image and stored it in its code flash under the names lp-primary-0 or lp-secondary-0. By default, the BigIron RX system checks the interface modules’ IronWare images, which reside in the code flash of the interface modules and the management module to make sure they are the same in both locations.
• Hitless O/S Layer 2 upgrade support is in 2.3.00a and higher patch releases (unless indicated otherwise in the target software’s release notes). • Hitless upgrade maintains forwarding states and control plane functionality of the active software from which you are upgrading (i.e. 2.3.00a to 2.3.00d would only maintain the functionality supported by 2.3.00a). • Hitless downgrades are recommended only between compatible patch releases of a feature release such as between 2.3.00b to 2.3.
• The active management module changes from the initial active management module to the standby management module during the hitless upgrade process. This makes it necessary to have a connection to the console interface on both management modules. • Upon being reset, the management and interface module CPUs are unable to send and receive any packets.
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.
Table 12: Additional publications Title Contents Brocade BigIron RX Series Installation Guide • Product Overview • Installation • Product Management • Hardware Maintenance and Replacement • Air filters • Fiber optic connectors • Replaceable modules • AC Power supply • Fans • Software Upgrades • Hardware Specifications • Regulatory Statements BigIron RX Series Configuration Guide Information on how to configure all the features in a BigIron RX Series switch.
Closed defects with code change in Multi-Service IronWare R02.8.00 Defect ID: DEFECT000336030 Summary: Technical Severity: Critical Interface Module unexpectedly reloaded due to IPv6 packet that caused some internal looping when processing Feature: IPv6 Forwarding Function: FIB Probability: Low Found in Release: RX 02.7.00 Service Request ID: 522363 Defect ID: DEFECT000343061 Technical Severity: Critical Summary: The management module unexpectedly reloaded due to AAA abnormal activity.
Defect ID: DEFECT000272067 Technical Severity: High Summary: Need ability to resolve IPv6 addresses using IPv4 transport per the RFC 3596 Symptom: RX cannot resolve IPv6 addresses through IPv4 DNS queries Feature: DNS Function: PROTOCOL Probability: High Found in Release: RX 02.7.00 Service Request ID: 215029 Defect ID: DEFECT000310529 Technical Severity: High Summary: An Interface module may reload when a new L2 multicast stream is received. Symptom: Interface module may reload.
Defect ID: DEFECT000340501 Technical Severity: High Summary: Issuing the OSPF command 'no ip ospf network point-to-point’ on VE interface may cause an unexpected reset. Symptom: After changing the OSPF parameter ‘no ip ospf network point-to-point’ on a VE (VE71).the router reset immediately. Feature: OSPF Function: CONFIGURATION Probability: Medium Found in Release: RX 02.7.
Defect ID: DEFECT000340184 Technical Severity: Medium Summary: SNMP unable to get area ID from ospfAreaId table when backbone area 0 or 0.0.0.0 is not configured Symptom: Unable to get the OSPF area ID from MIB. This works correctly when area 0 is present. Feature: SNMP Management Function: Routing Mib Probability: High Found in Release: RX 02.5.
Defect ID: DEFECT000323367 Technical Severity: Medium Summary: IP Cache-entry is not removed until either ARP entry is removed or IP Cache entry is cleared. Symptom: IP next-hop table may become full on the router. Feature: IPv4 Forwarding Function: Next Hop Table Probability: High Found in Release: RX 02.7.02 Service Request ID: 265521 Defect ID: DEFECT000325133 Technical Severity: Medium Summary: Simultaneous use of IPv6 and IPv4 ACLs is not possible.
Defect ID: DEFECT000287890 Technical Severity: Medium Summary: BGP "allowas-in" does not work correctly with confederation configuration. Symptom: BGP Routes received from peer with local AS (in as-path) are dropped even though "allowas-in" is used for that particular peer. This issue observed only when confederation is configured, wIthout confederation it works as expected. Feature: BGP Function: BGPv4 Probability: High Found in Release: RX 02.7.
Defect ID: DEFECT000274156 Technical Severity: Medium Summary: Executing command "show interface slot 0" may cause a system reset. Symptom: System may reload. Feature: CLI Infrastructure Function: Parser Engine Probability: Medium Found in Release: RX 02.7.02 Service Request ID: 238294 Where Else Fixed: PATCH: RX 02.7.02 e Defect ID: DEFECT000271667 Technical Severity: Medium Summary: Line Modules may reload during multicast memory request because of memory corruption. Cannot reproduce.
Defect ID: DEFECT000350901 Technical Severity: Medium Summary: IPv6 SNMP-client not displayed in running configuration. Symptom: Unable to add “snmp-client ipv6 2606:8200::ffff” to the configuration. When configuring the clause, the system seemed to take the command without any warning, but running configuration did not appear to save it. Feature: SNMP Management Function: CLI Probability: High Found in Release: RX 02.7.
