Mellanox Technologies Mellanox SX1018 Instruction Manual

www.mellanox.com
Mellanox MLNX-OS® Release Notes
for SX1018HP Ethernet Managed Blade Switch
Software Ver. 3.3.4100
Mellanox® Technologies Confidential

Mellanox Technologies
2
Mellanox® Technologies Confidential

Mellanox Techologies 3
Table of Contents
Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Chapter 2 Supported Platforms, Firmware, Cables and Licenses . . . . . . . . . . 4
2.1 Supported Switch Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Supported CPU Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3 Supported Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.4 Supported Software Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.5 Supported Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 3 Changes and New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Chapter 4 Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1 General Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2 Ethernet Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 5 Bug Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 6 Submitting a Service Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Mellanox® Technologies Confidential

Mellanox Technologies 4
1 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.
The MLNX-OS documentation package includes the following 3 documents:
• Command Reference Guide – provides general information concerning the MLNX-OS
command line interface
• User Manual – provides general information concerning the scope and organization of
MLNX-OS as well as basic configuration examples
• Release 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.1 Supported Switch Systems
Table 1 - Supported Switch Systems
Model Number Description
2.2 Supported CPU Architecture
• PPC 460 CPU families
2.3 Supported Firmware
• SwitchX® firmware version 9.2.4340
• SwitchX®-2 firmware version 9.2.4340
• ConnectX®-2 firmware version 2.9.1200 and higher
• ConnectX®-3 firmware version 2.11.1250 and higher
2.4 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 User Manual.
SX1018HP 34-Port 40Gb/s Ethernet Blade Switch System
Mellanox® Technologies Confidential

Mellanox Technologies 5
2.5 Supported Cables
The following are the qualified cables for SX1018HP:
Table 2 - Qualified Cables for SX1018HP
Mellanox P/N HP P/N Description Cable
Length
N/A 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 1m
MC2207130-0A1 670759-B23 HP IB FDR QSFP copper cable 1.5m
MC2207130-002 670759-B24 HP IB FDR QSFP copper cable 2m
MC2207128-003 670759-B25 HP IB FDR QSFP copper cable 3m
MFS4R12CB-003 670760-B21 HP IB FDR QSFP optical cable 3m
MFS4R12CB-005/
MC2207310-005
670760-B22 HP IB FDR QSFP optical cable 5m
MFS4R12CB-010 670760-B23 HP IB FDR QSFP optical cable 7m
MFS4R12CB-010/
MC2207310-010
670760-B24 HP IB FDR QSFP optical cable 10m
Mellanox® Technologies Confidential

Mellanox Technologies 6
3 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.
General Improved debug file upload mechanism.
Refer to “file debug-dump” command in the CLI reference guide.
General Added support for displaying system hardware revision.
Refer to “show inventory” command in the CLI reference guide.
Logging Added support for event notification to monitor.
Refer to Event Notification chapter in the User Manual.
User Interfaces Improved login timeout mechanism.
Release 3.3.3500
Management Interfaces In-band management.
Ethernet Switching Port mirroring.
Ethernet Switching sFlow.
Release 3.3.3000
General New Linux kernel 2.6.32.
Network Interfaces Added interface range support.
By using the interface range configuration mode, a range of ports can be easily config-
ured with the same parameters.
Ethernet Interfaces Added Ethernet interfaces ingress and egress rate counters. The sampling interval can
be tuned using the command load-interval in the interface configuration mode. The out-
put is given in the “show interface ethernet” command. Refer to the CLI reference guide
for additional details.
Release 3.3.1000
U-boot Updated U-boot - memory access optimization.
WebUI Added VLAN configuration page to the WebUI.
General Bug fixes.
Mellanox® Technologies Confidential

Mellanox Technologies 7
4 Known Issues
The following table describes MLNX-OS® known issues in this software release and possible
workarounds.
4.1 General Known Issues
For any possible errata due to hardware issues, please refer to the switch support prod-
uct page.
Table 4 - General Known Issues (Sheet 1 of 2)
Index Category Description Possible Workaround
1. Management Interfaces 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.
2. In-Band Management In-band management mode does not support IPv6.
3. In-Band Management In-band management ARPs are not taken into
account in the “show ip are count” command.
4. 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.
5. 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.
6. Software Management Upgrading to v3.2.0594 (or later) forces all Con-
nectX®-3 adapters that are connected to this
switch to upgrade their firmware to adapter firm-
ware v2.10.7204 (or later). For switch-to-switch
connections, it is highly recommended that all
SwitchX® switches be upgraded to MLNX-OS
version v3.2.0594 (or later) to guarantee robust
interoperability.
7. 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 sequence-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.
8. 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.
Mellanox® Technologies Confidential

Mellanox Technologies 8
9. Configuration Manage-
ment
Loading the wrong system configuration file may
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.
10. Configuration Manage-
ment
After loading a new configuration file, please
reboot the system. Otherwise, configuration might
not be properly applied.
11. Configuration Manage-
ment
Prior to license deletion make sure to be in an
allowed profile. Failing to do so results in errors.
12. Logging “DROPPED MSG” errors may appear during
reload (shutdown phase). These errors can be
safely ignored.
13. Logging The following error may appear in the log during
system de-init:
“[mdreq.ERR]: init(), mdr_main.c:634, build 1:
Error code 14014”
This error can be safely ignored.
14. User Management Some RADIUS and TACACS+ configurations
keep the user locked out of the machine due to
timeout limitation.
Press the reset button for 15
seconds, and then log in
using your local authentica-
tion. Additionally, fix the
configuration to avoid any
future timeout issues.
15. WebUI Only a single WebUI login per host is possible. To have multi-sessions,
open several browser simul-
taneously.
16. WebUI Reversing the time clock can result in WebUI
graphs’ corrupted data.
Clear the graphs data after
setting the clock.
17. WebUI Enabling/disabling HTTPS while connected via
HTTP to the WebUI may result in temporary loss
of connection to the webpage.
Refresh the page or navi-
gate back using the
browser’s back button.
18. SNMP The error “Cannot find module (MELLANOX-
MIB)” can appear in the log when performing roll-
back to a MLNX-OS version older than 3.3.3000.
This error can be safely ignored.
19. Chassis Management Supported USB flash drives are USBv2 protocol
and above.
20. IP Routing The current release does not support L3.
Table 4 - General Known Issues (Sheet 2 of 2)
Index Category Description Possible Workaround
Mellanox® Technologies Confidential

Mellanox Technologies 9
4.2 Ethernet Known Issues
Table 5 - 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 In case of faulty cable, rise time of other interfaces
in the system may be delayed.
3. Ethernet Interfaces 40GbE passive copper cable of 5m length might
experience link rise issues when connected to
some 3rd party 40GbE interfaces.
Replace copper cable with
fiber cable
4. Ethernet Interfaces Default MTU is modified as 1500 instead of 1522.
5. Ethernet Interfaces There are no port counters for packet sizes 1518-
1522.
6. LAG Convergence time of port removal from a LAG
exceeds the specification by up to 30 seconds.
Shut down the port prior of
removing it from the LAG.
7. LAG The remote LACP admin-key #1 cannot be estab-
lished with some third party vendors.
Use a different admin-key
number.
8. LAG Traffic running over LAG may not be evenly dis-
tributed when testing small number of SMACs.
9. LAG When converting static LAG to dynamic LAG
(LACP), some of the ports remain in DOWN state.
Disable and enable the
LAG.
10. LAG LAG Hash function lacks configuration of a ran-
domization seed parameter. Traffic passed over
LAG in hierarchy topology via multiple SwitchX
based systems is not distributed evenly.
Change the distribution
function between layers per-
forming LAG using the
command
port-channel
load-balance
. The work-
around is applicable in case
there are multiple mixed
flows.
11. LAG When removing all ports of a port-channel and
then re-adding them to the port-channel in a differ-
ent type, port-channel may not converge.
Disable and enable the port-
channel.
12. LAG The following LACP port-states are not available
in MLNX-OS®:
• I – Individual H – hot-standby (LACP only)
• s – Suspended R – module-removed
13. VLAN It might take approximately 20 seconds to create/
delete 1000 VLANs, or to change the switchport
mode of an interface.
14. VLAN Deleting VLAN ranges on trunk/hybrid ports is
correlated to the number of the trunk/hybrid ports
in the system.
Restrict the range of
VLANs deleted to groups of
up to a 100 VLANs.
Mellanox® Technologies Confidential

Mellanox Technologies 10
15. VLAN When working with more than 2000 VLANs and
trying to change a port’s VLAN membership in
modes hybrid/trunk using the command
inter-
face 1/x switchport trunk allowed-vlan
,
the operation may timeout on account of it being
too heavy. Thus, the port does not become prop-
erly configured as a member of those VLANs.
Assuming port 1 is in trunk mode and there are
3000 VLANs created, a good practice would be to
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
.
To fix the problem, run the
commands
interface
ethernet 1/x switch-
port trunk allowed-
vlan all
and interface
ethernet 1/x switch-
port trunk allowed-
vlan remove 1-100
in
succession.
16. Spanning Tree Non-standard behavior may occur on third party
switch STP functionality when the port moves
from Root to Alternate state. The standard Pro-
posal-Agreement sent by MLNX-OS is unan-
swered which may result in traffic loss of up to 30
seconds.
17. IGMP Snooping Setting the
ip igmp snooping unregistered
multicast
option to forward-to-mrouter-
ports
option reduces the amount of supported
VLANs to 250.
18. IGMP Snooping There is no possibility to have more than one
mrouter port on a single VLAN if igmp snooping
is disabled for that vlan
After enabling igmp snoop-
ing on that VLAN, the user
needs to add again the
mrouter-ports on that
VLAN.
19. LLDP LLDP notifications are not supported.
20. LLDP The mgmt0, mgmt1 IPv6 addresses and the in-
band management address are not advertised on
LLDP TLV(s).
21. ACLs A mask of IPv4 ACL rule can contain either 255
or 0 in any of the 4 bytes assembling it.
22. ACLs Packets dropped by the switch due to congestion
or ACL rules are added to the bad type counter of
the matching VLAN interface.
23. Modules When using 5m splitter cable (P/N MC2609125-
005), wrong data is displayed under transceiver
information.
24. Modules Using 1GbE copper modules leads to the port sta-
tus being constantly reported as active regardless
from the actual link state.
Table 5 - Ethernet Known Issues (Sheet 2 of 3)
Index Category Description Possible Workaround
Mellanox® Technologies Confidential

Mellanox Technologies 11
25. SNMP LLDP MIB OID lldpRemPortDesc is not sup-
ported.
26. 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.
27. sFlow The discarded packets counter in sFlow samples
may not be accurate and may expose a skew of
one second.
Table 5 - Ethernet Known Issues (Sheet 3 of 3)
Index Category Description Possible Workaround
Mellanox® Technologies Confidential

Mellanox Techologies 12
5 Bug Fixes
The following table describes MLNX-OS® bug fixes in this software release.
Table 6 - Bug Fixes
Index Category Description
6 Submitting a Service Request
The Mellanox® 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.
1. 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. If the running-config of that switch is
exported to another, the process fails.
2. Ethernet Interfaces Ethernet link may fail to rise when using SFP+ modules or splitter cable.
3. Ethernet Interfaces Traffic loss may occur when enabling flow control on a packet with an MTU
larger then 8K.
4. IGMP Snooping Only one mrouter interface can be added on a certain VLAN when IGMP Snoop-
ing is disabled on that VLAN (or globally). If more are added, they overwrite their
predecessors.
Mellanox® Technologies Confidential