MLNX-OS_Ethernet_Rel..
Contents
1. ee 4 2 6 Supported System Director 5 2 7 Supported Software Licenses 5 2 8 Supported Cables Depos ee eek ee aad o c e 5 Chapter 3 Changes and New Features 6 Chapter 4 Known 5 8 4 1 General Known Issues 8 4 2 Ethernet Known 55 10 Chapter 5 Bug Fixes some oa AR bas Gace eese PRU 13 Chapter 6 Submitting a Service Request 13 Mellanox Techologies 3 J Mellanox Technologies Confidential 1 Introduction This document is the Mellanox MLNX OS Release Notes for IBM 90Y3474 6 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 The MLNX OS documentation package includes the following 3 documents e A command reference guide provides general information concerning the MLNX OS command line interface Auser manual provides general information concerning the scope and organization of MLNX OS as well as basic configuration examples Release2. Interfaces By using the interface range configuration mode a range of ports can be easily configured with the same parameters Ethernet Interfaces Added Ethernet interfaces ingress and egress rate counters The sampling inter val can be tuned using the command load interval in the interface configuration mode The output is given in the show interface ethernet command Refer to the CLI reference guide for additional details Release 3 2 1050 WebUI Added support for internal ports in WebUI WebUI Applied new Apache version Mellanox Technologies 6 Mellanox Technologies Confidential Table 2 IBM 90Y3476 Changes and New Features Category Description SNMP Added support for SNMPv3 notifications Configuration Management Removed jump start configuration wizard feature Network Interfaces Quality enhancement to link initialization Software Management Added support for fetching image from TFTP server using IPv6 Mellanox Technologies 7 Mellanox Technologies Confidential 4 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 4 1 Table 3 General Known Issues Sheet 1 of 3 Index Category Description Possible Workaround Management Interfac
3. notes provides information on the supported platforms changes and new fea tures and reports on software known issues as well as bug fixes 2 Supported Platforms Firmware Cables and Licenses 2 4 Supported Switch Systems Table 1 Supported Switch Systems Model Number Description SX90Y 3474 Sierra 32 Port 40Gb s Ethernet Blade Switch System 2 2 Supported CPU Architecture PPC 460 CPU families 2 3 Supported Firmware e SwitchX firmware version 9 2 3002 e SwitchX 2 firmware version 9 2 3002 ConnectX 2 firmware version 2 9 1314 and higher ConnectX 3 firmware version 2 11 1250 and higher 2 4 Supported Mezzanine ConnectX 2 Mezzanine P N 90Y3460 MalayaP 2 9 1314 and higher ConnectX 2 Mezzanine P N 90Y3480 MalayaP Net 2 9 1314 and higher ConnectX 3 Mezzanine P N 90Y3488 Merlin 2 30 2010 and higher ConnectX 3 Mezzanine P N 90Y3484 Nevada 2 11 1450 and higher ConnectX 3 Mezzanine P N 90Y3456 MalayaX 2 11 1450 and higher ConnectX 3 Mezzanine P N 90Y3468 MalayaX Net 2 11 1450 and higher 2 5 Supported CPLD 1 0 18 Mellanox Technologies 4 Mellanox Technologies Confidential 2 6 Supported System Director Plug In Plug in software version 003d 2 7 Supported Software Licenses For the software licenses supported with MLNX OS software please refer to the Licenses section of the Getting Started chapter of the Mellanox MLNX OS Use
4. F SUCH DAMAGE Mellanox TECHNOLOGIES Mellanox Technologies Mellanox Technologies Ltd 350 Oakmead Parkway Suite 100 Beit Mellanox Sunnyvale CA 94085 PO Box 586 Y okneam 20692 USA Israel www mellanox com www mellanox com Tel 408 970 3400 Tel 972 0 74 723 7200 Fax 408 970 3403 Fax 972 0 4 959 3245 Copyright 2013 Mellanox Technologies All Rights Reserved Mellanox amp Mellanox logo BridgeX amp ConnectX CORE Direct Infini Bridge InfiniHost InfiniScale MLNX OS PhyX SwitchX Virtual Protocol Interconnect and Voltaire are registered trademarks of Mellanox Technologies Ltd Connect IB FabricIT Mellanox Open Ethernet Mellanox Virtual Modular Switch MetroX MetroDX ScalableHPCTM Unbreakable Link are trademarks of Mellanox Technologies Ltd All other trademarks are property of their respective owners 2 Mellanox Technologies J Mellanox Technologies Confidential Table of Contents Chapter 1 Introduction sacs soo has RE beer RR ERE PEE erae 4 Chapter 2 Supported Platforms Firmware Cables and Licenses 4 2 1 Supported Switch Systems 4 2 2 Supported CPU 4 2 3 Supported Firmware 4 2 4 Supported gt 22 4 2 5 Supported CPLD scs hare aye alae ee
5. Mellanox TECHNOLOGIES Mellanox MLNX OS Release Notes for IBM SX90Y3474 Software Ver 3 3 3706 www mellanox com Mellanox Technologies Confidential NOTE THIS HARDWARE SOFTWARE OR TEST SUITE PRODUCT PRODUCT S AND ITS RELATED DOCUMENTATION ARE PROVIDED BY MELLANOX TECHNOLOGIES AS IS WITH ALL FAULTS OF ANY KIND AND SOLELY FOR THE PURPOSE OF AIDING THE CUSTOMER IN TESTING APPLICATIONS THAT USE THE PRODUCTS IN DESIGNATED SOLUTIONS THE CUSTOMER S MANUFACTURING TEST ENVIRONMENT HAS NOT MET THE STANDARDS SET BY MELLANOX TECHNOLOGIES TO FULLY QUALIFY THE PRODUCTO S AND OR THE SYSTEM USING IT THEREFORE MELLANOX TECHNOLOGIES CANNOT AND DOES NOT GUARANTEE OR WARRANT THAT THE PRODUCTS WILL OPERATE WITH THE HIGHEST QUALITY ANY EXPRESS ORIMPLIED WARRANTIES INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT ARE DISCLAIMED IN NO EVENT SHALL MELLANOX BE LIABLE TO CUSTOMER OR ANY THIRD PARTIES FOR ANY DIRECT INDIRECT SPECIAL EXEMPLARY OR CONSEQUENTIAL DAMAGES OF ANY KIND INCLUDING BUT NOT LIMITED TO PAYMENT FOR PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY WHETHER IN CONTRACT STRICT LIABILITY OR TORT INCLUDING NEGLIGENCE OR OTHERWISE ARISING IN ANY WAY FROM THE USE OF THE PRODUCT S AND RELATED DOCUMENTATION EVEN IF ADVISED OF THE POSSIBILITY O
6. 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 28 sFlow The discarded packets counter in sFlow samples may not be accurate and may expose a skew of one second Mellanox Technologies 12 Mellanox Technologies Confidential 5 Bug Fixes The following table describes MLNX OS bug fixes in this software release Table 5 Bug Fixes Index Category Description 1 Configuration Manage Binary and text configuration files apply fix ment 2 Configuration Manage The output of the commands show running config and configuration text gen ment erate are not displayed properly when using the VLAN range commands e g interface ethernet port switchport trunk hybrid allowed vlan lt gt Applying a configuration text file generated with these commands on a switch will result with port configured as being a member only of the last VLAN in the range 3 Configuration Manage The output of the commands show running config and configuration ment text generate is not displayed properly after the command priority flow control enable is used 4 EHCM Switch reload is added after update activate CMM command run 5 EHCM Image update may not complete successful
7. equence num ber 0 is deleted In other cases where there is an ACL entry with sequence number 0 it is moved to be sequence number 1 within the system upgrade procedure In case you have an ACL entry with sequence number 0 recreate it with different sequence number prior to the upgrade procedure Mellanox Technologies 8 J Mellanox Technologies Confidential Table 3 General Known Issues Sheet 2 of 3 Index Category Description Possible Workaround 9 Software Management Upon upgrade if there are more than 4 ACLs all of the ACL configuration is deleted If there are 4 ACLs or less rules with a sequence number larger than 495 are deleted 10 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 11 Configuration After loading a new configuration file please ment reboot the system Otherwise configuration might not be properly applied 12 Configuration Manage The command set revert factory keep Use the equivalent CMM ment basic keep connect saved is removed command instead 13 Configuration Manage Merging two binary configuration files using the Use the configuration text ment command configuration merge is currently not file Apply option instead su
8. es The CLI command ip default gateway interface sets the gateway address to 0 0 0 0 and prevents the user from adding other gateways Delete the entry by using the no ip default gate way command Management Interfaces The switch might have an expired HTTPS certifi cation Generate a new certificate by changing the hostname In Band Management In band management mode does not support IPv6 In Band Management In band management ARPs are not taken into account in the show ip are count command NTP The command show ntp always lists the last con figured NTP server even if it has been deleted This output can be safely ignore Software Management Only one image is allowed to be copied into the system using the image fetch command The user must remove old image files prior to fetching a new one Software Management Upgrading to v3 2 1050 or later forces all Con nectX 3 adapters that are connected to this switch to upgrade their firmware to adapter firm ware v2 11 0960 or later For switch to switch connections it is highly recommended that all SwitchX switches be upgraded to MLNX OSTM version v3 2 1050 or later to guarantee robust interoperability Software Management In case of an upgrade ACL sequence number 0 is not valid any more In case there are two ACL entries with sequence number of 0 and 1 sequential entries the ACL with s
9. f 3 Index 21 Category SNMP Description The error Cannot find module MELLANOX MIB can appear in the log when performing roll back to an older MLNX OS version This error can be safely ignored Possible Workaround 22 Chassis Management Upon reaching critical thermal threshold SR bit 2 is not set although the system is shut down and SR bit 3 is set instead 23 IP Routing The current release does not support L3 4 2 Ethernet Known Issues Table 4 Ethernet Known Issues Sheet 1 of 3 Index Category Description Possible Workaround 1 Ethernet Interfaces The system allows tolerance of 4 bytes on top of the set MTU 2 Ethernet Interfaces Running RDMA traffic without enabling flow Enable flow control over control might cause poor performance the specific ports 3 Ethernet Interfaces In case of faulty cable rise time of other interfaces in the system may be delayed 4 Ethernet Interfaces 40GDE passive copper cable of 5m length might Replace copper cable with experience link rise issues when connected to fiber cable some 3rd party 40GbE interfaces 5 Ethernet Interfaces Default MTU is modified as 1500 instead of 1522 6 Ethernet Interfaces There are no port counters for packet sizes 1518 1522 Ts Ethernet Interfaces Setting an interface switchport mode to access Reconfigure the interface to using the command s
10. ly if performed using CMM 6 Submitting a Service Request The Mellanox amp Support Center is at your service for any issues You may access the Warranty Service through the Web Request Form by using the following link http www mellanox com content pages php pg support index Mellanox Techologies 13 J Mellanox Technologies Confidential
11. nnel ent type port channel may not converge 14 LAG The following LACP port states are not available in MLNX OS I Individual H hot standby LACP only s Suspended R module removed 15 VLAN It might take approximately 20 seconds to create delete 1000 VLANs or to change the switchport mode of an interface 16 VLAN Deleting VLAN ranges on trunk hybrid ports is Restrict the range of correlated to the number of the trunk hybrid ports VLANSs deleted to groups of in the system up to a 100 VLANs 17 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 port trunk allowed the operation may timeout on account of it being vlan all interface too heavy Thus the port does not become prop ethernet 1 x switch erly configured as a member of those VLANs port trunk allowed Assuming port 1 is in trunk mode and there are vlan remove 1 100 in 3000 VLANs created a good practice would be to succession achieve membership of port 1 in VLANs 100 3000 use the command interface ethernet 1 x switchport trunk allowed vlan remove 1 100 instead of interface ethernet 1 x switchport trunk allowed vlan 100 3000 18 Spanning Tree Non standard behavior may occur on third party switch STP functionality when the port moves from Root to Alte
12. pported 14 Logging DROPPED MSG errors may appear during reload shutdown phase These errors can be safely ignored 15 User Management Some RADIUS and TACACS configurations Press the reset button for 15 keep the user locked out of the machine due to seconds and then log in timeout limitation using your local authentica tion Additionally fix the configuration to avoid any future timeout issues 16 User Management Logging into the system as USERID from the Log in again The second Serial Connection results in login failure the first attempt will result is suc attempt cessful login 17 WebUI Only a single WebUI login per host is possible To have multi sessions open several browser simul taneously 18 WebUI Reversing the time clock can result in WebUI Clear the graphs data after graphs corrupted data setting the clock 19 WebUI Enabling disabling HTTPS while connected via Refresh the page or navi HTTP to the WebUI may result in temporary loss gate back using the of connection to the webpage browser s back button 20 WebUI Switching between binary configuration files when connected to the WebUI using HTTPS might result in the following message being dis played Switched configuration to which was already the active database This message is incorrect and can be safely ignored Mellanox Technologies 9 J Mellanox Technologies Confidential Table 3 General Known Issues Sheet 3 o
13. r Manual 2 8 Supported Cables Please refer to the Mellanox Products Approved Cable Lists document for the list of supported cables http www mellanox com related docs user_manuals Mellanox_approved_cables pdf When using AOC cables longer than 100m use one VL to achieve full wire speed Ad Mellanox Technologies 5 J Mellanox Technologies Confidential 3 Changes and New Features Table 2 IBM 90Y3476 Changes and New Features Category Description Release 3 3 3706 General Bug fixes Release 3 3 3704 VPD Changes to VPD block 1 capability bits Release 3 3 3702 EHCM Added detailed reasons for failure of CMM upgrade feature EHCM Added fingerprint support for CMM update feature EHCM Image bank 1 represents the active image and image bank 2 represents the non active 1mage VPD Boot Rom will be reported in image segment 1 WebUI Security enhancements Release 3 3 3500 Management Interfaces In band management Ethernet Switching Port mirroring Ethernet Switching sFlow EHCM Enhancements to software update using CMM feature Release 3 3 3400 EHCM Added fwlImageProtocols OIDs support Release 3 3 3000 General New Linux kernel 2 6 32 Added VLAN configuration page to the WebUI West Added temperature critical and warning thresholds to temperature graph U boot Updated u boot memory access optimization Added interface range support Network
14. rnate state The standard Pro posal Agreement sent by MLNX OS is unan swered which may result in traffic loss of up to 30 seconds 19 IGMP Snooping Setting the ip igmp snooping unregistered multicast option to forward to mrouter ports option reduces the amount of supported VLANS to 250 Mellanox Technologies 11 Mellanox Technologies Confidential Table 4 Ethernet Known Issues Sheet 3 of 3 Index Category Description Possible Workaround 20 IGMP Snooping Only one mrouter interface can be added a cer Before adding an mrouter tain VLAN when IGMP Snooping is disabled on interface enable IGMP that VLAN or globally If more are added they Snooping globally and per overwrite their predecessors VLAN using the command ip igmp snooping 21 LLDP LLDP notifications are not supported 22 LLDP The mgmt0 mgmt1 IPv6 addresses the in band management address are not advertised on LLDP TLV s 23 ACLs A mask of IPv4 ACL rule can contain either 255 or 0 in any of the 4 bytes assembling it 24 ACLs Packets dropped by the switch due to congestion or ACL rules are added to the bad type counter of the matching VLAN interface 25 Modules Using 1GbE copper modules leads to the port sta tus being constantly reported as active regardless from the actual link state 26 SNMP LLDP MIB OID IldpRemPortDesc is not sup ported 27 Port Mirroring When port mirroring congestion is
15. witchport mode then delet have a valid access VLAN ing the access VLAN using the command no vlan results in said interface showing as a mem ber of VLAN 0 If the running config of that switch is exported to another the process fails 8 LAG Convergence time of port removal from a LAG Shut down the port prior of exceeds the specification by up to 30 seconds removing it from the LAG 9 LAG The remote LACP admin key 1 cannot be estab Use a different admin key lished with some third party vendors number 10 LAG Traffic running over LAG may not be evenly dis tributed when testing small number of SMACs 11 LAG When converting static LAG to dynamic LAG Disable and enable the LACP some of the ports remain in DOWN state LAG Mellanox Technologies 10 J Mellanox Technologies Confidential Table 4 Ethernet Known Issues Sheet 2 of 3 Index Category Description Possible Workaround 12 LAG LAG Hash function lacks configuration of a ran Change the distribution domization seed parameter Traffic passed over function between layers per LAG in hierarchy topology via multiple SwitchX forming LAG using the based systems is not distributed evenly command port channel load balance The work around is applicable in case there are multiple mixed flows 13 LAG When removing all ports of a port channel and Disable and enable the port then re adding them to the port channel in a differ cha
Download Pdf Manuals
Related Search
MLNX OS_Ethernet_Rel..