Home » HP Manuals » Servers » HP Mellanox SX1018 » Manual Viewer

HP Mellanox SX1018 Mellanox MLNX-OS User Manual for SX1018HP Ethernet Managed - Page 45

Upgrading System Firmware

Add to My Manuals
Save this manual to your list of manuals

Page 45 highlights

Rev 1.6.2 Step 2. Step 3. Step 4. Set the boot partition. Run: switch (config)# image boot next Save the configuration. Run: switch (config)# configuration write Reload the system. Run: switch (config)# reload 4.2.4 Upgrading System Firmware Each MLNX-OS software package version has a default switch firmware version. When you update the MLNX-OS software to a new version, an automatic firmware update process will be attempted by MLNX-OS. This process is described below. 4.2.4.1 After Updating MLNX-OS Software Upon rebooting your switch system after updating the MLNX-OS software, MLNX-OS software will first compare its default firmware version with the currently programmed firmware versions on all the switch modules (leafs and spines on director-class switches, or simply the switch card on edge switch systems). If one or more of the switch modules is programmed with a firmware version other than the default version, then MLNX-OS will automatically attempt to burn the default firmware version instead. If a firmware update takes place, then the login process will be delayed for a few minutes. To verify that the firmware update was successful, login to MLNX-OS and run the command "show asic-version" (can be run in any mode). This command lists all of the switch modules along with their FW versions. Make sure that all the FW versions are the same and match the default firmware version. If the firmware update failed for one or more modules, then the following warning will be displayed. Warning : Some of the subsystems are not updated with default FW . If you detect a firmware version mismatch for one or more modules of the switch system, please contact your assigned Mellanox Technologies field application engineer. 4.2.4.2 Importing Firmware and Changing the Default Firmware To perform an automatic firmware update by MLNX-OS for a different switch firmware version without changing the MLNX-OS version, import the firmware package as described below. MLNX-OS sets it as the new default firmware and performs the firmware update automatically as described in the previous subsections. Mellanox Technologies 45

Section	Page
Mellanox MLNX-OS™ User Manual for SX1018HP Ethernet Managed Blade Switch	1
Table of Contents	3
Document Revision History	6
About this Manual	7
1 Introduction	10
1.1 MLNX-OS Features	10
2 Getting Started	12
2.1 Configuring the Switch for the First Time - Installation Wizard	12
2.1.1 Re-running the Wizard	17
2.2 Starting The Command Line (CLI)	17
2.3 Starting the Web Interface	18
2.4 Licenses	20
2.4.1 Installing MLNX-OS License (CLI)	20
2.4.2 Installing MLNX-OS License (Web)	21
2.4.3 Retrieving Your Lost License Key	23
3 User Interfaces	25
3.1 Command Line Interface (CLI)	25
3.1.1 CLI Modes	25
3.1.2 Syntax Conventions	26
3.1.3 Getting Help	26
3.1.4 Prompt and Response Conventions	27
3.1.5 Using the Negation Form	28
3.1.6 Parameter Key	29
3.2 Web Interface	30
3.2.1 Setup Menu	31
3.2.2 System Menu	32
3.2.3 Security Menu	33
3.2.4 Ports Menu	33
3.2.5 Status Menu	34
3.2.6 IB SM Mgmt	34
3.2.7 Fabric Inspector	35
3.2.8 ETH Mgmt	36
4 System Management	37
4.1 Management Interface	37
4.1.1 Configuring Management Interfaces With Static IP Addresses	37
4.1.2 Configuring IPv6 Address on the Management Interface	37
4.1.3 Dynamic Host Configuration Protocol (DHCP)	37
4.1.4 Default Gateway	38
4.2 Software Management	38
4.2.1 Upgrading MLNX-OS Software	38
4.2.2 Deleting Unused Images	41
4.2.3 Downgrading MLNX-OS Software	42
4.2.3.1 Downloading Image	42
4.2.3.2 Downgrading Image	43
4.2.3.3 Switching to Partition with Older Software Version	44
4.2.4 Upgrading System Firmware	45
4.2.4.1 After Updating MLNX-OS Software	45
4.2.4.2 Importing Firmware and Changing the Default Firmware	45
4.3 File Management	46
4.3.1 Saving a Configuration File	46
4.3.2 Loading a Configuration File	47
4.3.3 Restoring Factory Default Configuration on a Switch System (Single Management Module)	47
4.4 Remote Logging	47
4.4.1 Configuring Remote Syslog to “info” Level	47
4.5 Event Notifications	48
4.5.1 E-mail Notifications	48
4.6 Diagnostics	49
4.6.1 Retrieving Return Codes when Executing Remote CLI Commands through SSH	49
4.7 User Management and Security	49
4.7.1 Authentication, Authorization and Accounting (AAA)	49
4.7.1.1 RADIUS	50
4.7.1.2 TACACS+	50
4.7.1.3 LDAP	50
4.7.2 Secure Shell (SSH)	51
4.7.2.1 Adding a Host and Providing an SSH Key	51
4.7.3 User Accounts	51
4.8 Network Management Interfaces	52
4.8.1 SNMP	52
4.8.1.1 Standard MIBs	52
4.8.1.2 Private MIB	54
4.8.1.3 Traps	54
4.8.1.4 Configuring SNMP	54
4.8.1.5 Configuring an SNMPv3 User	55
4.8.1.6 Configuring an SNMP notifications	55
4.8.2 MLNX-OS XML API	56
5 Ethernet Switching	58
5.1 Interface	58
5.1.1 Break-Out Cables	58
5.1.1.1 Changing the Module Type to a Split Mode	60
5.1.1.2 Returning to the Non-Split Mode	61
5.2 Link Aggregation Group (LAG)	61
5.2.1 Configuring Static Link Aggregation Group (LAG)	61
5.2.2 Configuring Link Aggregation Control Protocol (LACP)	62
5.3 VLANs	62
5.3.1 Configuring Access Mode and Assigning Port VLAN ID (PVID) to Interfaces	63
5.3.2 Configuring Hybrid Mode and Assigning Port VLAN ID (PVID) to Interfaces	63
5.3.3 Configuring Trunk Mode VLAN Membership	64
5.3.4 Configuring Hybrid Mode VLAN Membership	65
5.4 MAC Address Table	65
5.4.1 Configuring Unicast Static MAC Address	65
5.5 Spanning Tree	66
5.5.1 Rapid Spanning Tree Protocol	66
5.5.2 RSTP Enhancements	66
5.5.3 Disabling Spanning Tree Protocol	67
5.6 IGMP Snooping	67
5.6.1 Configuring IGMP Snooping	67
5.6.2 Defining a Multicast Router Port on a VLAN	68
5.7 Link Layer Discovery Protocol (LLDP)	69
5.7.1 Configuring LLDP	69
5.8 Quality of Service (QoS)	70
5.8.1 Priority Flow Control and Link Level Flow Control	70
5.8.2 Enhanced Transmission Selection (ETS)	72
5.9 Access Control List	73
5.9.1 Configuring Access Control List	74
5.9.2 ACL Actions	74
6 IP Routing	75
6.1 General	75
6.1.1 Interface VLAN	75
6.1.2 Equal Cost Multi-Path Routing (ECMP)	75

Match case Limit results 1 per page

Rev 1.6.2

Mellanox Technologies

Step 2.

Set the boot partition. Run:

Step 3.

Save the configuration. Run:

Step 4.

Reload the system. Run:

4.2.4

Upgrading System Firmware

Each MLNX-OS software package version has a default switch firmware version. When you

update the MLNX-OS software to a new version, an automatic firmware update process will be

attempted by MLNX-OS. This process is described below.

4.2.4.1

After Updating MLNX-OS Software

Upon rebooting your switch system after updating the MLNX-OS software, MLNX-OS software

will first compare its default firmware version with the currently programmed firmware versions

on all the switch modules (leafs and spines on director-class switches, or simply the switch card

on edge switch systems).

If one or more of the switch modules is programmed with a firmware version other than the

default version, then MLNX-OS will automatically attempt to burn the default firmware version

instead.

To verify that the firmware update was successful, login to MLNX-OS and run the command

“show asic-version” (can be run in any mode). This command lists all of the switch modules

along with their FW versions. Make sure that all the FW versions are the same and match the

default firmware version. If the firmware update failed for one or more modules, then the follow-

ing warning will be displayed.

Warning : Some of the subsystems are not updated with default FW <ver>.

4.2.4.2

Importing Firmware and Changing the Default Firmware

To perform an automatic firmware update by MLNX-OS for a different switch firmware version

without changing the MLNX-OS version, import the firmware package as described below.

MLNX-OS sets it as the new default firmware and performs the firmware update automatically

as described in the previous subsections.

switch (config)# image boot next

switch (config)# configuration write

switch (config)# reload

If a firmware update takes place, then the login process will be delayed for a few min-

utes.

If you detect a firmware version mismatch for one or more modules of the switch sys-

tem, please contact your assigned Mellanox Technologies field application engineer.