 Feedback
|
Table Of Contents
Release Notes for TopspinOS Release 2.9.0 Update 1
Determining the Software Version
Upgrading to a New Software Release
Changes From Release 2.9.0 FCS (build 147) to 2.9.0 Update 1 (build 163)
Changes From Release 2.7.0 FCS (build 14) to 2.9.0 FCS (build 147)
Changes From Release 2.5.0 Update 1 (build 251) to 2.7.0 FCS (build 14)
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for TopspinOS Release 2.9.0 Update 1
Release Date: May 15, 2007
Part Number: OL-9388-05Contents
This document contains these 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.9.0 Update 1 (build 163) and Element Manager 2.9.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-7000P> show version=========================================================================System Version Information=========================================================================system-version : TopspinOS 2.9.0 releng #163 ...contact : tac@cisco.comname : SFS-7000PUpgrading 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-7000 (http://www.cisco.com/cgi-bin/tablebuild.pl/sfs-bladecenter for BladeCenter). 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.9.0.
For general information about upgrading to a new software release, see the Install Software Images section in the Cisco SFS Product Family Chassis Manager User Guide and the Cisco 4x InfiniBand Switch Module for IBM BladeCenter User Guide.
New and Changed Information
TopspinOS 2.9.0 is a major release that introduces significant new features and documentation. It includes the following changes:
•
•
•
•
•
•
Changes From Release 2.9.0 FCS (build 147) to 2.9.0 Update 1 (build 163)
This section describes the new features and resolved caveats since the 2.9.0 FCS (build 147) release.
Note
InfiniBand
•
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 Element Manager GUI did not correctly display DDR/SDR speed information in the InfiniBand Topology View.
•
A problem has been fixed where the IB Subnet Manager did not always set Attribute Offset in GetTable Responses IB protocol messages.
Management
•
A problem has been fixed where snmpwalk of all MIBs failed on BladeCenter H in the tsDevGlobal MIB.
•
A problem has been fixed where scp file transfers would complete but would not update the progress meter.
•
A problem has been fixed where after executing the delete or clock set CLI commands, the reload CLI command would unnecessarily prompt if you wish to save changes.
•
The InfiniBand subnet manager max-hops value can now be set to 0 from the CLI.
•
Several errors were fixed in the GUI online help.
•
A problem has been fixed on BladeCenter H where a powered IB interface overcurrent event was not indicated to the BladeCenter H Management Module.
Changes From Release 2.7.0 FCS (build 14) to 2.9.0 FCS (build 147)
This section describes the new features and resolved caveats since the 2.7.0 FCS (build 14) release.
InfiniBand
•
Support has been added for configuration and management of 20 Gbps InfiniBand Double Data Rate links. All CLI, SNMP, and GUI areas support DDR. Note that the longest DDR copper IB cable supported at this time is 8 meters.
•
Support has been added for disabling IPoIB on an InfiniBand partition. This feature can be used to increase security on the default IB partition FFFF. Note that in 2.9.0 the mgmt-ib management InfiniBand interface cannot be used with a non-default IB partition.
•
Support has been added for routing around InfiniBand components that need maintenance. This feature adds a new route-around IB CLI command that isolates the component without disrupting traffic.
•
Support has been added for automatically determining the maximum number of hops (depth) that the InfiniBand subnet manager has to search when configuring the InfiniBand fabric. This feature adds a new value 0 to the max-hops IB CLI configure command, which will cause the Subnet Manager to optimize IB paths for shortest distance.
Management
•
TopspinOS 2.9.0 is the first release to support the SFS 7000D chassis. The management Ethernet port on the 7000D defaults to using DHCP to obtain an IP address.
•
Support has been added for clearing InfiniBand switch port counters with the new clear CLI command.
•
A problem has been fixed where CLI SSH logins would not authenticate with RADIUS or TACACS+.
•
A problem has been fixed where CLI logins would authenticate using local passwords after RADIUS or TACACS+ authentication failed.
•
Syslog message format is now more consistent with other Cisco products.
•
CLI error handling for incorrect commands is now more consistent with other Cisco products.
•
A problem has been fixed where command editing did not work properly in CLI SSH logins.
•
A problem has been fixed where the CLI copy command would fail with symbolic links on a remote FTP server.
•
A problem has been fixed where the CLI copy command would fail with filenames longer than 128 characters.
•
Several problems were fixed in the CLI diagnostic test commands.
Changes From Release 2.5.0 Update 1 (build 251) to 2.7.0 FCS (build 14)
This section describes the new features and resolved caveats since the 2.5.0 Update 1 (build 251) release.
InfiniBand
•
On SFS 7000P and SFS 7008P, power to an InfiniBand-powered interface is now turned off when the port is shut down. Power status is now displayed along with other port status values.
•
Added support for viewing the InfiniBand Linear Forwarding Table (LFT) and Multicast Forwarding Table (MFT) to SNMP, Element Manager GUI, and CLI.
•
Added support for configuring several more InfiniBand Subnet Manager parameters.
Management
•
Added support for viewing Cisco-standard Unique Device Indentifier Information with the new show inventory CLI command.
•
Added support for authentication with TACACS+.
•
Added support for secondary syslog server.
•
Added support for up to three RADIUS servers.
•
Added support for displaying a CLI login banner through the optional config:login-banner file.
•
The show card-inventory CLI command now displays uptime (number of seconds since booting) for each card.
•
Several problems were fixed in hardware fault error reporting.
Caveats
This section describes temporary limitations of this release. These restrictions will be resolved in a future release of this product.
InfiniBand
•
In autonegotiation mode, it is possible for an unconnected InfiniBand port to report errors if the port is part of a cluster of three ports, where at least one of the other ports is connected.
Management
•
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 addr-option value for the BladeCenter InfiniBand switch module Ethernet management interface should always be dynamic. Setting addr-option to static or dhcp will cause the BladeCenter Management Module to lose communication with the Switch Module.
•
An InfiniBand subnet manager max-hops value of 0 is not persistent across chassis reboots.
Workaround: Set max-hops to 0 each time the chassis is rebooted.
•
The Topspin 270, Cisco SFS 7008, and Cisco SFS 7008P Management Interface Module firmware is not automatically upgraded on hotplug (hotswap). If a new Management Interface Module is inserted into the chassis, the chassis should be rebooted or power-cycled to ensure that the firmware is upgraded.
•
The diagnostic interface ib commands are not supported.
•
Diagnostic tests should not be run during a Topspin 270, Cisco SFS 7008, and Cisco SFS 7008P controller hot standby failover. The diagnostic commands should not be run until all cards are up and running.
•
If a power cycle is performed on a Topspin 270, Cisco SFS 7008, and Cisco SFS 7008P after a software upgrade, rather than performing a reload command, it is possible that the core fabric in slot 12 can become the master after the power cycle.
•
It is possible for POST to detect a fan that is not completely plugged in, but the error does not show up in the show diag post or show diag fru-error command output. The error is reported in the hwif_log.
•
The Topspin 270, Cisco SFS 7008, and Cisco SFS 7008P incorrectly attempts to boot when no Management Interface Modules are present.
•
•
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.
Related Documentation
The following list describes the documentation available with TopspinOS 2.9.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.
CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0705R)
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.
