 Feedback
|
Table Of Contents
Release Notes for TopspinOS Release 2.8.0 Update 2
Determining the Software Version
Upgrading to a New Software Release
Changes From Release 2.8.0 Update 1 (build 99) to 2.8.0 Update 2 (build 164)
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for TopspinOS Release 2.8.0 Update 2
Release Date: Nov 26, 2007
Part Number: OL-9388-06Contents
This document includes the following sections:
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
Introduction
These release notes describe the features and known issues for the Topspin and Cisco SFS Series Product Family operating system 2.8.0 Update 2 (build 164) and Element Manager 2.8.0.10 software releases.
Note
System Requirements
This section describes the system requirements for this software release.
Determining the Software Version
To determine the version of the operating system that you are running on the switch, log in to the CLI and enter the show version EXEC command.
SFS-3012R> show version=========================================================================System Version Information=========================================================================system-version : SFS-3012R TopspinOS 2.8.0 releng #164 ...contact : tac@cisco.comname : SFS-3012RUpgrading to a New Software Release
To verify that you are running the latest available release, compare your version against the latest version on the Cisco support website at http://www.cisco.com/cgi-bin/tablebuild.pl/sfs-3000. After registering your product, you should have received a username and password that grant you access to this site.
Switch software and Linux host drivers are now released and packaged separately. Switch software is also now packaged and released separately for the following products:
•
•
•
•
•
•
Old and new TopspinOS releases can be used in the same InfiniBand fabric, although InfiniBand subnet manager synchronization will not occur between TopspinOS 2.9.0 and older releases.
Switches should be upgraded before the InfiniBand hosts. The CLI install command will prevent an incompatible software image from being installed. To upgrade Element Manager (EM) GUI, first uninstall the older version and then install software release 2.8.0.
For general information about upgrading to a new software release, see the Installing Software Images section in the Cisco SFS Product Family Element Manager User Guide.
New and Changed Information
TopspinOS 2.8.0 is a major release that introduces significant new features and documentation. It includes the following changes:
•
•
•
•
Changes From Release 2.8.0 Update 1 (build 99) to 2.8.0 Update 2 (build 164)
This section describes the new features and resolved caveats since the 2.8.0 Update 1 (build 99) release.
Note
InfiniBand
•
A problem has been fixed where the path MTU returned in PathRecord query could be set incorrectly, resulting in low throughput, especially for paths traversing DDR IB links.
•
A problem has been fixed where user configured IPoIB multicast groups were not saved and restored correctly if the multicast group was first automatically created by IPoIB.
•
A problem has been fixed where the IB Performance Management feature would not work with the High-Performance Subnet Manager (HSM) running on OFED.
•
A problem has been fixed where the IB Subnet Manager would fail and the chassis would reboot, due to a deadlock caused by a temporary InfiniBand packet credit loop while rerouting a network. The solution was to change the default packet lifetime from infinite (never discard) to approximately one second.
•
A problem has been fixed where the CLI show ib sm neighbor command could show incorrect information.
•
A problem has been fixed where the IB Subnet Manager did not always set the Attribute Offset in GetTable Response IB protocol messages.
Management
•
A problem has been fixed where SFS 3012R/3012 and Topspin 360 controller card could hang during normal operation.
•
Support has been added for configuring the timezone in TopspinOS. The local time will be printed in the chassis syslog and other logging information.
•
A problem has been fixed where closed telnet CLI sessions might not be cleaned up by the CLI. Note that the CLI terminal time-out must be set to non-zero for cleanup to always occur.
•
A problem has been fixed where user account settings would not be saved correctly when the configuration was saved from a GUI.
•
A problem has been fixed where configuring the mgmt-ib management InfiniBand interface with a non-default IB partition would also configure the interface on the default partition.
•
A problem has been fixed where configuring the mgmt-ib management InfiniBand interface with a non-default IB partition would not function correctly in a multi-chassis configuration.
Fibre Channel Gateway
•
Support has been added for displaying an SRP LUN size.
•
A problem has been fixed where the Fibre Channel gateway could crash during failover.
•
A problem has been fixed where the Fibre Channel gateway could cause SRP hosts to lose a path to storage.
•
A problem has been fixed where Solaris SRP hosts did not get their SRP connections evenly distributed across multiple gateways.
Ethernet Gateway
•
A problem has been fixed where all Ethernet gateway bridge groups would incorrectly become primary redundancy group when using non-default InfiniBand partition.
•
Support has been added for enabling directed IP broadcast on Ethernet gateway bridge groups and redundancy groups.
•
A problem has been fixed where IP multicast through Ethernet gateway would fail when an IB host left and then quickly rejoined an IP multicast group.
•
A problem has been fixed where IGMP leave messages were not being sent by Ethernet gateway.
•
A problem has been fixed where IGMP join and leave messages were sent in wrong order by Ethernet gateway.
•
A problem has been fixed where the first bridge group added to an Ethernet gateway redundancy group would not become the primary bridge group.
•
A problem has been fixed where Ethernet gateway redundancy group configuration changes did not get applied correctly.
•
A problem has been fixed where Ethernet gateway redundancy group deletion did not get applied correctly.
•
The maximum number of multicast groups in the Ethernet gateway has been increased from 128 to 512.
Caveats
This section describes temporary limitations of this release. These restrictions will be resolved in a future release of this product.
InfiniBand
•
InfiniBand switch cards cannot be hot swapped on SFS 3012R/3012 and Topspin 360, and there must always be an InfiniBand switch card present in slot 16 (bottom slot).
•
Management
•
If power is lost while the system image is being upgraded on SFS 3012R/3012 and Topspin 360, the chassis may not reboot correctly. The workaround is to put the chassis on a UPS while it is being upgraded.
•
The CLI command show card does not show all status for SFS 3012R/3012 and Topspin 360 InfiniBand switch cards.
•
The CLI command reload no-failover produces cryptic output on SFS 3012R/3012 and Topspin 360 on the second controller card, if there is one.
•
On Windows Internet Explorer, the Chassis Manager web interface may pop up in front of all other windows. This condition is due to a bug in the Sun JVM and is fixed in the latest Sun release, which can be downloaded at http://www.java.com/en/download/windows_ie.jsp.
•
The Ethernet management port (interface mgmt-ethernet) 100Base-T supports only full-duplex connectivity.
•
If a firmware upgrade fails, the CLI does not report why the failure occurred.
Workaround: Use the show logging end command to review the failure.
•
The error messages in the show logging command for environmental monitoring failures, such as failed power supplies, are cryptic.
•
The CLI does not provide any diagnostics if the NTP server(s) is not responding.
•
The EM GUI will not install if there is not sufficient temporary space in /tmp.
•
The Serial/Mgmt-Ethernet and Maintenance->System Info windows in the GUI may not display if the GUI has been running for a while.
•
The ALT-TAB icon for the Element Manager GUI is blank on Linux.
Fibre Channel Gateway
•
Each Fibre Channel gateway is limited to discovering 64 SRP hosts and 64 targets.
•
Fibre Channel gateway port status may not be displayed correctly if directly connected to storage and ports are manually enabled or disabled. The port status is correct, just not displayed correctly.
•
Configuring an SRP policy after Fibre Channel gateways are first booted may fail with the error message "Operation temporarily failed - try again." The workaround is to try again after approximately one minute.
•
The second HCA in a host doesn't connect to storage when SRP policies are restricted.
•
The Storage Manager GUI has a limit on the number of LUNs whose access policies can be modified at once. The workaround is to configure 60 or fewer LUNs at a time.
•
ITL (Initiator/Target/LUN) statistics are zero even if traffic is running to that ITL.
•
The Fibre Channel gateway does not correctly autonegotiate speed to 1Gbps if only one of the two ports are connected to a 1Gbps device. You must manually set the port speed to 1Gbps using the CLI/GUI.
•
The Storage Manager GUI online help is incomplete.
Ethernet Gateway
•
L3 routing mode is not supported. Only L2.5 bridging is supported.
•
Disabling or enabling IPoIB on an InfiniBand partition requires all Ethernet gateways and hosts to be rebooted for the change to take full effect.
•
The mgmt-ib interface must be configured and enabled for Ethernet redundancy to function.
•
The Ethernet gateway does not implement ARP aging.
•
The CLI command show card-inventory does not support displaying the SFS 3012R/3012 and Topspin 360 Ethernet gateway FPGA version.
•
Some Element Manager GUI IP statistics are not available in L2.5 bridging mode.
Related Documentation
The following list describes the documentation available with TopspinOS 2.8.0, which is available in electronic form and printed form upon request.
Note
You can download the latest documentation updates on the Cisco support site at http://www.cisco.com/en/US/partner/products/ps6418/tsd_products_support_category_home.html.
•
•
•
•
•
•
•
•
•
•
Service and Support
For additional support, you must first register your product at http://www.cisco.com. After registering, you may contact your supplier for support, or Cisco directly.
Refer to the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section in this document.
When you call Cisco Technical Support or use the Cisco Technical Support website at http://www.cisco.com, be prepared to provide the following information to support personnel:
General Information
•
•
•
•
Server Configuration
•
•
•
Chassis Configuration
•
•
Chassis Serial Number
The chassis serial number and corresponding bar code are provided on the serial number label, as shown in this example:
Model: TS360
SN UST323XXXXXXXXX
This chassis serial number can be found on the bottom of the chassis or the outside of the chassis box packaging. It can also be found in the output of the show backplane command.
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.
