Mellanox Technologies Mellanox SX1018 Release Note
Ethernet managed blade switch
Hide thumbs
Also See for Mellanox SX1018:
- Command reference manual (419 pages) ,
- User manual (88 pages) ,
- Release note (10 pages)
Table of Contents
Advertisement
Quick Links
Download this manual
See also:
User Manual
Advertisement
Table of Contents
Related Manuals for Mellanox Technologies Mellanox SX1018
Summary of Contents for Mellanox Technologies Mellanox SX1018
- Page 1 Mellanox MLNX-OS® Release Notes for SX1018HP Ethernet Managed Blade Switch Software Ver. 3.3.4100 www.mellanox.com Mellanox® Technologies Confidential...
- Page 2 Mellanox Technologies Mellanox® Technologies Confidential...
-
Page 3: Table Of Contents
Table of Contents Chapter 1 Introduction ..........4 Chapter 2 Supported Platforms, Firmware, Cables and Licenses . -
Page 4: Chapter 1 Introduction
Introduction This document is the Mellanox MLNX-OS® Release Notes for HP 689638-B21. MLNX-OS is a comprehensive management software solution that provides optimal perfor- mance for cluster computing, enterprise data centers, and cloud computing over Mellanox SwitchX® family. The fabric management capabilities ensure the highest fabric performance while the chassis management ensures the longest switch up time. -
Page 5: Supported Cables
Supported Cables The following are the qualified cables for SX1018HP: Table 2 - Qualified Cables for SX1018HP Cable Mellanox P/N HP P/N Description Length 655874-B21 HP QSFP/SFP+ adapter MC2207130-00A 670759-B21 HP IB FDR QSFP copper cable 0.5m MC2207130-001 670759-B22 HP IB FDR QSFP copper cable MC2207130-0A1 670759-B23 HP IB FDR QSFP copper cable... -
Page 6: Chapter 3 Changes And New Features
Changes and New Features Table 3 - SX1018HP Changes and New Features Category Description Release 3.3.4100 General HP switch blade reset factory using OA. General HP switch blade restore admin password using OA. Improved debug file upload mechanism. General Refer to “file debug-dump” command in the CLI reference guide. Added support for displaying system hardware revision. -
Page 7: Chapter 4 Known Issues
Known Issues For any possible errata due to hardware issues, please refer to the switch support prod- uct page. The following table describes MLNX-OS® known issues in this software release and possible workarounds. General Known Issues Table 4 - General Known Issues (Sheet 1 of 2) Index Category Description... - Page 8 Table 4 - General Known Issues (Sheet 2 of 2) Index Category Description Possible Workaround Configuration Manage- Loading the wrong system configuration file may ment hang the system. For example: an attempt to use an SX1016 config- uration file on an SX6036/SX6536/SX1035 sys- tem may cause the system to hang.
-
Page 9: Ethernet Known Issues
Ethernet Known Issues Table 5 - Ethernet Known Issues (Sheet 1 of 3) Index Category Description Possible Workaround Ethernet Interfaces The system allows tolerance of 4 bytes on top of the set MTU. Ethernet Interfaces In case of faulty cable, rise time of other interfaces in the system may be delayed. - Page 10 Table 5 - Ethernet Known Issues (Sheet 2 of 3) Index Category Description Possible Workaround VLAN When working with more than 2000 VLANs and To fix the problem, run the trying to change a port’s VLAN membership in commands interface modes hybrid/trunk using the command inter- ethernet 1/x switch- face 1/x switchport trunk allowed-vlan,...
- Page 11 Table 5 - Ethernet Known Issues (Sheet 3 of 3) Index Category Description Possible Workaround SNMP LLDP MIB OID lldpRemPortDesc is not sup- ported. Port Mirroring When port mirroring congestion is configured to “drop-excessive-frames” (best effort), while using the same analyzer port for more than a single mir- roring session, that port could drops packets from all flows not according to their configured priori- ties.
-
Page 12: Chapter 5 Bug Fixes
Bug Fixes The following table describes MLNX-OS® bug fixes in this software release. Table 6 - Bug Fixes Index Category Description Ethernet Interfaces Setting an interface switchport mode to “access” using the command switchport mode then deleting the access VLAN using the command no vlan results in said interface showing as a member of VLAN 0.