IronWare Software Release R07.2.02j for Brocade FESX, SuperX, FSX, FCX, FGS, FGS-STK, FLS, FLS-STK, and FWS Switches Release Notes v1.0 June 28, 2013 Document History Document Title Summary of Changes Publication Date IronWare Software Release 07.2.02j for Brocade FESX, SuperX, FSX, FCX, FGS, FGS-STK, FLS, FLS-STK, and FWS Switches Release Notes v1.0 New document June 2013 Copyright © 2013 Brocade Communications Systems, Inc. All Rights Reserved.
Copyright © 2013 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, NetIron, SAN Health, ServerIron, and TurboIron are registered trademarks, and Brocade Assurance, Brocade NET Health, Brocade One, CloudPlex, MLX, VCS, VDX, and When the Mission Is Critical, the Network Is Brocade are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
Contents Supported devices ........................................................................................................ 6 Summary of enhancements in IronWare release R07.2.02j .......................... 6 Summary of enhancements in IronWare release R07.2.02h......................... 6 Summary of enhancements in IronWare release R07.2.02g ......................... 6 Summary of enhancements in IronWare release R07.2.02f .......................... 6 Summary of enhancements in IronWare release R07.
Show interface brief command output ................................................................................................... 18 ICMP redirect messages ............................................................................................................................... 19 Enabling and Disabling DHCP-client service on FSX Base Layer 3 devices ............................... 19 Note regarding Telnet and Internet Explorer 7 ...................................................................
E-mail and telephone access ...................................................................................................................... 45 Reporting document errors ....................................................................................................................... 45 Additional resources ................................................................................................. 45 Defects ..................................................................................
Supported devices This software release applies to the following Brocade FastIron switches: • FastIron X Series: • FastIron Edge Switch X Series (FESX) • FastIron Edge Switch X Series Expanded (FESXE) • FastIron SuperX Switch (SuperX) • FastIron SX 800, 1600, and 1600-ANR (FSX or SX) • • • • FastIron GS (FGS) and FastIron LS (FLS) FastIron GS-STK (FGS-STK) and FastIron LS-STK (FLS-STK) FastIron CX (FCX) FastIron WS (FWS) Summary of enhancements in IronWare release R07.2.02j Release 07.2.
Summary of enhancements in IronWare release R07.2.02 This section lists the enhancements in software release 07.2.02. Summary of enhancements in FSX R07.2.02 Table 1 lists the enhancements in software release 07.2.02 for FESX, SuperX, and FSX devices. Table 1 Enhancements in FSX R07.2.02 Feature Description Refer to the FastIron Configuration Guide, section entitled... PoE firmware upgrade via CLI You can install PoE firmware from the TFTP server on a FastIron switch with the CLI command.
Summary of enhancements in FCX R07.2.02 Table 2 lists the enhancements in software release 07.2.02 for FCX devices. Table 2 Enhancements in FCX R07.2.02 Feature Description Fast Uplink Span Fast Uplink Span transitions the forwarding of “Fast Uplink Span” traffic to one of the redundant ports in the Fast Uplink Span group in one second bypassing listening and learning port states. Hitless support for PBR This release adds support for Hitless PBR on FCX devices.
Feature Description See the FastIron Configuration Guide, section entitled... New SNMP MIBs SNMP MIB support has been added for the following features: • 802.1x authentication • Support for MIBs in RFC 2932, RFC 2933 and RFC 2934 • Power Over Ethernet MIB with the following table: • snAgentPoeUnitTable (stacking systems) IronWare MIB Reference Guide Summary of enhancements in FGS R07.2.02 Table 3 lists the enhancements in software release 07.2.02 for FGS, FGS-STK, FLS, FLS-STK, and FWS devices.
Feature Description See the FastIron Configuration Guide, section entitled... New SNMP MIBs SNMP MIB support has been added for the following features: • 802.1x authentication • Support for MIBs in RFC 2932, RFC 2933 and RFC 2934 • Power Over Ethernet MIB with the following table: • snAgentPoeUnitTable (stacking systems) IronWare MIB Reference Guide User-configurable buffer profile This buffer profile is a simpler form of “User-configurable buffer profiles allocation of qd descriptors and qd buffers.
To identify an SNTP server with IP address 208.99.8.95 to act as the clock reference for a Brocade device, enter the following. Brocade(config)# sntp server 208.99.8.95 Syntax: [no] sntp server { | | ipv6 } [] [ authentication-key ] The parameter specifies the SNTP version the server is running and can be from 1 – 4. The default is 4.
The following table describes the information displayed by the show sntp associations command. Table 4 Output from the show sntp association command Field Description (leading character) One or both of the following:*Synchronized to this peer ~Peer is statically configured address IP address of the peer ref clock IP address of the peer reference clock, or the reference ID of the external clock source if the peer is stratum 1. Examples of external clock source IDs: GPS, CDMA, WWV (Ft.
Field Description authenticated If MD5 authentication is enabled for the peer. sane or insane If the SNTP server passes sanity checks. synched or unsynched If the system is synchronized or unsynchronized to the NTP peer. valid or invalid If the peer time is valid or invalid. stratum The NTP stratum level of the peer. reference ID The IP address of the peer (if any) to which the unit is synchronized. The reference ID can also refer to the external clock source if the peer is stratum 1.
Syntax: show sntp status The following table describes the information displayed by the show sntp status command. Table 6 Output from the show sntp status command Field Description unsynchronized System is not synchronized to an NTP peer. synchronized System is synchronized to an NTP peer. stratum NTP stratum level of the upstream time server. reference clock IP address of the peer reference clock, or the reference ID of the external clock source if the peer is stratum 1.
the specified stratum number (or the default value of 1). When it is synchronized with the upstream server, the Brocade device will use the upstream server’s stratum number plus 1. If you do not include the use-local-clock option the Brocade device will function as specified by RFC 4330: when the Brocade device loses upstream synchronization, it will respond to client SNTP requests with a “kiss-of-death” response (stratum value=0).
Table 7 Output from the show sntp server-mode command Field Description status The operational state of the SNTP server. “Up” means that the SNTP port is open; “down” means that the SNTP port is closed. (If sntp server-mode is disabled, the show sntp server-mode command will display the message “SNTP server is not operational.) stratum Stratum number of this server. The range is from 1 through 15. If the device is synchronized to an upstream SNTP server, this will show that server’s stratum number +1.
Brocade(config)#sntp broadcast client Brocade(config)#sntp broadcast server 1.1.1.1 To enable an SNTP client to listen to only one specific IPv6 NTP broadcast server, enter the following commands.
VRRP show command output In some of the VRRP show command outputs in the FastIron Configuration Guide, Hello-Interval and Dead-Interval timers are displayed in seconds instead of milliseconds. 48-port 10/100/1000 Mbps Ethernet POE (SX-FI48GPP) interface module limitations The following configuration limitations apply to this module: • • Q-in-Q and SAV (VLAN stacking) are not supported on this module.
ICMP redirect messages In software release 07.2.02, ICMP redirect messages are disabled by default, whereas in releases prior to 07.2.02, ICMP redirect messages are enabled by default. • • If ICMP redirect messages were enabled prior to upgrading to release 07.2.02, you will need to reenable this feature after upgrading to 07.2.02. To do so, enter the ip icmp redirect command at the global CONFIG level of the CLI. If ICMP redirect messages were disabled prior to upgrading to release 07.2.
Once the device has reloaded, the DHCP-client service will start up and a new dynamic IP address is assigned to the interface. The DHCP-client service feature is now enabled on the interface. Note regarding Telnet and Internet Explorer 7 The Telnet function in Web management does not work with Internet Explorer version 7.0.5730. The system goes to "telnet://10.43.43.145" page when the user clicks web/general system configuration/ (telnet) in Internet Explorer version 7.0.5730.
Feature support These release notes include a list of supported features in IronWare software for the FastIron devices supported in this release. For more information about supported features, refer to the manuals listed in Additional resources. Supported management features Table 8 lists the supported management features. These features are supported in the Layer 2, base Layer 3, edge Layer 3, and full Layer 3 software images.
Category and description FESX FGS SuperX FLS FSX 800 FSX 1600 • only) Hitless OS upgrade FGS-STK FLS-STK FWS FCX Hitless stacking management: • Hitless stacking switchover • Hitless stacking failover No No No No Yes Hitless support for: • PBR • GRE Tunnels • IPv6 to IPv4 Tunnels Yes (FSX 800 and FSX 1600 only) No No No Yes (PBR only) IronView Network Manager (optional standalone and HP OpenView GUI) Yes Yes Yes Yes Yes Remote monitoring (RMON) Yes Yes Yes Yes Yes Retaining Sy
Category and description FESX FGS SuperX FLS FSX 800 FSX 1600 FGS-STK FLS-STK FWS FCX Specifying the maximum number of entries allowed in the RMON Control Table Yes No No No Yes Specifying which IP address will be included in a DHCP/BOOTP reply packet Yes No No No Yes Traffic counters for outbound traffic Yes No No No No Web-based GUI Yes Yes Yes Yes Yes Web-based management HTTPS/SSL Yes Yes Yes Yes Yes Supported security features Table 9 lists the supported security feat
Category and description FESX FGS SuperX FLS FSX 800 FSX 1600 FGS-STK FLS-STK FWS FCX Authentication, Authorization and Accounting (AAA): • RADIUS • TACACS/TACACS+ Yes Yes Yes Yes Yes Denial of Service (DoS) attack protection: • Smurf (ICMP) attacks • TCP SYN attacks Yes Yes Yes Yes Yes DHCP Snooping Yes Yes Yes Yes Yes Dynamic ARP Inspection Yes Yes Yes Yes Yes EAP Pass-through Support Yes Yes Yes Yes Yes HTTPS Yes Yes Yes Yes Yes IP Source Guard Yes Yes Yes Yes
Category and description FESX FGS SuperX FLS FSX 800 FSX 1600 FGS-STK FLS-STK FWS FCX • Denial of Service (DoS) attack protection Yes No No No Yes • Source guard protection Yes Yes Yes Yes Yes • ACL-per-port-per-VLAN Yes Yes Yes Yes Yes Multi-device port authentication password override Yes Yes Yes Yes Yes Multi-device port authentication RADIUS timeout action Yes Yes Yes Yes Yes Secure Copy (SCP) Yes Yes Yes Yes Yes Secure Shell (SSH) v2 Yes Yes Yes Yes Yes
Supported system-level features Table 10 lists the supported system-level features. These features are supported in the Layer 2, base Layer 3, edge Layer 3, and full Layer 3 software images.
Category and description FESX FGS SuperX FLS FSX 800 FSX 1600 FGS-STK FLS-STK FWS FCX Displaying interface names in Syslog messages Yes Yes Yes Yes Yes Displaying TCP and UDP port numbers in Syslog messages Yes Yes Yes Yes Yes Dynamic buffer allocation for QoS priorities Yes Yes Yes Yes Yes Flow control: Yes • Responds to flow control packets, but does not generate them Yes Yes Yes Yes Inbound rate limiting (port-based fixed rate limiting on inbound ports) Yes Yes Yes Yes Ye
Category and description FESX FGS SuperX FLS FSX 800 FSX 1600 FGS-STK FLS-STK FWS FCX Port mirroring and monitoring (mirroring of both inbound and outbound traffic on individual ports) Yes Yes Yes Yes Yes Power over Ethernet (POE) Yes (POEenabled Interface modules with POE power supply) Yes (FGS-POE only) Yes Yes (FGS-POE- (FWS-POE STK only) and FWSG-POE only) Yes (FCX-SHPOE only) Power over Ethernet (POE)+ with 2:1 oversubscription Yes (SXFI48GPP module only) No No No Yes (FCX-SHPOE on
Supported Layer 2 features Layer 2 software images include all of the management, security, and system-level features listed in the previous tables, plus the features listed in Table 11. Table 11 Supported Layer 2 features Category and description FESX FGS SuperX FLS FSX 800 FSX 1600 FGS-STK FLS-STK FWS FCX 802.
Category and description FESX FGS SuperX FLS FSX 800 FSX 1600 FGS-STK FLS-STK FWS FCX Jumbo frames: • Up to 10240 bytes, or • Up to 10232 bytes in an IronStack Yes Yes Yes Yes Yes Link Aggregation Control Protocol (LACP) Yes Yes Yes Yes Yes Link Fault Signaling (LFS) for 10G Yes Yes Yes Yes Yes MAC-Based VLANs, including support for dynamic MAC-Based VLAN activation No Yes Yes Yes Yes Metro Ring Protocol 1 (MRP 1) Yes Yes Yes Yes Yes Metro Ring Protocol 2 (MRP 2) Yes Yes
Category and description FESX FGS SuperX FLS FSX 800 FSX 1600 FGS-STK FLS-STK FWS FCX Topology groups Yes Yes Yes Yes Yes Uni-directional Link Detection (UDLD) (Link keepalive) Yes Yes Yes Yes Yes Uplink Ports within a Port-Based VLAN Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes VLAN-based mirroring No Yes Yes Yes Yes VoIP Autoconfiguration and CDP Yes Yes Yes Yes Yes Virtual Switch Redundancy Protocol (VSRP) Yes Yes Yes Yes Yes VSRP-Aware security features Yes Yes
Supported base Layer 3 features Base Layer 3 software images include all of the management, security, system, and Layer 2 features listed in the previous tables, plus the features listed in Table 12. NOTE: FCX devices will not contain a base Layer 3 image. The features in this table will be supported on the full Layer 3 image for these devices.
Table 13 Supported edge Layer 3 features Category and description FGS-EPREM FLS-EPREM FWS-EPREM FWSG-EPREM OSPF V2 (IPv4) Yes Full RIP V1 and V2 Yes Route-only support (Global configuration level only) Yes Route redistribution Yes 1020 routes in hardware maximum Yes VRRP-E Yes Supported full Layer 3 features Full Layer 3 software images include all of the management, security, system, Layer 2, base Layer 3 and edge Layer 3 features listed in the previous tables, plus the features listed in Tab
Category and description FESX-PREM SuperX-PREM FSX 800-PREM FSX 1600-PREM FCX Internet Group Management Protocol (IGMP) V1, V2, and V3 (for multicast routing scenarios) Yes Yes ICMP Redirect messages Yes Yes IGMP V3 fast leave (for routing) Yes Yes IPv4 point-to-point GRE IP tunnels Yes (IPv6 devices only) No IPv6 Layer 3 forwarding1 Yes No IPv6 over IPv4 tunnels in hardware1 Yes No IPv6 Redistribution1 Yes No IPv6 Static Routes1 Yes No Multiprotocol Source Discovery Protocol (MSD
Category and description FESX-PREM SuperX-PREM FSX 800-PREM FSX 1600-PREM FCX RIPng (IPv6)1 Yes No Route-only support (Global CONFIG level and Interface level) Yes Yes Route redistribution (including BGP4) Yes Yes (BGP4 supported on ADV models only) Routes in hardware maximum: • FESX4 – up to 128K routes • FESX6 – up to 256K routes • FESX6-E – up to 512K routes • FSX – up to 256K routes • FCX – up to 16K routes Yes Yes Static ARP entries Yes (up to 6,000) Yes (up to 1,000) VRRP-E Yes Yes
Category and description FESX FGS SuperX FLS FSX 800 FSX 1600 FGS-STK FLS-STK FWS FCX IPv6 ncopy Yes Yes Yes Yes Yes IPv6 debug Yes Yes Yes Yes Yes IPv6 ping Yes Yes Yes Yes Yes IPv6 traceroute Yes Yes Yes Yes Yes DNS server name resolution Yes Yes Yes Yes Yes HTTP/HTTPS Yes Yes Yes Yes Yes Logging (Syslog) Yes Yes Yes Yes Yes RADIUS Yes Yes Yes Yes Yes SCP Yes Yes Yes Yes Yes SSH Yes Yes Yes Yes Yes SNMP Yes Yes Yes Yes Yes SNMP traps
Unsupported features Table 16 lists the features that are not supported on the FastIron devices. If required, these features are available on other Brocade devices.
Software image files for IronWare release R07.2.02j Table 17 lists the software image files that are available for IronWare Release 07.2.02j. Table 17 Software image files Device Boot Image Flash Image FESX SuperX FSX 800 FSX 1600 SXZ07200.bin SXS07202j.bin (Layer 2) or SXL07202j.bin (base Layer 3) or SXR07202j.bin (full Layer 3) FGS FLS FWS FGZ05000.bin FGS07202j.bin (Layer 2) or FGSL07202j.bin (base Layer 3) or FGSR07202j.bin (edge Layer 3) FGS-STK FLS-STK FGZ05000.bin FGS07202j.
Model Software Images Primary Flash Secondary Flash FGS FGS-STK FLS FLS-STK FWS Layer 2 Base Layer 3 FGS EPREM FLS EPREM FWS EPREM Edge Layer 3 Layer 2 FCX Layer 2 Layer 3 PoE Firmware files Table 19 lists the PoE firmware file types supported for IronWare Release 07.2.02j. The firmware files are specific to their devices and are not interchangeable. For example, you cannot load FCX PoE firmware on a FSX device. IronWare Software Release R07.2.02j.
still be functional but without PoE circuitry. Should you encounter such an issue, please contact Brocade Technical Support for servicing. Upgrading the software Use the procedures in this section to upgrade the software. Important notes about upgrading or downgrading the software Note the following when upgrading to software release 07.2.
earlier, all configuration items relating to port numbers will be invalid and will need to be reprogrammed in the switch. Upgrading the software to the new release This section describes how to upgrade the software to run release 07.2.02j. Before upgrading the software on the device, first read Important notes about upgrading or downgrading the software. Upgrading the boot code To upgrade the boot code, perform the following steps. 1.
FastIron Router# erase flash primary FastIron Router# erase flash secondary NOTE: If the primary flash contains additional files not related to the software update, it is recommended that you also delete these files. 3. Copy the flash code from the TFTP server into flash memory. To do so, use the copy command at the Privileged EXEC level of the CLI. copy tftp flash primary | secondary You should see output similar to the following.
NOTE: If the stacking EEPROM is missing or is not installed correctly, or if you have installed the wrong EEPROM, you will see an error message on the console. For details, see the FastIron Configuration Guide. 6. For devices in an IronStack, make sure all devices are running the same software image. See “Confirming software versions (IronStack devices)” in the next section. Confirming software versions (IronStack devices) All units in an IronStack must be running the same software image.
UNIT 3: SL 1: FCX-24GS POE 24-port Management Module Serial #: BCW22926209 License: FCX_ADV_ROUTER_SOFT_PACKAGE (LID: ) P-ENGINE 0: type DB90, rev 01 ========================================================================== UNIT 3: SL 2: FCX-2XGC 2-port 16G Module (2-CX4) ========================================================================== UNIT 3: SL 3: FCX-2XG 2-port 10G Module (2-XFP) ========================================================================== UNIT 4: SL 1: FCX-24GS 24-port Managemen
• Description of any troubleshooting steps already performed, with the results 2. Switch Serial Number Getting help or reporting errors E-mail and telephone access Go to http://www.brocade.com/services-support/index.page for the latest e-mail and telephone contact information. Go to http://www.brocade.com/ethernetproducts to obtain the latest version of the user guides. Reporting document errors Send an email to documentation@brocade.com to report errors you find in the user guides.
Defects This section lists the closed and opened defects in this release. Customer reported defects closed with code in Release R07.2.02j Defect ID: DEFECT000338448 Technical Severity: Medium Summary: CLI throws error message when SSH is accessed through the NMS system. Symptom: An error string “fips_hash_Update failed with 0x000000B3, CKR_SESSION_HANDLE_INVALID” appears on the CLI when SSH is accessed through the NMS system.
Defect ID: DEFECT000412264 Technical Severity: Medium Summary: [SX] Error message is printed while loading boot image for 7202X code. Symptom: Error message is printed while loading boot image for 7202X code. Feature: SX_SYSTEM Function: UNDETERMINED Reported In Release: FI 07.2.02 Service Request ID: 1095368 Defect ID: DEFECT000414072 Technical Severity: Medium Summary: Unable to reload the switches using IPv6 SNMP. Symptom: Unable to reload the switches using IPv6 SNMP.
Defect ID: DEFECT000448413 Technical Severity: Medium Summary: During boot up, a few characters at the start of syslog messages may be omitted. Symptom: When the FastIron device is reloaded, some of the initial characters are omitted for the first few Syslog messages. After some period of time, the messages are generated correctly. Probability: Medium Risk of Fix: Medium Feature: FI Embedded Management Function: SYSLOG Reported In Release: FI 07.3.
Customer reported defects closed with code in Release R07.2.02h Defect ID: DEFECT000347917 Technical Severity: Medium Summary: FCX device does not forward ARP broadcast packets when raw packet debugging is enabled. Symptom: When the "dm raw packet debugging" command is executed in a Telnet console, the incoming ARP broadcast packets may not be forwarded in FCX devices. Workaround: Turn off "dm raw".
Defect ID: DEFECT000406631 Technical Severity: Medium Summary: Bridge TC Event log is missing on FastIron SX switches from code 07.2.00 and later. Symptom: SX device running Multiple Spanning Tree(MSTP) may not log the reception of Bridge TC Event. Workaround: Configure edge port on all switch ports where servers and laptops are to be connected. Probability: Medium Feature: SX L2 Control Function: SpanningTree Protocols Reported In Release: FI 07.2.
Defect ID: DEFECT000415275 Technical Severity: Medium Summary: In some cases hardware route in FESX show as DROP and packets are not forwarded even if default route is configured. Symptom: SX router may drop packets matching to the routes configured earlier to drop, but were deleted and default route is configured. Workaround: This issue is not seen in 7.3c code and above. Probability: Low Feature: SX Layer 3 Forwarding - IPV4 Function: Data Forwarding (IPV4) Reported In Release: FI 07.2.
Defect ID: DEFECT000424399 Technical Severity: Medium Summary: Software might not be able to read optical monitoring values in M-SX optics. Symptom: FLS Device may not be able to read Digital Optical Monitoring (DOM) information from Optical Monitoring enabled optics. Probability: High Feature: DOM Function: DOM Reported In Release: FI 07.2.02 Service Request ID: 1094609 Customer reported defects closed with code in Release R07.2.
Defect ID: DEFECT000355892 Technical Severity: High Summary: The command “no snmp-server comm Public ro” is not retained after a reload. Symptom: When using the command “no snmp-server comm Public ro” the public community will be disabled and the device will no longer respond to SNMP requests using the Public community. However it is not placed in the running config or retained after a reload. Once the Device reloads it will begin to respond to polling and read only operations using this community.
Defect ID: DEFECT000388009 Technical Severity: Medium Summary: DNS resolution does not work when multiple DNS domain lists are used. Symptom: If several domain names are created using the “ip dns domain-list " command and the first domain name fails, the device keeps trying to reach it instead of trying the other configured domain names. Probability: High Feature: FCX Management Functionality Function: HTTPs/HTTP Reported In Release: FI 07.2.
Defect ID: DEFECT000392006 Technical Severity: Medium Summary: MIB OID snAgentPoePortWattage does not return the configured value. Symptom: The power limit on a PoE port can be set via SNMP and the value is configured correctly on the port, but it cannot be read and always displays the power value as 0 using the snAgentPoePortWattage MIB OID. Probability: High Feature: FCX Network Management Function: SNMP V4/V6 Reported In Release: FI 07.3.
Defect ID: DEFECT000396159 Technical Severity: Low Summary: RADIUS IP Address may be displayed incorrectly in the output of “show table-mac-vlan detail” command. Symptom: In the "show table-mac-vlan detail" display, not enough characters are allocated for the RADIUS IP address column, which can cause trailing characters to be lost for a given IP address. Probability: Medium Feature: FCX L2 Forwarding Function: MAC- BASED VLAN Reported In Release: FI 07.2.
Defect ID: DEFECT000400771 Technical Severity: Medium Summary: If the usage of TCAM entries reaches near the maximum, a route entry could be overwritten by another route entry. Symptom: Routed traffic may not be forwarded to directly connected hosts in rare instances if the TCAM usage reaches near its maximum limit. Workaround: Clear the ARP cache and MAC table, then disable and re-enable the relevant IP interface.
Customer reported defects closed with code in Release R07.2.02f Defect ID: DEFECT000315704 Technical Severity: High Summary: VE interface's line protocol remains up even if interface itself is not. Symptom: The outputs of "show ip interface" and "show interface ve" display a given VE's line protocol as 'Up' even though the interface is not enabled. Probability: High Risk of Fix: Medium Feature: FCX Layer 3 Forwarding - IPV4 and IPV6 Function: Virtual interface (ve) Manager Reported In Release: FI 07.1.
Defect ID: DEFECT000334383 Technical Severity: Medium Summary: With "delay-link-event" configured to dampen port flapping, unnecessary Syslog messages are generated if a 10G port goes down. Symptom: With "delay-link-event" configured to dampen port flapping, unnecessary Syslog messages are generated if a 10G port goes down. Probability: Low Risk of Fix: Low Feature: SX Layer1 features Function: port flap dampening Reported In Release: FI 07.2.
Defect ID: DEFECT000351270 Technical Severity: High Summary: When an FCX stack is reloaded, the Standby unit may reset unexpectedly. Symptom: When an FCX stack is reloaded or if the power cord to the Active unit is removed while the stack is up, the Standby unit may experience an unexpected reset. Probability: Low Risk of Fix: Low Feature: FCX L2 Forwarding Function: MAC Table/FDB Manager Reported In Release: FI 07.3.
Defect ID: DEFECT000362807 Technical Severity: Critical Summary: The newly elected Active Management module may reset after a switchover due to incomplete synchronization of ARP entries. Symptom: After doing a Switchover on SX, a flood of error messages indicating an invalid next hop entry are seen, followed by the Active Management module experiencing a reset. Probability: Medium Risk of Fix: Medium Feature: FI L3 Unicast Function: Forwarding - SX v4 Reported In Release: FI 07.3.
Defect ID: DEFECT000369368 Technical Severity: Medium Summary: SX momentarily forwards packets during boot up process. Symptom: During boot up process, SX forwards packets on a port for a short time when initializing that port even though it is disabled in the saved configuration. Probability: Medium Feature: SX Layer1 features Function: link status - speed and duplex status Reported In Release: FI 07.2.
Defect ID: DEFECT000375567 Technical Severity: Medium Summary: If hitless OS upgrade between incompatible SW code versions is attempted, a system reset may be experienced. Symptom: If hitless OS upgrade between incompatible software code versions is attempted, a system reset may be experienced. Workaround: Issue a regular 'reload' or 'boot system flash primary/secondary' instead of hitless-reload to upgrade.
Defect ID: DEFECT000377099 Technical Severity: Medium Summary: Interface and Port descriptions for 10/100M ports on some FWS models are incorrectly displayed as 'GigabitEthernet'. Symptom: On non-Gigabit capable FWS models (FWS624, FWS624-EPREM, FWS624-POE, FWS648, FWS648-EPREM & FWS648-POE), ifDescr and port description for 10/100M ports are displayed as 'GigabitEthernet' instead of 'FastEthernet'.
Defect ID: DEFECT000379697 Technical Severity: Critical Summary: ARP age is not refreshed after disabling/enabling a module even though there is constant traffic from/to the host. Symptom: ARP age is not refreshed after disabling/enabling the module even though there is constant traffic from/to the host. Probability: High Feature: SX Layer 3 Forwarding - IPV4 Function: Data Forwarding (IPV4) Reported In Release: FI 07.2.
Defect ID: DEFECT000383469 Technical Severity: Medium Summary: A Layer 2 loop may be created if the Native VLAN ID is changed on other vendors' switches. Symptom: If the Native VLAN ID is changed from the default on other vendors' switches that are connected to a Brocade device, a Layer 2 loop may result due to the Brocade device expecting an IEEE BPDU in the default VLAN 1.
Customer reported defects closed with code in Release R07.2.02e Defect ID: DEFECT000330146 Technical Severity: High Summary: Newly inserted Management Module may have invalid LID displayed, after which the module cannot be upgraded via SW Licensing. Symptom: On the Standby module, the LID value is displayed as ÿÿÿÿÿÿÿÿÿÿ. After a failover, the new Active will have this same LID and thus cannot be upgraded. Probability: High Feature: SX Management Functionality Function: CLI and parser Reported In FI 07.2.
Defect ID: DEFECT000344380 Technical Severity: Medium Summary: FCX IP traffic goes to the CPU if it ingresses an IP Subnet VE interface. Symptom: IP traffic goes to CPU with a VE interface configured on an IP Subnet VLAN, or if the VE is created first before adding ports to the VLAN. Probability: High Feature: FI L2 Function: Forwarding - VLAN Manager Reported In FI 07.3.
Defect ID: DEFECT000354169 Technical Severity: Medium Summary: A system memory leak may be seen on devices configured with PIM Routing. Symptom: Stack trace messages are printed on the console while the “show memory” output shows a rapid increase in memory consumption, eventually leading to a system reload. Probability: Medium Feature: SX L2/L3 Multicast Features Function: PIM Sparse Reported In FI 07.3.
Defect ID: DEFECT000356415 Technical Severity: Critical Summary: System unexpectedly resets after becoming unresponsive. Symptom: Device displays LID message, then freezes and is unresponsive even from console. Probability: Low Feature: Sw licensing Function: Licensing All Reported In FI 07.3.
Defect ID: DEFECT000359744 Technical Severity: Medium Summary: FESX code flash memory size is displayed incorrectly. Symptom: FESX code flash memory is displayed as 16MB even if it is only 8MB in size. Probability: High Feature: SX Management Functionality Function: CLI and parser Reported In FI 07.2.
Defect ID: DEFECT000364076 Technical Severity: High Summary: ARP request is not forward between Primary and Isolated VLANs. Symptom: When Private VLANs are configured, an ARP request is not forward between the Primary and Isolated VLANs. Probability: High Feature: FCX L2 Forwarding Function: Private VLAN Reported In FI 07.2.
Defect ID: DEFECT000366413 Technical Severity: Critical Summary: Static default route does not get updated after the master unit of the stack goes down. Symptom: If there are multiple static default routes from both master and non-master units, the default route from the master unit is correctly displayed in the routing table. But if the master unit is powered down, this route will still be displayed instead of the route from the non-master unit.
Defect ID: DEFECT000369317 Technical Severity: Medium Summary: Layer 3 connectivity is lost and ARP error messages are displayed on the console. Symptom: Messages such as "pp_find_arp_entry failed to create ARP entry" are seen on the console, while connectivity to the Internet is lost. Probability: High Feature: FCX Layer 3 Forwarding - IPV4 Function: Data Forwarding (IPV4) Reported In FI 07.2.02 Service Request ID: 671567 Release: Open defects in Release 07.2.
Defect ID: DEFECT000301831 Technical Severity: High Summary: When strict priority is configured on the FGS624P, QoS priority 7 traffic dropped in preference to QoS priority 0 traffic. Feature: FCX Quality Of Service Function: TOS/QOS Reported In FI 07.1.00 Release: Defect ID: DEFECT000302513 Technical Severity: Medium Summary: Following OSPF area configuration change, type4 LSA may be incorrectly advertized. Feature: SX Layer3 Control Protocols Function: OSPFV2 - IPV4 Reported In FI 07.1.
Defect ID: DEFECT000321932 Technical Severity: High Summary: SX router performed a system reset during system bringup and layer 3 protocol convergence along with reload of neighboring router. Probability: Low Feature: SX Layer 3 Forwarding - IPV4 and IPV6 Function: Data Forwarding Reported In FI 07.2.00 Release: Defect ID: DEFECT000321950 Technical Severity: High Summary: A 48-port FWS or FGS can be made to continuously flood known unicast frames out of all ports.
Defect ID: DEFECT000324507 Technical Severity: Medium Summary: Router cannot install a router LSA with more than 8304 bytes LSA size and generate a checksum error resulting in the OSPF neighbor staying in LOADING state. Probability: Medium Feature: OSPF Function: OSPF Reported In FI 07.2.00 Service Request ID: 265202 Release: Defect ID: DEFECT000326611 Technical Severity: High Summary: Executing "dm pp-interrupts counters" command with any device number causes an FESX to reload.
Defect ID: DEFECT000328640 Technical Severity: Medium Summary: The error "Internal error! var_tree_get_one_entry_prefer_end() no entry but avail=57" is displayed when IP address is created or removed on a virtual interface. Symptom: Error message "Internal error! var_tree_get_one_entry_prefer_end() no entry but avail=57" is displayed when the IP address is created or removed on a virtual interface.
Customer reported defects closed without code in Release R07.2.02 The following table lists the customer defects fixed in this release. Defect ID: DEFECT000333601 Technical Severity: High Summary: Receiving one RADIUS packet with an erroneous, unparsable attribute breaks the switch's ability to receive RADIUS packets until after the next reload. Reason Code: Already Fixed in Release Probability: High Feature: FCX L2 Forwarding Function: MAC- BASED VLAN Reported In Release: FI FGS 04.3.
