Brocade fabric os troubleshooting and diagnostics guide v7.1.0 (53-1002751-01, march 2013) (146 pages)
Summary of Contents for Brocade Communications Systems PowerConnect B-RX
Page 1
Multi-Service IronWare Software Release 02.8.00a for Brocade BigIron RX Series Switches Release Notes v1.0 August 12, 2011 Document History Document Title Summary of Changes Publication Date Multi-Service IronWare Software Release Release 02.8.00a August 2011 02.8.00a for Brocade BigIron RX Series Switches Release Notes v1.0...
Contents Supported devices for Multi-Service IronWare Release 02.8.00a ....... 5 Enhancements ......................5 Release 02.8.00a ........................5 Release 02.8.00 ........................5 Feature support ......................7 Supported features ........................7 Unsupported features ......................12 Software image files for Multi-Service IronWare Release 02.8.00a ....12 Images and procedures required ...................
Page 4
General Information ......................29 Getting Help or Reporting Errors ................29 Additional resources ....................30 Defects ........................30 Closed defects with code change in Multi-Service IronWare Release 02.8.00a ....31 Closed defects with code change in Multi-Service IronWare Release 02.8.00 ....33 IronWare Software Release 02.8.00a for Brocade BigIron RX Series Swtches Release Notes v 1.0 Page 4 of 40...
Supported devices for Multi-Service IronWare Release 02.8.00a 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.
Page 6
Table 1: Enhancements for Release 02.8.00 Enhancement Description Described in Multi-device Port Multi-device port authentication is now Book: BigIron RX Series Configuration Authentication supported on the BigIron RX tagged and Guide untagged ports. Chapter: Configuring Multi-Device Port Authentication Section: How multi-device port authentication works Enhanced show arp The show arp command has been enhanced to...
Enhancement Description Described in Enhancement in ACL Brocade RX devices now support IPv4 and IPv6 Book: BigIron RX Series Configuration Support ACLs on the same interface Guide Feature support The following is a list of all the features supported on the BigIron RX switches. See Unsupported features, for features not supported.
Page 8
Category Feature description • AAA Authentication Security Local passwords RADIUS SSHv2 Secure Copy (SCP) TACACS/TACACS+ User accounts 802.1x: All EAP types, including MD5, TLS, TTLS, and PEAP Multi-device port authentication Note: Telnet, SSH, Web and SNMP servers are disabled by default, and can be enabled selectively.
Page 9
Category Feature description • Port Security 802.1x • Dynamic Link Aggregation on tagged and untagged trunks 802.3ad • Layer 2 jumbo packet support Jumbo packets • Provides automatic failover from the active management module to the Layer 2 Hitless failover standby management module without interrupting operation of any interface modules in the chassis.
Category Feature description • PIM-SM IPv6 Multicast Unsupported features The following features are not supported in software release 02.8.00 on BigIron RX: • AppleTalk • • Mirroring across VLANs • MPLS • • RARP • VLAN translation • Subnet VLANs •...
Module Image type Image name BigIron RX-32 mbridge32.xsvf Interface Module Boot and Monitor rlb02800a.bin IronWare rlp02800a.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 based on version upgrade – This sub-section describes the procedures required for your software upgrade depending upon the version you are upgrading from or to.
4. In most cases, this is all that will be required. If you are directed by the release notes to upgrade the boot image, use the upgrade procedure for upgrading the BigIron RX Series switches boot image, presented later in this document. 5.
Field Description Monitor Image Indicates the monitor 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. The “xx” indicates the hardware type, while the “y”...
Field Description Monitor Image Indicates the monitor 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”...
1. Copy the unified software image (rx02800a.bin) from a TFTP server to the switch. For example, to copy the entire unified software image from a TFTP server at IP address 10.10.12.12, use the following command. BigIron RX# copy tftp image 10.10.12.12 rx02800a.bin 2.
Table 6: Command syntax for upgrading monitor and boot images on the management module Command syntax Description copy tftp flash <TFTP-server-ip-addr> <image-name> Copies the latest monitor image from the TFTP server to flash. copy tftp flash <TFTP-server-ip-addr> <image-name> Copies the latest boot images from the TFTP server to flash. boot copy tftp flash <TFTP-server-ip-addr>...
Table 7: Command syntax for upgrading IronWare image on the management module Command syntax Description copy tftp flash <TFTP-server-ip-addr> <image-name> Copies the images from the TFTP server to the primary or primary | secondary secondary locations in flash memory. copy tftp slot1 | slot2 <TFTP-server-ip-addr> <image- Copies the images from the TFTP server to a flash card.
Table 8: 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 22
Table 9: Command syntax for upgrading IronWare image on the interface module Command syntax Description copy tftp lp <TFTP-server-ip-addr> <image-name> Copies the images from the TFTP server to the interface primary | secondary all module. copy tftp lp <TFTP-server-ip-addr> <image-name> Copies the images from the TFTP server to the interface primary | secondary <chassis-slot-number>...
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.00a version.
Software image installed FPGA image Compatible FPGA on BigIron RX version 02.7.00 SBRIDGE 02.7.01 SBRIDGE 02.7.01a through 02.7.01b SBRIDGE 02.7.02 SBRIDGE 02.7.02a through 02.7.02h SBRIDGE 02.7.03 through 02.7.03a SBRIDGE 02.8.00 through 02.8.00a SBRIDGE 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’...
When performing a hitless O/S Layer 2 upgrade or downgrade, use the following guidance: • Hitless O/S Layer 2 upgrade or downgrade is not supported in 2.3.00 or earlier. • 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).
The message "---SW Upgrade In Progress - Please Wait---" is printed at the console when configuration is attempted. Operational command of the switch is allowed during the upgrade process. • The active management module changes from the initial active management module to the standby management module during the hitless upgrade process.
Management module (MP) and Interface Module (LP) Hitless Upgrade Process provides a detailed diagram of the Hitless reload process. 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: •...
you need to have management sessions enabled on both the active and the standby management modules. When the reload is complete, the management module that was in the standby condition at the beginning will be in the active state. If you want the original management module to be active, you must manually fail-over control to it.
Additional resources The following are some additional publications you can reference to find more information on the products supported in this software release. Table 12: Additional publications Title Contents • Brocade BigIron RX Series Installation Guide Product Overview • Installation •...
Closed defects with code change in Multi-Service IronWare Release 02.8.00a Defect ID: DEFECT000350761 Technical Severity: Critical Summary: Under certain VRRP configurations Application Buffers may become depleted. Symptom: Under certain VRRP configurations Application Buffers may become depleted causing unexpected reset of the Feature: VRRP Function: VRRPE Probability: Medium...
Defect ID: DEFECT000352293 Technical Severity: Medium Summary: Burst of jumbo frames may cause forwarding to cease on some ports of the 16x10 modules. Symptom: With 8Gb/s of ISCI traffic at layer-2 sent through the RX, the traffic was balanced across 2 10G ports on ingress and 2 on egress.
Defect ID: DEFECT000355173 Technical Severity: Low Summary: Adding hidden command to disable internal ACLs for BGP and BFD Symptom: Adding hidden command to disable internal ACLs for BGP and BFD. This has been reported by US-CERT http://www.kb.cert.org/vuls/id/853246. Feature: ACL Function: IPv4 Probability: Low Found in Release: RX 02.8.00 Service Request ID:...
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. Feature: L2 Protocol Function: VSRP1 Probability: Medium Found in Release: RX 02.4.00 Service Request ID: 178709 Defect ID: DEFECT000272067 Technical Severity: High Summary:...
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.
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...
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: 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.
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:...
Page 40
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...