Mlnx-Os Um PDF
Mlnx-Os Um PDF
User Manual
Rev 5.5
Software Version 3.7.1000
Mellanox Technologies
350 Oakmead Parkway Suite 100
Sunnyvale, CA 94085
U.S.A.
www.mellanox.com
Tel: (408) 970-3400
Fax: (408) 970-3403
Mellanox®, Mellanox logo, Accelio®, BridgeX®, CloudX logo, CompustorX®, Connect-IB®, ConnectX®,
CoolBox®, CORE-Direct®, EZchip®, EZchip logo, EZappliance®, EZdesign®, EZdriver® , EZsystem®,
GPUDirect®, InfiniHost®, InfiniBridge®, InfiniScale®, Kotura®, Kotura logo, Mellanox CloudRack®, Mellanox
CloudXMellanox®, Mellanox Federal Systems®, Mellanox HostDirect®, Mellanox Multi-Host®, Mellanox Open
Ethernet®, Mellanox OpenCloud®, Mellanox OpenCloud Logo®, Mellanox PeerDirect®, Mellanox ScalableHPC®,
Mellanox StorageX®, Mellanox TuneX®, Mellanox Connect Accelerate Outperform logo, Mellanox Virtual Modular
Switch®, MetroDX®, MetroX® , MLNX-OS®, NP-1c®, NP-2®, NP-3®, NPS® , Open Ethernet logo, PhyX®,
PlatformX®, PSIPHY®, SiPhy®, StoreX®, SwitchX®, Tilera®, Tilera logo, TestX®, TuneX®, The Generation of
Open Ethernet logo, UFM®, Unbreakable Link®, Virtual Protocol Interconnect®, Voltaire® and Voltaire logo are
registered trademarks of Mellanox Technologies, Ltd.
Mellanox Technologies . 3
3.2.8 CLI Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.3 Web Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.3.1 Setup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
3.3.2 System Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.3.3 Security Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.3.4 Ports Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.3.5 Status Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.3.6 IB SM Mgmt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
3.3.7 Fabric Inspector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
3.3.8 IB Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.4 Secure Shell (SSH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.4.1 Adding a Host and Providing an SSH Key . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.4.2 Retrieving Return Codes when Executing Remote Commands. . . . . . . . . 70
3.5 Management Information Bases (MIBs). . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.6 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
3.6.1 CLI Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
3.6.2 Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
3.6.3 SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
3.6.4 Remote Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
3.6.5 Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Chapter 4 System Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
4.1 Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
4.1.1 Configuring Management Interfaces with Static IP Addresses . . . . . . . . 126
4.1.2 Configuring IPv6 Address on the Management Interface . . . . . . . . . . . . 126
4.1.3 Dynamic Host Configuration Protocol (DHCP) . . . . . . . . . . . . . . . . . . . . . 127
4.1.4 Default Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
4.1.5 Configuring Hostname via DHCP (DHCP Client Option 12) . . . . . . . . . . . 127
4.1.6 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
4.1.6.1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
4.1.6.2 Hostname Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
4.1.6.3 Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
4.1.6.4 Network to Media Resolution (ARP & NDP) . . . . . . . . . . . . . . . . . . . . . . 159
4.1.6.5 DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
4.1.6.6 IP Diagnostic Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
4.2 NTP, Clock & Time Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
4.2.1 NTP Authenticate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
4.2.2 NTP Authentication Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
4.2.3 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
4.3 Unbreakable Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
4.3.1 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
4.4 Software Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Mellanox Technologies . 4
4.4.1 Important Pre-OS Upgrade Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
4.4.2 Upgrading MLNX-OS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
4.4.3 Upgrading MLNX-OS Software on Director Switches. . . . . . . . . . . . . . . . 208
4.4.4 Upgrading MLNX-OS HA Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
4.4.5 Upgrading MLNX-OS MLAG-STP Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
4.4.6 Deleting Unused Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
4.4.7 Downgrading MLNX-OS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
4.4.7.1 Downloading Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
4.4.7.2 Downgrading Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
4.4.7.3 Switching to Partition with Older Software Version . . . . . . . . . . . . . . . . 213
4.4.8 Upgrading System Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
4.4.8.1 After Updating MLNX-OS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
4.4.8.2 After Inserting a Switch Spine or Leaf . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
4.4.8.3 Importing Firmware and Changing the Default Firmware . . . . . . . . . . . 215
4.4.9 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
4.5 Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
4.5.1 Saving a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
4.5.2 Loading a Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
4.5.3 Restoring Factory Default Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . 230
4.5.4 Managing Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
4.5.4.1 BIN Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
4.5.4.2 Text Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
4.5.5 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
4.5.5.1 File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
4.5.5.2 Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
4.6 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
4.6.1 Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
4.6.2 Remote Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
4.6.3 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
4.7 Link Diagnostic Per Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
4.7.1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
4.7.2 List of Possible Output Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
4.7.3 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
4.8 Signal Degradation Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
4.8.1 Effective-BER Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
4.8.2 Configuring Signal Degradation Monitoring . . . . . . . . . . . . . . . . . . . . . . . 295
4.8.3 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
4.9 Event Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
4.9.1 Supported Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
4.9.2 SNMP Trap Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
4.9.3 Terminal Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
4.9.4 Email Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Mellanox Technologies . 5
4.9.5 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
4.9.5.1 Email Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
4.10 Telemetry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
4.10.1 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
4.11 mDNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
4.11.1 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
4.12 User Management and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
4.12.1 User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
4.12.2 Authentication, Authorization and Accounting (AAA). . . . . . . . . . . . . . . 347
4.12.2.1 User Re-authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
4.12.2.2 RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
4.12.2.3 TACACS+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
4.12.2.4 LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
4.12.3 System Secure Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
4.12.4 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
4.12.4.1 User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
4.12.4.2 AAA Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
4.12.4.3 RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
4.12.4.4 TACACS+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
4.12.4.5 LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
4.12.4.6 System Secure Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
4.13 Cryptographic (X.509, IPSec) and Encryption. . . . . . . . . . . . . . . . . . . . . . 395
4.13.1 System File Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
4.13.1.1 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
4.14 Scheduled Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
4.14.1 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
4.15 Statistics and Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
4.15.1 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
4.16 Chassis Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
4.16.1 System Health Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
4.16.1.1 Re-Notification on Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
4.16.1.2 System Health Monitor Alerts Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . 444
4.16.2 Power Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
4.16.2.1 Power Supply Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
4.16.2.2 Width Reduction Power Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
4.16.2.3 Managing Chassis Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
4.16.3 Monitoring Environmental Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
4.16.4 USB Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
4.16.5 Unit Identification LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
4.16.6 High Availability (HA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
4.16.6.1 Chassis High Availability Nodes Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
4.16.6.2 Malfunctioned CPU Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Mellanox Technologies . 6
4.16.6.3 Box IP Centralized Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
4.16.6.4 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
4.16.6.5 Takeover Functionally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
4.16.7 System Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
4.16.7.1 Rebooting 1U Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
4.16.7.2 Rebooting Director Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
4.16.8 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
4.16.8.1 Chassis Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
4.16.8.2 Chassis High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
4.17 Network Management Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
4.17.1 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
4.17.1.1 Standard MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
4.17.1.2 Private MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
4.17.1.3 Proprietary Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
4.17.1.4 Configuring SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
4.17.1.5 Resetting SNMPv3 Engine ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
4.17.1.6 Configuring an SNMPv3 User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
4.17.1.7 Configuring an SNMP Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
4.17.1.8 SNMP SET Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
4.17.1.9 IF-MIB and Interface Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
4.17.2 JSON API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
4.17.2.1 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
4.17.2.2 Sending the Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
4.17.2.3 JSON Request Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
4.17.2.4 JSON Response Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
4.17.2.5 Supported Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
4.17.2.6 JSON Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
4.17.2.7 JSON Request Using WebUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
4.17.3 XML API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
4.17.4 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
4.17.4.1 SNMP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
4.17.4.2 XML API Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
4.17.4.3 JSON API Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
4.18 Puppet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
4.18.1 Setting the Puppet Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
4.18.2 Accepting the Switch Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
4.18.3 Installing Modules on the Puppet Server . . . . . . . . . . . . . . . . . . . . . . . . . 546
4.18.4 Supported Configuration Capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
4.18.4.1 InfiniBand Interface Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
4.18.4.2 SNMP Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
4.18.4.3 Fetched Image Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
4.18.4.4 Installed Image Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
4.18.5 Supported Resources for Each Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Mellanox Technologies . 7
4.18.6 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
4.18.6.1 Switch and Server Clocks are not Synchronized . . . . . . . . . . . . . . . . . . . 548
4.18.6.2 Outdated or Invalid SSL Certificates Either on the Switch or the Server 548
4.18.6.3 Communications Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
4.18.7 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
4.19 Control Plane Policing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
4.19.1 IP Table Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
4.19.1.1 Configuring IP Table Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
4.19.1.2 Modifying IP Table Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
4.19.1.3 Rate-limit Rule Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
4.19.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
4.19.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
Chapter 5 InfiniBand Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
5.1 Node Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
5.1.1 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
5.2 Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
5.2.1 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
5.3 IB Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
5.3.1 Configuring IB Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
5.3.2 Subnet Prefix Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
5.3.3 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
5.4 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
5.4.1 Transceiver Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
5.4.2 High Power Transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
5.4.3 Forward Error Correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
5.4.4 Break-Out Cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
5.4.4.1 Changing System Profile to Allow for Split-Ready Configuration . . . . . 594
5.4.4.2 Changing the Module Type to a Split Mode . . . . . . . . . . . . . . . . . . . . . . 594
5.4.4.3 Unsplitting a Split Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
5.4.5 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
5.5 Subnet Manager (SM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
5.5.1 Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
5.5.1.1 Relationship with ib0 Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
5.5.1.2 Configuring Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
5.5.2 Adaptive Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
5.5.3 Scatter Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
5.5.4 GUID Routing Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
5.5.5 Bulk Update Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
5.5.6 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
5.5.6.1 Subnet Manager (SM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
5.5.6.2 Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
Mellanox Technologies . 8
5.5.6.3 Quality of Service (SM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
5.5.6.4 Scatter Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
5.5.6.5 GUID Routing Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
5.5.6.6 Bulk Update Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
5.6 Subnet Manager (SM) High Availability (HA) . . . . . . . . . . . . . . . . . . . . . . 803
5.6.1 Joining, Creating or Leaving an InfiniBand Subnet ID. . . . . . . . . . . . . . . . 803
5.6.2 MLNX-OS Management Centralized Location . . . . . . . . . . . . . . . . . . . . . 804
5.6.3 High Availability Node Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804
5.6.4 Configuring MLNX-OS SM HA Centralized Location . . . . . . . . . . . . . . . . . 805
5.6.5 Creating and Adding Systems to an InfiniBand Subnet ID . . . . . . . . . . . . 805
5.6.6 Restoring Subnet Manager Configuration . . . . . . . . . . . . . . . . . . . . . . . . 805
5.6.6.1 Subnet Manager Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
5.6.6.2 Mellanox High Availability and Opensm Handover/Failover . . . . . . . . . 806
5.6.7 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
5.7 Fabric Inspector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
5.7.1 Running Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
5.7.2 Mapping GUIDs to Node Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
5.7.3 Importing ibdiagnet Fabric Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
5.7.4 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821
Appendix A Enhancing System Security According to NIST SP 800-131A . . 843
A.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
A.2 Web Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
A.3 Code Signing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
A.4 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
A.5 SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
A.6 HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
A.7 LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
Appendix B Splunk Integration with Mellanox Products . . . . . . . . . . . . . . . 849
B.1 Getting Started with Splunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
B.2 Switch Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
B.3 Adding a Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
B.4 Retrieving Data from TCP and UDP Ports . . . . . . . . . . . . . . . . . . . . . . 852
B.5 SNMP Input to Poll Attribute Values and Catch Traps . . . . . . . . . . . . 854
B.6 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
B.7 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
Mellanox Technologies . 9
List of Tables
Mellanox Technologies . 10
Table 33: SNMP MELLANOX-EFM-MIB Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .491
Table 34: SNMP MELLANOX-POWER-CYCLE Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .492
Table 35: Supported SET OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .497
Table 36: Ethernet and Port-Channel Interface Capabilities . . . . . . . . . . . . . . . . . . . . . . . .546
Table 37: Protocol Enable/Disable Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .547
Table 38: Fetched Image Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .547
Table 39: Installed Image Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .548
Table 40: Fetched Image Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .548
Table 41: Supported Event Notifications and MIB Mapping. . . . . . . . . . . . . . . . . . . . . . . . .843
Mellanox Technologies . 11
List of Figures
Mellanox Technologies . 12
Document Revision History
Rev 5.5 – November 29, 2018
Added:
• the command “email autosupport mailhub” on page 312
• the command “email autosupport recipient” on page 313
• the command “snmp-server cache enable” on page 515
• Section 5.4.4, “Break-Out Cables,” on page 593
Updated:
• Section 3.3.6, “IB SM Mgmt,” on page 68
• Section 4.1.6.6, “IP Diagnostic Tools,” on page 167
•
•
• Section 4.9.1, “Supported Events,” on page 298
• the command “aaa authorization” on page 366
• the command “show aaa” on page 368
• Section 4.13.1, “System File Encryption,” on page 395
• Table 28, “System Health Monitor Alerts Scenarios,” on page 444
• the command “show memory” on page 471
• the command “Configuring an SNMPv3 User” on page 494
• the command “snmp-server user” on page 532
• the command “show snmp auto-refresh” on page 535
• the command “show puppet-agent” on page 555
• Section 5.3.1, “Configuring IB Router,” on page 583
• the command “ib sm m-key” on page 651
• the command “show ib sm m-key” on page 724
Removed Appendix “Show Commands Not Supported by JSON”
Mellanox Technologies . 13
Updated:
• the command “{ip | ipv6} route” on page 155
• the command “image install” on page 224
• the command “image options” on page 226
• Section 4.12.2, “Authentication, Authorization and Accounting (AAA),” on page 347
• the command “aaa authorization” on page 366
• the command “show virtual-machine install” on page 611
• the command “show telemetry” on page 340
• the command “show telemetry threshold record” on page 341
• the command “show system profile” on page 478
• the command “start” on page 642
• the command “show ib fabric messages” on page 830
Mellanox Technologies . 14
• Section 5.8.6, “Interoperability with MLAG,” on page 804
• Section 6.1.4, “ARP Neighbor Discovery Responder,” on page 1164
• the command “show interfaces” on page 1189
• the command “show interfaces vlan” on page 1190
• the command “show ip interface” on page 1191
• the command “show ip interface brief” on page 1193
• the command “show interface configured” on page 1194
• the command “show ip” on page 1195
• the command “show ip interface mgmt0” on page 1198
• the command “ip arp responder” on page 1232
• the command “default-information originate” on page 1293
• the command “clear ip pim counters” on page 1465
• the command “show ip pim interface brief” on page 1470
• the command “show ip igmp groups” on page 1496
• the command “show ip igmp interface brief” on page 1499
• the command “use-secondary-ip” on page 1531
• Section 5.5.3, “Scatter Ports,” on page 620
• Section 5.5.4, “GUID Routing Order,” on page 620
• Section 5.5.5, “Bulk Update Mode,” on page 620
• Section 5.5.6.4, “Scatter Ports,” on page 790
• Section 5.5.6.5, “GUID Routing Order,” on page 792
• Section 5.5.6.6, “Bulk Update Mode,” on page 801
• Appendix B, “Show Commands Not Supported by JSON” on page 1943
Updated:
• the command “show web” on page 125
• Table 25, “Supported Event Notifications and MIB Mapping,” on page 298
• Section 4.10, “Telemetry,” on page 324
• the command “show telemetry threshold record” on page 341
• the command “show files stats telemetry” on page 344
• the command “ldap ssl” on page 386
• the command “show ldap” on page 391
• Section 4.17.2.7.1, “To Execute a JSON Request,” on page 512
• Section 4.17.2.7.2, “To Query an Asynchronous JSON Request,” on page 512
• the command “show interfaces ethernet” on page 679
• the command “show lacp interfaces ethernet” on page 711
• the command “show interfaces port-channel compatibility-parameters” on page 720
Mellanox Technologies . 15
• the command “show interfaces port-channel” on page 716
• the command “lldp tlv-select” on page 731
• Section 5.8.5, “Upgrading MLAG Pair,” on page 804
• the command “show mlag-vip” on page 824
• the command “show interfaces mlag-port-channel” on page 825
• the command “show access-lists log config” on page 897
• the command “openflow add-flows” on page 917
• the command “show ip igmp snooping” on page 986
• the command “show ip igmp snooping groups” on page 987
• the command “show ip routing” on page 1174
• the command “show ip interface vrf” on page 1203
• the command “show interfaces loopback” on page 1217
• the command “show ip route” on page 1220
• the command “show ip route vrf” on page 1222
• the command “show ip route failed” on page 1225
• the command “show ip route static” on page 1226
• the command “show ip route static multicast-override” on page 1227
• the command “neighbor update-source” on page 1370
• Section 6.7.4.3, “Configuring PIM,” on page 1449
• the command “ip pim bsr-candidate” on page 1454
• the command “ip pim register-source” on page 1456
• the command “show ip pim protocol” on page 1466
• the command “show ip pim bsr” on page 1467
• the command “show ip pim interface” on page 1468
• the command “show ip pim neighbor” on page 1471
• the command “show ip pim rp” on page 1472
• the command “show ip pim rp-candidate” on page 1474
• the command “show ip pim ssm range” on page 1475
• the command “show ip pim upstream joins” on page 1476
• the configuration mode for the command “clear ip mroute” on page 1480
• the command “show ip mroute” on page 1481
• the command “show ip mroute summary” on page 1485
• the configuration mode for the command “clear ip igmp groups” on page 1495
• the command “show ip igmp groups” on page 1496
• the command “show ip igmp interface brief” on page 1499
• the command “address” on page 1506
Mellanox Technologies . 16
• the command “show vrrp detail” on page 1513
• the command “show ip dhcp relay” on page 1536
• the command “show ip dhcp relay counters” on page 1537
• the command “show interfaces ib” on page 607
• the command “show interfaces ib” on page 607
• the command “ib partition” on page 763
• the command “ipoib” on page 767
• the command “show ib partition” on page 772
• Appendix A, “Enhancing System Security According to NIST SP 800-131A” on
page 843
Mellanox Technologies . 17
• the command “show ip pim rp” on page 1472
Mellanox Technologies . 18
• the command “show snmp auto-refresh” on page 535
• the command “speed” on page 672
• the command “show interfaces ethernet” on page 679
• the command “show interfaces ethernet transceiver diagnostics” on page 688
• the command “show lacp counters” on page 710
• the command “show interfaces port-channel compatibility-parameters” on page 720
• the command “switchport mode” on page 748
• the command “switchport access” on page 750
• the command “show spanning-tree” on page 782
• the command “show spanning-tree mst” on page 786
• the command “show interfaces mlag-port-channel” on page 825
• the command “show interfaces mlag-port-channel summary” on page 828
• the command “show ipv4 access-lists” on page 889
• the command “show mac access-lists” on page 892
• the command “show access-lists policers (ipv4/ipv4-udk/ipv6/mac/mac-udk)” on
page 898
• the command “clear ip igmp snooping counters” on page 985
• the command “dcb priority-flow-control mode” on page 1000
• Section 6.1.3, “Virtual Routing and Forwarding,” on page 1164
• the command “vrf definition” on page 1167
• the command “show vrf” on page 1177
• the command “show ip interface vrf” on page 1203
• the command “ip route” on page 1218
• the command “show ip route” on page 1220
• the command “show {ip | ipv6} bgp” on page 1379
• the command “show ip pim rp-candidate” on page 1474
• the command “ip mroute” on page 1478
• the command “ip dhcp relay instance (interface config)” on page 1533
• the command “show ip dhcp relay” on page 1536
• the command “show interfaces ib internal llr” on page 612
• the command “show interfaces ib transceiver diagnostics” on page 615
• the command “show ib fabric connections” on page 829
• the command “show ib fabric node” on page 832
• the command “show ib fabric node ports” on page 833
• the command “show ib fabric nodes” on page 834
• the command “show ib fabric port” on page 835
• the command “show ib fabric ports” on page 837
Mellanox Technologies . 19
• the command “show ib fabric system” on page 840
• the command “show ib fabric system nodes” on page 841
• the command “show ib fabric system ports” on page 842
• Appendix B, “Show Commands Not Supported by JSON” on page 1943
Rev 4.80
Software Ver. 3.6.5000 – November 05, 2017
Added:
• Section 2.1.1, “Configuring the Switch with ZTP,” on page 34
• Section 2.4, “Zero-touch Provisioning,” on page 38
• the command “logging level” on page 280
• the command “show log” on page 286
• Section 4.19, “Control Plane Policing,” on page 556
• Section 5.11.3, “ACL Logging,” on page 840
• Section 5.11.4, “ACL Capability Summary,” on page 841
• the command “clear ip dhcp relay counters” on page 1534
• the command “show magp interface vlan” on page 1523
• the command “width” on page 602
Deleted:
• the command “mc-unaware tc binding”
Updated:
• Table 19, “WebUI IP Route Submenus,” on page 73
• the command “cli max-sessions” on page 76
• the command “show ip dhcp” on page 166
• the command “show interfaces ethernet” on page 679
• the command “show interfaces counters” on page 675
• the command “show isolation-group” on page 699
• the command “show interfaces port-channel” on page 716
• the command “show spanning-tree detail” on page 784
• the command “show spanning-tree vlan” on page 788
• the command “show interfaces mlag-port-channel” on page 825
• the command “show access-lists summary” on page 900
• the command “destination interface” on page 1109
• the command “show monitor session summary” on page 1116
• the command “show ip interface vrf” on page 1203
Mellanox Technologies . 20
• the command “show ip route summary” on page 1228
• the command “show ip route interface” on page 1229
• the command “show vrrp detail” on page 1513
• the command “show vrrp statistics” on page 1514
• the command “show magp” on page 1522
• the command “show ip dhcp relay counters” on page 1537
• Updated max SM nodes supported on switches in Section 5.5, “Subnet Manager (SM),”
on page 618
• Appendix B, “Show Commands Not Supported by JSON” on page 1943
Mellanox Technologies . 21
About this Manual
This manual provides general information concerning the scope and organization of this User’s
Manual.
Intended Audience
This manual is intended for network administrators who are responsible for configuring and
managing Mellanox Technologies’ switch platforms.
Related Documentation
The following table lists the documents referenced in this User’s Manual.
Table 1 - Reference Documents
Document Name Description
InfiniBand Architecture Specification, Vol. 1, The InfiniBand Architecture Specification that is pro-
Release 1.2.1 vided by IBTA.
System Hardware User Manual This document contains hardware descriptions, LED
assignments and hardware specifications among other
things.
Switch Product Release Notes Please look up the relevant switch system/series
release note file
Mellanox Virtual Modular Switch This reference architecture provides general informa-
Reference Guide tion concerning Mellanox L2 and L3 Virtual Modular
Switch (VMS) configuration and design.
Configuring Mellanox Hardware for VPI This manual provides information on basic configura-
Operation Application Note tion of the converged VPI networks.
MLNX-OS XML API Reference Guide This manual provides general information concerning
MLNX-OS XML API.
All of these documents can be found on the Mellanox website. They are available either through
the product pages or through the support page with a login and password.
Glossary
Table 2 - Glossary
AAA Authentication, Authorization, and Accounting.
Authentication - verifies user credentials (username and password).
Authorization - grants or refuses privileges to a user/client for accessing
specific services.
Accounting - tracks network resources consumption by users.
ARP Address Resolution Protocol. A protocol that translates IP addresses
into MAC addresses for communication over a local area network
(LAN).
Mellanox Technologies . 22
Table 2 - Glossary
CLI Command Line Interface. A user interface in which you type commands
at the prompt
DCB Data Center Bridging
DCBX DCBX protocol is an extension of the Link Layer Discovery Protocol
(LLDP). DCBX end points exchange request and acknowledgment
messages. For flexibility, parameters are coded in a type-length-value
(TLV) format.
DHCP The Dynamic Host Configuration Protocol (DHCP) is an automatic
configuration protocol used on IP networks.
Director Class Switch A high density InfiniBand chassis switch system
DNS Domain Name System. A hierarchical naming system for devices in a
computer network
ETS ETS provides a common management framework for assignment of
bandwidth to traffic classes.
Fabric Management The use of a set of tools (APIs) to configure, discover, and manage and
a group of devices organized as a connected fabric.
FTP/TFTP/sFTP File Transfer Protocol (FTP) is a standard network protocol used to
transfer files from one host to another over a TCP-based network, such
as the Internet.
Gateway A network node that interfaces with another network using a different
network protocol
GID (Global Identifier) A 128-bit number used to identify a Port on a network adapter (see
below), a port on a Router, or a Multicast Group.
GUID (Globally Unique Identi- A 64-bit number that uniquely identifies a device or component in a
fier) subnet
HA (High Availability) A system design protocol that provides redundancy of system compo-
nents, thus enables overcoming single or multiple failures in minimal
downtime
Host A computer platform executing an Operating System which may con-
trol one or more network adapters
IB InfiniBand
LACP Link Aggregation Control Protocol (LACP) provides a method to con-
trol the bundling of several physical ports together to form a single log-
ical channel. LACP allows a network device to negotiate an automatic
bundling of links by sending LACP packets to the peer (directly con-
nected device that also implements LACP).
LDAP The Lightweight Directory Access Protocol is an application protocol
for reading and editing directories over an IP network.
LID (Local Identifier) A 16 bit address assigned to end nodes by the subnet manager
Each LID is unique within its subnet.
LLDP (Link Layer Discovery A vendor neutral link layer protocol used by network devices to adver-
Protocol) tise their identify, capabilities and for neighbor discovery
Mellanox Technologies . 23
Table 2 - Glossary
MAC A Media Access Control address (MAC address) is a unique identifier
assigned to network interfaces for communications on the physical net-
work segment. MAC addresses are used for numerous network technol-
ogies and most IEEE 802 network technologies including Ethernet.
MTU (Maximum Transfer Unit) The maximum size of a packet payload (not including headers) that can
be sent /received from a port
Network Adapter A hardware device that allows for communication between computers
in a network
PFC/FC Priority Based Flow Control applies pause functionality to traffic
classes OR classes of service on the Ethernet link.
RADIUS Remote Authentication Dial In User Service. A networking protocol
that enables AAA centralized management for computers to connect
and use a network service.
RDMA (Remote Direct Memory Accessing memory in a remote side without involvement of the remote
Access) CPU
RSTP Rapid Spanning Tree Protocol. A spanning-tree protocol used to prevent
loops in bridge configurations. RSTP is not aware of VLANs and
blocks ports at the physical level.
SA (Subnet Administrator) The interface for querying and manipulating subnet management data
SCP Secure Copy or SCP is a means of securely transferring computer files
between a local and a remote host or between two remote hosts. It is
based on the Secure Shell (SSH) protocol.
SM (Subnet Manager) An entity that configures and manages the subnet, discovers the net-
work topology, assign LIDs, determines the routing schemes and sets
the routing tables. There is only one master SM and possible several
slaves (Standby mode) at a given time. The SM administers switch rout-
ing tables thereby establishing paths through the fabric
SNMP Simple Network Management Protocol. A network protocol for the
management of a network and the monitoring of network devices and
their functions
NTP Network Time Protocol. A protocol for synchronizing computer clocks
in a network
SSH Secure Shell. A protocol (program) for securely logging in to and run-
ning programs on remote machines across a network. The program
authenticates access to the remote machine and encrypts the transferred
information through the connection.
syslog A standard for forwarding log messages in an IP network
TACACS+ Terminal Access Controller Access-Control System Plus. A networking
protocol that enables access to a network of devices via one or more
centralized servers. TACACS+ provides separate AAA services.
XML Gateway Extensible Markup Language Gateway. Provides an XML request-
response protocol for setting and retrieving HW management informa-
tion.
Mellanox Technologies . 24
Introduction
1 Introduction
Mellanox® Operating System (MLNX-OS®) enables the management and configuration of Mel-
lanox Technologies’ switch system platforms.
MLNX-OS provides a full suite of management options, including support for Mellanox’s Uni-
fied Fabric Manager® (UFM), SNMPv1, 2, 3, and web user interface (WebUI). In addition, it
incorporates a familiar industry-standard CLI, which enables administrators to easily configure
and manage the system.
Mellanox Technologies . 25
Introduction
Mellanox Technologies . 26
Getting Started
2 Getting Started
The procedures described in this chapter assume that you have already installed and powered on
your switch according to the instructions in the Hardware Installation Guide, which was shipped
with the product.
Make sure to connect to the console RJ-45 port of the switch and not to the MGT port.
DHCP is enabled by default over the MGT port. Therefore, if you have configured
your DHCP server and connected an RJ-45 cable to the MGT port, simply log in using
the designated IP address.
Mellanox Technologies . 27
Getting Started
This step may be skipped if the DHCP option is used and an IP is already configured
for the MGT port.
1: <image #1>
2: <image #2>
u: USB menu (if USB device is connected) (password required)
c: Command prompt (password required)
Choice:
Mellanox Technologies . 28
Getting Started
Mellanox configuration wizard You must perform this configuration the first
Do you want to use the wizard for initial con- time you operate the switch or after resetting
figuration? yes the switch to the factory defaults. Type “y” and
then press <Enter>.
Step1: Hostname? [switch-1] If you wish to accept the default hostname,
then press <Enter>. Otherwise, type a different
hostname and press <Enter>.
Step 2: Use DHCP on mgmt0 interface? [yes] Perform this step to obtain an IP address for the
switch. (mgmt0 is the management port of the
switch.)
If you wish the DHCP server to assign the IP
address, type “yes” and press <Enter>.
Mellanox Technologies . 29
Getting Started
You have entered the following information: The wizard displays a summary of your
choices and then asks you to confirm the
1. Hostname: <switch name> choices or to re-edit them.
2. Use DHCP on mgmt0 interface: yes
3. Enable IPv6: yes
4. Enable IPv6 autoconfig (SLAAC) on Either press <Enter> to save changes and exit,
mgmt0 interface: yes or enter the configuration step number that you
5. Enable DHCPv6 on mgmt0 interface: no wish to return to.
6. Admin password (Enter to leave
unchanged): (CHANGED)
Note:
To change an answer, enter the step number to To run the command “configuration jump-
return to. start” you must be in Config mode.
Otherwise hit <enter> to save changes and exit.
Choice: <Enter>
Mellanox Technologies . 30
Getting Started
1. Hostname: switch-112126
2. Use DHCP on mgmt0 interface: no
3. Use zeroconf on mgmt0 interface: yes
4. Default gateway: 192.168.10.1
5. Primary DNS server:
6. Domain name:
7. Enable IPv6: yes
8. Enable IPv6 autoconfig (SLAAC) on mgmt0 interface: yes
9. Admin password (Enter to leave unchanged): (unchanged)
Choice:
To return to the wizard from the CLI, enter the “configuration jump-start”
command from configure mode. Launching CLI...
Mellanox Technologies . 31
Getting Started
1. Hostname: switch-112126
2. Use DHCP on mgmt0 interface: no
3. Use zeroconf on mgmt0 interface: no
4. Primary IP address: 192.168.10.4
5. Netmask: 255.255.255.0
6. Default gateway: 192.168.10.1
7. Primary DNS server:
8. Domain name:
9. Enable IPv6: yes
10. Enable IPv6 autoconfig (SLAAC) on mgmt0 interface: no
11. Admin password (Enter to leave unchanged): (unchanged)
Choice:
To return to the wizard from the CLI, enter the “configuration jump-start”
command from configure mode. Launching CLI...
Mellanox Technologies . 32
Getting Started
Step 6. Check the mgmt0 interface configuration before attempting a remote (for example, SSH)
connection to the switch. Specifically, verify the existence of an IP address.
switch # show interfaces mgmt0
IPv6 address:
fe80::268a:7ff:fe53:3d8e/64
Rx:
11700449 bytes
55753 packets
0 mcast packets
0 discards
0 errors
0 overruns
0 frame
Tx:
5139846 bytes
28452 packets
0 discards
0 errors
0 overruns
0 carrier
0 collisions
1000 queue len
Mellanox Technologies . 33
Getting Started
Password:
Last login: <time> from <ip-address>
Mellanox Switch
Please read and accept the Mellanox End User License Agreement located at:
https://www.mellanox.com/related-docs/prod_management_software/MLNX-OS_EULA.pdf
switch >
Mellanox Technologies . 34
Getting Started
Step 1. Set up an Ethernet connection between the switch and a local network machine using a stan-
dard RJ-45 connector.
Step 2. Open a web browser – Firefox 12, Chrome 18, IE 8, Safari 5 or higher.
Note: Make sure the screen resolution is set to 1024*768 or higher.
Step 3. Type in the IP address of the switch or its DNS name in the format: https://<switch_IP_
address>.
Step 4. Log into the switch (default user name is admin, password admin).
Mellanox Technologies . 35
Getting Started
Step 6. The Welcome popup appears. After reading through the content, click OK to continue.
You may click on the links under Documentation to reach the MLNX-OS documentation.
The link under What’s New takes you straight to the Changes and New Features section of
the switch OS Release Notes.
Mellanox Technologies . 36
Getting Started
You may also tick the box to not show this popup again. But should you wish to see this
window again, click “Product Documents” on the upper right corner of the WebUI.
Step 7. A default status summary is displayed as shown in Figure 7.
Mellanox Technologies . 37
Getting Started
The user-defined docker image can be used by customers to run their own applications in a sand-
box on a MLNX-OS platform. And can therefore be also used for automating initial configura-
tion.
Mellanox Technologies . 38
Getting Started
While performing file transfer via HTTP, the same information as DHCP option 43 is
expected to be carried in a HTTP GET request. MLNX-OS supports the following pro-
prietary HTTP headers:
• MlnxSysProfile
• MlnxMgmtMac
• MlnxSerialNumber
• MlnxModelName
• MlnxPartNumber
• MlnxReleaseVersion
Mellanox Technologies . 39
Getting Started
In case of failure, the switch waits a random number of seconds between 1 and 20 and reattempts
the operation. The switch attempts this up to 10 times.
ZTP progress is printed to terminals including console and active SSH sessions.
Mellanox Technologies . 40
Getting Started
Mellanox Technologies . 41
Getting Started
2.4.6 Commands
no zero-touch suppress-write
no zero-touch suppress-write
Default Enabled
History 3.6.5000
Role admin
Notes When ZTP is active, “configuration write” is suppressed because it may interfere
with ZTP operation. Therefore, after running “no zero-touch suppress-write” if
“configuration write” is performed, then ZTP is disabled as a consequence of the
database save.
Mellanox Technologies . 42
Getting Started
zero-touch abort
zero-touch abort
Default Enabled
History 3.6.5000
Role admin
Notes
Mellanox Technologies . 43
Getting Started
show zero-touch
show zero-touch
Default N/A
History 3.6.5000
Role admin
Notes
Mellanox Technologies . 44
Getting Started
2.5 Licenses
MLNX-OS software package can be extended with premium features. Installing a license allows
you to access the specified premium features.
This section is relevant only to switch systems with an internal management capability.
If you do not save the installation session, you will lose the license at the next system
start up.
Mellanox Technologies . 45
Getting Started
Step 3. Enter your license key(s) in the text box. If you have more than one license, please enter
each license in a separate line. Click “Add Licenses” after entering the last license key to
install them.
If you wish to add another license key in the future, you can simply enter it in the text
box and click “Add Licenses” to install it.
Mellanox Technologies . 46
Getting Started
Mellanox Technologies . 47
Getting Started
If you do not save the installation session, you will lose the installed licenses at the
next system boot.
Step 3. Send your Mellanox reseller the following information to obtain the license key:
• The chassis serial number
• The type of license you need to retrieve. Refer to “Licenses” on page 45.
Step 4. Once you receive the license key, you can install the license as described in the sections
above.
Mellanox Technologies . 48
Getting Started
2.5.4 Commands
Uploads the Mellanox End User License Agreement to a specified remote location.
Default N/A
History 3.4.1100
Role monitor/admin
Note
Mellanox Technologies . 49
Getting Started
Default N/A
History 3.4.1100
Role admin
Related Commands
Note
Mellanox Technologies . 50
Getting Started
license delete
license delete <license-number>
Default N/A
History 3.4.1100
Role admin
Related Commands
Note Before deleting a license from a switch which is configured to a system profile other
than its default, the user must first disable all interfaces and then return the switch to
its default system profile.
Mellanox Technologies . 51
Getting Started
license install
license install <license-key>
Default N/A
History 3.4.1100
Role admin
Related Commands
Note
Mellanox Technologies . 52
Getting Started
show licenses
show licenses
Displays a list of all installed licenses. For each license, the following is displayed:
• a unique ID which is a small integer
• the text of the license key as it was added
• whether or not it is valid and active
• which feature(s) it is activating
• a list of all licensable features specifying whether or not it is currently activated
by a license
Default N/A
History 3.4.1100
Role admin
Related Commands
Note
Mellanox Technologies . 53
User Interfaces
3 User Interfaces
3.1 LED Indicators
Table 9 - LED Behavior Details
LED Qty. Color Description
Standard When the CLI is launched, it begins in Standard mode. This is the
most restrictive mode and only has commands to query a
restricted set of state information. Users cannot take any actions
that directly affect the system, nor can they change any configu-
ration.
Enable The enable command moves the user to Enable mode. This
mode offers commands to view all state information and take
actions like rebooting the system, but it does not allow any con-
figurations to be changed. Its commands are a superset of those
in Standard mode.
Mellanox Technologies . 54
User Interfaces
< > Angled brackets Indicate a value/variable that must be replaced. <1...65535> or <switch inter-
face>
[ ] Square brackets Enclose optional parameters. [destination-ip | destination-port |
However, only one parameter out of the list of destination-mac]
parameters listed can be used. The user cannot
have a combination of the parameters unless
stated otherwise.
{ } Braces Enclose alternatives or variables that are [mode {active | on | passive}]
required for the parameter in square brackets.
| Vertical bars Identify mutually exclusive choices. active | on | passive
Do not type the angled or square brackets, vertical bar, or braces in command lines. This
guide uses these symbols only to show the types of entries.
Mellanox Technologies . 55
User Interfaces
Mellanox Technologies . 56
User Interfaces
Mellanox Technologies . 57
User Interfaces
Mellanox Technologies . 58
User Interfaces
Mellanox Technologies . 59
User Interfaces
The filtering parameters are separated from the show command they filter by a pipe character
(i.e. “|”). Quotation marks may be used to include or exclude a string including space, and multi-
ple filters can be used simultaneously. For example:
switch (config) # <show command> | {include <extended regular expression>} [<ignore-
case>] [next <lines>] [prev <lines>] | exclude <extended regular expression> [<ignore-
case>] [next <lines>] [prev <lines>]]
Examples:
switch (config) # show asic-version | include SX
MGMT SX 9.3.3150
Mellanox Technologies . 60
User Interfaces
Running the command as such displays an output of the show command that gets updated at a
time interval which may be specified using the “interval” parameter (2 seconds by default).
The “diff” parameter highlights the differences between each iteration of the command. For
example running the command “show power | watch diff interval 1” yields something
similar to the following:
With the highlighted black blocks indicating the change that has occurred between one iteration
of the command from one second to the next.
To exit “watch” mode, press Ctrl+C.
The “watch” option may also be used in conjunction with the “include” and “exclude” options as
follows:
switch (config) # <show command> | {include | exclude} <extended regular expression> |
watch [diff] [interval <1-100 secs>]
For example:
switch (config) # show power | include PS | watch diff interval 1
Mellanox Technologies . 61
User Interfaces
Mellanox Technologies . 62
User Interfaces
Make sure to save your changes before switching between menus or submenus. Click the
“Save” button to the right of “Save Changes?”.
Mellanox Technologies . 63
User Interfaces
Interfaces Obtains the status of, configures, or disables interfaces to the fabric. Thus, you
can: set or clear the IP address and netmask of an interface; enable DHCP to
dynamically assign the IP address and netmask; and set interface attributes such
as MTU, speed, duplex, etc.
HA Creates, joins or modifies an InfiniBand subnet
Routing Configures, removes or displays the default gateway, and the static and dynamic
routes
Hostname Configures or modifies the hostname
Configures or deletes static hosts
Note: Changing hostname stamps a new HTTPS certificate
Mellanox Technologies . 64
User Interfaces
DNS Configures, removes, modifies or displays static and dynamic name servers
Login Messages Edits the login messages: Message of the Day (MOTD), Remote Login message,
and Local Login message
Address Resolution Adds static and dynamic ARP entries, and clears the dynamic ARP cache
IPSec Configures IPSec
Neighbors Displays IPv6 neighbor discovery protocol
Virtualization Manages the virtualization and virtual machines
Virtual Switch Mgmt Configures the system profile
Web Configures web user interface and proxy settings
SNMP Configures SNMP attributes, SNMP admin user, and trap sinks
Email Alerts Configures the destination of email alerts and the recipients to be notified
XML gateway Provides an XML request-response protocol to get and set hardware manage-
ment information
JSON API Manages JSON API
Logging Sets up system log files, remote log sinks, and log formats
Configurations Manages, activates, saves, and imports MLNX-OS configuration files, and exe-
cutes CLI commands
Docker Manages docker images and containers.
Date and Time Configures the date, time, and time zone of the switch system
NTP Configures NTP (Network Time Protocol) and NTP servers
Licensing Manages MLNX-OS licenses
Modules Displays a graphic illustration of the system modules. By moving the mouse
over the ports in the front view, a pop-up caption is displayed to indicate the sta-
tus of the port. The port state (active/down) is differentiated by a color scheme
(green for active, gray/black for down). By moving the mouse over the rear view,
a pop-up caption is displayed to indicate the leaf part information.
Inventory Displays a table with the following information about the system modules: mod-
ule name, type, serial number, ordering part number and ASIC firmware version
Mellanox Technologies . 65
User Interfaces
Power Management Displays a table with the following information about the system power supplies:
power supply name, power, voltage level, current consumption, and status. A
total power summary table is also displayed providing the power used, the power
capacity, and the power available.
MLNX-OS Upgrade Displays the installed MLNX-OS images (and the active partition), uploads a
new image, and installs a new image
Reboot Reboots the system. Make sure that you save your configuration prior to clicking
reboot.
Ports Manages port attributes, counters, transceiver info and displays a graphical
counters histogram
Phy Profile Provides the ability to manage PHY profiles
Monitor Session Displays monitor session summary and enables configuration of a selected ses-
sion
Mellanox Technologies . 66
User Interfaces
Summary Displays general information about the switch system and the MLNX-OS image,
including current date and time, hostname, uptime of system, system memory,
CPU load averages, etc.
Profile and Capabilities Displays general information about the switch system capabilities such as the
enabled profiles (e.g IB/ETH) and their corresponding values
What Just Happened Displays and configures What Just Happened packet drop reasons.
Temperature Provides a graphical display of the switch module sensors’ temperature levels
over time (1 hour). It is possible to display either the temperature level of one
module’s sensor or the temperature levels of all the module sensors’ together.
Power Supplies Provides a graphical display of one of the switch’s power supplies voltage level
over time (1 hour)
Fans Provides a graphical display of fan speeds over time (1 hour). The display is per
fan unit within a fan module.
CPU Load Provides a graphical display of the management CPU load over time (1 hour)
Memory Provides a graphical display of memory utilization over time (1 day)
Network Provides a graphical display of network usage (transmitted and received packets)
over time (1 day). It also provides per interface statistics.
Logs Displays the system log messages. It is possible to display either the currently
saved system log or a continuous system log.
Maintenance Performs specific maintenance operations automatically on a predefined sched-
ule
Alerts Displays a list of the recent health alerts and enables the user to configure health
settings
Virtualization Displays the virtual machines, networks and volumes
Mellanox Technologies . 67
User Interfaces
3.3.6 IB SM Mgmt
The IB SM Mgmt menu makes available the following submenus (listed in order of appearance
from top to bottom):
Table 19 - WebUI IB SM Mgmt Submenus
Submenu Title Description
Summary Displays the local Subnet Manager (SM) status (running time, failures, etc)
Base SM Manages basic SM configuration (enabling SM, priority level, and restoring ini-
tial configuration)
Advanced SM Manages basic SM configuration (enabling SM, priority level, and restoring ini-
tial configuration)
Expert SM 1. Configures security and GUID based prefixes (m_key, sm_key, sa_key, etc),
and manages special SM attributes that should not be changed except by expert
users of the Subnet Manager who understand the risks of manipulating these
attributes.
2. Fabric inspector, and many standalone InfiniBand utilities, may not function
on subnets with a non-default m-key.
Compute nodes Adds compute nodes using network adapter port GUIDs
Root nodes Adds root nodes using switch GUIDs
Partitions Manages partition keys (sets removes or displays the partition keys)
Basic Qos Configures basic QoS attributes such as default QoS settings, and VL arbitration
low and high entries. It also displays and manages SL-to-VL mappings.
The Fabric Inspctr menu makes available the following sub-menus (listed in order of appear-
ance from top to bottom):
Table 20 - WebUI Fabric Inspctr Submenus
Submenu Title Description
Summary Displays a fabric status summary, including the time of last fabric update, what
systems are in the fabric, what InfiniBand devices are identified, etc
IB Systems Displays information about all identified InfiniBand systems in the fabric (adapt-
ers, switches, etc)
IB Nodes Displays information about InfiniBand nodes in the fabric. It is possible to filter
display by the type of InfiniBand node (HCA adapter, switch, etc)
Mellanox Technologies . 68
User Interfaces
IB Ports Displays all active InfiniBand ports in the fabric. It is possible to filter display by
the type of InfiniBand port (HCA port, switch port, switch management port,
etc), by the port rate (speed or width), by the Subnet Manager status on the node,
by node traffic, etc.
Connections Displays all active connections in the fabric. It is possible to filter display by the
link type (switch to switch, switch to HCA, etc) and by the link rate (speed or
width)
System Names Allows the mapping of System Names to GUIDs to ease system identification
3.3.8 IB Router
The IB Router menu makes available the following sub-menus (listed in order of appearance
from top to bottom):
Table 21 - WebUI IB Router Submenus
Submenu Title Description
It is recommended not to use more than 50 concurrent SSH sessions to the switch.
Mellanox Technologies . 69
User Interfaces
Mellanox Technologies . 70
User Interfaces
Each position could indicate different types of component according to the following criteria:
Table 22 - Module Type
Number Description
1 Chassis
2 Management
3 Spine
4 Leaf
5 Fan
6 Power supply
7 BBU
8 x86 CPU
9 Port module
01 PS
02 FAN
03 BOARD_MONITOR
04 CPU_BOARD_MONITOR
05 SX
06 SIB
07 CPU_MEZZ_TEMP
08 CPU Package Sensor
09 CPU Core Sensor
10 SX_AMBIENT_TEMP
11 SX_MONITOR
12 AUX_IN_TMP_SNSR
13 AUX_OUT_TMP_SNSR
14 MAIN_IN_TMP_SNSR
15 MAIN_OUT_TMP_SNSR
16 CPU_MEZZ_TEMP
17 Controller
18 QSFP_TEMP
19 QSFP-ASIC
20 Board AMB temp
21 Ports AMB temp
Mellanox Technologies . 71
User Interfaces
22 Power monitor
23 PS_MONITOR
24 SWB AMB temp
25 pcie-switch-temp
26 SPC
1 t – temperature sensor
2 f – fan sensor
For example:
• 401191311
The first layer is “401” where:
• “4”, according to Table 22, indicates a leaf
• “01” indicates index #1 (Leaf #1)
The second layer is “1913” where:
• “19”, according to Table 23, indicates a QSFP ASIC
• “1” indicates ASIC #1
• “3” indicates sensor #3 (QSFP-ASIC1-3)
The third layer is “11” where:
• “1”, according to Table 24, indicates a temperature sensor
• “1” indicates sensor #1 (T1)
The resulting output in the entPhysicalDescr column of the MIB would be: L01/QSFP-ASIC-1/
T1.
• 501020021
The first layer is 501 where
• “5”, according to Table 22, indicates a fan
• “01 indicates index #1 (Fan #1)
The second layer is 0200 where:
• 02, according to Table 23, indicates a fan
• 0 – indicates that there is no first index
• 0 – indicates that there is no second index
The third layer is 21 where:
• “2”, according to Table 24, indicates a fan sensor
• “1” indicates sensor #1 (F1)
Mellanox Technologies . 72
User Interfaces
The resulting output in the entPhysicalDescr column of the MIB would be: FAN1/FAN/F1.
Mellanox Technologies . 73
User Interfaces
3.6 Commands
cli clear-history
cli clear-history
Default N/A
History 3.1.0000
Role admin
Note
Mellanox Technologies . 74
User Interfaces
cli default
cli default {auto-logout <minutes> | paging enable | prefix-modes {enable | show-
config} | progress enable | prompt {confirm-reload | confirm-reset | confirm-
unsaved | empty-password}}
no cli default {auto-logout | paging enable | prefix-modes {enable | show-config} |
progress enable prompt {confirm-reload | confirm-reset | confirm-unsaved |
empty-password}
Default N/A
History 3.1.0000
Role admin
Note
Mellanox Technologies . 75
User Interfaces
cli max-sessions
cli max-sessions <number>
no cli max-sessions
Default 30 sessions
History 3.5.0200
Role admin
Note
Mellanox Technologies . 76
User Interfaces
cli session
cli session {auto-logout <minutes> | paging enable | prefix-modes {enable | show-
config} | progress enable | terminal {length <size> | resize | type <terminal-type>
| width} | x-display full <display>}
no cli session {auto-logout | paging enable | prefix-modes {enable | show-config} |
progress enable | terminal type | x-display}
terminal length Sets the number of lines for the current terminal. Valid
range is 5-999.
terminal resize Resizes the CLI terminal settings (to match the actual
terminal window).
terminal width Sets the width of the terminal in characters. Valid range
is 34-999.
x-display full <display> Specifies the display as a raw string, e.g localhost:0.0.
Default N/A
Mellanox Technologies . 77
User Interfaces
History 3.1.0000
Role admin
Note
Mellanox Technologies . 78
User Interfaces
terminal
terminal {length <number of lines> | resize | type <terminal type> | width <num-
ber of characters>}
no terminal type
Syntax Description length Sets the number of lines for this terminal
Range: 5-999
resize Resizes the CLI terminal settings (to match with real
terminal)
Default N/A
History 3.1.0000
Role admin
Note
Mellanox Technologies . 79
User Interfaces
Default Enabled
History 3.4.3000
Role admin
Note
Mellanox Technologies . 80
User Interfaces
show cli
show cli
Default N/A
History 3.1.0000
Role admin
Note
Mellanox Technologies . 81
User Interfaces
Default N/A
History 3.5.0200
Role admin
Related Commands
Note
Mellanox Technologies . 82
User Interfaces
Default N/A
History 3.5.0200
Role admin
Related Commands
Note
Mellanox Technologies . 83
User Interfaces
3.6.2 Banner
banner login
banner login <string>
no banner login
History 3.1.0000
Role admin
Note If more than one word is used (there is a space) quotation marks should be added (i.e.
“xxxx xxxx”).
Mellanox Technologies . 84
User Interfaces
banner login-local
banner login-local <string>
no banner login-local
Default N/A
History 3.1.0000
Role admin
Mellanox Technologies . 85
User Interfaces
banner login-remote
banner login-remote <string>
no banner login-remote
Default N/A
History 3.1.0000
Role admin
Mellanox Technologies . 86
User Interfaces
banner logout
banner logout <string>
no banner logout
Set system logout banner (for both local and remote logins).
The no form of the command resets the banner.
Default N/A
History 3.5.0200
Role admin
Note If more than one word is used (there is a space) quotation marks should be added (i.e.
“xxxx xxxx”).
Mellanox Technologies . 87
User Interfaces
banner logout-local
banner logout-local <string>
no banner logout-local
Default N/A
History 3.5.0200
Role admin
Mellanox Technologies . 88
User Interfaces
banner logout-remote
banner logout-remote <string>
no banner logout-remote
Default N/A
History 3.5.0200
Role admin
Mellanox Technologies . 89
User Interfaces
banner motd
banner motd <string>
no banner motd
History 3.1.0000
Role admin
Note • If more than one word is used (there is a space) quotation marks should be added
(i.e. “xxxx xxxx”).
• To insert a multi-line MotD, hit Ctrl-V (escape sequence) followed by Ctrl-J (new
line sequence). The symbol “^J” should appear. Then, whatever is typed after it
becomes the new line of the MotD. Remember to also include the string between
quotation marks.
Mellanox Technologies . 90
User Interfaces
show banner
show banner
Default N/A
History 3.1.0000
Banners:
Message of the Day (MOTD):
Mellanox Switch
Login:
Mellanox MLNX-OS Switch Management
Logout:
Goodbye
Note
Mellanox Technologies . 91
User Interfaces
3.6.3 SSH
History 3.1.0000
Role admin
Note Disabling SSH server does not terminate existing SSH sessions, it only prevents new
ones from being established.
Mellanox Technologies . 92
User Interfaces
private-key Sets new private-key for the host keys of the specified
type
public-key Sets new public-key for the host keys of the specified
type
generate Generates new RSA and DSA host keys for SSH
History 3.1.0000
Role admin
Note When working in secure mode, the commands “ssh server host-key rsa1” and “ssh
server host-key generate” do not create RSAv1 key-type.
Mellanox Technologies . 93
User Interfaces
Enables the listen interface restricted list for SSH. If enabled, and at least one non-
DHCP interface is specified in the list, the SSH connections are only accepted on
those specified interfaces.
The no form of the command disables the listen interface restricted list for SSH.
When disabled, SSH connections are not accepted on any interface.
Syntax Description enable Enables SSH interface restrictions on access to this sys-
tem.
History 3.1.0000
Role admin
Note
Mellanox Technologies . 94
User Interfaces
Default 6 attempts
History 3.5.0200
Role admin
Note
Mellanox Technologies . 95
User Interfaces
History 3.5.0200
Role admin
Note
Mellanox Technologies . 96
User Interfaces
Sets the minimum version of the SSH protocol that the server supports.
The no form of the command resets the minimum version of SSH protocol supported.
Default 2
History 3.1.0000
Role admin
Note
Mellanox Technologies . 97
User Interfaces
Default 22
History 3.1.0000
Role admin
Mellanox Technologies . 98
User Interfaces
Default N/A
History 3.3.5060
3.6.4000
Role admin
Note The following ciphers are disabled for SSH when strict security is enabled:
• aes256-cbc
• aes192-cbc
• aes128-cbc
• arcfour
• blowfish-cbc
• cast128-cbc
• [email protected]
• 3des-cbc
Mellanox Technologies . 99
User Interfaces
Default N/A
History 3.1.0000
Role admin
Note
History 3.1.0000
Role admin
Note
Syntax Description host-key-check <policy> Sets SSH client configuration to control how host key
checking is performed. This parameter may be set in 3
ways.
• If set to “no” it always permits connection, and
accepts any new or changed host keys without
checking
• If set to “ask” it prompts user to accept new host
keys, but does not permit a connection if there was
already a known host entry that does not match the
one presented by the host
• If set to “yes” it only permits connection if a match-
ing host key is already in the known hosts file
History 3.1.0000
Role admin
switch (config) #
Note
Adds an entry to the global known-hosts configuration file, either by generating new
key, or by adding manually a public or private key.
The no form of the command removes a public key from the specified user's autho-
rized key list, or changes the key type.
Syntax Description username The specified user must be a valid account on the sys-
tem. Possible values for this parameter are “admin”,
“monitor”, “xmladmin”, and “xmluser”.
authorized-key sshv2 Adds the specified key to the list of authorized SSHv2
<public key> RSA or DSA public keys for this user account. These
keys can be used to log into the user's account.
identity <key type> Sets certain SSH client identity settings for a user, dsa2
or rsa2.
private-key Sets private key SSH client identity settings for the
user.
public-key Sets public key SSH client identity settings for the user.
known-host <known host> Removes host from user's known host file.
remove
History 3.1.0000
Role admin
Example switch (config) # ssh client user admin known-host 172.30.1.116 remove
Note If a key is being pasted from a cut buffer and was displayed with a paging program, it
is likely that newline characters have been inserted, even if the output was not long
enough to require paging. One can specify “no cli session paging enable” before run-
ning the “show” command to prevent the newlines from being inserted.
slogin
slogin [<slogin options>] <hostname>
Invokes the SSH client. The user is returned to the CLI when SSH finishes.
Default N/A
History 3.1.0000
Role monitor/admin
Mellanox Switch
switch (config) #
Note
Default N/A
History 3.1.0000
Role admin
switch (config) #
Note
Default N/A
History 3.1.0000
Role admin
Note
Default N/A
Role admin
Host Keys:
RSA v1 host key: "kebo-2100-1 2048 65537 21801469875<...>27851"
RSA v2 host key: "kebo-2100-1 ssh-rsa AAAAB3Nza<...>KE5"
DSA v2 host key: "kebo-2100-1 ssh-dss AAAAB3Nza<...>/s="
Note
telnet
telnet
Default N/A
History 3.1.0000
Role admin
Note
telnet-server enable
telnet-server enable
no telnet-server enable
History 3.1.0000
Role admin
Note
show telnet-server
show telnet-server
Default N/A
History 3.1.0000
Role admin
Note
web auto-logout
web auto-logout <number of minutes>
no web auto-logout <number of minutes>
Default 60 minutes
History 3.1.0000
Role admin
Note The no form of the command does not automatically log users out due to inactivity.
web cache-enable
web cache-enable
no web cache-enable
Default Enabled
History 3.4.1100
Role admin
Note
Default N/A
History 3.2.3000
Role admin
Note
Default default-ca-list
History 3.2.3000
Role admin
Note
web enable
web enable
no web enable
Default enable
History 3.1.0000
Role admin
Note
web http
web http {enable | port <port number> | redirect}
no web http {enable | port | redirect}
History 3.1.0000
Role admin
web httpd
web httpd listen {enable | interface <ifName>}
no web httpd listen {enable | interface <ifName>}
Enables the listen interface restricted list for HTTP and HTTPS.
The no form of the command disables the HTTP server listen ability.
Syntax Description enable Enables Web interface restrictions on access to this sys-
tem.
interface <ifName> Adds interface to Web server access restriction list (i.e.
mgmt0, mgmt1)
History 3.1.0000
Role admin
Note If enabled, and if at least one of the interfaces listed is eligible to be a listen interface,
then HTTP/HTTPS requests will only be accepted on those interfaces. Otherwise,
HTTP/HTTPS requests are accepted on any interface.
web https
web https {certificate {regenerate | name | default-cert} | enable | port <port
number> | ssl ciphers {all | TLS | TLS1.2}}
no web https {enable | port <port number>}
Syntax Description certificate regenerate Re-generates certificate to use for HTTPS connections.
History 3.1.0000
Role admin
History 3.6.8008
Role admin
Note
Default Enabled
History 3.6.8008
Role admin
Note
History 3.1.0000
Role admin
Note
Syntax Description password Sets plaintext password for HTTP basic authentication
with web proxy
Default N/A
History 3.1.0000
Role admin
Note
Default N/A
History 3.1.0000
Role admin
Note
show web
show web
Default N/A
History 3.6.6000
Role admin
Inactivity timeout: 1 hr
Session timeout: 2 hr 30 min
Session renewal: 30 min
Related Commands
Note
4 System Management
4.1 Management Interface
Management interfaces are used in order to provide access to switch management user interfaces
(e.g. CLI, WebUI). Mellanox switches support out-of-band (OOB) dedicated interfaces (e.g.
mgmt0, mgmt1) and in-band dedicated interfaces. In addition, most Mellanox switches feature a
serial port that provides access to the CLI only.
On switch systems with two OOB management ports, both of them may be configured on the
same VLAN if needed. In this case, ARP replies to the IP of those management interfaces is
answered from either of them.
Getting the hostname through DHCP is enable by default and will change the switch
hostname if the hostname is not set by the user. Therefore, if a switch is part of an HA
cluster (e.g. SM HA, GW HA) the user would need to make sure the HA master has the
same HA node names as the DHCP server.
4.1.6 Commands
4.1.6.1 Interface
This chapter describes the commands should be used to configure and monitor the management
interface.
interface
interface {mgmt0 | mgmt1 | lo | vlan<id> | ib0}
lo Loopback interface.
Default N/A
History 3.1.0000
Role admin
Notes
ip address
ip address <IP address> <netmask>
no ip address
Default 0.0.0.0/0
History 3.1.0000
Role admin
Notes If DHCP is enabled on the specified interface, then the DHCP IP assignment will
hold until DHCP is disabled.
ip default-gateway
ip default-gateway <next hop IP address or interface name>
no ip default-gateway
Default N/A
History 3.1.0000
Role admin
Related Commands
Notes
alias
alias <index> ip address < IP address> <netmask>
no alias <index>
Adds an additional IP address to the specified interface. The secondary address will
appear in the output of “show interface” under the data of the primary interface along
with the alias.
The no form of the command removes the secondary address to the specified inter-
face.
Default N/A
History 3.1.0000
Role admin
Notes • If DHCP is enabled on the specified interface, then the DHCP IP assignment will
hold until DHCP is disabled
• More than one additional IP address can be added to the interface
mtu
mtu <bytes>
no mtu <bytes>
Default 1500
History 3.6.3004
Role admin
Notes
duplex
duplex <duplex>
no duplex
Syntax Description duplex Sets the duplex mode of the interface. The following
are the possible values:
• half - half duplex
• full - full duplex
• auto - auto duplex sensing (half or full)
Default auto
History 3.1.0000
Role admin
Notes • Setting the duplex to “auto” also sets the speed to “auto”
• Setting the duplex to one of the settings “half” or “full” also sets the speed to a
manual setting which is determined by querying the interface to find out its cur-
rent auto-detected state
speed
speed <speed>
no speed
Syntax Description speed Sets the speed of the interface. The following are the
possible values:
• 10 - fixed to 10Mbps
• 100 - fixed to 1000Mbps
• 1000 - fixed to 1000Mbps
• auto - auto speed sensing (10/100/1000Mbps)
Default auto
History 3.1.0000
Role admin
Notes • Setting the speed to “auto” also sets the duplex to “auto”
• Setting the speed to one of the manual settings (generally “10”, “100”, or “1000”)
also sets the duplex to a manual setting which is determined by querying the inter-
face to find out its current auto-detected state
dhcp
dhcp [renew]
no dhcp
Default Could be enabled or disabled (per part number) manufactured with 3.2.0500
History 3.1.0000
Role admin
Notes • When enabling DHCP, the IP address and netmask are received via DHCP hence,
the static IP address configuration is ignored
• Enabling DHCP disables zeroconf and vice versa
• Setting a static IP address and netmask does not disable DHCP. DHCP is disabled
using the “no” form of this command, or by enabling zeroconf.
dhcp hostname
dhcp hostname
no dhcp hostname
Default Enabled
History 3.5.1000
Role admin
Notes • If a hostname is configured manually by the user, that configuration would over-
ride the “dhcp hostname” configuration
• After upgrading to version 3.5.1000 when a default hostname is not configured,
the DHCP server assigns the new hostname for your machine
• These commands do not work on in-band interfaces
shutdown
shutdown
no shutdown
Default no shutdown
History 3.1.0000
Role admin
Notes
zeroconf
zeroconf
no zeroconf
Default no zeroconf
History 3.1.0000
Role admin
comment
comment <comment>
no comment
Syntax Description comment A free-form string that has no semantics other than
being displayed when the interface records are listed.
Default no comment
History 3.1.0000
Role admin
Notes
ipv6 enable
ipv6 enable
no ipv6 enable
History 3.1.0000
Role admin
Notes • The interface identifier is a 64-bit long modified EUI-64, which is based on the
MAC address of the interface
• If IPv6 is enabled on an interface, the system will automatically add a link-local
address to the interface. Link-local addresses can only be used to communicate
with other hosts on the same link, and packets with link-local addresses are never
forwarded by a router.
• A link-local address, which may not be removed, is required for proper IPv6 oper-
ation. The link-local addresses start with “fe80::”, and are combined with the
interface identifier to form the complete address.
ipv6 address
ipv6 address {<IPv6 address/netmask> | autoconfig [default | privacy]}
no ipv6 {<IPv6 address/netmask> | autoconfig [default | privacy]}
Configures IPv6 address and netmask to this interface, static or autoconfig options
are possible.
The no form of the command removes the given IPv6 address and netmask or dis-
ables the autoconfig options.
Syntax Description IPv6 address/netmask Configures a static IPv6 address and netmask.
Format example: 2001:db8:1234::5678/64.
autoconfig default Enables default learning routes. The default route will
be discovered automatically, if the autoconfig is
enabled.
History 3.1.0000
Role admin
Default N/A
History 3.1.0000
Role admin
Notes
Default N/A
History 3.1.0000
Role admin
Notes • This command only gets DNS configuration, not an IPv6 address
• The no form of the command requests all information, including an IPv6 address
Default N/A
History 3.1.0000
Role admin
IPv6 address:
fe80::268a:7ff:fe53:3d8e/64
Rx:
2055054 bytes
28830 packets
0 mcast packets
0 discards
0 errors
0 overruns
0 frame
Tx:
377716 bytes
3200 packets
0 discards
0 errors
0 overruns
0 carrier
0 collisions
0 queue len
Notes
Default N/A
History 3.1.0000
Role admin
IPv6 address:
fe80::268a:7ff:fe53:3d8e/64
Notes
Default N/A
History 3.1.0000
Role admin
Notes
hostname
hostname <hostname>
no hostname
History 3.1.0000
Role admin
Notes • Hostname may contain letters, numbers, periods (‘.’), and hyphens (‘-’), in any
combination
• Hostname may be 1-63 characters long
• Hostname may not begin with a hyphen
• Hostname may not contain other characters, such as “%”, “_” etc.
• Hostname may not be set to one of the valid logging commands (i.e. debug-files,
fields, files, format, level, local, monitor, receive, trap)
• Changing the hostname stamps a new HTTPS certificate
ip name-server
ip name-server <IPv4/IPv6 address>
no name-server <IPv4/IPv6 address>
History 3.1.0000
Role admin
Notes
ip domain-list
ip domain-list <domain-name>
no ip domain-list <domain-name>
History 3.1.0000
Role admin
Notes
ip/ipv6 host
{ip | ipv6} host <hostname> <IP Address>
no {ip | ipv6} host <hostname> <IP Address>
History 3.1.0000
Role admin
Notes
ip/ipv6 map-hostname
{ip |ipv6} map-hostname
no {ip | ipv6} map-hostname
History 3.1.0000
Role admin
Notes • If no mapping is configured, a mapping between the hostname and the IPv4 loop-
back address 127.0.0.1 will be added
• The no form of the command maps the hostname to the IPv6 loopback address if
there is no statically configured mapping from the hostname to an IPv6 address
(disabled by default)
• Static host mappings are preferred over DNS results. As a result, with this option
set, you will not be able to look up your hostname on your configured DNS
server; but without it set, some problems may arise if your hostname cannot be
looked up in DNS.
show hosts
show hosts
Default N/A
History 3.1.0000
Role admin
Notes
4.1.6.3 Routing
nexthop-address The IPv4 or IPv6 address of the next hop router for this
route.
Default N/A
History 3.1.0000
Role admin
Notes
ipv6 default-gateway
ipv6 default-gateway {<ip-address> | <ifname>}
no ipv6 default-gateway
Default N/A
History 3.1.0000
Role admin
Notes • The configured default gateway will not be used if DHCP is enabled.
• In order to configure ipv4 default-gateway use ‘ip route’ command.
Syntax Description static Filters the table with the static route entries.
Default N/A
History 3.1.0000
Role admin
Notes
Syntax Description static Displays the static configuration of the default gateway
Default N/A
History 3.1.0000
Role admin
Notes The configured IPv4 default gateway will not be used if DHCP is enabled.
IPv4 network use Address Resolution Protocol (ARP) to resolve IP address to MAC address,
while IPv6 network uses Network Discovery Protocol (NDP) that performs basically the same as
ARP.
ip arp
ip arp <ip-address> <mac-address>
no ip arp <ip-address> <mac-address>
Default N/A
History 3.2.0500
Role admin
Notes
ip arp timeout
ip arp [vrf <vrf-name>] timeout <timeout-value>
no ip arp [vrf <vrf-name>] timeout
Syntax Description timeout-value Time (in seconds) that an entry remains in the ARP
cache. Range: 60-28800.
History 3.2.0230
Role admin
Notes • This value is used as the default ARP timeout whenever a new IP interface is cre-
ated
• The time interval after which each ARP entry becomes stale may actually vary
from 50-150% of the configured value
show ip arp
show ip arp [interface <type> | <ip-address> | count]
Syntax Description interface type Filters the table according to a specific interface (i.e.
mgmt0)
Default N/A
History 3.3.3000
Role admin
Related Commands
Notes
ipv6 neighbor
ipv6 neighbor <ipv6-address> <ifname> <mac-address>
no ipv6 neighbor <ipv6-address> <ifname> <mac-address>
Default N/A
History 3.1.0000
Role admin
Notes • ARP is used only with IPv4. In IPv6 networks, Neighbor Discovery Protocol
(NDP) is used similarly.
• Use The no form of the command to remove static entries. Dynamic entries can be
cleared via the “clear ipv6 neighbors” command.
Default N/A
History 3.1.0000
Role admin
Notes • Clearing Neighbor Discovery Protocol (NDP) cache removes only the dynamic
entries learned and not the static entries configured
• Use the no form of the command to remove static entries
Syntax Description static Filters only the table of the static entries.
Default N/A
History 3.1.0000
Role admin
Notes
4.1.6.5 DHCP
ip dhcp
ip dhcp {default-gateway yield-to-static| hostname <hostname>| primary-intf
<ifname> | send-hostname }
no ip dhcp {default-gateway yield-to-static| hostname | | primary-intf | send-host-
name}
Syntax Description yield-to-static| Does not allow you to install a default gateway from
DHCP if there is already a statically configured one.
History 3.1.0000
Role admin
show ip dhcp
show ip dhcp
Default N/A
History 3.1.0000
Role admin
Notes
ping
ping [-LRUbdfnqrvVaA] [-c count] [-i interval] [-w deadline] [-p pattern] [-s
packetsize] [-t ttl] [-I interface or address] [-M mtu discovery hint] [-S sndbuf] [-
T timestamp option ] [-Q tos ] [hop1 ...] destination
Default N/A
History 3.1.0000
Role admin
Notes
traceroute
traceroute [-46dFITUnrAV] [-f first_ttl] [-g gate,...] [-i device] [-m max_ttl] [-N
squeries] [-p port] [-t tos] [-l flow_label] [-w waittime] [-q nqueries] [-s src_addr]
[-z sendwait] host [packetlen]
-6 Uses IPv6
Default N/A
History 3.1.0000
Role admin
Related Commands
Notes
tcpdump
tcpdump [-aAdDeflLnNOpqRStuUvxX] [-c count] [ -C file_size ]
[ -E algo:secret ] [ -F file ] [ -i interface ] [ -M secret ]
[ -r file ] [ -s snaplen ] [ -T type ] [ -w file ]
[ -W filecount ] [ -y datalinktype ] [ -Z user ]
[ -D list possible interfaces ] [ expression ]
Invokes standard binary, passing command line parameters straight through. Runs in
foreground, printing packets as they arrive, until the user hits Ctrl+C.
Default N/A
History 3.1.0000
Role admin
Notes
4.2.3 Commands
clock set
clock set <hh:mm:ss> [<yyyy/mm/dd>]
yyyy/mm/dd Date.
Default N/A
History 3.1.0000
Role admin
clock timezone
clock timezone [<zone word> [<zone word> [<zone
word>] [<zone word>]]]
Sets the system time zone. The time zone may be specified in one of three ways:
• A nearby city whose time zone rules to follow. The system has a large list of cities
which can be displayed by the help and completion system. They are organized
hierarchically because there are too many of them to display in a flat list. A given
city may be required to be specified in two, three, or four words, depending on the
city.
• An offset from UTC. This will be in the form UTC-offset UTC, UTC-offset
UTC+<0-14>, UTC-offset UTC-<1-12>.
• UTC (Universal Time, which is almost identical to GMT), and this is the default
time zone
The no form of the command resets time zone to its default (GMT).
Syntax Description zone word The possible forms this could take include: continent,
city, continent, country, city, continent, region, country,
city, ocean, and/or island.
Default GMT
History 3.1.0000
Role admin
Notes
ntp
ntp {disable | enable | {peer | server} <IP address> [version <number> | disable]}
no ntp {disable | enable | {peer | server} <IP address> [version <number> | dis-
able]}
Configures NTP.
The no form of the command negates NTP options.
History 3.1.0000
Role admin
Notes
ntpdate
ntpdate <IP address>
Default N/A
History 3.1.0000
Role admin
Notes This is a one-time operation and does not cause the clock to be kept in sync on an
ongoing basis. It will generate an error if SNTP is enabled since the socket it requires
will already be in use.
ntp authenticate
ntp authenticate
no ntp authenticate
Default Disabled
History 3.5.0200
Role admin
Notes
ntp authentication-key
ntp authentication-key <key_id> <encrypt_type> [<password>]
no ntp authentication-key <key_id>
Syntax Description key_id Specifies a key ID, whether existing or a new one to be
added. Range: 1-65534.
Default Disabled
History 3.5.0200
Role admin
Notes If a password is not entered, a prompt appears requiring that a password is introduced.
Syntax Description ip_address IP address of the peer. IPv4, IPv6 and hostname
(FQDN) are acceptable.
Default Disabled
History 3.5.0200
Role admin
Notes • IP addresses must be in IPv4 format (e.g., '192.168.0.1') or IPv6 format with scope
zone id for IPv6 link-local addresses (e.g., '2001:db8:701f::8f9' or
'fe80::21c:23f:ec1:4fb%7'.)
• The length of a hostname is limited to 255 characters. Each label (node delimited
by a dot in the hostname) is limited to 63 characters and may contain letters, num-
bers and hyphens ('-'), but may not begin with a hyphen.
Syntax Description ip_address IP address of the peer. IPv4, IPv6 and hostname
(FQDN) are acceptable.
Default Disabled
History 3.5.0200
Role admin
Notes • IP addresses must be in IPv4 format (e.g., '192.168.0.1') or IPv6 format with scope
zone id for IPv6 link-local addresses (e.g., '2001:db8:701f::8f9' or
'fe80::21c:23f:ec1:4fb%7'.)
• The length of a hostname is limited to 255 characters. Each label (node delimited
by a dot in the hostname) is limited to 63 characters and may contain letters, num-
bers and hyphens ('-'), but may not begin with a hyphen.
Syntax Description ip_address IP address of the peer. IPv4, IPv6 and hostname
(FQDN) are acceptable.
Default 4
History 3.5.0200
Role admin
Notes • IP addresses must be in IPv4 format (e.g., '192.168.0.1') or IPv6 format with scope
zone id for IPv6 link-local addresses (e.g., '2001:db8:701f::8f9' or
'fe80::21c:23f:ec1:4fb%7'.)
• The length of a hostname is limited to 255 characters. Each label (node delimited
by a dot in the hostname) is limited to 63 characters and may contain letters, num-
bers and hyphens ('-'), but may not begin with a hyphen.
Syntax Description ip_address IP address of the peer. IPv4, IPv6 and hostname
(FQDN) are acceptable.
Default Disabled
History 3.5.0000
Role admin
Notes • IP addresses must be in IPv4 format (e.g., '192.168.0.1') or IPv6 format with scope
zone id for IPv6 link-local addresses (e.g., '2001:db8:701f::8f9' or
'fe80::21c:23f:ec1:4fb%7'.)
• The length of a hostname is limited to 255 characters. Each label (node delimited
by a dot in the hostname) is limited to 63 characters and may contain letters, num-
bers and hyphens ('-'), but may not begin with a hyphen.
Syntax Description ip_address IP address of the peer. IPv4, IPv6 and hostname
(FQDN) are acceptable.
Default Disabled
History 3.5.0200
Role admin
Notes • IP addresses must be in IPv4 format (e.g., '192.168.0.1') or IPv6 format with scope
zone id for IPv6 link-local addresses (e.g., '2001:db8:701f::8f9' or
'fe80::21c:23f:ec1:4fb%7'.)
• The length of a hostname is limited to 255 characters. Each label (node delimited
by a dot in the hostname) is limited to 63 characters and may contain letters, num-
bers and hyphens ('-'), but may not begin with a hyphen.
Trusts this NTP server; if authentication is configured this will additionally force all
time updates to only use trusted servers.
The no form of the command removes trust from this NTP server
Syntax Description ip_address IP address of the peer. IPv4, IPv6 and hostname
(FQDN) are acceptable.
Default N/A
History 3.6.2002
Role admin
Notes • IP addresses must be in IPv4 format (e.g., '192.168.0.1') or IPv6 format with scope
zone id for IPv6 link-local addresses (e.g., '2001:db8:701f::8f9' or
'fe80::21c:23f:ec1:4fb%7'.)
• The length of a hostname is limited to 255 characters. Each label (node delimited
by a dot in the hostname) is limited to 63 characters and may contain letters, num-
bers and hyphens ('-'), but may not begin with a hyphen.
• NTP trusted servers can be used as a mitigation for Sybil attacks which is a vulner-
ability caused by NTP peers sharing the same NTP key base. This mitigation adds
the concept of trusted servers which if enabled in conjunction with NTP authenti-
cation ensures that time information will only be obtained from trusted servers.
Syntax Description ip_address IP address of the peer. IPv4, IPv6 and hostname
(FQDN) are acceptable.
Default 4
History 3.5.0200
Role admin
Notes • IP addresses must be in IPv4 format (e.g., '192.168.0.1') or IPv6 format with scope
zone id for IPv6 link-local addresses (e.g., '2001:db8:701f::8f9' or
'fe80::21c:23f:ec1:4fb%7'.)
• The length of a hostname is limited to 255 characters. Each label (node delimited
by a dot in the hostname) is limited to 63 characters and may contain letters, num-
bers and hyphens ('-'), but may not begin with a hyphen.
ntp trusted-key
ntp trusted-key <key(s)>
no ntp trusted-key <key(s)>
Default Disabled
History 3.5.0200
Role admin
Notes Keys may be separated with commas without any space, or they may be set as a range
using a hyphen.
show clock
show clock
Default N/A
History 3.1.0000
Role admin
Notes
show ntp
show ntp
Default N/A
History 3.1.0000
Role admin
10.7.144.19 # IP configuration
Conf Type : peer
Status : sys.peer(*)
Stratum : 2
Offset(msec) : -1.747
Ref clock : 128.59.0.245
Poll Interval (sec): 64
Last Response (sec): 1
Auth state : none
Notes
Default N/A
History 3.5.0200
Role admin
Notes
Default N/A
History 3.5.0200
Role admin
Notes
LLR is a Mellanox proprietary feature and will only work with Mellanox to Mellanox
ports.
LLR Mode
The following LLR modes are applicable per port per speed:
• disable – no LLR
• enable – the port becomes passive, only if it got a request to use LLR it activates, other-
wise it remains disabled
• enable-request – the port becomes active, it keeps sending LLR requests to the peer
LLR Negotiation
Both ports on the link perform LLR discovery and negotiation. In order the LLR to be in active
state on the link, the following should apply:
• One port must be configured with LLR “enable-request” on the specified speed.
• The other port (peer) may be configured with LLR “enable-request” or “enable” on the
same specified speed
If both the local port and remote port configured with LLR “enabled” the LLR negotia-
tion will not be activated - the ports will remain in LLR in-active state.
LLR Status
LLR status is a port parameter that states the current state of the LLR.
• Active – LLR is operationally running
• In-Active – LLR is not running
4.3.1 Commands
Default N/A
History 3.2.0500
Role admin
Related Commands
Notes
Partition 1:
<old_image>
Partition 2:
<old_image>
When deleting an image, you delete the file but not the partition. This is recommended
so as to not overload system resources.
To recover from image corruption (e.g. due to power interruption), there are two
installed images on the system. See the commands “image boot next”, and “image boot
location” for more information.
Partition 1:
<old_image>
Partition 2:
<old_image>
Step 7. Have the new image activate during the next boot. Run:
switch (config) # image boot next
Partition 1:
<new_image>
Partition 2:
<old_image>
After software reboot, the software upgrade will also automatically upgrade the firm-
ware version.
On systems with dual management, the software must be upgraded on both the master
and the slave modules.
In order to upgrade the system on dual management system refer to Section 4.4.3,
“Upgrading MLNX-OS Software on Director Switches,” on page 208.
When performing upgrade from the WebUI, make sure that the image you are trying to
upgrade to is not located already in the system (i.e. fetched from the CLI).
Step 7. Verify all the systems are back online as members of the IB subnet ID. Run:
show ib smnodes {brief}
Using a director switch with different software versions on its two management boards
is not supported.
When replacing a management board the software running on the replacement board
must be aligned with the version of the software running on the other management
board.
In situations of heavy CPU load or noisy network, it is possible that another node
assumes the role of cluster master before all standby nodes have rejoined the group. If
this happens, you may stop waiting and proceed directly to Step 4.
Step 4. Upgrade the master node in the HA group according to steps 1-10 in Section •, “When
upgrading from a version older than 3.6.3130 with an MLAG cluster, output appears as in
“UP” and “Peering” state instead of “Upgrade” on both MLAG VIP clusters. The upgrade
process will not be affected.,” on page 204.
When deleting an image, you delete the file but not the partition. This is recommended
so as to not overload system resources.
The procedure below assumes that booting and running is done from Partition 1 and the
downgrade procedure is performed on Partition 2.
Partition 2:
<downgrade version> 2010-09-19 16:52:50
Last boot partition: 1
Next boot partition: 2
No boot manager password is set.
switch (config) #
Step 6. Configure the boot location to be the other (next) partition. Run:
switch (config) # image boot next
There are two installed images on the system. Therefore, if one of the images gets cor-
rupted (due to power interruption, for example), in the next reboot the image will go up
from the second partition.
In case you are downloading to an older software version which has never been run yet
on the switch, use the following command sequence as well:
switch (config) # no boot next fallback-reboot enable
switch (config) # configuration write
Step 7. Reload the switch. Run:
switch (config) # reload
***IMPORTANT NOTE***
All configuration changes done with the new software are lost when returning to the
older software version.
There are 2 instances where the backup configuration file does not exist:
• The user has run “reset factory” command, which clears all configuration files in the sys-
tem
• The user has run “configuration switch-to” to a configuration file with different name
then the backup file
Note that the configuration file becomes empty if the switch is downgraded to a software version
which has never been installed yet.
To allow switching partition to the older software version for the 2 aforementioned cases only,
follow the steps below:
Step 1. Run the command:
switch (config)# no boot next fallback-reboot enable
Step 2. Set the boot partition. Run:
switch (config)# image boot next
If a firmware update takes place, then the login process is delayed a few minutes.
To verify that the firmware update was successful, log into 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 firmware versions. Make sure that all the firmware versions are the same and
match the default firmware version. If the firmware update failed for one or more modules, then
the following warning is displayed.
Some subsystems are not updated with a default firmware.
If you detect a mismatch in firmware version for one or more modules of the switch
system, please contact your assigned Mellanox Technologies field application engi-
neer.
If you insert a switch spine or leaf with a firmware version other than the default version of
MLNX-OS, an automatic firmware update process will take place immediately to the inserted
module only.
The firmware update may take a few minutes. It is recommended not to run any com-
mands until the firmware update completes.
During firmware upgrade internal link status (up/down) notifications may be sent.
To verify that the firmware update was successful, run the command “show asic-version” (can be
run in any mode). Check that the firmware version of the inserted switch spine or leaf has the
default firmware version.
If you detect a firmware version mismatch for the newly inserted module, please con-
tact your assigned Mellanox Technologies field application engineer.
From version 3.3.4400 and above, the firmware update file format has been changed to
mfa format. TGZ format is no longer supported.
4.4.9 Commands
image boot
image boot {location <location ID> | next}
Specifies the default location where the system should be booted from.
Syntax Description location ID Specifies the default destination location. There can be
up to 2 images on the system. The possible values are 1
or 2.
next Sets the boot location to be the next once after the one
currently booted from, thus avoiding a cycle through all
the available locations.
Default N/A
History 3.1.0000
Role admin
Notes
boot next
boot next fallback-reboot enable
no boot next fallback-reboot enable
Sets the default setting for next boot. Normally, if the system fails to apply the config-
uration on startup (after attempting upgrades or downgrades, as appropriate), it will
reboot to the other partition as a fallback.
The no form of the command tells the system not to do that, only for the next boot.
Default N/A
History 3.2.0506
Role admin
Notes • Normally, if the system fails to apply the configuration on startup (after attempt-
ing upgrades or downgrades, as appropriate) it reboots to the other partition as a
fallback.
• The no form of this command tells the system not to do that only for the next
boot. In other words, this setting is not persistent, and goes back to enabled auto-
matically after each boot.
• When downgrading to an older software version which has never been run yet on
a system, the “fallback reboot” always happens, unless the command “no boot
next fallback-reboot enable” is used. However, this also happens when the older
software version has been run before, but the configuration file has been switched
since upgrading. In general, a downgrade only works (without having the fallback
reboot forcibly disabled) if the process can find a snapshot of the configuration
file (by the same name as the currently active one) which was taken before
upgrading from the older software version. If that is not found, a fallback reboot is
performed in preference to falling back to the initial database because the latter
generally involves a loss of network connectivity, and avoiding that is of para-
mount importance.
boot system
boot system {location | next}
no boot system next
Default N/A
History 3.2.0506
Role admin
Notes
image default-chip-fw
image default-chip-fw <filename>
no image default-chip-fw <original-fw-filename>
Default N/A
History 3.1.0000
Role admin
Notes
image delete
image delete <image name>
Default N/A
History 3.1.0000
Role admin
Notes
image fetch
image fetch <URL> [<filename>]
Syntax Description URL HTTP, HTTPS, FTP, TFTP, SCP and SFTP are sup-
ported. Example: scp://username[:password]@host-
name/path/filename.
Default N/A
History 3.1.0000
Role admin
Other options:
Notes • Please delete the previously available image, prior to fetching the new image
• The path to the file in the case of TFTP depends on the server configuration.
Therefore, it may not be an absolute path but a relative one.
• See Section •, “When upgrading from a version older than 3.6.3130 with an
MLAG cluster, output appears as in “UP” and “Peering” state instead of
“Upgrade” on both MLAG VIP clusters. The upgrade process will not be
affected.,” on page 204
image install
image install <image filename> [location <location ID>] | [progress <prog-
options>]
Default N/A
History 3.1.0000
Role admin
Notes • The image cannot be installed on the “active” location (the one which is currently
being booted)
• On a two-location system, the location is chosen automatically if no location is
specified
image move
image move <src image name> <dest image name>
Syntax Description src image name Specifies the old image name.
Default N/A
History 3.1.0000
Role admin
Notes
image options
image options serve all
no image options serve all
Syntax Description serve all Specifies that the image files present on this appliance
should be made available for HTTP and/or HTTPS
download
Default N/A
History 3.1.0000
Role admin
Notes The parameter “serve all” affects not only the files currently present, but also any
files that are later downloaded. It only applies to image files, not the installed images,
which are not themselves in a downloadable format.
After running “serve all” the URLs where the images will be available are:
• http://<HOSTNAME>/system_images/<FILENAME>
• https://<HOSTNAME>/system_images/<FILENAME>
show bootvar
show bootvar
Default N/A
History 3.1.0000
Role admin
Partition 1:
X86_64 3.6.4110-12 2017-07-26 06:54:12 x86_64
Partition 2:
X86_64 3.6.4006 2017-07-03 16:17:39 x86_64
Notes
show images
show image
Default N/A
History 3.1.0000
Role admin
Partition 1:
X86_64 3.6.4110-12 2017-07-26 06:54:12 x86_64
Partition 2:
X86_64 3.6.4006 2017-07-03 16:17:39 x86_64
webimage.tbz
X86_64 3.6.4071-12 2017-07-26 06:54:12 x86_64
Notes
If the configuration file is loaded on a different CPU than the SM HA master (SM HA
master that servers the VIP), the SM configuration is overwritten.
A takeover will occur changing the Slave management module role to Master.
A newly created BIN configuration file is always empty and is not created from the run-
ning-config.
Applying a new BIN configuration file changes the whole switch’s configuration and
requires system reboot which can be preformed using the command reload.
A binary configuration file uploaded from the switch is encrypted and has integrity ver-
ification. If the file is modified in any manner, the fetch to the switch fails.
A newly created text configuration file is always created from the running-config.
4.5.5 Commands
Default N/A
History 3.1.0000
Role admin
Notes The dump can then be manipulated using the “file debug-dump...” commands.
file debug-dump
file debug-dump {delete {<filename> | all | latest} | email {<filename> | latest} |
upload {<filename> | latest} <URL>}
Default N/A
History 3.1.0000
Role admin
Notes
file debug-dump
file debug-dump {delete {<filename> | latest} | email {<filename> | latest} |
upload {{<filename> | latest} <URL>}}
upload {{<filename> | lat- Uploads a debug dump file to a remote host. The URL
est} <URL>}} to the remote host: HTTP, HTTPS, FTP, TFTP, SCP
and SFTP are supported. Example: scp://user-
name[:password]@hostname/path/filename.
Default N/A
History 3.1.0000
Role admin
Notes
file stats
file stats {delete <filename> | move {<source filename> | <destination filename>}
| upload <filename> <URL>}
Default N/A
History 3.1.0000
Role admin
Notes
file tcpdump
file tcpdump {delete <filename> | upload <filename> <URL>}
Syntax Description delete <filename> Deletes the specified tcpdump output file.
upload <filename> Uploads the specified tcpdump output file to the speci-
<URL> fied URL.
Default N/A
History 3.1.0000
Role admin
Notes
reload
reload [force immediate | halt [noconfirm] | noconfirm]
Syntax Description force immediate Forces an immediate reboot of the system even if the
system is busy.
Default N/A
History 3.1.0000
Role admin
Notes BBU discharge must be disabled before any planned shutdown of the switch
reset factory
reset factory [keep-all-config | keep-basic | keep-virt-vols | only-config] [halt]
Default N/A
History 3.1.0000
Role admin
Default N/A
History 3.1.0000
Role admin
Hostname: switch
Version: X86_64 3.6.4006 2017-07-03 16:17:39 x86_64
Current time: 2017-07-31 16:10:38
System uptime: 19d 18h 20m 12s
==================================================
==================================================
Output of 'uname -a':
==================================================
Notes
Syntax Description filename Display the contents of a particular statistics report file.
Default N/A
History 3.1.0000
Role admin
Notes
Default N/A
History 3.1.0000
Role admin
Notes
Default N/A
History 3.1.0000
Role admin
Notes
configuration audit
configuration audit max-changes <number>
Syntax Description max-changes Set maximum number of audit messages to log per
change.
Default 1000
History 3.1.0000
Role admin
Notes N/A
configuration copy
configuration copy <source name> <dest name>
Default N/A
History 3.1.0000
Role admin
Related Commands
Notes • This command does not affect the current running configuration
• The active configuration file may not be the target of a copy. However, it may be
the source of a copy in which case the original remains active.
configuration delete
configuration delete <filename>
Default N/A
History 3.1.0000
Role admin
Notes • This command does not affect the current running configuration
• The active configuration file may not be deleted
configuration fetch
configuration fetch <URL> [<name>]
Syntax Description URL HTTP, HTTPS, FTP, TFTP, SCP and SFTP are sup-
ported. Example: scp://username[:password]@host-
name/path/filename.
Default N/A
History 3.1.0000
Role admin
Notes • The downloaded file should not override the active configuration file, using the
<name> parameter
• If no name is specified for a configuration fetch, it is given the same name as it
had on the server
• No configuration file may have the name “active”
configuration jump-start
configuration jump-start
Default N/A
History 3.1.0000
Role admin
Notes • The wizard is automatically invoked whenever the CLI is launched when the
active configuration file is fresh (i.e. not modified from its initial contents)
• This command invokes the wizard on demand – see chapter “Initializing the
Switch for the First Time” in the MLNX-OS User Manual
configuration merge
configuration merge <filename>
Merges the “shared configuration” from one configuration file into the running con-
figuration.
Default N/A
History 3.1.0000
Role admin
Related Commands
configuration move
configuration move <source name> <dest name>
Default N/A
History 3.1.0000
Role admin
Notes • This command does not affect the current running configuration
• The active configuration file may not be the target of a move
configuration new
configuration new <filename> [factory [keep-basic] [keep-connect]]
Creates a new configuration file under the specified name. The parameters specify
what configuration, if any, to carry forward from the current running configuration.
History 3.1.0000
Role admin
Notes
configuration revert
configuration revert {factory [keep-basic | keep-connect]| saved}
Syntax Description factory Creates new file with only factory defaults.
Default N/A
History 3.1.0000
Role admin
Notes This command is only available when working with an InfiniBand profile
This command is not available on IB multi-SWID system profile
configuration switch-to
configuration switch-to <filename> [no-reboot]
Loads the configuration from the specified file and makes it the active configuration
file.
Default N/A
History 3.1.0000
Role admin
Notes • The current running configuration is lost and not automatically saved to the previ-
ous active configuration file.
• When running the command without the “no-reboot” parameter, the user is
prompted to OK a reboot. If the answer is “yes”, the configuration is replaced and
the switch is rebooted immediately.
Fetches a text configuration file (list of CLI commands) from a specified URL.
Syntax Description apply Applies the file to the running configuration (i.e. exe-
cutes the commands in it). This option has the follow-
ing parameters:
• discard: Does not keep downloaded configuration
text file after applying it to the system
• fail-continue: If applying commands, continues
execution even if one of them fails
• overwrite: If saving the file and the filename
already exists, replaces the old file
• verbose: Displays all commands being executed
and their output instead of just those that get errors
overwrite Downloads the file and saves it using the same name it
had on the server. This option has the following param-
eters:
• apply: Applies the downloaded configuration to the
running system
• filename: Specifies filename for saving downloaded
text file
Default N/A
History 3.2.1000
Role admin
Notes
upload <URL> Supported types are HTTP, HTTPS, FTP, TFTP, SCP
and SFTP. For example: scp://username[:pass-
word]@hostname/path/filename.
Default N/A
History 3.1.0000
Role admin
Notes
upload <URL> Supported types are HTTP, HTTPS, FTP, TFTP, SCP
and SFTP. For example: scp://username[:pass-
word]@hostname/path/filename.
Default N/A
History 3.1.0000
Role admin
Notes
configuration upload
configuration upload {active | <name>} <URL or scp or sftp://username:pass-
word@hostname[:port]/path/filename>
Default N/A
History 3.1.0000
Role admin
configuration write
configuration write [local | to <filename> [no-switch]]
Syntax Description local Saves the running configuration locally (same as “write
memory local”)
no-switch Saves the running configuration to this file but keep the
current one active
Default N/A
History 3.1.0000
Role admin
Notes
write
write {memory [local] | terminal}
Default N/A
History 3.1.0000
Role admin
Notes
show configuration
show configuration [audit | files [<filename>] | running | text files]
Displays a list of CLI commands that will bring the state of a fresh system up to
match the current persistent state of this system.
Default N/A
History 3.1.0000
Role monitor/admin
Related Commands
Notes
show running-config
show running-config [expanded | protocol <protocol>]
Default N/A
History 3.1.0000
Role monitor/admin
##
## Running-config temporary prefix mode setting
##
no cli default prefix-modes enable
##
## License keys
##
license install <license>
##
## Other IP configuration
##
hostname switch
##
## Local user account configuration
##
username root nopassword
##
## AAA remote server configuration
##
# ldap bind-password ********
# radius-server key ********
# tacacs-server key ********
##
## SNMP configuration
##
snmp-server user 7YLAyJrC77 v3 capability admin
snmp-server user 7YLAyJrC77 v3 enable
snmp-server user 7YLAyJrC77 v3 enable sets
no snmp-server user 7YLAyJrC77 v3 require-privacy
snmp-server user kRg5dmdogX v3 capability admin
snmp-server user kRg5dmdogX v3 enable
snmp-server user kRg5dmdogX v3 enable sets
no snmp-server user kRg5dmdogX v3 require-privacy
##
## Network management configuration
##
# web proxy auth basic password ********
##
## Persistent prefix mode setting
##
cli default prefix-modes enable
Related Commands
Notes
4.6 Logging
4.6.1 Monitor
To print logging events to the terminal:
Set the modules or events you wish to print to the terminal. For example, run:
switch (config) # logging monitor events notice
switch (config) # logging monitor sx-sdk warning
These commands print system events in severity “notice” and “sx-sdk” module notifications in
severity “warning” to the screen. For example, in case of interface-down event, the following
gets printed to the screen.
switch (config) #
Wed Jul 10 11:30:42 2013: Interface IB1/17 changed state to DOWN
Wed Jul 10 11:30:43 2013: Interface IB1/18 changed state to DOWN
To see a list of the events, refer to Table 25, “Supported Event Notifications and MIB Map-
ping,” on page 298.
4.6.3 Commands
logging port
logging <syslog IPv4 address/hostname> port <destination-port>
no logging <syslog IPv4 address/hostname> port
History 3.6.2002
Role admin
Notes
logging trap
logging <syslog IPv4 address/hostname> [trap {<log-level> | override class
<class> priority <log-level>}]
no logging <syslog IPv4 address/hostname> [trap {<log-level> | override class
<class> priority <log-level>}]
Enables (by setting the IPv4 address/hostname) sending logging messages, with abil-
ity to filter the logging messages according to their classes.
The no form of the command stops sending messages to the remote syslog server.
Syntax Description syslog IPv4 address/host- IPv4 address/hostname of the remote syslog server.
name Hostname is limited to 64 characters
History 3.1.0000
Role admin
Notes
logging debug-files
logging debug-files {delete {current | oldest} | rotation {criteria | force | max-
num} | update {<number> | current} | upload <log-file> <upload URL>}
upload URL HTTP, HTTPS, FTP, TFTP, SCP and SFTP are sup-
ported (e.g.: scp://username[:password]@hostname/
path/filename)
Default N/A
History 3.3.4150
Role admin
Related Commands
Notes
Default N/A
History 3.6.6000
Role admin
Related Commands
Notes
Configures number of events after which the system begins to generate events to the
log file.
The no form of the command resets this parameter to its default value.
History 3.6.6000
Role admin
Related Commands
Notes
Syntax Description interfaces | protocols Logical groups with specified set of counters
History 3.6.6000
Role admin
Related Commands
Notes
Configures the number of allowed events per time window and that window’s dura-
tion.
The no form of the command resets these parameters to their default values.
Syntax Description interfaces | protocols Logical groups with specified set of counters
Configuration config
Mode
History 3.6.6000
Role admin
Related Commands
Notes • The goal of this command is to restrict the number of events in the log. To achieve
this end, it is possible to specify the allowed number (parameter “count”) of mes-
sages per period of time (parameter “window”).
logging fields
logging fields seconds {enable | fractional-digits <f-digit> | whole-digits <w-
digit>}
no logging fields seconds {enable | fractional-digits <f-digit> | whole-digits <w-
digit>}
Specifies whether to include an additional field in each log message that shows the
number of seconds since the Epoch or not.
The no form of the command disallows including an additional field in each log mes-
sage that shows the number of seconds since the Epoch.
Default disabled
History 3.1.0000
Role admin
Notes This is independent of the standard syslog date and time at the beginning of each
message in the format of “July 15 18:00:00”. Aside from indicating the year at full
precision, its main purpose is to provide subsecond precision.
Default CLI commands and audit message are set to notice logging level
History 3.1.0000
Role admin
Notes
Default 10 files are kept by default with rotation criteria of 5% of the log partition size
History 3.1.0000
Role admin
Notes
Default 10 files are kept by default with rotation criteria of 5% of the log partition size
History 3.1.0000
Role admin
Notes
logging format
logging format {standard | welf [fw-name <hostname>]}
no logging format {standard | welf [fw-name <hostname>]}
Default standard
History 3.1.0000
Role admin
Notes
logging level
logging level {cli commands <log-level> | audit mgmt <log-level>}
Sets the severity level at which CLI commands or the management audit message that
the user executes are logged. This includes auditing of both configuration changes
and actions.
Syntax Description cli commands Sets the severity level at which CLI commands which
the user executes are logged.
audit mgmt Sets the severity level at which all network manage-
ment audit messages are logged.
Default CLI commands and audit message are set to notice logging level
History 3.1.0000
Role admin
Notes
Syntax Description override Enables class-specific overrides to the local log level.
History 3.1.0000
Role admin
Notes
logging monitor
logging monitor <facility> <priority-level>
no logging monitor <facility> <priority-level>
priority-level • none
• emerg
• alert
• crit
• err
• warming
• notice
• info
• debug
History 3.3.4000
Role admin
Related Commands
Notes
logging receive
logging receive
no logging receive
History 3.1.0000
Role admin
logging trap
logging trap <log-level>
no logging trap
Syntax Description log-level The minimum severity level for all configured syslog
servers:
• none – disable logging
• emerg – emergency: system is unusable
• alert – action must be taken immediately
• crit – critical conditions
• err – error conditions
• warning – warning conditions
• notice – normal but significant condition
• info – informational messages
• debug – debug-level messages
History 3.1.0000
Role admin
Related Commands
Notes
show log
show log [continuous | files [<file-number>]] [[not] matching <reg-exp>]
Syntax Description continues Displays the last few lines of the current log file and
then continues to display new lines as they come in
until the user hits Ctrl+C, similar to LINUX “tail” util-
ity.
[not] matching <reg-exp> The file is piped through a LINUX “grep” utility to
only include lines either matching, or not matching, the
provided regular expression.
Default N/A
History 3.1.0000
Role admin
Notes • When using a regular expression containing | (OR), the expression should be sur-
rounded by quotes (“<expression>”), otherwise it is parsed as filter (PIPE) com-
mand.
• The command’s output has many of the options as the Linux “less” command.
These options allow navigating the log file and perform searches. To see help for
different option press “h” after running the “show log” command.
show logging
show logging
Default N/A
History 3.1.0000
Role admin
Notes
Syntax Description interfaces | protocols Logical groups with specified set of counters
Default N/A
History 3.6.6000
Role admin
interfaces:
Admin mode : no
Interval : 5 minutes
Error threshold: 10
protocols:
Admin mode : no
Interval : 1 minute
Error threshold: 2
Related Commands
Notes
Syntax Description interfaces | protocols Logical groups with specified set of counters
Default N/A
History 3.6.6000
Role admin
interfaces:
Counters: Rx discard packets, Rx error packets, Rx fcs errors, Rx
undersize packets, Rx oversize packets, Rx unknown control opcode, Rx
symbol errors, Rx discard packets by Storm Control, Tx discard packets,
Tx error packets, Tx hoq discard packets
Related Commands
Notes
4.7.1 General
When debugging a system, it is important to be able to quickly identify the root of a problem.
The Diagnostic commands enables an insight into the physical layer components where the user
is able to see information such as a cable status (plugged/unplugged) or if Auto-Negotiation has
failed.
4.7.3 Commands
Default N/A
History 3.6.4000
Role admin
Related Commands
Notes
Default N/A
History 3.6.4000
Role admin
Related Commands
Notes
Default N/A
History 3.6.4000
Role admin
Related Commands
Notes
4.8.3 Commands
ib signal-degrade
ib <slot>/<port> signal-degrade [no-shutdown]
no ib <slot>/<port> signal-degrade [no-shutdown]
Default Disabled
History 3.6.6102
Role admin
Related Commands
Notes
Default N/A
History 3.6.6102
Role admin
Related Commands
This command prints system events in the severity “notice” to the screen. For example, in case
of interface-down event, the following gets printed to the screen.
switch (config) #
Wed Jul 10 11:30:42 2013: Interface IB1/17 changed state to DOWN
Wed Jul 10 11:30:43 2013: Interface IB1/18 changed state to DOWN
switch (config) #
4.9.5 Commands
Default N/A
History 3.2.3000
Role admin
Notes
Default N/A
History 3.2.3000
Role admin
Notes
Syntax Description none Does not use TLS to secure auto-support email.
tls Uses TLS over the default server port to secure auto-
support email and does not send an email if TLS fails.
Default tls-none
History 3.2.3000
Role admin
Notes
Default N/A
History 3.2.3000
Role admin
Notes
Default default_ca_list
History 3.2.3000
Role admin
Notes
email dead-letter
email dead-letter {cleanup max-age <duration> | enable}
no email dead-letter
History 3.1.0000
Role admin
Notes
email domain
email domain <hostname or IP address>
no email domain
Sets the domain name from which the emails will appear to come from (provided that
the return address is not already fully-qualified). This is used in conjunction with the
system hostname to form the full name of the host from which the email appears to
come.
The no form of the command clears email domain override.
History 3.1.0000
Role admin
Notes
email mailhub
email mailhub <hostname or IP address>
no email mailhub
Default N/A
History 3.1.0000
Role admin
Notes
Sets the mail relay to be used for sending autosupport notification emails. The no
form of the command clears the mail relay to be used for sending autosupport notifi-
cation emails.
Default N/A
History 3.7.10xx
Role Admin
Autosupport emails
Enabled: no
Recipient:
Mail hub: 10.10.10.1
Security mode: tls-none
Verify server cert: yes
Supplemental CA list: default-ca-list
Notes
Default N/A
History 3.7.10xx
Role Admin
Autosupport emails
Enabled: no
Recipient: [email protected]
Mail hub:
Security mode: tls-none
Verify server cert: yes
Supplemental CA list: default-ca-list
Notes
email mailhub-port
email mailhub-port <hostname or IP address>
no email mailhub-port
Default 25
History 3.1.0000
Role admin
Notes
Syntax Description event name Example event names would include “process-crash”
and “cpu-util-high”.
History 3.1.0000
Role admin
Notes This does not affect auto-support emails. Auto-support can be disabled overall, but if
it is enabled, all auto-support events are sent as emails.
Adds an email address from the list of addresses to which to send email notifications
of events.
The no form of the command removes an email address from the list of addresses to
which to send email notifications of events.
History 3.1.0000
Role admin
Notes
email return-addr
email return-addr <username>
no email domain
Sets the username or fully-qualified return address from which email notifications are
sent.
• If the string provided contains an “@” character, it is considered to be fully-quali-
fied and used as-is.
• Otherwise, it is considered to be just the username, and we append “@<host-
name>.<domain>”. The default is “do-not-reply”, but this can be changed to
“admin” or whatnot in case something along the line does not like fictitious
addresses.
The no form of the command resets this attribute to its default.
Default do-not-reply
History 3.1.0000
Role admin
Notes
email return-host
email return-host
no email return-host
History 3.1.0000
Role admin
No recipients configured.
Autosupport emails
Enabled: no
Recipient: [email protected]
Mail hub: autosupport.mellanox.com
switch (config) #
Notes This only takes effect if the return address does not contain an “@” character.
email send-test
email send-test
Default N/A
History 3.1.0000
Role admin
Notes
Default default-cert
History 3.2.3000
Role admin
Notes
Default N/A
History 3.2.3000
Role admin
Specifies the list of supplemental certificates of authority (CA) from the certificate
configuration database that is to be used for verification of server certificates when
sending email using TLS, if any.
The no form of the command uses no list of supplemental certificates.
Default default-ca-list
History 3.2.3000
Role admin
Notes This command has no impact unless TLS is used, and certificate verification is
enabled.
show email
show email [events]
Displays email configuration or events for which email should be sent upon.
Default N/A
History 3.7.10xx
Role admin
Autosupport emails
Enabled: no
Recipient:
Mail hub: 10.10.10.1
Security mode: tls-none
Verify server cert: yes
Supplemental CA list: default-ca-list
Notes
4.10 Telemetry
As it is becoming increasingly complex to manage networks, and network administrators need
more tools to understand network behavior, it is necessary to provide basic information about
network performance, identify network bottlenecks, and provide information for the purposes of
network optimization and future planning.
Therefore, network administrators are required to constantly review network port behavior,
record port buffer consumption, and identify shortage in buffer resources and record flows which
lead to the excessive buffer consumption.
MLNX-OS provides the following mechanisms to perform these tasks:
• Sampling (histograms) – a network administrator can enable a sampling of the port buf-
fer occupancy, record occupancy changes over time, and provide information for differ-
ent levels of buffer occupancy, and amount of time the buffer has been occupied during
the observation period.
• Thresholds – thresholds may be enabled per port to record the network time when port
buffer occupancy crosses the defined threshold and when buffer occupancy drops below
it.
• Flow recording – a record of the most active flows which cause an excessive usage of the
port buffers may be kept. Once enabled, the system may identify flow patterns and pres-
ent a user with a list of flows, based on which a network administrator can rearrange dis-
tribution of the data flows in the network and minimize data loss.
4.10.1 Commands
protocol telemetry
protocol telemetry
no protocol telemetry
Default Disabled.
History 3.6.3004
Role admin
Related Commands
Notes
telemetry shutdown
telemetry shutdown
no telemetry shutdown
Disables the telemetry protocol, threshold detection, and histogram fetching for all
sampling enabled interfaces without changing any internal configuration.
The no form of the command enables telemetry protocol.
Default Disabled
History 3.6.3004
Role admin
Related Commands
Notes
telemetry sampling
interface ib <slot>/<port> telemetry sampling
no interface ib <slot>/<port> telemetry sampling
Default N/A
History 3.6.3004
Role admin
Related Commands
Notes
History 3.6.3004
Role admin
Related Commands
Notes
telemetry threshold
telemetry threshold
no telemetry threshold
Default false
History 3.6.4006
Role admin
Related Commands
Notes
Default 69984
History 3.6.4006
Role admin
Related Commands
Notes
Default false
History 3.6.4006
Role admin
Related Commands
Notes
Default Disabled
History 3.6.6105
Role admin
Notes • When top talker is enabled, the minimal threshold window supported is 20 msecs.
• Due to event timing issues, very short threshold events may not gather sufficient
traffic samples to allow top-talker analysis. As a result, top-talkers may not be
fully displayed in the relevant show command.
The command sets threshold events logging rate on per hour basis.
The no form of the command sets the logging rate back to default.
Syntax Description time Max rate per hour. Input range: 1-3600
Default 100
History 3.6.4006
Role admin
Related Commands
Notes
clear telemetry
clear telemetry {threshold | sampling} [interface <type> <port-id>]]
Default N/A
History 3.6.5000
Role admin
Related Commands
Notes
Default N/A
History 3.6.6105
Role admin
Related Commands
Notes
Default N/A
History 3.6.6105
Role admin
Notes
Default N/A
History 3.6.3004
Role admin
Related Commands
Notes
Deletes the given .csv file created by “stats export” command to user directory.
Default N/A
History 3.6.3004
Role admin
Related Commands
Notes
Default N/A
History 3.6.3004
Role admin
Related Commands
Notes
show telemetry
show telemetry
Default
History 3.6.4000
Role admin
Example
switch (config) # show telemetry
Telemetry Status : Enabled
H/W Sampling Interval(nsec) : 512
S/W Sampling Interval(ms) : 1000
Threshold Logging : Disabled
Threshold Logging(rate per hour) : 100
--------------------------------------------------------------------------------------------
Interface Sampling Threshold Record Level (bytes)
--------------------------------------------------------------------------------------------
IB1/1 Disabled Enabled Enabled 100 (96)
IB1/2 Disabled Enabled Enabled 100 (96)
IB1/3 Disabled Disabled Disabled N/A
IB1/4 Disabled Disabled Disabled N/A
IB1/5 Disabled Disabled Disabled N/A
IB1/6 Disabled Disabled Disabled N/A
IB1/7 Disabled Disabled Disabled N/A
...
IB1/36 Disabled Disabled Disabled N/A
Related Commands
Notes
Default N/A
History 3.6.4006
Role admin
Example
switch (config) # show telemetry threshold record interface ib 1/11-1/12
-----------------------------------------------------------------------------------------------------------------
Event-id Date Time Port Level Duration(100 usec) Repeated DestQP DLID SLID Percent(%)
-----------------------------------------------------------------------------------------------------------------
1 07/10/18 14:00:31 IB 1/11 69984 48749.77 1 2741 29 32 62.30
2 07/10/18 14:01:47 IB 1/11 69984 63936.16 1 2745 29 32 54.55
Notes • The values displayed of the SLID, DLID, and QP fields are in decimal
• The command supports displaying up to 1000 threshold events. As a result, if
more than 1000 thresholds configured in total, some interfaces may not be dis-
played. Therefore, to query thresholds for a specific interface, please use “show
telemetry threshold interface ib <interface>”.
Default N/A
History 3.6.3004
Role admin
Example
switch (config) # show telemetry sampling interface ib 1/32
-------------------------------------------------------------------------------------------------------------------------------------
Telemetry histogram: IB1/32
System-time Bin sizes (128 nsec tx buffer was occupied in bytes range)
-------------------------------------------------------------------------------------------------------------------------------------
02/09/17 <2976 35744 68512 101280 134048 166816 199584 232352 265120 265120<
12:19:03.41948 1883 8538 7802080 0 0 0 0 0 0 0
12:19:04.42107 830 9001 7802670 0 0 0 0 0 0 0
12:19:05.42249 96 9705 7802700 0 0 0 0 0 0 0
12:19:06.42388 32 9035 7803434 0 0 0 0 0 0 0
12:19:07.42573 80 9461 7802960 0 0 0 0 0 0 0
12:19:08.42761 160 9302 7803040 0 0 0 0 0 0 0
12:19:09.42915 304 9369 7802829 0 0 0 0 0 0 0
12:19:10.43071 96 8906 7803500 0 0 0 0 0 0 0
12:19:11.43215 463 8907 7803132 0 0 0 0 0 0 0
12:19:12.43369 256 8571 7803675 0 0 0 0 0 0 0
Related Commands
Notes In case requested entries are more than what the DB contains it will print the amount
in the table.
num_of_entries
Default N/A
History 3.6.3004
Role admin
Example
switch (config) # show telemetry sampling interface ib 1/36 last 20
Legend:
2976 bytes - between 0 - 2976 of tx bytes buffer consumed
35744 bytes - between 2977 - 35744 of tx bytes buffer consumed
-------------------------------------------------------------------------------------------------------------------------------------
Telemetry histogram: IB1/36
System-time Bin sizes (128 nsec tx buffer was occupied in bytes range)
-------------------------------------------------------------------------------------------------------------------------------------
02/09/17 <2976 35744 68512 101280 134048 166816 199584 232352 265120 265120<
12:19:03.41948 1883 8538 7802080 0 0 0 0 0 0 0
12:19:04.42107 830 9001 7802670 0 0 0 0 0 0 0
12:19:05.42249 96 9705 7802700 0 0 0 0 0 0 0
12:19:06.42388 32 9035 7803434 0 0 0 0 0 0 0
12:19:07.42573 80 9461 7802960 0 0 0 0 0 0 0
Related Commands
Notes If requested entries are more than what the DB contains, it prints the amount in the
table.
Displays all files created by the command “stats export csv telemetry”.
Default N/A
History 3.6.3004
Role admin
Notes
4.11 mDNS
Multicast DNS (mDNS) protocol is used by the SM HA to deliver control information between
the InfiniBand nodes via the management interface. To block sending mDNS traffic from the
management interface run the command no ha dns enable.
4.11.1 Commands
ha dns enable
ha dns enable
no ha dns enable
Default Enabled.
History 3.3.4000
Role admin
Related Commands
Notes
admin admin
monitor monitor
xmladmin xmladmin
xmluser xmluser
To remove passwords from the XML users, run the command username <username>
nopassword.
Authentication, authorization, and accounting services are often provided by a dedicated AAA
server, a program that performs these functions. Network access servers interface with AAA
servers using the Remote Authentication Dial-In User Service (RADIUS) protocol.
4.12.2.2 RADIUS
RADIUS (Remote Authentication Dial-In User Service), widely used in network environments,
is a client/server protocol and software that enables remote access servers to communicate with a
central server to authenticate dial-in users and authorize their access to the requested system or
service. It is commonly used for embedded network devices such as routers, modem servers,
switches and so on. RADIUS is currently the de-facto standard for remote authentication. It is
prevalent in both new and legacy systems.
It is used for several reasons:
• RADIUS facilitates centralized user administration
• RADIUS consistently provides some level of protection against an active attacker
4.12.2.3 TACACS+
TACACS (Terminal Access Controller Access Control System), widely used in network environ-
ments, is a client/server protocol that enables remote access servers to communicate with a cen-
tral server to authenticate dial-in users and authorize their access to the requested system or
service. It is commonly used for providing NAS (Network Access Security). NAS ensures secure
access from remotely connected users. TACACS implements the TACACS Client and provides
the AAA (Authentication, Authorization and Accounting) functionalities.
TACACS is used for several reasons:
• Facilitates centralized user administration
• Uses TCP for transport to ensure reliable delivery
• Supports inbound authentication, outbound authentication and change password request
for the authentication service
• Provides some level of protection against an active attacker
4.12.2.4 LDAP
LDAP (Lightweight Directory Access Protocol) is an authentication protocol that allows a
remote access server to forward a user's log-on password to an authentication server to determine
whether access can be allowed to a given system. LDAP is based on a client/server model. The
switch acts as a client to the LDAP server. A remote user (the remote administrator) interacts
only with the switch, not the back-end server and database.
LDAP authentication consists of the following components:
If a necessary prerequisite is not fulfilled the system does not activate secure mode and
issues an advisory message accordingly.
4.12.4 Commands
username
username <username> [capability <cap> | disable [login | password] | disconnect
| full-name <name> | nopassword | password [0 | 7] <password>]
no username <username> [capability | disable [login | password] | full-name]
Syntax Description username Specifies a username and creates a user account. New
users are created initially with admin privileges but is
disabled.
nopassword The next login of the user will not require password.
History 3.1.0000
Role admin
Notes • To enable a user account, just set a password on it (or use the command user-
name <user> nopassword to enable it with no password required for login)
• Removing a user account does not terminate any current sessions that user has
open; it just prevents new sessions from being established
• Encrypted password is useful for the command show configuration, since
the cleartext password cannot be recovered after it is set
show usernames
show usernames
Default N/A
History 3.1.0000
Role admin
Notes
show users
show users [history]
Displays logged in users and related information such as idle time and what host they
have connected from.
Default N/A
History 3.1.0000
Role admin
Notes
show whoami
show whoami
Default N/A
History 3.1.0000
Role admin
Notes
aaa accounting
aaa accounting changes default stop-only tacacs+
no aaa accounting changes default stop-only tacacs+
Default N/A
History 3.1.0000
Role admin
Default local
History 3.1.0000
Role admin
Example switch (config) # aaa authentication login default local radius tacacs+
ldap
switch (config) # show aaa
AAA authorization:
Default User: admin
Map Order: local-only
Authentication method(s):
local
radius
tacacs+
ldap
Accounting method(s):
tacacs+
switch (config) #
Notes The order in which the methods are specified is the order in which the authentication
is attempted. It is required that “local” is one of the methods selected. It is recom-
mended that “local” be listed first to avoid potential problems logging in to local
accounts in the face of network or remote server issues.
Configures delay for a specific period of time after every authentication failure.
The no form of the command resets the fail-delay to its default value.
Default 0
History 3.5.0200
Role admin
Notes
Syntax Description downcase Does not convert all usernames to lowercase (for
authentication failure tracking purposes only).
Default N/A
History 3.2.3000
Role admin
Notes • This is required for the lockout functionality described below, but can also be
used on its own for informational purposes.
• Disabling tracking does not clear any records of past authentication failures, or
the locks in the database. However, it does prevent any updates to this database
from being made: no new failures are recorded. It also disables lockout, prevent-
ing new lockouts from being recorded and existing lockouts from being enforced.
Syntax Description enable Enables locking out of user accounts based on authenti-
cation failures.
This both suspends enforcement of any existing lock-
outs, and prevents any new lockouts from being
recorded. If lockouts are later re-enabled, any lockouts
that had been recorded previously resume being
enforced; but accounts which have passed the max-fail
limit in the meantime are NOT automatically locked at
this time. They would be permitted one more attempt,
and then locked, because of how the locking is done:
lockouts are applied after an authentication failure, if
the user has surpassed the threshold at that time.
Lockouts only work if tracking is enabled. Enabling
lockouts automatically enables tracking. Disabling
tracking automatically disables lockouts.
Default N/A
History 3.2.3000
Role admin
Notes
Overrides the global settings for tracking and lockouts for a type of account.
The no form of the command removes this override and lets the admin be handled
according to the global settings.
Syntax Description admin Overrides the global settings for tracking and lockouts
for the admin account. This applies only to the single
account with the username “admin”. It does not apply
to any other users with administrative privileges.
no-lockout Prevents the admin user from being locked out, though
the authentication failure history is still tracked (if
tracking is enabled overall).
Default N/A
History 3.2.3000
Role admin
Notes
Default N/A
History 3.2.3000
Role admin
Example switch (config) # aaa authentication attempts reset user admin all
Notes
Default N/A
History 3.2.3000
Role admin
Example switch (config) # aaa authentication attempts reset user admin no-
clear-history
Notes
aaa authorization
aaa authorization map [default-user <username> | order <policy> | fallback]
no aaa authorization map [default-user | order | fallback]
Syntax Description username Specifies what local account the authenticated user will
be logged on as when a user is authenticated (via
RADIUS or TACACS+ or LDAP) and does not have a
local account. If the username is local, this mapping is
ignored.
History 3.1.0000
Role admin
Notes • If, for example, the user is locally defined to have admin permission, but in a
remote server such as RADIUS the user is authenticated as monitor and the order
is remote-first, then the user is given monitor permissions.
• If AAA authorization order policy is configured to remote-only, then when
upgrading to 3.4.3000 or later from an older MLNX-OS version, this policy is
changed to remote-first.
• The user must be careful when disabling AAA authorization map fallback server-
err, because if the remote server stops working then the user may lock themselves
out.
show aaa
show aaa
Default N/A
History 3.1.0000
Role admin
Notes
Default N/A
History 3.2.1000
Role admin
Username Known Locked Failures Last fail time Last fail from
-------- ----- ------ -------- -------------- --------------
0Q72B43EHBKT8CB5AF5PGRX3U3B3TUL4CYJP93N(*) no no 1 2012/08/20 14:29:19 ttyS0
Notes
4.12.4.3 RADIUS
radius-server
radius-server {key <secret>| retransmit <retries> | timeout <seconds>}
no radius-server {key | retransmit | timeout}
Syntax Description secret Sets a secret key (shared hidden text string), known to
the system and to the RADIUS server.
History 3.1.0000
Role admin
Notes Each RADIUS server can override those global parameters using the command
“radius-server host”.
radius-server host
radius-server host <IP address> [enable | auth-port <port> | key <secret> |
prompt-key | retransmit <retries> | timeout <seconds>]
no radius-server host <IP address> [auth-port | enable]
History 3.1.0000
Role admin
Notes • RADIUS servers are tried in the order they are configured
• If you do not specify a parameter for this configured RADIUS server, the config-
uration will be taken from the global RADIUS server configuration. Refer to
“radius-server” command.
show radius
show radius
Default N/A
History 3.1.0000
Role admin
RADIUS servers:
1.1.1.1:1812:
Enabled : yes
Key : ********
Timeout : 3 (default)
Retransmit: 1 (default)
Notes
4.12.4.4 TACACS+
tacacs-server
tacacs-server {key <secret>| retransmit <retries> | timeout <seconds>}
no tacacs-server {key | retransmit | timeout}
Syntax Description secret Set a secret key (shared hidden text string), known to
the system and to the TACACS+ server.
History 3.1.0000
Role admin
Notes Each TACACS+ server can override those global parameters using the command
“tacacs-server host”.
tacacs-server host
tacacs-server host <IP address> {enable | auth-port <port> | auth-type <type> |
key <secret> | prompt-key | retransmit <retries> | timeout <seconds>}
no tacacs-server host <IP address> {enable | auth-port}
History 3.1.0000
Role admin
Notes • TACACS+ servers are tried in the order they are configured
• A PAP auth-type similar to an ASCII login, except that the username and pass-
word arrive at the network access server in a PAP protocol packet instead of being
typed in by the user, so the user is not prompted
• If the user does not specify a parameter for this configured TACACS+ server, the
configuration will be taken from the global TACACS+ server configuration.
Refer to “tacacs-server” command.
show tacacs
show tacacs
Default N/A
History 3.1.0000
Role admin
TACACS+ servers:
1.1.1.1:49:
Enabled : yes
Auth Type : pap
Key : ********
Timeout : 3 (default)
Retransmit: 1 (default)
Notes
4.12.4.5 LDAP
ldap base-dn
ldap base-dn <string>
no ldap base-dn
Sets the base distinguished name (location) of the user information in the schema of
the LDAP server.
The no form of the command resets the attribute to its default values.
Syntax Description string A case-sensitive string that specifies the location in the
LDAP hierarchy where the server should begin search-
ing when it receives an authorization request.
For example:
“ou=users,dc=example,dc=com”, with no spaces.
when:
ou - Organizational unit
dc - Domain component
cn - Common name
sn - Surname
Default ou=users,dc=example,dc=com
History 3.1.0000
Role admin
Notes
ldap bind-dn/bind-password
ldap {bind-dn | bind-password} <string>
no ldap {bind-dn | bind-password}
Gives the distinguished name or password to bind to on the LDAP server. This can be
left empty for anonymous login (the default).
The no form of the command resets the attribute to its default values.
Default “”
History 3.1.0000
Role admin
Notes For anonymous login, bind-dn and bind-password should be empty strings “”.
ldap group-attribute/group-dn
ldap {group-attribute {<group-att> |member | uniqueMember} | group-dn
<group-dn>}
no ldap {group-attribute | group-dn}
Sets the distinguished name or attribute name of a group on the LDAP server.
The no form of the command resets the attribute to its default values.
History 3.1.0000
Role admin
Notes • The user’s distinguished name must be listed as one of the values of this attribute,
or the user will not be authorized to log in
• After login authentication, if the group-dn is set, a user must be a member of this
group or the user will not be authorized to log in. If the group is not set (“” - the
default) no authorization checks are done.
ldap host
ldap host <IP Address> [order <number> last]
no ldap host <IP Address>
History 3.1.0000
Role admin
Notes • The system will select the LDAP host to try according to its order
• New servers are by default added at the end of the list of servers
History 3.6.8008
Role admin
Notes
ldap login-attribute
ldap login-attribute {<string> | uid | sAMAccountName}
no ldap login-attribute
Sets the attribute name which contains the login name of the user.
The no form of the command resets this attribute to its default.
uid LDAP login name is taken from the user login user-
name.
Default sAMAccountName
History 3.1.0000
Role admin
Notes
ldap port
ldap port <port>
no ldap port
Sets the TCP port on the LDAP server to connect to for authentication.
The no form of the command resets this attribute to its default value.
Default 389
History 3.1.0000
Role admin
Notes
ldap referrals
ldap referrals
no ldap referrals
History 3.1.0000
Role admin
Notes Referral is the process by which an LDAP server, instead of returning a result, will
return a referral (a reference) to another LDAP server which may contain further
information.
ldap scope
ldap scope <scope>
no ldap scope
Specifies the extent of the search in the LDAP hierarchy that the server should make
when it receives an authorization request.
The no form of the command resets the attribute to its default value.
Default subtree
History 3.1.0000
Role admin
Notes
ldap ssl
ldap ssl {ca-list <options> | cert-verify | ciphers {all | TLS1.2} | crl-check {enable
| file fetch <path>} | mode <mode> | port <port-number>}
no ldap ssl {cert-verify | ciphers | crl-check enable | mode | port}
Syntax Description options This command specifies the list of supplemental certifi-
cates of authority (CAs) from the certificate configura-
tion database that is to be used by LDAP for
authentication of servers when in TLS or SSL mode.
The options are:
• default-ca-list - uses default supplemental CA cer-
tificate list
• none - no supplemental list, uses the built-in one
only
CA certificates are ignored if “ldap ssl mode” is not
configured as either “tls” or “ssl”, or if “no ldap ssl
cert-verify” is configured.
The default-ca-list is empty in the factory default con-
figuration. Use the command: “crypto certificate ca-list
default-ca-list name” to add trusted certificates to that
list.
The “default-ca-list” option requires LDAP to consult
the system’s configured global default CA-list for sup-
plemental certificates.
crl-check file fetch Fetches CRL from remote server. CRL must be a valid
PEM file unless a proper message shown. Supported
formats: SCP, HTTP, HTTPS, FTP, and FTPS.
History 3.1.0000
Role admin
100.0%
[#####################################################################]
Notes • If available, the TLS mode is recommended, as it is standardized, and may also be
of higher security
• The port number is used only for SSL mode. In case the mode is TLS, the LDAP
port number will be used.
ldap timeout
ldap {timeout-bind | timeout-search} <seconds>
no ldap {timeout-bind | timeout-search}
Sets a global communication timeout in seconds for all LDAP servers to specify the
extent of the search in the LDAP hierarchy that the server should make when it
receives an authorization request.
The no form of the command resets the attribute to its default value.
Syntax Description timeout-bind Sets the global LDAP bind timeout for all LDAP serv-
ers.
timeout-search Sets the global LDAP search timeout for all LDAP
servers.
Default 5 seconds
History 3.1.0000
Role admin
Notes
ldap version
ldap version <version>
no ldap version
Default 3
History 3.1.0000
Role admin
Notes
show ldap
show ldap
Default N/A
History 3.1.0000
Role admin
Notes
Default N/A
History 3.6.8008
Role admin
Notes
Default Disabled
History 3.5.0200
Role admin
Notes Before enabling secure mode, the command performs the following configuration
checks:
• NTP Key ID cannot be MD5 when secure mode is enabled
• SSH min-version cannot be 1 when enabling secure mode
• SSH security must be set to strict security
• SNMPv3 user auth cannot be md5 when enabling secure mode
• SNMPv3 user priv cannot be des when enabling secure mode
• SNMPv3 trap auth cannot be md5 when enabling secure mode
• SNMPv3 trap priv cannot be des when enabling secure mode
• Router BGP neighbor password cannot be set when enabling secure mode
• Router BGP peer-group password cannot be set when enabling with secure mode
• User password hash cannot be MD5 when secure mode is enabled
Only if the check passes, secure mode is enabled on the switch system.
Default N/A
History 3.4.2300
Role admin
***IMPORTANT NOTE***
Encryption and decryption perform “reset factory keep-config” on the switch system
once configured. This means that sysdumps, logs, and images are deleted.
The key may be saved locally as well by using the parameter “local” instead of “usb”
but that configuration is less secure.
Once encryption is enabled, reverting back to an older version while encrypted is not
possible. The command “no crypto encrypt-data” must be run before attempting to
downgrade to an older MLNX-OS version.
4.13.1.1 Commands
crypto encrypt-data
crypto encrypt-data key-location <local | usb> key <password>
no crypto encrypt-data
Default N/A
History 3.6.1002
Role admin
Related Commands
Notes • It is recommended to store the encryption password on a USB device rather than
locally
• Enabling encryption may slightly slow system performance
• If the key is stored on the USB, it must be plugged into the switch in order for the
switch to boot. After the switch has booted, the USB key is no longer required
and, for security purposes, it is recommended to remove it after running “usb
eject”. The USB key may be needed again if the switch is rebooted or if the switch
needs to be decrypted.
IPv4 or IPv6 address Clears security associations for the specified IKE peer-
ing (remote peer is affected)
Default N/A
History 3.2.3000
Role admin
Notes
Default N/A
History 3.2.3000
Role admin
Example switch (config)# crypto ipsec peer 10.10.10.10 local 10.7.34.139 enable
switch (config)#
Notes
Default N/A
History 3.2.3000
Role admin
Notes • Two certificates with the same subject and issuer fields cannot both be placed
onto the CA list
• The no form of the command does not delete the certificate from the certificate
database
• Unless specified otherwise, applications that use CA certificates will still consult
the well-known certificate bundle before looking at the default-ca-list
Designates the named certificate as the global default certificate role for authentica-
tion of this system to clients.
The no form of the command reverts the default-cert name to “system-self-signed”
(the “cert-name” value is optional and ignored).
Default N/A
History 3.2.3000
Role admin
Notes • A certificate must already be defined before it can be configured in the default-
cert role
• If the named default-cert is deleted from the database, the default-cert automati-
cally becomes reconfigured to the factory default, the “system-self-signed” certif-
icate
Syntax Description country-code Configures the default certificate value for country
code with a two-alphanumeric-character code or -- for
none.
Default N/A
History 3.2.1000
Role admin
Default N/A
History 3.2.3000
Role admin
Notes
Syntax Description days-valid Specifies the number of days the certificate is valid
Default N/A
History 3.2.1000
Role admin
Notes
Default N/A
History 3.2.1000
Role admin
Validity:
Starts: 2012/12/02 13:45:05
Expires: 2013/12/02 13:45:05
Subject:
Common Name: IBM-DEV-Bay4
Country: IS
State or Province:
Locality:
Organization:
Organizational Unit:
E-mail Address:
Issuer:
Common Name: IBM-DEV-Bay4
Country: IS
State or Province:
Locality:
Organization:
Organizational Unit:
E-mail Address:
switch (config)#
Notes
Default N/A
History 3.6.1002
Role admin
Notes
Default N/A
History 3.2.1000
Role admin
Notes
4.14.1 Commands
job
job <job ID>
no job <job ID>
Creates a job.
The no form of the command deletes the job.
Default N/A
History 3.1.0000
Role admin
command
command <sequence #> | <command>
no command <sequence #>
Syntax Description sequence # An integer that controls the order the command is exe-
cuted relative to other commands in this job. The com-
mands are executed in an ascending order.
Default N/A
History 3.1.0000
Role admin
comment
comment <comment>
no comment
Default “”
History 3.1.0000
Role admin
Notes
enable
enable
no enable
Default N/A
History 3.1.0000
Role admin
Notes If a job is disabled, it will not be executed automatically according to its schedule;
nor can it be executed manually.
execute
execute
Default N/A
History 3.1.0000
Role admin
Notes • The job timer (if set) is not canceled and the job state is not changed: i.e. the time
of the next automatic execution is not affected
• The job will not be run if not currently enabled
fail-continue
fail-continue
no fail-continue
Default A job will halt execution as soon as any of its commands fails
History 3.1.0000
Role admin
Notes
name
name <job name>
no name
Default “”.
History 3.1.0000
Role admin
Notes
schedule type
schedule type <recurrence type>
no schedule type
Sets the type of schedule the job will automatically execute on.
The no form of the command resets the schedule type to its default.
Default once
History 3.1.0000
Role admin
Notes A schedule type is essentially a structure for specifying one or more future dates and
times for a job to execute.
Sets the type of schedule the job will automatically execute on.
The no form of the command resets the schedule type to its default.
Default once
History 3.1.0000
Role admin
Notes A schedule type is essentially a structure for specifying one or more future dates and
times for a job to execute.
show jobs
show jobs [<job-id>]
Displays configuration and state (including results of last execution, if any exist) of
all jobs, or of one job if a job ID is specified.
Default N/A
History 3.1.0000
Role admin
switch (config) #
Notes
4.15.1 Commands
Default N/A
History 3.1.0000
Role admin
Notes
History 3.1.0000
Role admin
Notes
single Does not repeat events: only sends one event whenever
the alarm changes state.
Default single
History 3.1.0000
Role monitor/admin
Notes
falling Configures alarm for when the statistic falls too low.
rising Configures alarm for when the statistic rises too high.
History 3.1.0000
Role admin
History 3.1.0000
Role monitor/admin
Example switch (config) # stats alarm paging rate-limit window long 2000
switch (config) #
Notes
Default N/A
History 3.1.0000
Role admin
Notes
Default Enabled
History 3.1.0000
Role monitor/admin
Notes
History 3.1.0000
Role monitor/admin
Example switch (config) # stats chd memory_day compute time interval 120
switch (config) # show stats chd memory_day
CHD "memory_day" (Average physical memory usage: bytes):
Source dataset: sample "memory"
Computation basis: time
Interval: 120 second(s)
Range: 1800 second(s)
switch (config) #
Notes
Default N/A
History 3.1.0000
Role admin
Notes
Default Enabled
History 3.1.0000
Role admin
Notes
Sets the amount of time between samples for the specified group of sample data.
History 3.1.0000
Role admin
Notes
stats clear-all
stats clear all
Clears data for all samples, CHDs, and status for all alarms.
Default N/A
History 3.1.0000
Role admin
Notes
stats export
stats export <format> <report name> [{after | before} <yyyy/mm/dd>
<hh:mm:ss>] [filename <filename>]
Syntax Description format Currently the only supported value for <format> is
“csv” (comma-separated value).
Default N/A
History 3.1.0000
Role admin
Notes
Default N/A
History 3.1.0000
Role admin
Notes
Default N/A
History 3.1.0000
Role admin
Notes
Default N/A
History 3.1.0000
Role admin
CPU 0
Utilization: 6%
Peak Utilization Last Hour: 16% at 2012/02/28 08:47:32
Avg. Utilization Last Hour: 8%
switch (config) #
Notes
Default N/A
History 3.1.0000
Role admin
Notes
<fan_name> A chassis fan speed is Email, fan LED and Check the fan “<fan_name> has
speed is below below minimal threshold: system status LED set and replace it if been restored to
minimal range 15% of maximum speed red, log alert, SNMP. required its normal state”
Fan <fan_num- A spine fan speed is below Email, fan LED and Check the fan “Fan speed
ber> speed in minimal threshold: system status LED set and replace it if <fan_number> in
spine number 30% of maximum speed red, log alert, SNMP required spine number
<spine_num- <spine_number>
ber> is below has been restored
minimal range to its normal
state”
<fan_name> is A chassis fan is not respon- Email, fan LED and Check fan con- “<fan_name> has
unresponsive sive on MLNX-OS sys- system status LED set nectivity and been restored to
tems red, log alert, SNMP replace it if its normal state”
required
Fan <fan_num- A spine fan is not respon- Email, fan LED and Check fan con- “Fan <fan_num-
ber> in spine sive on MLNX-OS sys- system status LED set nectivity and ber> in spine
number tems red, log alert, SNMP replace it if number
<spine_num- required <spine_number>
ber> is unre- has been restored
sponsive to its normal
state”
<fan_name> is A chassis fan is missing Email, fan LED and Insert a fan unit “<fan_name> has
not present system status LED set been restored to
red, log alert, SNMP its normal state”
Fan <fan_num- A spine fan is missing Email, fan LED and Insert a fan unit “Fan <fan_num-
ber> in spine system status LED set ber> in spine
number red, log alert, SNMP number
<spine_num- <spine_number>
ber> is not pres- has been restored
ent. to its normal
state”
Insufficient Insufficient number of Email, fan LED and Plug in addi- “The system cur-
number of work- working fans in the system system status LED set tional fans or rently has suffi-
ing fans in the red, log alert, SNMP change faulty cient number of
system fans working fans”
Power Supply The power supply voltage Email, power supply Check the “Power Supply
<ps_number> is out of range. LED and system sta- power connec- <ps_number>
voltage is out of tus LED set red, log tion of the PS voltage is in
range alert, SNMP range”
Power supply A power supply unit tem- Email, power supply Check chassis “Power supply
<ps_number> perature is higher than the LED and system sta- fans connec- <ps_number>
temperature is maximum threshold of 70 tus LED set red, log tions. On temperature is
too hot Celsius on MLNX-OS sys- alert, SNMP MLNX-OS sys- back to normal”
tems tems, check
system fan con-
nections.
Power Supply A power supply is mal- Email, system status Connect power “Power supply
<number> is functioning or discon- LED set red, log alert, cable or replace has been
unresponsive nected SNMP malfunctioning removed” or “PS
PS has been restored
to its normal
state”
Unit/leaf/spine A leaf/spine is not respon- Email, system status Check leaf/ “Leaf/spine num-
<leaf/spine num- sive LED set red, log alert, spine connec- ber <leaf/spine
ber> is unre- SNMP tivity and number> has
sponsive replace it if been restored to
required its normal state”
Unit/leaf/spine One of the voltages in a Email, system status Check leaf con- “Unit voltage is
voltage is out of MLNX-OS unit is below LED set red, log alert, nectivity in range”
range minimal threshold or SNMP
higher than the maximum
threshold - both thresholds
are 15% of the expected
voltage
ASIC tempera- A ASIC unit temperature is Email, system status Check the fans “ASIC tempera-
ture is too hot higher than the maximum LED set red, log alert, system ture is back to
threshold of 105 Celsius on SNMP normal”
MLNX-OS systems.
nents, MLNX-OS enables and/or disables switch components according to the available
power budget.
MLNX-OS may send power alarms (via SNMP or email) as follow:
• If the available budget is insufficient for all the system components an insufficient-
Power event is generated. In this mode several switch components may be disabled.
• If the total power of the system is insufficient for redundancy, a lowPower event is gen-
erated.
• If a connected power supply provides below 1.6K Watts or grid-redundancy mode is
configured and a power supply is connected to a 110V grid, then a powerRedundancy-
Mismatch event is generated, where grid redundancy can not be achieved in such config-
uration.
In case of an insufficient-power mode, the order in which the FRUs are turned ON is first spines
(1,2,3...max) and then the leafs (1,2,3...max), while the order of the FRUs in case of turning them
OFF is first the spines (max...3) and then the leafs (max...1). The management modules are not
affected.
For the trap OID, please refer to the Mellanox-MIB file.
Power cycle is needed after changing power redundancy mode on a director switch
system.
When “show interfaces” is used, a port’s speed appears unchanged even when only one
lane is active.
the port for a certain time period – after which the port should be configured to one of the
other two modes, to allow higher throughput to pass through the port.
Examples:
To fetch an image from a USB device, run the command:
switch (config) # “image fetch scp://admin:[email protected]/var/mnt/usb1/image.img
To save log file ‘my-logfile’ to a USB device under the name test_logfile using the log-
ging files command, run (in Enable or Config mode):
switch (config) # logging files upload my-logfile scp://username:password@hostname/var/
mnt/usb1/test_logfile
To safely remove the USB and to flush the cache, after writing (log files, for example) to a
USB, use the usb eject command (in Enable or Config mode).
switch (config) # usb eject
• Master – the node that manages chassis configurations and services the chassis IP
addresses
• Slave – the node that replaces the Master node and takes over its responsibilities once the
Master node is down.
The master node is the only node that has access to chassis components such as tem-
perature, inventory and firmware.
The CPU role of the current management node can be recognized by the following methods:
• Run the show chassis ha command.
switch (config) # show chassis ha
2-node HA state:
Box management IP: 172.30.1.200/16
interface: mgmt0
switch (config) #
• Check the LEDs in the management modules as displayed in the figure below.
• Go to the WebUI => System => Modules page and see the information on the LEDs.
To verify if a CPU has been shut down, either run the following command:
switch [default: master] (config) # show chassis ha
2-node HA state:
Box management IP: 172.30.1.200/16
interface: mgmt0
powered off, the user should replace the malfunctioned CPU module. To power on the CPU and
the attached spine, plug the module in, log into the Master CPU and run the “chassis ha power
enable other” command.
Although the LEDs are functional during the takeover, wait for approximately 3 min-
utes before making any other hardware change.
Master example:
switch [default: master] (config) # show chassis ha
2-node HA state:
Box management IP: 172.30.1.200/16
interface: mgmt0
Not following these instructions may result in some errors in the log. These errors may
be safely ignored.
4.16.8 Commands
clear counters
clear counters [all | interface <type> <number>] [ethernet | port-channel]
Default N/A
History 3.2.3000
Role admin
Related Commands
health
health {max-report-len <length> | re-notif-cntr <counter> | report-clear}
Syntax Description max-report-len <length> Sets the length of the health report - number of line
entries. Range: 10-2048.
Default max-report-len: 50
re-notif-cntr:
History 3.1.0000
Role admin
Notes
led uid
led <module> uid <on | off>
Syntax Description module Specifies the module whose UID LED to configure
Default N/A
History 3.6.1002
Role admin
power enable
power enable <module name>
no power enable <module name>
History 3.1.0000
Role admin
power-management width
power-management width {auto | force}
no power-management width
Default Disabled
History 3.3.4000
Role admin
Notes
power redundancy-mode
power redundancy-mode [combined | grid-redundant | ps-redundant]
Default N/A
Role admin
Notes • The difference between the modes sets the threshold for power supply redundancy
failure. It does not change any power supply configuration.
• This command is not applicable for 1U or blade systems.
system profile
system profile {ib-single-switch | ib-no-adaptive-routing-single-switch | ib [split-
ready] [num-of-swids <swid-num>] [no-adaptive-routing] [ib-router] [adaptive-
routing-groups <value>]} [force]
History 3.1.0000
Role admin
Notes • This command requires a license. Refer to “Licenses” section in the MLNX-OS
SwitchX User Manual
• This command requires approval because reboot is performed and all configura-
tion is removed
• This command deletes all switch configuration (keeping IP connectivity) and
resets the system
• System profile “ib-no-adaptive-routing-single-switch profile” is the default pro-
file for InfiniBand switches
• The parameter “adaptive-routing-groups” is only available when “adaptive-rout-
ing” is configured
• Refer to the ‘port type’ command in order to change the link protocol
• System profile “ib split-ready” must run together with num-of-swids <count>
• IB router and adaptive routing are enabled only if specified but cannot be enabled
at the same time
• IB router only works when adaptive routing is disabled.
usb eject
usb eject
Default N/A
History 3.1.0000
Role admin
show asic-version
show asic-version
Default N/A
History 3.1.0000
Role admin
Notes
show bios
show bios
Default N/A
History 3.3.4150
Role admin
Related Commands
Notes
show cpld
show cpld
Default N/A
History 3.1.0000
Role admin
Notes
show fan
show fan
Default N/A
History 3.1.0000
Role admin
Notes
show health-report
show health-report
Default N/A
History 3.1.0000
Role admin
Notes
show inventory
show inventory
Default N/A
History 3.1.0000
Role admin
Notes
show leds
show leds [<module>]
Syntax Description module Specifies the module whose LED status to display
Default N/A
History 3.6.1002
Role admin
Notes
show memory
show memory
Default N/A
History 3.1.0000
Role admin
-----------------------------------------------------------------------
Memory Space Total Used Free Used+B/C Free-B/C
-----------------------------------------------------------------------
Physical 15848 MB 2849 MB 12999 MB 3854 MB 11994 MB
Swap 0 MB 0 MB 0 MB
Notes
show module
show module
Default N/A
History 3.1.0000
Role admin
Notes The Status column may have one of the following values: error, fatal, not-present,
powered-off, powered-on, ready.
show power
show power
Default N/A
History 3.1.0000
Role admin
Notes
Default N/A
History 3.1.0000
Role admin
Notes
show protocols
show protocols
Default N/A
History 3.2.3000
Role admin
Infiniband enabled
sm enabled
router disabled
Notes
show resources
show resources
Default N/A
History 3.1.0000
Role admin
Number of CPUs: 1
CPU load averages: 0.11 / 0.23 / 0.23
CPU 1
Utilization: 5%
Peak Utilization Last Hour: 19% at 2012/02/15 13:26:19
Avg. Utilization Last Hour: 7%
switch (config) #
Notes
Default N/A
History 3.1.0000
Role admin
Notes
Default N/A
History 3.2.0000
Role admin
Profile : ib
Number of SWIDs : 1
Adaptive Routing : yes
Adaptive Routing Groups : 2048
IB Routing : no
Notes
Default N/A
History 3.6.6000
Role admin
Profile: eth-default
-----------------------------------------------
Parameter Guaranteed Max Value
-----------------------------------------------
FDB size 102400
IPMC-L2 lists 10240
IPMC-L3 lists 10240
IPv4 MC/IGMP routes 10240
IPv4 neighbors 51200
IPv6 neighbors 8192
IPv4 routes 100000
IPv6 shorts 51200
IPv6 routes 21504
VRF 64
RIF 999
Related Commands
Notes
Default N/A
History 3.5.1000
Role admin
Related Commands
Notes
show temperature
show temperature
Default N/A
History 3.1.0000
Role admin
Notes
show version
show version
Default N/A
History 3.1.0000
Role admin
Notes
Displays concise version information for the currently running system image.
Default N/A
History 3.1.0000
Role admin
Notes
show voltage
show voltage
Default N/A
History 3.1.0000
Role admin
Notes
chassis ha bip
chassis ha bip <board IP address>
Default 0.0.0.0
History 3.1.0000
Role admin
chassis ha
chassis ha reset other
Default N/A
History 3.1.0000
Role admin
History 3.1.0000
Role admin
show chassis ha
show chassis ha
Default N/A
History 3.1.0000
Role admin
show chassis ha
show chassis ha
Default N/A
History 3.1.0000
Role admin
4.17.1 SNMP
Simple Network Management Protocol (SNMP), is a network protocol for the management of a
network and the monitoring of network devices and their functions. SNMP supports asynchro-
nous event (trap) notifications and queries.
MLNX-OS supports:
• SNMP versions v1, v2c and v3
• SNMP trap notifications
• Standard MIBs
• Mellanox private MIBs
INET-ADDRESS-MIB RFC-4001
SNMPV2-CONF
SNMPV2-TC RFC 2579
SNMPV2-TM RFC 3417
SNMP-USM-AES-MIB RFC 3826
IANA-LANGUAGE-MIB RFC 2591
IANA-RTPROTO-MIB RFC 2932
IANAifType-MIB
IANA-ADDRESS-FAMILY-NUMBERS-
MIB
Mellanox private MIBs can be downloaded from the Mellanox Support webpage.
lowPowerRecover N/A
insufficientFans Check Fans and environmental conditions.
insufficientFansRecover N/A
insufficientPower Add/connect power supplies, or change power mode using the com-
mand “power redundancy mode”.
insufficientPowerRecover N/A
For event-to-MIB mapping, please refer to Table 25, “Supported Event Notifications
and MIB Mapping,” on page 298.
mellanoxPowerCyclePlannedReload N/A
Switch systems shipped with OS versions older than 3.6.6102 have all had the exact same
SNMPv3 engine ID. Going forward, however, all switch systems will ship with a system-specific
engine ID.
Upgrading the OS version to 3.6.6102 or higher does not automatically change the current engine
ID. That can be done through one of the following methods after performing the software
upgrade:
• Changing a switch system’s profile
• Running “reset factory”
• Using the command “snmp-server engineID reset” (for more details, please see the pro-
cedure below)
To reset SNMP engine ID using “snmp-server engineID reset”:
Prerequisites:
Step 1. If any of the following SNMP configurations exist, please delete/disable them and re-
enable/reconfigure them only after SNMP engine ID reset is performed:
1. Make sure SNMP is disabled. Run:
switch (config) # no snmp-server enable
2. Make sure no SNMP trap host is configured. Run:
switch (config) # no snmp-server host <ip-address>
3. Make sure no SNMP users are configured. Run:
switch (config) # no snmp-server user <username> v3
Procedure:
Step 1. Check existing engine ID:
switch (config) # show snmp engineID
Local SNMP engineID: <current_key>
Step 2. Reset existing engine ID:
switch (config) # snmp-server engineID reset
Step 3. Verify new engine ID:
switch (config) # show snmp engineID
Local SNMP engineID: <new_key>
Notification sinks:
10.134.47.3
Enabled: yes
Port: 162 (default)
Notification type: SNMP v3 trap
Username: my-username
Authentication type: sha
Privacy type: aes-128
Authentication password: (set)
Privacy password: (set)
Step 4. Configure the desired event to be sent via SNMP. Run:
switch (config) # snmp-server notify event interface-up
Step 5. Verify the list of traps and informs being sent to out of the system. Run:
switch (config) # show snmp events
Events for which traps will be sent:
asic-chip-down: ASIC (Chip) Down
cpu-util-high: CPU utilization has risen too high
disk-space-low: Filesystem free space has fallen too low
health-module-status: Health module Status
insufficient-fans: Insufficient amount of fans in system
insufficient-fans-recover: Insufficient amount of fans in system recovered
insufficient-power: Insufficient power supply
interface-down: An interface's link state has changed to down
interface-up: An interface's link state has changed to up
internal-bus-error: Internal bus (I2C) Error
liveness-failure: A process in the system was detected as hung
low-power: Low power supply
low-power-recover: Low power supply Recover
new_root: local bridge became a root bridge
paging-high: Paging activity has risen too high
power-redundancy-mismatch: Power redundancy mismatch
process-crash: A process in the system has crashed
process-exit: A process in the system unexpectedly exited
snmp-authtrap: An SNMP v3 request has failed authentication
topology_change: local bridge triggered a topology change
unexpected-shutdown: Unexpected system shutdown
To print event notifications to the terminal (SSH or CONSOLE) refer to Section 4.6.1,
“Monitor,” on page 264.
Read-only communities:
public
Read-write communities:
my-community-name
Listen Interfaces:
Interface: mgmt0
It is possible to use other configuration options not specified in the example above.
Please refer to the command “snmp-server user” on page 532 for more information.
Step 2. Make sure the username is enabled for SET access and has admin capability level. Run:
switch (config) # show snmp user
User name: myuser
Enabled overall: yes
Authentication type: sha
Privacy type: aes-128
Authentication password: (set)
Privacy password: (set)
Require privacy: yes
SET access:
Enabled: yes
Capability level: admin
MLNX-OS supports the OIDs for SET operation listed in Table 35 which are expanded upon in
the following subsections.
Table 35 - Supported SET OIDs
MIB Name OID Name OID
MLNX-OS allows the user to use test the notification mechanism via SNMP SET. Sending a SET
request with the designated OID triggers a test trap.
Prerequisites:
1. Enable SET operations by following the instructions in Section 4.17.1.8.1, “Enabling SNMP
SET,” on page 496.
2. Configure host to which to send SNMP notifications.
3. Set a trap receiver in the MIB browser.
To send a test trap:
Step 1. Send a SET request to the switch IP with the OID 1.3.6.1.4.1.33049.2.1.1.1.6.0.
Step 2. Make sure the test trap is received by the aforementioned trap receiver (OID:
1.3.6.1.4.1.33049.2.1.2.13).
Mellanox supports setting system hostname using an SNMP SET request as described in
SNMPv2-MIB (sysName, OID: 1.3.6.1.2.1.1.5.0).
The restrictions on setting a hostname via CLI also apply to setting a hostname through SNMP.
Refer to the command “hostname” on page 149 for more information.
Mellanox supports power cycling its systems using an SNMP SET request as described in MEL-
LANOX-POWER-CYCLE MIB.
Power cycle command is issued via the OID mellanoxPowerCycleCmdExecute. The following
options are available:
• Reload – saves any unsaved configuration and reloads the switch
• Reload discard – reboots the system and discards of any unsaved changes
• Reload force – forces an expedited reload on the system even if it is busy without saving
unsaved configuration (equals the CLI command reload force)
• Reload slave – reloads the slave management on dual management systems (must be
executed from the master management module)
On dual management systems it is advised to connect via the BIP to make sure com-
mands are executed from the master management.
Mellanox supports making configuration changes on its systems using SNMP SET requests.
Configuration requests are performed by setting several values (arguments) and then executing a
command by setting the value for the relevant operation.
It is possible to set the parameters and execute the commands on the same SNMP request or sep-
arate them to several SET operations. Upon executing a command, the values of its arguments
remain and can be read using GET commands.
Once a command is executed there may be two types of errors:
• Immediate: This error results in a failure of the SNMP request. This means a critical
error in the SNMP request has occurred or that a previous SET request is being executed
• Delayed: The SET request has been accepted by the switch but an error occurred during
its execution.
For example, when performing a fetch (download) operation, an immediate error can occur when
the given URL is invalid. A delayed error can occur if the download process fails due to network
connectivity issues.
The following parameters are arguments are supported:
• Command URI – URI to fetch the configuration file from or upload the file to (for sup-
ported URI format please refer to the CLI command “configuration fetch” for more
details)
• Config file name – filename to save the configuration file to or to upload to remote loca-
tion
The following commands are supported:
• BinarySwitchTo – replaces the configuration file with a new binary configuration file.
This option fetches the configuration file from the URI provided in the mellanoxConfigD-
BCmdUri and switches to that configuration file. This command should be preceded by a reload
command in order for the new configuration to apply.
• TextApply – fetches a configuration file in human-readable format and applies its con-
figuration upon the current configuration.
• BinaryUpload – uploads a binary format configuration file of the current running config-
uration or an existing configuration file on the switch to the URI in the mellanoxConfigD-
BCmdUri command. The filename parameter indicates what configuration file on the switch to
upload.
• TextUpload – uploads a human-readable configuration file of the current running config-
uration of an existing configuration file on the switch to the URI in the mellanoxConfigD-
BCmdUri command. The filename parameter indicates what configuration file on the
switch to upload (same as the CLI command configuration text generate file
<filename> upload).
• ConfigWrite – saves active configuration to a filename on the switch as given in the file-
name parameter. In case filename is “active”, active configuration is saved to the current
saved configuration (same as the CLI command configuration write).
• BinaryDelete – deletes a binary based configuration file
• TextDelete – deletes a text based configuration file
Mellanox supports upgrading MLNX-OS software using an SNMP SET request as described in
MELLANOX-SW-UPDATE MIB.
The software upgrade command is issued via the OID mellanoxSWUpdateCmdExecute. The fol-
lowing options are available:
• Update – fetches the image from a specified URI (equivalent to the command “image
fetch” followed by “image install”)
The image to update from is defined by the OID mellanoxSWUpdateCmdUri. The restrictions
on the URI are identical to what is supported in the CLI command “image fetch” on page 222.
• Set-Next – changes the image for the next boot equivalent to the CLI command “image
boot”)
The partition from which to boot is defined by the OID mellanoxSWUpdateCmdSetNext. The
parameters for this OID are as follows:
• 0 – no change
• 1 – partition 1
• 2 – partition 2
• 3 – next partition (default)
Using the OIDs mellanoxSWUpdateCmdStatus and mellanoxSWUpdateCmdStatusString you
may view the status of the latest operation performed from the aforementioned in either integer
values, or human-readable forms, respectively. The integer values presented may be as follows:
• 0 – no operation
• 1-100 – progress in percentage
• 101 – success
• 200 – failure
4.17.2.1 Authentication
The JSON API protocol runs over HTTP/HTTPS and uses the existing web authentication mech-
anism.
In order to access the system via HTTP/HTTPS, an HTTP/HTTPS client is needed to send POST
requests to the system.
HTTPS access to the web-based management console needs to be enabled using the com-
mand “web https enable” to allow POST requests.
The HTTPS client must first be authenticated by sending a POST request to the following URL:
https://<switch-ip-address>/admin/launch?script=rh&template=login&action=login
The POST request content should contain the following data:
"f_user_id=<user name>&f_password=<user password>"
After a successful login, a session id (cookie) is returned to be used for other HTTPS requests in
the system.
See Section 4.17.2.6, “JSON Examples,” on page 506 for examples.
JSON execution requests are HTTPS POST requests that contain CLI commands to be executed
in the system.
Execution request can contain a single command or multiple commands to be executed.
Single command execution request format:
{
"cmd": "<CLI command to execute>"
}
Example:
{
"cmd": "show 1/1"
}
Multiple command execution request format:
{
"commands":["<CLI cmd 1>", "<CLI cmd 2>", … , <CLI cmd n>]
}
Example:
{
"commands":
[
"show 1/1",
"show 1/2"
]
}
In case of a multiple command request, the execution of the commands is done in the order they
appear in the execution list. Note that the execution of a multiple command request will be
stopped upon first failure. That is, in case the execution of one of the commands fails, none of the
remaining commands will be executed.
See Section 4.17.2.6, “JSON Examples,” on page 506 for examples.
Execution Types
Execution requests can be either synchronous (default) or asynchronous.
Synchronous requests will wait for a JSON response from the system. The synchronous request
has a defined wait time after which the user will receive a timeout response. The timeout for a
synchronous request is configurable by the user and is 30 seconds by default (see the CLI com-
mand “json-gw synchronous-request-timeout” on page 543).
Asynchronous requests will return immediately after sending the request with a reply containing
a “job_id” key. The user can use the given job ID to later query for request status and execution
results. Queries for asynchronous request results are guaranteed to be accessible up to 60 seconds
after the request has been completed.
To specify the execution type, the user needs to add the following key to the JSON execution
request:
"execution_type":"<async|sync>"
Example:
{
"execution_type":"async",
"cmd": "show 1/1"
}
See Section 4.17.2.6, “JSON Examples,” on page 506 for examples.
JSON Query requests are HTTPS GET requests that contain a job ID parameter. Using a query
request, the user can get information on the current execution state of an ongoing request or the
execution results of a completed request. To send a query request, the user should add the follow-
ing parameters to the JSON URL:
job_id=<job number>
Example:
https://<switch-ip-address>/admin/launch?script=json&job_id=<job number>
See Section 4.17.2.6, “JSON Examples,” on page 506 for more examples.
Set commands normally do not return any data or output. If a set command does return an
output, it will be displayed in the “status_message” field.
The HTTPS POST response format structure is a JSON object consisting of 4 name-value pairs
as follows:
{
"executed_command": "<CLI command that was executed>",
"status" = "<OK|ERROR>",
"status_message" = "<information on the status received>",
"data" = {the information that was asked for in the request}
}
Example:
{
“executed_command”: “show 1/1
"status": "OK",
"status_message": "",
"data":
{
"speed": "40GbE",
"admin_state": "up"
}
}
See Section 4.17.2.6, “JSON Examples,” on page 506 for more examples.
The HTTPS response format structure is a JSON object consisting of a list of JSON results. Each
JSON structure in the list is structured the same as in the single command execution response
(see the previous section).
However, the status field can contain in this case an additional value, “ABORTED”, in case a
previous command failed. This status value indicates that the command has not been executed at
all in the system.
{
"results": [
{
"executed_command": "<…>",
"status": "<OK|ERROR|ABORTED>",
"status_message": "<…>",
"data": {…}
},
{
"executed_command": "<…>",
"status": "<OK|ERROR|ABORTED>",
"status_message": "<…>",
"data": {…}
},
…
{
"executed_command": "<…>",
"status": "<OK|ERROR|ABORTED>",
"status_message": "<…>",
"data": {…}
}
]
}
Example:
{
"results": [
{
"executed_command": "show 1/1",
"status": "OK",
"status_message": ""
"data": {"speed":"40GbE", "admin_state":"up"}
},
{
"executed_command": "show 1/100",
"status": "ERROR",
"status_message": "wrong interface name",
"data": ""
},
{
"executed_command": "show 1/2",
"status": "ABORTED",
"status_message": "",
"data": ""
}
]
}
See Section 4.17.2.6, “JSON Examples,” on page 506 for more examples.
Response to a query request can be of two types. In case the request completes its execution, the
response will be similar to the single/multiple command response format, depending on the for-
mat of the request, and will display the execution results.
In case the execution is not complete yet, the response format will be similar to the single com-
mand response format. However, the status field will contain in this case the value “PENDING”
to indicate that the request is still in progress. In addition, the “executed_command” field will
contain the current request command being handled by the system.
Example:
{
"executed_command": "show 1/1",
"status": "PENDING",
"status_message": "",
"data":""
}
See Section 4.17.2.6, “JSON Examples,” on page 506 for examples.
Response to an asynchronous request is similar to the HTTPS response format of the single com-
mand response. However, an additional unique field will be added, “job_id”, containing the job
id number for querying the request later. The value of the job_id key is of type string.
4.17.2.5.1Set Commands
Interactive commands are commands which require user interaction to complete (e.g., type
“yes” to confirm). These commands are not supported by the JSON API.
4.17.2.5.2Show Commands
Not all CLI show commands are currently supported by the JSON API. Unsupported commands
return an error indication.
Support for all show commands will be completed in future MLNX-OS releases.
For a list “show” commands not currently supported, please refer to Appendix B,“Show Com-
mands Not Supported by JSON,” on page 1943.
4.17.2.6.1Authentication Example
Before sending JSON HTTPS request, the user must first authenticate. Run the following from
your server’s shell to create a login session ID in the file: /tmp/cookie.
curl -c /tmp/cookie -d "f_user_id=admin&f_password=admin"
"https://10.10.10.10/admin/launch?script=rh&template=login&action=login"
Upon a successful login, you will receive a reply similar to the following:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a href="https://10.10.10.10/admin/launch?script=rh&tem-
plate=home">here</a>.</p>
<hr>
<address>Apache Server at 10.10.10.10 Port 80</address>
</body></html>
The session id can now be used in all other JSON HTTPS requests to the system.
Single Command
This example sends a request to query the system profile.
Request (save it to a file named req.json):
{"cmd": "show system profile"}
Send the request:
curl -b /tmp/cookie -X POST -d @req.json "https://10.10.10.10/admin/launch?script=json"
Response:
When the system finishes processing the request, the user will receive a response similar to the
following:
{
"status": "OK",
"executed_command": "show system profile",
"status_message": "",
"data": {
"Profile": "ib",
"Adaptive Routing": "yes",
"Number of SWIDs": "1"
}
}
Multiple Commands
This example sends a request to change an interface description and then queries for its status.
Request (save it to a file named req.json):
{"commands": ["interface ib 1/1 description test description",
"show interfaces ib 1/1 status"]}
Send the request:
curl -b /tmp/cookie -X POST -d @req.json "https://10.10.10.10/admin/launch?script=json"
Response:
When the system finishes processing the request, the user will receive a response similar to the
following:
{
"results": [
{
"status": "OK",
"executed_command": "interface ib 1/1 description test description",
"status_message": "",
"data": ""
},
{
"status": "OK",
"executed_command": "show interfaces ib 1/1 status",
"status_message": "",
"data": {
"IB1/1": [
{
"Description": "test description",
"Speed": "fdr",
"Logical port state": "Initialize",
"Physical port state": "LinkUp",
"Current line rate": "56.0 Gbps",
"IB Subnet": "infiniband-default"
}
]
}
}
]
}
This example sends an asynchronous request to change an interface description and then queries
for its status.
Request (save it to a file named req.json):
{"execution_type":"async",
"commands": ["interface ib 1/1 description test description",
"show interfaces ib 1/1 status"]}
Send the request:
curl -b /tmp/cookie -X POST -d @req.json "https://10.10.10.10/admin/launch?script=json"
Response:
The system immediately returns a response similar to the following:
{
"executed_command": "",
"status": "OK",
"status_message": "",
"data": "",
"job_id": "91329386"
}
This example sends a request to query for a job ID received from a previous execution request.
Request:
The request is a an HTTPS GET operation to the JSON URL with the “job_id” parameter.
Send the request:
curl -b /tmp/cookie -X GET "https://10.10.10.10/admin/
launch?script=json&job_id=91329386"
Response:
If the system is still processing the request, the user receives a response similar to the following:
{
"executed_command": " interface ib 1/1 description test description ",
"status": "PENDING",
"status_message": "",
"data": ""
}
If the system is done processing the request, the user receives a response similar to the following:
{
"results": [
{
"status": "OK",
"executed_command": "interface ib 1/1 description test description",
"status_message": "",
"data": ""
},
{
"status": "OK",
"executed_command": "show interfaces ib 1/1 status",
"status_message": "",
"data": {
"IB1/1": [
{
"Description": "test description",
"Speed": "fdr",
"Logical port state": "Initialize",
"Physical port state": "LinkUp",
"Current line rate": "56.0 Gbps",
"IB Subnet": "infiniband-default"
}
]
}
}
]
}
General Error
This example sends a request with an illegal JSON structure.
Request - without closing bracket “]” (save it to a file named req.json):
{"commands": ["interface ib 1/1 description test description",
"show interfaces ib 1/1 status"}
Send the request:
curl -b /tmp/cookie -X POST -d @req.json "https://10.10.10.10/admin/launch?script=json"
Error response:
{
"status": "ERROR",
"executed_command": "",
"status_message": "Handle request failed. Reason:\nIllegal JSON structure found in
given JSON data.\nExpecting , delimiter: line 1 column 95 (char 94)",
"data": ""
}
This section is displayed only if JSON API is enabled using the command “json-gw enable”.
4.17.4 Commands
snmp-server auto-refresh
snmp-server auto-refresh {enable | interval <time>}
no snmp-server auto-refresh enable
Default Enabled.
Interval: 60 secs
History 3.2.3000
Role admin
Notes • When configuring an interval lower than 60 seconds, the following warning mes-
sage appears asking for confirmation: “Warning: this configuration may increase
CPU utilization, Type 'YES' to confirm: YES”.
• When disabling SNMP auto-refresh, information is retrieved no more than once
every 60 seconds just like SNMP tables that do not have an auto-refresh mecha-
nism.
Syntax Description If snmp cache is disabled, every snmp request will get updated data.
Default Enabled
History 3.7.00xx
Role admin
snmp-server community
snmp-server community <community> [ ro | rw]
no snmp-server community <community>
History 3.1.0000
Role admin
Notes • If neither the “ro” or the “rw” parameters are specified, the read-only community
is set as the default community
• If the read-only community is specified, only queries can be performed
• If the read-write community is specified, both queries and sets can be performed
snmp-server contact
snmp-server contact <contact name>
no snmp-server contact
Default “”
History 3.1.0000
Role admin
Notes
snmp-server enable
snmp-server enable
no snmp-server enable
History 3.1.0000
Role admin
Notes
snmp-server enable
snmp-server enable
no snmp-server enable
History 3.1.0000
Role admin
Notes
History 3.6.6102
Role admin
Notes Changing system profile or performing “reset factory...” causes the engine ID to
change to the new node-unique one.
History N/A
Role admin
Notes
History N/A
Role admin
Notes SNMP traps are only sent if there are trap sinks configured with the “snmp-server
host...” command, and if these trap sinks are themselves enabled.
Default SNMP MIBs are all given permission for SET requests by default
History 3.6.3004
Role admin
Notes
Default N/A
History 3.1.0000
Role admin
Notes
Send SNMP v2c informs to this host with the default trap community.
The no form of the commands removes a host from which SNMP traps should be
sent.
hash-type • MD5
• SHA
History 3.2.1050
Role admin
Notes
Send SNMP v2c traps to this host with the default trap community.
The no form of the commands removes a host from which SNMP traps should be
sent.
hash-type • MD5
• SHA
History 3.1.0000
Role admin
Example switch (config) # snmp-server host 1.1.1.1 informs version 3 user test
auth md5 password priv aes-128 password
Notes
snmp-server listen
snmp-server listen {enable | interface <ifName>}
no snmp-server listen {enable | interface <ifName>}
Default N/A
History 3.1.0000
Role admin
Notes If enabled, and if at least one of the interfaces listed is eligible to be a listen interface,
then SNMP requests will only be accepted on those interfaces. Otherwise, SNMP
requests are accepted on any interface.
snmp-server notify
snmp-server notify {community <community> | event <event name> | port
<port> | send-test}
no snmp-server notify {community | event <event name> | port}
Syntax Description community Sets the default community for traps sent to hosts
which do not have a custom community string set.
History 3.1.0000
Role admin
Notes • This setting is only meaningful if traps are enabled, though the list of hosts may
still be edited if traps are disabled
• Refer to Mellanox MIB file for the list of supported traps
snmp-server port
snmp-server port <port>
no snmp-server port
Default 161
History 3.1.0000
Role admin
Notes
snmp-server user
snmp-server user {admin | <username>} v3 {[encrypted] auth <hash-type>
<password> [priv <privacy-type> [<password>]] | capability <cap> | enable
<sets> | prompt auth <hash-type> [priv <privacy-type>] | require-privacy}
no snmp-server user {admin | <username> } v3 {[encrypted] auth <hash-type>
<password> [priv <privacy-type> [<password>]] | capability <cap> | enable
<sets> | prompt auth <hash-type> [priv <privacy-type>]}
History 3.1.0000
3.7.00xx
Role admin
Notes • The username chosen here may be anything that is valid as a local UNIX user-
name (alphanumeric, plus '-', '_', and '.'), but these usernames are unrelated to, and
independent of, local user accounts. That is, they need not have the same capabil-
ity level as a local user account of the same name. Note that these usernames
should not be longer than 31 characters, or they will not work.
• The hash algorithm specified is used both to create digests of the authentication
and privacy passwords for storage in configuration, and also in HMAC form for
the authentication protocol itself.
• There are three variants of the command, which branch out after the “v3” key-
word. If “auth” is used next, the passwords are specified in plaintext on the com-
mand line. If “encrypted” is used next, the passwords are specified encrypted
(hashed) on the command line. If “prompt-pass” is used, the passwords are not
specified on the command line the user is prompted for them when the command
is executing. If “priv” is not specified, only the auth password is prompted for. If
“priv” is specified, the privacy password is prompted for; entering an empty string
for this prompt will result in using the same password specified for authentication.
• AES privacy type encryption using the newest algorithm, which means we use
aes-blumenthal. For more information see - http://www.snmp.com/eso/esoCon-
sortiumMIB.txt
• No more than 30 SNMP V3 users are allowed in the database.
show snmp
show snmp [events | host]
Default N/A
History 3.1.0000
Role admin
SNMP enabled : no
SNMP port : 161
System contact : Test
System location: Boston
Read-only communities:
public
Read-write communities:
good
Listen Interfaces:
Interface: mgmt0
Notes
Default N/A
History 3.1.0000
Role admin
Auto-Refreshed tables:
ifTable
ifXTable
mellanoxIfVPITable
Notes
Default N/A
History 3.6.6102
Role admin
Notes
Default N/A
History 3.6.3004
Role admin
Notes
Default N/A
History 3.1.0000
Role admin
Notes
Default N/A
History 3.3.4318
Role admin
Notes
xml-gw enable
xml-gw enable
no xml-gw enable
History 3.1.0000
Role admin
Notes
show xml-gw
show xml-gw
Default N/A
History 3.1.0000
Role admin
Notes
json-gw enable
json-gw enable
no json-gw enable
History 3.6.3004
Role admin
Notes
json-gw synchronous-request-timeout
json-gw synchronous-request-timeout <time out value>
no json-gw synchronous-request-timeout
Default N/A
History 3.6.3004
Role admin
Notes
show json-gw
show json-gw
Default N/A
History 3.6.3004
Role admin
Notes
In case of an already installed module, please use the command “puppet module
upgrade <module_name>” or “puppet module install <module_name> -
-force” instead of “puppet module install <module_name>” to reinstall the
modules.
For more information please refer to the Network Automation Tools document or Puppet cate-
gory in the Mellanox community site at: http://community.mellanox.com/community/support/
solutions.
ensure Sets the given values or absent, present ensure => present
restores the interface to
default
speed Sets the speed of the inter- auto*|10m|100m|1g|10g|40 speed => 1g
face. g|56g
ensure Specifies if the image ver- present, absent ensure => present
sion given in as resource
ID is ensured to be
installed or not
is_next_boot Ensures that the installed yes, no is_next_boot => yes
image is the next boot par-
tition
configuration_write Writes configurations to yes, no configuration_write => yes
database.
force_reload Reload if image is in other yes, no force_reload => no
partition.
4.18.6 Troubleshooting
This section presents common issues that may prevent the switch from connecting to the puppet
server.
4.18.6.2 Outdated or Invalid SSL Certificates Either on the Switch or the Server
This can be fixed on the switch using the CLI command puppet-agent clear-certificates
(requires puppet-agent restart to take effect).
On the server it can be fixed by running puppet cert clean <switch_fqdn> (FQDN is the
Fully Qualified Domain Name which consists of a hostname and a domain suffix).
4.18.7 Commands
puppet-agent
puppet-agent
Default None
History 3.3.4200
Role admin
Related Commands
Notes
master-hostname
master-hostname <hostname>
no master-hostname
Syntax Description hostname Puppet server hostname. Free string may be entered.
Default puppet
History 3.3.4200
Role admin
Related Commands
Notes
enable
enable
no enable
Default Disabled
History 3.3.4200
Role admin
Related Commands
Notes
run-interval
run-interval <time>
Configures the time interval in which the puppet agent reports to the puppet server.
Default 30m
History 3.3.4302
Role admin
Notes
restart
puppet-agent restart
Default N/A
History 3.3.4200
Role admin
Related Commands
Notes
show puppet-agent
show puppet-agent
Default N/A
History 3.3.4200
Role admin
Related Commands
Notes
Default N/A
History 3.3.4200
Role admin
Related Commands
Notes
Control Plane Policing or Policies (CoPP) ensures the CPU and control plane are not over-uti-
lized which is essential for the robustness of the switch. CoPP limits the number of control plane
packets. MLNX-OS implements several CoPP mechanisms:
• ACLs may be used to limit the rate of packets or bytes of a certain type, including L3
control packets (L2 control packets are forwarded to the CPU before the ACL)
• Policers on traffic going to the CPU – these policers are configured by MLNX-OS and
cannot be modified by the user
• IP filter tables limit the traffic to the CPU coming in from the management ports.
IPv4 configuration:
Chain 'input' Policy 'accept':
Rule 1:
Target : rate-limit 2 pps
Protocol : udp
Source : all
Destination : all
Interface : all
State : any
Other Filter: -
Rule 2:
Target : drop
Protocol : icmp
Source : all
Destination : all
Interface : mgmt1 (ingress)
State : any
Other Filter: -
4.19.2 Commands
ip filter enable
ipv6 filter enable
{ip | ipv6} filter enable
no {ip | ipv6} filter enable
Enables IP filtering.
The no form of the command disables IP filtering.
Default Disabled
History 3.5.1000
Role admin
Notes It is recommended to run this command only after configuring all of the IP table filter
parameters.
Configures default policy for a specific chain (if no rule matches this default policy
action shall apply).
The no form of the command resets default policy for a specific chain.
Syntax Description chain_name Selects a chain for which to add or modify a filter:
• input – input chain or ingress interfaces
• output – output chain or egress interfaces
History 3.5.1000
Role admin
Notes
target • accept – allows the packets that match the rule into
the management plane
• drop – drops packets that match the rule
• rate-limit – allows with rate limiting in packets per
sec (PPS)
• reject-with – drops the packet and replies with an
ICMP error message
Default N/A
History 3.5.1000
Role admin
Example switch (config) # ipv6 filter enable chain input rule append tail target
drop state related protocol all dup-delete
switch (config) #
Notes • The source and destination ports may each be either a single number, or a range
specified as “<low>-<high>”. For example: “10-20” would specify ports 10
through 20 (inclusive).
• The port parameter only works in conjunction with TCP and UDP.
• Setting a “positive” rule removes any corresponding “not-” rules, and vice-versa
• The “state” parameter is a classification of the packet relative to existing connec-
tions
• If TCP or UDP are selected for the “protocol” parameter, source and/or destina-
tion ports may be specified. If ICMP is selected, these options are either ignored,
or an error is produced.
show ip filter
show ip filter
Default N/A
Role admin
Notes N/A
Default N/A
Role admin
Notes N/A
Default N/A
Role admin
IPv4 configuration:
Chain 'input' Policy 'accept':
Rule 1:
Target : accept
Protocol : all
Source : all
Destination : 1.1.1.0/24
Interface : all
State : any
Other Filter: -
Notes N/A
Default N/A
Role admin
Notes N/A
Default N/A
Role admin
Notes N/A
Default N/A
Role admin
IPv6 configuration:
Chain 'input' Policy 'accept':
Rule 1:
Target : accept
Protocol : all
Source : all
Destination : 1.1.1.0/24
Interface : all
State : any
Other Filter: -
Notes N/A
4.19.3
5 InfiniBand Switching
5.1 Node Name
5.1.1 Commands
ib nodename
ib nodename <guid> name <name>
no ib nodename <guid>
Default N/A
History 3.1.0000
Role admin
Related Commands
Notes If an entry with GUID exists, the existing name will be replaced with a new name.
show ib nodename
show ib nodename
Default N/A
History 3.1.0000
Role admin
Notes
5.2 Fabric
5.2.1 Commands
fabric zero-counters
fabric zero-counters
Default N/A
History 3.1.0000
Role monitor/admin
Related Commands
Notes
show fabric
show fabric {pm | sm}
Default N/A
History 3.1.0000
Role admin
SM - master
Port=0 lid=0x0005 guid=0x0002c903004a2980 dev=51000 priority:15
SM - standby
Port=0 lid=0x0001 guid=0x0000000000000111 dev=51000 priority:0
switch (config) #
Related Commands
show guids
show guids
Default N/A
History 3.1.0000
Role admin
Related Commands
Notes
Default N/A
History 3.1.0000
Role admin
Related Commands
Notes
show lids
show lids
Default N/A
History 3.1.0000
Role admin/monitor
Related Commands
Notes
5.3 IB Router
IB router provides the ability to send traffic between two or more IB subnets thereby potentially
expanding the size of the network to over 40k end-ports, enabling separation and fault resilience
between islands and IB subnets, and enabling connection to different topologies used by different
subnets.
The forwarding between the InfiniBand subnets is performed using GRH (global route header)
lookup.
IB router capabilities are supported only on SB7780 switch system which comes with the follow-
ing default configuration:
• L3 capabilities enabled
• 2 SWIDs, with interface 1/1 mapped to infiniband-default and interface 1/2 mapped to
infiniband-1
The IB router’s basic functionality includes:
• Removal of current L2 LRH (local routing header)
• Routing table lookup – using GID from GRH
• Building new LRH according to the destination and the routing table
The DLID in the new LRH is built using simplified GID-to-LID mapping (where LID = 16 LSB
bits of GID) thereby not requiring to send for ARP query/lookup.
LID[15:0]
For this to work, the SM allocates an alias GID for each host in the fabric where the alias GID =
{subnet prefix[127:64], reserved[63:16], LID[15:0]}. Hosts should use alias GIDs in order to
transmit traffic to peers on remote subnets.
1. IP address
resolution
Dest GID
Path Query
(Path, Router LID)
Mapping between L3
address to L2 address
For more information on IB router architecture and functionality, please refer to the fol-
lowing Mellanox Community page: https://community.mellanox.com/docs/DOC-2384.
IB router requires HCA configuration such as SM, partition key, MPI, GID translation,
and more. To learn more about these configurations, please refer to the following Mella-
nox Community page: https://community.mellanox.com/docs/DOC-2466.
For more advanced information on IB router configuration, please refer to the following
Mellanox Community page: https://community.mellanox.com/docs/DOC-2466.
5.3.3 Commands
ib router
ib router
no ib router
Default N/A
History 3.6.0500
Role admin
Notes
ib router shutdown
ib router shutdown
no ib router shutdown
Disables IB router.
The no form of the command enables IB router.
Default Disabled
History 3.6.0500
Role admin
Related Commands
interface ib-subnet
interface ib-subnet <swid-name>
no interface ib-subnet <swid-name>
Default N/A
History 3.6.0500
Role admin
Notes The maximum number of SWIDs depends on the number of SWIDs defined in the
profile
Default Disabled
History 3.6.0500
Role admin
Related Commands
Notes
show ib router
show ib router
Default N/A
History 3.6.0500
Role admin
switch (config) #
Related Commands
Notes
Default Disabled
History 3.6.0500
Role admin
Related Commands
Notes
5.4 Interface
switch (config) #
The break-out cable is a unique Mellanox capability, where a single physical quad-lane QSFP
port is divided into 2 dual-lane ports. It maximizes the flexibility of the end user to use the Mella-
nox switch with a combination of dual-lane and quad-lane interfaces according to the specific
requirements of its network. All system ports may be split into 2-lane ports. Splitting a port
changes the notation of that port from x/y to x/y/z with “x/y” indicating the previous notation of
the port prior to the split and “z” indicating the number of the resulting single-lane port (1,2).
Each sub-physical port is then handled as an individual port. For example, splitting port 5 into 2
lanes gives the following new ports: 1/5/1 & 1/5/2.
In order to use this feature, the system’s profile must be configured to “ib split-ready” as
described in Section 5.4.4.1, “Changing System Profile to Allow for Split-Ready Con-
figuration,” on page 594 using the command “system profile” on page 461.
5.4.5 Commands
interface ib
interface ib [internal] {<inf> | <inf-range>}
Default N/A
History 3.1.0000
Role admin
Notes Interface range (inf-range) option is not valid on director switch systems.
mtu
mtu <frame-size>
Configures the Maximum Transmission Unit (MTU) frame size for the interface.
History 3.1.0000
Role admin
Notes
shutdown
shutdown
no shutdown
History 3.1.0000
Role admin
Notes N/A
description
description <string>
Default “”
History 3.1.0000
Role admin
Notes
speed
speed <port speed> [force]
Default Depends on the port module type, not all interfaces support all speed options
History 3.1.0000
Role admin
Notes • This command is backwards compatible so old configuration file containing this
command with the old form (with legal bit mask) are still supported
• Configuring more than one speed is possible by typing in consecutive speed
names separated by spaces
• If the speed-options list does not include SDR speed, it is configured automati-
cally. However, if the force option is used (supported on FDR10 only), SDR is not
configured.
• If the other side of the link is a ConnectX®-3 device, to allow the link to raise in
FDR speed, QDR speed must also be allowed
op-vls
op-vls <value>
History 3.1.0000
Role admin
Notes
width
width <value>
no width
History 3.1.0000
Role admin
Notes
clear counters
clear counters
Default N/A
History 3.1.0000
Role admin
Notes
Syntax Description time Enables periodic notifications (traps and log) on inter-
nal link speed mismatch status. The time is in hours.
“0” disables the feature
Default Disabled
History 3.4.3000
Role admin
Default Disabled
History 3.3.4318
Role admin
Notes Link-state-change shows internal link entries in the ifTable and the ifXTable
Default Unmapped
History 3.6.0500
Role admin
Related Commands
show interfaces ib
show interfaces ib <inf>
Default N/A
History 3.1.0000
Role admin
RX bytes : 33258342076
RX packets : 16231513
RX errors : 0
Symbol errors : 0
VL15 dropped packets : 0
TX bytes : 34313606888
TX packets : 16046018
Related Commands
Notes
Default N/A
History 3.2.0500
Role admin
Ib 1/1
LLR: FDR10, FDR,
switch (config)
Related Commands
Notes
Displays the status, speed and negotiation mode of the specified interface.
Default N/A
History 3.2.0500
Role admin
Interface Description IB Subnet Speed Current line rate Logical port state Physical port state
--------- ----------- --------- --------- ----------------- ------------------ -------------------
IB1/1 infiniband-1 fdr 56.0 Gbps Active LinkUp
IB1/2 infiniband-2 fdr 56.0 Gbps Active LinkUp
IB1/3 infiniband-default - - Down Polling
IB1/4 infiniband-default - - Down Polling
IB1/5 infiniband-default - - Down Polling
IB1/6 infiniband-default - - Down Polling
IB1/7 infiniband-default - - Down Polling
IB1/8 infiniband-default - - Down Polling
IB1/9 infiniband-default - - Down Polling
IB1/10 infiniband-default - - Down Polling
IB1/11 infiniband-default - - Down Polling
....
switch (config) #
Related Commands
Notes
Default N/A
History 3.2.0500
Role admin
switch (config) #
Related Commands
Notes
Default N/A
History 3.2.0500
Role admin
IB1/1/26
LLR: FDR10, FDR,
switch (config) #
Related Commands
Notes
Default N/A
History 3.2.0500
Role admin
----------------------------------
Interface LLR status
----------------------------------
IB1/1/26 Active
switch (config) #
Related Commands
Notes
Default N/A
History 3.2.0500
Role admin
Interface Description Speed Current line rate Logical port state Physical port
state
--------- ----------- --------- ----------------- ------------------ -------------
IB1/1/26 fdr 56.0 Gbps Active LinkUp
switch (config) #
Related Commands
Notes
Default N/A
History 3.1.0000
Role admin
Related Commands
Notes • For a full list of the supported cables and transceivers, please refer to the LinkX™
Cables and Transceivers webpage in Mellanox.com: http://www.mellanox.com/
page/cables?mtag=cable_overview.
Displays cable channel monitoring and diagnostics info for this interface.
Default N/A
History 3.6.2002
Role admin
Related Commands
Default N/A
History 3.6.1002
Role admin
Related Commands
Notes
The SM applies network traffic related configurations such as Quality of Service (QoS), routing,
and partitioning of the fabric devices. You can view and configure the Subnet Parameters (SM)
via the CLI/WebUI menu. The embedded SM on the MLNX-OS can be used to manage fabrics
up to 2048 nodes on x86 based systems.
The SM is used to discover and configure all the InfiniBand fabric devices to enable traffic flow
between those devices.
To enable Subnet Manager:
Step 1. Enable Subnet Manager (disabled by default). Run:
switch (config) # ib smnode my-sm enable
Step 2. (Optional) Set the priority for the Subnet Manager. Run:
switch (config) # ib smnode my-sm sm-priority <priority>
5.5.1 Partitions
Partitioning enforces isolation among systems sharing an InfiniBand fabric. Partitioning is not
related to boundaries established by subnets, switches, or routers. Rather, a partition describes a
set of end nodes within the fabric that may communicate. Each port of an end node is a member
of at least one partition and may be a member of multiple partitions. A partition manager (part of
the SM) assigns partition keys (PKEYs) to each channel adapter port. Each PKEY represents a
partition. Reception of an invalid PKEY causes the packet to be discarded. Switches and routers
may optionally be used to enforce partitioning. In this case the partition manager programs the
switch or router with PKEY information and when the switch or router detects a packet with an
invalid PKEY, it discards the packet.
Fabric administration can assign certain Service Levels (SLs) for particular partitions. This
allows the SM to isolate traffic flows between those partitions, and even if both partitions operate
at the same QoS level, each partition can be guaranteed its fair share of bandwidth regardless of
whether nodes in other partitions misbehave or are over subscribed.
The switch enables the configuration of partitions in an InfiniBand fabric.
The default partition is created by the SM unconditionally (whether it was defined or not).
The partitions configuration is applicable and to be used only when the SM is enabled
and running on the system.
To configure a partition:
Step 1. Create a partition. Run:
switch (config) # ib partition my-partition pkey 0x7ff2
Step 2. Enter partition configuration mode. Run:
switch (config) # partition my-partition
switch (config partition name my-partition) #
Step 3. Add partition members. Run:
switch (config partition my-partition) # member all
Step 4. Verify the partition configuration. Run:
switch (config partition my-partition) # show ib partition
Default
PKey = 0x7FFF
defmember = full
ipoib = yes
members
GUID='ALL' member='full'
my-partition
PKey = 0x7ff2
members
GUID='ALL' member='default'
switch (config partition name my-partition) #
The embedded SM over the switch does not support configuring adaptive routing. To
use this option in the fabric please use an external SM.
Show commands convey every configuration change even if it is not applied yet.
5.5.6 Commands
ib sm
ib sm
no ib sm
Enables the SM on this node.
The no form of the command disables the SM on this node.
Default disable
History 3.1.0000
Role admin
Notes
ib sm accum-log-file
ib sm accum-log-file
no ib sm accum-log-file
Default Enabled
History 3.1.0000
Role admin
Notes
ib sm allow-both-pkeys
ib sm allow-both-pkeys
no ib sm allow-both-pkeys
Enables having both full and limited membership on the same partition.
The no form of the command disables having both full and limited membership on
the same partition.
Default Disabled
History 3.4.1100
Role admin
Notes
ib sm babbling-policy
ib sm babbling-policy
no ib sm babbling-policy
Default disable
History 3.1.0000
Role admin
Notes In case the babbling policy is enabled, and decides to close a babbling interface (one
which sends 129,130,131 traps, for example), the SM disables the port.
ib sm connect-roots
ib sm connect-roots
no ib sm connect-roots
Default true
History 3.1.0000
Role admin
Notes • This command is relevant only for ‘updn’ and ‘ftree’ algorithm (refer to ‘ib sm
routing-engines’ command)
• This option enforces routing engines (up/down and fat-tree) to make connectivity
between root switches and in this way to be fully IBA complaint. This may violate
the “deadlock-free” status of the algorithm. Hence, it is recommended to use the
command carefully.
ib sm drop-event-subscription
ib sm drop-event-subscription
no ib sm drop-event-subscription
History 3.4.2008
Role admin
Related Commands
Notes
ib sm enable-quirks
ib sm enable-quirks
no ib sm enable-quirks
Enables the SM to use high risk features and handle hardware workarounds.
The no form of the command disables the SM from using high risk features and hard-
ware workarounds.
Default disable
History 3.1.0000
Role admin
Notes
ib sm exit-on-fatal
ib sm exit-on-fatal
no ib sm exit-on-fatal
Default enable
History 3.1.0000
Role admin
Notes
ib sm force-link-speed
ib sm force-link-speed <speed-options>
no ib sm force-link-speed
History 3.1.0000
Role admin
ib sm force-log-flush
ib sm force-log-flush
no ib sm force-log-flush
Default disable
History 3.1.0000
Role admin
Notes
ib sm guid2lid-cache
ib sm guid2lid-cache
no ib sm guid2lid-cache
Allows SM to use cached GUID-to-lid mapping data. When enabled, the SM honors
the cached GUID-to-lid mapping information if:
• It exists
• It is valid
• sm_reassign_lids is disabled
The no form of the command disallows use of cached GUID-to-lid mapping data.
Default disable
History 3.1.0000
Role admin
Notes
ib sm honor-partitions
ib sm honor-partitions
no ib sm honor-partitions
Sets the no_partition_enforcement flag to 0. This setting controls global support for
partitioning in the subnet.
The no form of the command disables subnet partition support.
Default Enable
History 3.1.0000
Role admin
ib sm hoq-lifetime
ib sm hoq-lifetime <time>
Sets the maximum time a frame can wait at the head of a switch-to-switch port queue
before it is dropped.
Syntax Description time The time is 4.096 uS * 2time. The range of time is 0 to
20. A time of 20 means infinite, and the default value is
18 which translates to about 1 second.
History 3.1.0000
Role admin
Notes
ib sm ignore-other-sm
ib sm ignore-other-sm
no ib sm ignore-other-sm
Ignores all the rules governing SM elections and attempts to manage the fabric.
The no form of the command does not allow the SM to manage fabric if it loses the
election.
Default Disable
History 3.1.0000
Role admin
Notes
ib sm ipv6-nsm
ib sm ipv6-nsm
no ib sm ipv6-nsm
Default Disable
History 3.1.0000
Role admin
Notes
ib sm lash
ib sm lash {do-mesh-analysis | start-vl <vl-value>}
no ib sm lash do-mesh-analysis
History 3.1.0000
Role admin
Notes
ib sm leafhoq-lifetime
ib sm leafhoq-lifetime <time>
Sets the maximum time a frame can wait at the head of a switch-to-CA_or_Router
port queue before it is dropped.
Syntax Description time The time is 4.096 uS * 2time. The range of time is 0 to
20. A time of 20 means infinite, and the default value is
16 which translates to about 268 millisecond.
History 3.1.0000
Role admin
Notes
ib sm leafvl-stalls
ib sm leafvl-stalls <count>
Sets the number of sequential frame drops that cause a switch-to-CA_or_Router port
to enter the VLStalled state.
Default 7
History 3.1.0000
Role admin
Notes
ib sm lmc
ib sm lmc <mask>
Sets the LID Mask Control (LMC) value to be used on this subnet.
Default The default value is 0, which means that every port has exactly one unique LID.
History 3.1.0000
Role admin
Notes
ib sm lmc-esp0
ib sm lmc-esp0
no ib sm lmc-esp0
Sets the LMC for the subnet to be used for Enhanced Switch Port 0.
Default disable
History 3.1.0000
Role admin
Notes
ib sm log-flags
ib sm log-flags [all] [debug] [error] [frames] [funcs] [info] [none] [routing] [ver-
bose]
no ib sm log-flags
Syntax Description all Turns on all the flags that follow (error info verbose
debug funcs frames routing).
History 3.1.0000
Role admin
Notes • Every execution of this command replaces the current logging flags
• The options “all” and “none” must be specified as the only parameter
ib sm log-max-size
ib sm log-max-size <size>
Default 20 MBytes
History 3.1.0000
Role admin
Notes • The log file “opensm_<switch_name>.log” is rotated when it exceeds the config-
ured maximum file size up to 5 compressed files
• When the log gets to the maximum size, or system storage fills up, the current log
is deleted and messages start accumulating
• To successfully upgrade from a version prior to 3.5.1000, this parameter must be
set to a value in the range specified in the syntax description
ib sm m-key
ib sm m-key <m-key>
Default 00:00:00:00:00:00:00:00
History 3.1.0000
Role admin
Notes
ib sm max-op-vls
ib sm max-op-vls <count>
Default 15
History 3.1.0000
Role admin
Notes
ib sm max-reply-time
ib sm max-reply-time <time>
Sets the maximum time the SM waits for a reply before the transaction times out.
History 3.1.0000
Role admin
Notes
ib sm max-reverse-hops
ib sm max-reverse-hops <max-reverse-hops>
Sets the maximum number of hops from the top switch to an I/O node.
Default 0 hops
History 3.1.0000
Role admin
Notes
ib sm max-reverse-hops
ib sm max-reverse-hops <max-reverse-hops>
Sets the maximum number of hops from the top switch to an I/O node.
Default 0 hops
History 3.1.0000
Role admin
Notes
ib sm aguid_default_hop_limit
ib sm aguid_default_hop_limit <count>
no ib sm aguid_default_hop_limit
Configures the default value for hop limit returned in path records where either the
source or destination are alias an GUID.
The no form of the command resets the count to its default value.
Default 1
History 3.6.6102
Role admin
Notes
ib sm max-wire-smps2
ib sm max-wire-smps2 <count>
Default 4
History 3.1.0000
Role admin
Notes
ib sm m-key
ib sm m-key <mkey>
no ib sm m-key
Default 00:00:00:00:00:00:00:00
History 3.1.0000
Role admin
Notes • All nodes in the subnet may have to be reset or power-cycled after altering the SM
MKey configuration
• Fabric inspector, and many standalone InfiniBand utilities, may not function on
subnets with a non-default MKey.
ib sm mkey-lease
ib sm mkey-lease <time>
no ib sm mkey-lease
Default 0
History 3.6.2002
Role admin
Notes
ib sm mkey-lookup
ib sm mkey-lookup
no ib sm mkey-lookup
Default Enabled
History 3.6.2002
Role admin
Notes MKey lookup is a boolean value that controls how the SM finds the MKey of ports.
ib sm mkey-protect-level
ib sm mkey-protect-level <level>
no ib sm mkey-protect-level
Controls what data is returned to a get_PortInfo MAD request when the MKey in the
request does not match the MKey on the port.
The no form of the command resets the parameter to its default value.
Default 0
History 3.6.2002
Role admin
Notes
ib sm msgfifo-timeout
ib sm msgfifo-timeout <time>
Sets the time value to be used by the subnet administrator to control when a BUSY
status is returned to a client.
Default 10 seconds
History 3.1.0000
Role admin
Notes If there is more than one message in the SA queue, and it has been there longer than
time milliseconds, all additional incoming requests are immediately replied to with
BUSY status.
ib sm multicast
ib sm multicast
no ib sm multicast
Default Disable
History 3.1.0000
Role admin
Notes
ib sm no-client-rereg
ib sm no-client-rereg
no ib sm no-client-rereg
Default disable
History 3.1.0000
Role admin
Notes
ib sm overrun-trigger
ib sm overrun-trigger <count>
Enables SMA to generate standard InfiniBand trap number 130 when the number of
local buffer overrun errors equals the count value, and the port’s SMA supports traps.
Default 8
History 3.1.0000
Role admin
Notes Refer to the InfiniBand Architecture Specification V1 r1.2.1, section 14.2.5.1 table
131: Traps.
ib sm packet-life-time
ib sm packet-life-time <time>
Syntax Description time The time is 4.096 uS * 2*<time>. The rang is: 0-20. A
time of 20 means infinite. The value 0x14 disables this
mechanism.
History 3.1.0000
Role admin
Notes
ib sm phy-err-trigger
ib sm phy-err-trigger <count>
Enables SMA to generate trap 129 when the number of local link integrity errors
equals the <count> value, and the port’s SMA supports traps.
Default 8
History 3.1.0000
Role admin
Notes
ib sm polling-retries
ib sm polling-retries <value>
This variable defines the number of consecutive times an active SM must fail to
respond before it is declared dead.
Default 4
History 3.1.0000
Role admin
Notes The time between when the active SM fails and the time this SM declares it dead is:
(sm_sminfo_polling_timeout * value) milliseconds.
ib sm port-prof-switch
ib sm port-prof-switch
no ib sm port-prof-switch
Enables the counting of adapters, routers, and switches routed through links.
The no form of the command disables the counting of adapters, routers, and switches
routed through links.
Default False
History 3.1.0000
Role admin
Notes
ib sm reassign-lids
ib sm reassign-lids
no ib sm reassign-lids
Controls the ability of the SM to reassign LIDs to nodes it finds already configured
with a valid LID.
The no form of the command disables the SM from reassigning LIDs to nodes it finds
already configured with a valid LID.
Default disable
History 3.1.0000
Role admin
Notes • If enabled (ib sm reassign-lids), the SM can, but is not required to, reassign the
LID on a node with a pre-configured LID
• If disabled (no ib sm reassign-lids), the SM does not reassign LIDs
• There are times when the SM is required to reassign LIDs or the fabric cannot be
brought to a stable state, or a fabric option (like LMC) can not be fully applied
ib sm reset-config
ib sm reset-config
Default N/A
History 3.1.0000
Role admin
Related Commands
Notes
ib sm root-guid
ib sm root-guid <guid>
no ib sm root-guid <guid>
Default N/A
History 3.1.0000
Role admin
Notes The list of root GIDs are relevant when IB SM is running on the switch, and the rout-
ing algorithm is up-down or fat-tree.
ib sm routing-engines
ib sm routing-engines [dor] [file] [ftree] [lash] [minhop] [none] [updn]
no ib sm routing-engines
Default None
History 3.1.0000
Role admin
Notes Multiple routing engines can be specified separated by spaces so that specific order-
ing of routing algorithms will be tried if earlier routing engines fail.
ib sm rtr-aguid-enable
ib sm rtr-aguid-enable <value>
sm ib sm rtr-aguid-enable <value>
Default 0
History 3.6.2002
Role admin
Related Commands
Notes
ib sm rtr-pr-flow-label
ib sm rtr-pr-flow-label <value>
no ib sm rtr-pr-flow-label <value>
Default 0
History 3.6.2002
Role admin
Related Commands
Notes
ib sm rtr-pr-mtu
ib sm rtr-pr-mtu <value>
no ib sm rtr-pr-mtu <value>
Default 2K
History 3.6.2002
Role admin
Related Commands
Notes
ib sm rtr-pr-rate
ib sm rtr-pr-rate <value>
no ib sm rtr-pr-rate <value>
Syntax Description value Possible values: 2.5, 5, 10, 14, 20, 25, 40, 56, 100
Default 100
History 3.6.2002
Role admin
Related Commands
Notes
ib sm rtr-pr-sl
ib sm rtr-pr-sl <value>
no ib sm rtr-pr-sl <value>
Default 0
History 3.6.2002
Role admin
Related Commands
Notes
ib sm rtr-pr-tclass
ib sm rtr-pr-tclass <value>
no ib sm rtr-pr-tclass <value>
Default 0
History 3.6.2002
Role admin
Related Commands
Notes
ib sm sa-key
ib sm sa-key <SA_Key>
Sets the SA_Key 64-bit value used by SA to qualify that a query is “trusted”.
Default 00:00:00:00:00:00:00:01
History 3.1.0000
Role admin
Notes OpenSM version 3.2.1 and lower used the default value of “1” in host byte order. You
may need to change this value to inter-operate with older subnet managers.
ib sm single-thread
ib sm single-thread
no ib sm single-thread
Enables the Subnet Manager to use a single thread to service all requests.
The no form of the command enables SA to use multiple service threads.
History 3.1.0000
Role admin
Notes
ib sm sm-inactive
ib sm sm-inactive
no ib sm sm-inactive
Configures the SM to start in the “inactive” SM state. This option can be used to run
a standalone system without the SM/SA function.
The no form of the command configures the SM to start in “init” SM state.
Default Disable
History 3.1.0000
Role admin
Notes
ib sm sm-key
ib sm sm-key <SM_Key>
Default 00:00:00:00:00:00:00:01
History 3.1.0000
Role admin
Notes OpenSM version 3.2.1 and lower used the default value of “1” in host byte order. You
may need to change this value to inter-operate with older subnet managers.
ib sm sm-priority
ib sm sm-priority <priority>
Syntax Description priority Priority 0 is the least important, 15 the most important.
Default 0
History 3.1.0000
Role admin
Notes If two or more active SMs have the same highest priority, the one with the lowest port
GUID manages the fabric.
ib sm sm-sl
ib sm sm-sl <sm-sl>
Default 0
History 3.1.0000
Role admin
ib sm sminfo-poll-time
ib sm sminfo-poll-time <time>
This variable controls the timeout between two polls of an active subnet manager.
Default 10 seconds
History 3.1.0000
Role admin
Notes
ib sm subnet-prefix
ib sm subnet-prefix <prefix>
no ib sm subnet-prefix <prefix>
Sets the SM “Subnet Prefix” used to create scope qualifiers for all elements managed
by the SM.
The no form of the command resets the subnet prefix to its default value.
Default FE:80:00:00:00:00:00:00
History 3.6.1002
Role admin
Notes The default value is also the InfiniBand default for a locally administered subnet.
ib sm subnet-prefix-override
ib sm subnet-prefix-override
no ib sm subnet-override
Default Enabled
History 3.6.2002
Role admin
Notes
ib sm subnet-timeout
ib sm subnet-timeout <time>
Sets the global per-port subnet timeout value (PortInfo:SubnetTimeOut). This value
also controls the maximum trap frequency in which no traps are allowed to be sent
faster than the subnet_timeout value.
Syntax Description time The actual timeout is 4.096 uS * 2*<time>. The range
of time is 0-31 for this parameter which supports 32
discrete time values between 4 uS and about 2.4 hours.
History 3.1.0000
Role admin
Notes If the SMA generates a sequence of traps, the interval between successive traps
should not be smaller than <time>.
ib sm sweep-interval
ib sm sweep-interval <time>
no ib sm sweep-interval
Default 10 seconds
History 3.1.0000
Role admin
Notes
ib sm sweep-on-trap
ib sm sweep-on-trap
no ib sm sweep-on-trap
Enables every TRAP received by the SM to initiate a heavy sweep in addition to the
processing required by the TRAP.
The no form of the command enables SM to use a combination of light and heavy
sweeps based on the type of TRAP and other internal states.
Default enable
History 3.1.0000
Role admin
Notes More than 10 successive identical TRAPs disable the automatic sweep behavior until
at least one different TRAP has been received.
ib sm transaction-retries
ib sm transaction-retries <transaction-retries-count>
Default 3
History 3.1.0000
Role admin
Notes
ib sm use-heavy-sweeps
ib sm use-heavy-sweeps
no ib sm use-heavy-sweeps
Default disable
History 3.1.0000
Role admin
Notes
ib sm use-ucast-cache
ib sm use-ucast-cache
no ib sm use-ucast-cache
Default Disable
History 3.1.0000
Role admin
Notes
ib sm vl-stalls
ib sm vl-stalls <count>
Sets the number of sequential frame drops that cause a switch-to-switch port to enter
the VLStalled state.
Default 7
History 3.1.0000
Role admin
Notes
ib sm virt
ib sm virt {enable | disable | ignore}
no ib sm virt
Default Ignore
History 3.4.2008
Role admin
Related Commands
Notes
ib sm virt-default-hop-limit
ib sm virt-default-hop-limit <value>
no ib sm virt-default-hop-limit
Configures the default value for hop limit to be returned in path records.
The no form of the command resets this parameter to its default value.
Default 2
History 3.6.2002
Role admin
Related Commands
Notes
ib sm virt-max-ports-in-process
ib sm virt-max-ports-in-process <value>
no ib sm virt-max-ports-in-process
Default 4
History 3.6.2002
Role admin
Related Commands
Notes
show ib sm
show ib sm
Default N/A
History 3.1.0000
Role admin
Related Commands ib sm
Notes
show ib sm accum-log-file
show ib sm accum-log-file
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm babbling-policy
show ib sm babbling-policy
Displays the ability of the SM to disable babbling ports (i.e., generating frequent
traps).
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm connect-roots
show ib sm connect-roots
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm enable-quirks
show ib sm enable-quirks
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm exit-on-fatal
show ib sm exit-on-fatal
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm fdr10
show ib sm fdr10
Default N/A
History 3.1.0000
Role admin
Related Commands
Notes
show ib sm force-link-speed
show ib sm force-link-speed
Default N/A
History 3.1.0000
Role admin
show ib sm force-link-speed-ext
show ib sm force-link-speed-ext
Default N/A
History 3.1.0000
Role admin
Related Commands
show ib sm force-log-flush
show ib sm force-log-flush
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm guid2lid-cache
show ib sm guid2lid-cache
Displays whether or not the SM honors the cached GUID-to-LID mapping informa-
tion.
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm honor-partitions
show ib sm honor-partitions
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm hoq-lifetime
show ib sm hoq-lifetime
Displays the maximum time a frame can wait at the head of a switch-to-switch port
queue before it is dropped.
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm ignore-other-sm
show ib sm ignore-other-sm
Displays if the rules governing SM elections and attempt to manage the fabric on the
node are ignored by the SM.
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm ipv6-nsm
show ib sm ipv6-nsm
Displays the consolidation of IPv6 Solicited Node Multicast (SNM) group join
requests.
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm lash
show ib sm lash {do-mesh-analysis | start-vl}
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm leafhoq-lifetime
show ib sm leafhoq-lifetime
Displays the maximum time a frame can wait at the head of a switch-to-
CA_or_Router port queue before it is dropped.
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm leafvl-stalls
show ib sm leafvl-stalls
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm lmc
show ib sm lmc
Displays the LID Mask Control (LMC) value to be used on this subnet.
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm lmc-esp0
show ib sm lmc-esp0
Displays whether the LMC for the subnet is also used for Enhanced Switch Port 0 (ib
sm lmc-esp0) or if the LMC for ESP0 ports is 0 (no ib sm lmc-esp0).
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm log
show ib sm log [continuous] [[not] [matching <reg-expression>]]
Syntax Description continuous Displays IB SM new event log messages as they arrive
matching <regular expres- Displays IB SM event log messages that match a given
sion> regular expression.
Default N/A
History 3.1.0000
Role admin
switch (config) #
Notes
show ib sm log-flags
show ib sm log-flags
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm log-max-size
show ib sm log-max-size
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm max-op-vls
show ib sm max-op-vls
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm max-ports
show ib sm max-ports
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm max-reply-time
show ib sm max-reply-time
Displays the maximum time in milliseconds that the SM will wait for a reply before
the transaction times out.
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm max-reverse-hops
show ib sm max-reverse-hops
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm max-reverse-hops
show ib sm max-reverse-hops
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm aguid-default-hop-limit
show ib sm aguid-default-hop-limit
Displays the default value for hop limit returned in path records where either the
source or destination is an alias GUID.
Default N/A
History 3.6.6102
Role admin
Notes
show ib sm max-wire-smps
show ib sm max-wire-smps
Displays the maximal number of MADs the SM will have outstanding at one time to
count.
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm max-wire-smps2
show ib sm max-wire-smps2
Default N/A
History 3.1.0000
Role admin
Related Commands
Notes
show ib sm mkey-lease
show ib sm mkey-lease
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm m-key
show ib sm m-key
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm mkey-lookup
show ib sm mkey-lease
Displays whether SM looks in file cache for unknown node MKeys or not.
Default N/A
History 3.6.2002
Role admin
Notes
show ib sm mkey-protect-level
show ib sm mkey-protect-level
Default N/A
History 3.6.2002
Role admin
Notes
show ib sm msgfifo-timeout
show ib sm msgfifo-timeout
Displays the elapsed time in milliseconds before a frame at the head of Subnet Agent
queue causes an immediate BUSY state.
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm multicast
show ib sm multicast
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm no-client-rereg
show ib sm no-client-rereg
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm overrun-trigger
show ib sm overrun-trigger
Displays count of local buffer overrun errors for Infiniband trap 130
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm packet-life-time
show ib sm packet-life-time
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm phy-err-trigger
show ib sm phy-err-trigger
Displays the number of local link integrity errors and the port’s SMA supports traps.
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm polling-retries
show ib sm polling-retries
Displays the number of consecutive times an active SM must fail to respond before it
is declared dead.
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm port-prof-switch
show ib sm port-prof-switch
Displays whether or not the counting of adapters, routers, and switches through the
links is being done.
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm reassign-lids
show ib sm reassign-lids
Displays the ability of the SM to reassign LIDs to nodes it finds already configured
with a valid LID.
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm root-guid
show ib sm root-guid
Default N/A
History 3.1.0000
Role admin
Notes The list of root GUIDs are relevant when IB SM is running on the switch, and the
routing algorithm is up-down or fat-tree.
show ib sm routing-engines
show ib sm routing-engines
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm routing-info
show ib sm routing-info
Default N/A
History 3.1.0000
Role admin
Related Commands
Notes
show ib sm rtr-aguid-enable
show ib sm rtr-aguid-enable
Default N/A
History 3.6.2002
Role admin
Notes
show ib sm rtr-pr-flow-label
show ib sm rtr-pr-flow-label
Default N/A
History 3.6.2002
Role admin
show ib sm rtr-pr-mtu
show ib sm rtr-pr-mtu
Default N/A
History 3.6.2002
Role admin
Notes
show ib sm rtr-pr-rate
show ib sm rtr-pr-rate
Default N/A
History 3.6.2002
Role admin
Notes
show ib sm rtr-pr-sl
show ib sm rtr-pr-sl
Default N/A
History 3.6.2002
Role admin
Notes
show ib sm sa-key
show ib sm sa-key
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm single-thread
show ib sm single-thread
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm sm-inactive
show ib sm sm-inactive
Displays whether or not the SM starts in “inactive” rather than “init” SM state.
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm sm-key
show ib sm sm-key
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm sm-priority
show ib sm sm-priority
Default N/A
History 3.1.0000
Role admin
Notes Priority 0 is the least important, 15 the most important. If 2 or more active SMs have
the same highest priority, the one with the lowest port GUID will manage the fabric.
show ib sm sm-sl
show ib sm sm-sl
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm sminfo-poll-time
show ib sm sminfo-poll-time
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm subnet-prefix
show ib sm subnet-prefix
Displays the SM “Subnet Prefix” used to create scope qualifiers for all elements man-
aged by the SM.
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm subnet-prefix-override
show ib sm subnet-prefix
Default N/A
History 3.6.2002
Role admin
Notes
show ib sm subnet-timeout
show ib sm subnet-timeout
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm sweep-interval
show ib sm sweep-interval
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm sweep-on-trap
show ib sm sweep-on-trap
Displays whether or not a heavy sweep is initiated by the TRAP received by the SM.
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm transaction-retries
show ib sm transaction-retries
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm use-heavy-sweeps
show ib sm use-heavy-sweeps
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm use-ucast-cache
show ib sm use-ucast-cache
Default N/A
History 3.1.0000
Role admin
Notes
show ib sm version
show ib sm version
Default N/A
History 3.2.3000
Role admin
Related Commands
Notes
show ib sm virt-default-hop-limit
show ib sm virt-default-hop-limit
Displays the default value for hop limit to be returned in path records.
Default N/A
History 3.6.2002
Role admin
Notes
show ib sm virt-max-ports-in-process
show ib sm virt-max-ports-in-process
Default N/A
History 3.6.2002
Role admin
Notes
show ib sm vl-stalls
show ib sm use-vl-stalls
Displays the number of sequential frame drops that cause a switch-to-switch port to
enter the VLStalled state.
Default N/A
History 3.1.0000
Role admin
Notes
5.5.6.2 Partitions
ib partition
ib partition <partition-name> [pkey <pkey number>]
no ib partition <partition-name> [force]
History 3.2.0500
Role admin
Related Commands
Notes
pkey
pkey <number> [force]
no pkey <number>
Default N/A
History 3.2.0500
Role admin
Related Commands
defmember
defmember <type> [force]
no defmember
Default limited
History 3.2.0500
Role admin
Notes This parameter can be overwritten for specific GUID, using the “member” command.
member
member {<guid> | all | self} [type <member-type>] [force]
no member {<guid> | all | self} [type] [force]
all | self The option “all” can be used for all GUIDs in the fab-
ric, or “self” for the switch guide
Default N/A
History 3.2.0500
Role admin
Notes
ipoib
ipoib [force]
no ipoib [force]
Enables this partition to use IPoIB. As a result IPoIB multicast group will be created.
The no form of the command removes the use of IPoIB in this partition (it will not
appear in the partitions.conf file).
Default no ipoib
History 3.2.0500
Role admin
Notes “rate”, “mtu”, “sl” and “scope” commands can be used only when the IPoIB parame-
ter is enabled.
mtu
mtu <256, 512, 1K, 2K,4K> [force]
no mtu
Default 2K
History 3.2.0500
Role admin
Notes IPoIB parameter on the partitions must be enabled in order to use this parameter
rate
rate <rate> [force]
no rate
Default 10 Gbps.
History 3.2.0500
Role admin
Related Commands
Notes • Ports that do not support the IPoIB rate are not added to the partition
scope
scope <type> [force]
no scope <link-local, site-local, organization-local, global>
Default link-local
History 3.2.0500
Role admin
Related Commands
Notes ipoib parameter on the partitions must be enabled in order to use this parameter.
sl
sl <0-14, “default”> [force]
no sl
History 3.2.0500
Role admin
Related Commands
Notes ipoib parameter on the partitions must be enabled in order to use this parameter.
show ib partition
show ib partition [<partition-name> [member [<member-name>]]]
Default N/A
History 3.2.0500
Role admin
Default
PKey = 0x7FFF
ipoib = yes
members
GUID='ALL' member='full'
Related Commands
Notes If bulk update mode is enabled, this command notifies the user that these changes
may not have been applied yet.
Sets the high-limit value for the indicated port type. Thus the system will send at least
4096 * <count> bytes from the high priority list before sending any from the low pri-
ority list.
History 3.1.0000
Role admin
Notes A high-limit value of 255 means unlimited, and that makes it possible to starve the
low priority list.
Sets the maximum number of VLs for the indicated port type.
Default 15
History 3.1.0000
Role admin
Notes
History 3.1.0000
Role admin
History 3.1.0000
Role admin
History 3.1.0000
Role admin
Notes You may have multiple entries with the same VL on this list.
ib baseqos reset-config
ib baseqos reset-config
Default N/A
History 3.1.0000
Role admin
Related Commands
Notes
show ib baseqos
show ib baseqos <port-type> <baseqos-parameters>
Default N/A
History 3.1.0000
Role admin
Related Commands
Notes
ib qos
ib qos
no ib qos
History 3.1.0000
Role admin
Notes
ib qos level
ib qos level {<name> | default} {mtu-limit <mtu> | packet-life <time> | pkey
<number> | rate-limit <rate-value> | sl <sl-value>| use <description>}
no ib qos level {<name> | default} {mtu-limit | packet-life | pkey | rate-limit | sl |
use}
Syntax Description <name> | default Specify a name for this qos group, or use the “default”
for the default qos parameters.
packet-life <time> Time a packet can wait in switch egress queue before
being dropped. The bytes from 4 microsecond up to 2
seconds or infinite.
Possible values are 0-20
0 - 4usec
1 - 8usec
...
20 - unlimited
pkey <number> PKEY value: ranges between -1 and 32767 (hex 0x7fff)
History 3.1.0000
Role admin
Notes
ib qos match-rule
ib qos match-rule <rule-index> { {destination | source} <string> | {pkey | qos-
class | service-id} <index> {first | last} <value>} | qos-level-name <name>| use
<description>}
no ib qos match-rule <rule-index> { {destination | source} | {pkey | qos-class | ser-
vice-id} <index> {first | last} } | qos-level-name | use }
pkey | qos-class | service- Manages values for QoS Policy match rules.
id <index>
{first | last} <value> First or last value range (per PKEY / qos-class of ser-
vice id.
Default N/A
History 3.1.0000
Role admin
Notes
ib qos port-group
ib qos port-group <name> {node-type <index> type <node-type> | partition
<name>| pkey <number> | port-guid <index> {first | last} <value> | port-name
<index> name <name-value>| use <description>}
no ib qos port-group <name> {node-type <index> type | partition | pkey | port-
guid <index> {first | last} | port-name <index> name | use }
Default N/A
History 3.1.0000
Role admin
Notes
Default N/A
History 3.1.0000
Role admin
Notes
Syntax Description default sl <sl-value> Set the default sl. Range 1-15
Default N/A
History 3.1.0000
Role admin
Notes
Configures ULP IScsi Extensions for RDMA, Reliable Datagram Sockets or Sockets
Direct Protocol attributes.
The no form of the command deletes all rules.
Default N/A
History 3.1.0000
Role admin
Notes
Syntax Description target-port-guid <index> The index of the target port GUID
Default N/A
History 3.1.0000
Role admin
Notes
show ib qos
show ib qos [level | match-rule | port-group | ulp]
Default N/A
History 3.1.0000
Role admin
Related Commands
Notes
ib sm scatter-ports
ib sm scatter-ports <seed>
no ib sm scatter-ports
Activates scatter ports and sets seed for random number generation.
The no form of the command deactivates the partition.
Default Disabled
History 3.6.8008
Role admin
show ib sm scatter-ports
show ib sm scatter-ports
Default N/A
History 3.6.8008
Role admin
Notes
ib sm guid-routing-order add
ib sm guid-routing-order add <guid> [position <pos>]
Default If no position is specified, the new GUID is added to the end of the list
History 3.6.8008
Role admin
Notes
ib sm guid-routing-order delete
ib sm guid-routing-order delete {<guid> | position <pos>}
Deletes a guid from routing order list. The guid can be chosen by its guid or by its
position on guid routing order list.
Default N/A
History 3.6.8008
Role admin
Notes
ib sm guid-routing-order move
ib sm guid-routing-order move <guid> to-position <pos>
Default N/A
History 3.6.8008
Role admin
Notes
ib sm guid-routing-order move-down
ib sm guid-routing-order move-down <guid>
Default N/A
History 3.6.8008
Role admin
Notes
ib sm guid-routing-order move-up
ib sm guid-routing-order move-up <guid>
Default N/A
History 3.6.8008
Role admin
Notes
no ib sm guid-routing-order
no ib sm guid-routing-order
Disables the GUID routing order feature and cleans GUID routing order list.
Default N/A
History 3.6.8008
Role admin
Notes
show ib sm guid-routing-order
show ib sm guid-routing-order
Default N/A
History 3.6.8008
Role admin
1: E4:1D:2D:03:00:3D:5E:85
2: E4:1D:2D:03:00:3D:5E:82
3: E4:1D:2D:03:00:3D:5E:81
4: E4:1D:2D:03:00:3D:5E:84
5: E4:1D:2D:03:00:3D:5E:86
6: E4:1D:2D:03:00:3D:5E:87
7: E4:1D:2D:03:00:3D:5E:90
8: E4:1D:2D:03:00:3D:5E:88
9: E4:1D:2D:03:00:3D:5E:83
Notes
ib sm guid-routing-order-no-scatter
ib sm guid-routing-order-no-scatter
no ib sm guid-routing-order-no-scatter
Default N/A
History 3.6.8008
Role admin
Notes If scatter ports (randomization of the output port) is set to anything but zero, guid-
routing-order-no-scatter defines whether or not randomization should be applied to
the destination GUIDs mentioned in the GUID routing order list.
show ib sm guid-routing-order-no-scatter
show ib sm guid-routing-order-no-scatter
Default N/A
History 3.6.8008
Role admin
guid_routing_order_no_scatter: disabled
Notes
ib sm bulk-update enable
ib sm bulk-update enable
no ib sm bulk-update enable
Default Disabled
History 3.6.8008
Role admin
Notes
show ib sm bulk-update
show ib sm bulk-update
Default N/A
History 3.6.8008
Role admin
ib sm bulk-update: enabled
Notes
High availability (HA) refers to a system or component that is continuously operational for a
desirably extended period of time.
Mellanox Subnet Manager (SM) HA reduces subnet downtime and disruption as it is continu-
ously operational for a desirably long length of time. It assures continuity of the work even when
one of the SMs dies. The database is synchronized with all the nodes participating in the Infini-
Band subnet and a configuration change is prepared. The synchronization is done out-of-band
using an Ethernet management network.
Mellanox SM HA allows the systems’ manager to enter and modify all InfiniBand SM configura-
tion of different subnet managers from a single location. It creates an InfiniBand subnet and asso-
ciates all the Mellanox management appliances that are attached to the same InfiniBand subnet
into that InfiniBand subnet ID. All subnet managers can be controlled, started, or stopped from
this address.
All the nodes that participate in the Mellanox SM HA are joined to the InfiniBand subnet ID and
once joined, the synchronized SMs are launched. One of the nodes is elected as Master and the
others are Slaves (or down). Mellanox SM HA uses an IP address (VIP) that is always directed to
the SM HA master to monitor the SM state and to verify that all configurations are executed.
Every system that is not associated to an existing IB subnet (has never been part of an IB subnet
or has left an existing one) or does not have MLNX-OS license installed, is by default associated
to a subnet called “Standalone”.
In order to create, join or leave an InfiniBand subnet, one may use the following commands:
• Create – “ib ha <IB_subnet_ID> ip <ip_addr> <netmask>”
• Join – “ib ha <IB_subnet_ID>”
• Leave – “no ib ha”
For further information see Section 5.6.5, “Creating and Adding Systems to an InfiniBand Sub-
net ID,” on page 805.
To see a list of the existing nodes and details about the running state, run the command show ib
smnodes {brief}.
Step 4. Log into the system that you are going to join to the new created subnet.
Step 5. Join the system to the subnet, using the ib ha <IB_subnet_ID> command.
switch [standalone: master] (config) # ib ha subnet2
switch [subnet2: standby] (config) #
The asterisk in the example above (*switch-11a15e) indicates the local system from
where the command is running.
In order to receive information on the running state of a specific node one could run one of the
following commands with its requested parameter:
• show ib smnode <name> sm-licensed
• show ib smnode <name> sm-running
• show ib smnode <name> sm-state
• show ib smnode <name> sm-priority
• show ib smnode <name> active
• show ib smnode <name> ha-state
• show ib smnode <name> ha-role
The user can configure different SM parameters such as where to run the SM(s) or the SM prior-
ity by running the commands according to the desired action.
Mellanox Technologies products are fully compliant and interoperable with OpenSM.
Once an SM fails, the SM which takes over the subnet needs to reproduce the internal state of the
failed master. Most of the information required is obtained by scanning the subnet and extracting
the information from the devices. However, some information which is not stored directly in the
network devices cannot be reproduced this way. InfiniBand management architecture limits such
information to data exchanged between clients (either user-level programs or kernel modules)
and the Subnet Administration (SA) service (attached to the SM). The SA keeps this set of client
registrations in an internal data structure called SA-DB. The SA-DB information includes the
multicast groups, the multicast group members, subscriptions for event forwarding and service
records.
The new SM may retrieve the SA-DB by requesting the clients to re-register with the SA or by
obtaining a copy of the previous master SM internal SA-DB via an SA-DB dump file. The client-
re-registration offers database correctness and the SA-DB dump file replication provides lower
setup time. Client re-registration is required since the SA-DB may not be up-to-date on the regis-
trations listed in the master SM.
Furthermore, since the SM does not maintain SA-DB information for unknown nodes, it is very
possible that some of the SA-DB information relating to nodes momentarily disconnected from
the master SM become purged. Therefore, these nodes must re-register with the new SM when
they are reconnected (they receive a client-re-register request from the SM). Relying only on cli-
ent re-registration is also non-optimal as it takes some time to recreate the entire SA-DB and the
network state.
Mellanox SM HA replicates the SA-DB dump file from the current master SM to all the standby
SMs running on Mellanox switches. The SA-DB dump file replication provides further optimiza-
tion to the standby SM that becomes master.
Standby SM loads the existing SA-DB file the old master has used. By using the existing SA-DB
the amount of processing needed on client re-registration is lessened resulting in a reduced time
to complete setting up the network.
5.6.7 Commands
ib ha
ib ha <IB_subnet_ID> [ip <IP address> <subnet mask> [force]]
no ib ha
Default N/A
History 3.1.0000
Role admin
Notes • A new subnet may be joined only after leaving the current one
ib smnode
ib smnode <hostname> [create | disable | enable | sm-priority <priority>]
no ib smnode <hostname> [create | disable | enable | sm-priority]
Manages HA SM.
The no form of the command removes HA SM node configuration.
Default N/A
History 3.1.0000
Role admin
Notes
show ib smnode
show ib smnode <hostname> {active | ha-role | ha-state | ip | sm-licensed | sm-pri-
ority | sm-running | sm-state}
Default N/A
History 3.1.0000
Role admin
Notes
show ib smnodes
show ib smnodes [brief]
Displays information about all the systems that are active or might be able to run SM.
Default N/A
History 3.1.0000
Role admin
switch (config) #
Notes
show ib ha
show ib ha [brief]
Displays information about all the systems that are active or might be able to run SM.
Default N/A
History 3.1.0000
Role admin
Related Commands
Notes
-I---------------------------------------------------
-I- Bad Guids/LIDs Info
-I---------------------------------------------------
-I- skip option set. no report will be issued
-I---------------------------------------------------
-I- Links With Logical State = INIT
-I---------------------------------------------------
-W- link with LOG=INI found at direct path "24,19,17,20"
From: a Switch PortGUID=0x0002c90200405b98 Port=20
To: a Switch PortGUID=0x0002c90200405f98 Port=18
-W- link with LOG=INI found at direct path "24,19,17,21"
From: a Switch PortGUID=0x0002c90200405b98 Port=21
To: a Switch PortGUID=0x0002c90200405fa0 Port=18
-W- link with LOG=INI found at direct path "24,19,17,22"
From: a Switch PortGUID=0x0002c90200405b98 Port=22
To: a Switch PortGUID=0x0002c90200405fa0 Port=17
-W- link with LOG=INI found at direct path "24,19,17,23"
From: a Switch PortGUID=0x0002c90200405b98 Port=23
To: a Switch PortGUID=0x0002c90200405f70 Port=17
-W- link with LOG=INI found at direct path "24,19,17,24"
From: a Switch PortGUID=0x0002c90200405b98 Port=24
To: a Switch PortGUID=0x0002c90200405f70 Port=18
-W- link with LOG=INI found at direct path "24,19,17,25"
From: a Switch PortGUID=0x0002c90200405b98 Port=25
To: a Switch PortGUID=0x0002c90200405f80 Port=17
-W- link with LOG=INI found at direct path "24,19,17,26"
From: a Switch PortGUID=0x0002c90200405b98 Port=26
To: a Switch PortGUID=0x0002c90200405f80 Port=18
-W- link with LOG=INI found at direct path "24,19,17,27"
From: a Switch PortGUID=0x0002c90200405b98 Port=27
-I---------------------------------------------------
-I- PM Counters Info
-I---------------------------------------------------
-W- lid=0x0016 guid=0x0002c90200405a90 dev=48438 Port=23
Performance Monitor counter : Value
symbol_error_counter : 0xffff (overflow)
-I---------------------------------------------------
-I- Fabric Partitions Report (see ibdiagnet.pkey for a full hosts list)
-I---------------------------------------------------
-I- PKey:0x7fff Hosts:1 full:1 partial:0
-I---------------------------------------------------
-I- IPoIB Subnets Check
-I---------------------------------------------------
-I---------------------------------------------------
-I- Bad Links Info
-I- No bad link were found
-I---------------------------------------------------
SM - master
Port=9 lid=0x0001 guid=0x0002c90200405f60 dev=48438 priority:0
SM - standby
The Local Device : Port=0 lid=0x0017 guid=0x0002c9020040c6d0 dev=48438 priority:0
Port=10 lid=0x0018 guid=0x0002c9020040b2e8 dev=48438 priority:0
switch [subnet2: master] (config) #
Step 3. Run show fabric pm to display the performance counters’ status.
switch [subnet2: master] (config) # show fabric pm
% --------------------------------------------------------------------------------
Port=27 lid=0x0014 guid=0x0012c90200405a81 dev=48438
--------------------------------------------------------------------------------
symbol_error_counter = 0x0
link_error_recovery_counter = 0x0
link_down_counter = 0x0
port_rcv_errors = 0x0
port_xmit_discard = 0x0
vl15_dropped = 0x0
port_rcv_constraint_errors = 0x0
local_link_integrity_errors = 0x0
port_xmit_constraint_errors = 0x0
excesive_buffer_errors = 0x0
port_xmit_data = 0x7a1d8
port_rcv_data = 0x7a1d8
port_xmit_pkts = 0x1b23
port_rcv_pkts = 0x1b23
port_rcv_remote_physical_errors = 0x0
port_rcv_switch_relay_errors = 0x0
--------------------------------------------------------------------------------
Port=28 lid=0x0014 guid=0x0012c90200405a81 dev=48438
--------------------------------------------------------------------------------
symbol_error_counter = 0x0
link_error_recovery_counter = 0x0
link_down_counter = 0x0
port_rcv_errors = 0x0
port_xmit_discard = 0x0
vl15_dropped = 0x0
port_rcv_constraint_errors = 0x0
local_link_integrity_errors = 0x0
port_xmit_constraint_errors = 0x0
excesive_buffer_errors = 0x0
port_xmit_data = 0x7d7cf0
port_rcv_data = 0x7d7cf0
port_xmit_pkts = 0x1be2e
port_rcv_pkts = 0x1be2e
port_rcv_remote_physical_errors = 0x0
port_rcv_switch_relay_errors = 0x0
--------------------------------------------------------------------------------
Port=10 lid=0x0006 guid=0x0002c90200405f98 dev=48438
--------------------------------------------------------------------------------
symbol_error_counter = 0x0
link_error_recovery_counter = 0x0
link_down_counter = 0x0
port_rcv_errors = 0x0
...
...
...
--------------------------------------------------------------------------------
Port=26 lid=0x0014 guid=0x0012c90200405a81 dev=48438
--------------------------------------------------------------------------------
symbol_error_counter = 0x0
link_error_recovery_counter = 0x0
link_down_counter = 0x0
port_rcv_errors = 0x0
port_xmit_discard = 0x0
vl15_dropped = 0x0
port_rcv_constraint_errors = 0x0
local_link_integrity_errors = 0x0
port_xmit_constraint_errors = 0x0
excesive_buffer_errors = 0x0
port_xmit_data = 0x536d0
port_rcv_data = 0x536d0
port_xmit_pkts = 0x128a
port_rcv_pkts = 0x128a
port_rcv_remote_physical_errors = 0x0
port_rcv_switch_relay_errors = 0x0
switch [subnet2: master] (config) #
Step 4. Run show interfaces ib to display the status and configuration of the system’s Infini-
Band ports.
switch [subnet2: master] (config) # show interfaces ib
Slot 1 port 1 state
Logical port state : Active
Physical port state : 10
Current line rate : 40.0 Gbps
Supported speeds : 10
Speed : 10.0 Gbps
Supported widths : 10
Width : 12X
Max supported MTUs : 10
MTU : 10
VL capabilities : 10
Operational VLs : 10
RX bytes : 255
RX packets : 255
RX errors : 255
Symbol errors : 255
VL15 dropped packets: 255
TX bytes : 255
TX packets : 255
TX wait : 255
TX discarded packets: 255
RX bytes : 255
RX packets : 255
RX errors : 255
Symbol errors : 255
VL15 dropped packets: 255
TX bytes : 255
TX packets : 255
TX wait : 255
TX discarded packets: 255
RX bytes : 255
RX packets : 255
RX errors : 255
Symbol errors : 255
VL15 dropped packets: 255
TX bytes : 255
TX packets : 255
TX wait : 255
TX discarded packets: 255
5.7.4 Commands
ib fabric import
ib fabric import <filename>
Imports a “snapshot” of fabric data. It retrieves fabric data from the following ibdiag-
net output files: ibdiagnet.db, ibdiagnet.sm and ibdiagnet.pm.
Syntax Description filename The imported file. It is an output of the ibdiagnet tool
that has previously run on any node connected to the
fabric, and is assumed to be a zip file with a .gz or .tgz
extension.
Default N/A
History 3.1.1400
Role admin
Notes • To display the results of this import, you may run “show ib fabric” commands
(e.g., “show ib fabric node type switch”)
• Imported data can be displayed as long as you do not run the command “ib fabric
refresh”, which overwrites the imported data
• The import command cannot execute without the ibdiagnet.db file
ib fabric monitor
ib fabric monitor
no ib fabric monitor
Default N/A
History 3.1.1400
Role admin
Notes
ib fabric nodenames
ib fabric nodenames
no ib fabric nodenames
Default N/A
History 3.1.1400
Role admin
Related Commands
Notes
ib fabric refresh
ib fabric refresh
Default N/A
History 3.1.1400
Role admin
Notes If the fabric is large, this command may take a long time to complete.
this command requires license (LIC-fabric-inspector)
ib fabric transceiver-info
ib fabric transceiver-info enable
no ib fabric transceiver-info enable
Default N/A
History 3.1.1400
Role admin
Notes
test ib fabric
test ib fabric [route]
Default N/A
History 3.1.0000
Role monitor/admin
---------------------------------------------
Discovery
-I- Discovering ... 1 nodes (1 Switches & 0 CA-s) discovered.
-I- Discovery finished successfully
---------------------------------------------
Lids Check
-E- Lids Check finished with errors
---------------------------------------------
Links Check
-I- Links Check finished successfully
---------------------------------------------
Subnet Manager
-I- SM Info retrieving finished successfully
---------------------------------------------
Port Counters
-I- Lids Check failed, no response for some MADs can occurred
-I- Ports counters retrieving finished successfully
-I- Ports counters Difference Check will be skipped - pause time is zero
---------------------------------------------
Nodes Information
-I- Lids Check failed, no response for some MADs can occurred
-W- Nodes Info retrieving finished with errors
---------------------------------------------
Speed / Width checks
-I- Link Speed Check (Compare to supported link speed)
-I- Links Speed Check finished successfully
---------------------------------------------
Summary
-I- Stage Warnings Errors Comment
-I- Discovery 0 0
-I- Lids Check 0 1
-I- Links Check 0 0
-I- Subnet Manager 0 1
-I- Port Counters 0 0
-I- Nodes Information 1 0
-I- Speed / Width checks 0 0
...
switch (config) #
Related Commands
Notes
Default N/A
History 3.1.1400
Role admin
Related Commands
Notes
Default N/A
History 3.1.1400
Role admin
0:
Error : No SM on fabric
1:
Warning: Port m_key_violations found
Additional information:
port E4:1D:2D:03:00:5D:1E:A4-0001
2:
Warning: Port m_key_violations found
Additional information:
port E4:1D:2D:03:00:68:EA:CA-0001
3:
Warning: Loopback cable
Additional information:
port 7C:FE:90:03:00:A5:A4:60-0035
port 7C:FE:90:03:00:A5:A4:60-0036
Related Commands
Notes
Displays the InfiniBand fabric monitor admin state and statistics count.
Default N/A
History 3.1.1400
Role admin
Related Commands
Notes
Default N/A
History 3.1.1400
Role admin
Related Commands
Notes
Default N/A
History 3.1.1400
Role admin
------------------------------------------------------------------------------
Type Port Desc State Rate
------------------------------------------------------------------------------
CA 7C:FE:90:03:00:6F:3A:6B-0001 Port 1 Link Up 100 Gbps
Related Commands
Notes
Default N/A
History 3.1.1400
Role admin
Related Commands
Notes
Default N/A
History 3.1.1400
Role admin
Related Commands
Notes
Default
History 3.1.1400
Role admin
Related Commands
Notes
Default N/A
History 3.6.6000
Role admin
Related Commands
Notes
Default N/A
History 3.1.1400
Role admin
Related Commands
Notes
Displays InfiniBand fabric info on a specific system as well as a list of node info.
Default N/A
History 3.1.1400
Role admin
----------------------------------------------------------------------
Node GUID Role Ports Type Description
----------------------------------------------------------------------
F4:52:14:03:00:71:55:30 standalone 36 SW PCI 52000:713
Related Commands
Notes
Displays InfiniBand fabric info on a specific system as well as a list of port info.
Default N/A
History 3.1.1400
Role admin
------------------------------------------------------------------------------
Type Port Desc State Rate
------------------------------------------------------------------------------
SW F4:52:14:03:00:71:55:30-0000 Switch port 0 Link Up 10 Gbps
SW F4:52:14:03:00:71:55:30-0001 Port 1 Link Up 100 Gbps
SW F4:52:14:03:00:71:55:30-0002 Port 2 Link Up 100 Gbps
SW F4:52:14:03:00:71:55:30-0003 Port 3 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0004 Port 4 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0005 Port 5 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0006 Port 6 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0007 Port 7 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0008 Port 8 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0009 Port 9 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0010 Port 10 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0011 Port 11 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0012 Port 12 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0013 Port 13 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0014 Port 14 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0015 Port 15 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0016 Port 16 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0017 Port 17 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0018 Port 18 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0019 Port 19 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0020 Port 20 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0021 Port 21 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0022 Port 22 Polling Up to 100 Gbps
SW F4:52:14:03:00:71:55:30-0024 Port 23 Link Up 56 Gbps
...
Related Commands
Notes
Mellanox switch systems comply by default with NIST SP 800-131A as described in the table
below.
A.1 Overview
This appendix describes how to enhance the security of a system in order to comply with the
NIST SP 800-131A standard. This standard is a document which defines cryptographically
“acceptable” technologies. This document explains how to protect against possible cryptographic
vulnerabilities in the system by using secure methods. Because of compatibility issues, this secu-
rity state is not the default of the system and it should be manually set.
Some protocols, however, cannot be operated in a manner that complies with the NIST
SP 800-131A standard.
For more details and parameters refer to the command crypto certificate name in the
Mellanox MLNX-OS User Manual.
When no options are selected, the generated certificate uses the default values for each
field.
To test strict mode connect to the WebUI using HTTPS and get the certificate. Search for
“signature algorithm”.
There are other ways to configure the certificate to sha256. For example, it is possible to
use certificate generation default hash-algorithm and then regenerate the
certificate using these default values. Please refer to the Mellanox MLNX-OS User Man-
ual for further details.
A.4 SNMP
SNMPv3 supports configuring username, authentication keys and privacy keys. For authentica-
tion keys it is possible to use MD5 or SHA. For privacy keys AES or DES are to be used.
To configure strict mode, create a new user with HMAC-SHA1-96 and AES-128. Run:
switch (config) # snmp-server user <username> v3 auth sha <password1> priv aes-128
<password2>
To test strict mode, configure users and check them using the CLI, then run an SNMP
request with the new users.
For more information please refer to the Mellanox MLNX-OS User Manual.
SNMPv1 and SNMPv2 are not considered to be secure. To run in strict mode, only use
SNMPv3.
A.5 SSH
The SSH server on the switch by default uses secure ciphers only, message authentication code
(MAC), key exchange methods, and public key algorithm. When configuring SSH server to strict
mode, the aforementioned security methods only use approved algorithms as detailed in the
NIST 800-181A specification and the user can connect to the switch via SSH in strict mode only.
The following ciphers are disabled for SSH when strict security is enabled:
• 3des-cbc
• aes256-cbc
• aes192-cbc
• aes128-cbc
• arcfour
• blowfish-cbc
• cast128-cbc
• [email protected]
The no form of the command disables strict security mode.
Make sure to configure the SSH server to work with minimum version 2 since 1 is vulnerable to
security breaches.
To configure min-version to strict mode, run:
switch (config) # ssh server min-version 2
Once this is done, the user cannot revert back to minimum version 1.
A.6 HTTPS
By default, MLNX-OS supports HTTPS encryption using TLS1.2 only. Working in TLS1.2
mode also bans MD5 ciphers which are not allowed per NIST 800-131a. In strict mode, the
switch supports encryption with TLS1.2 only with the following supported ciphers:
• RSA_WITH_AES_128_CBC_SHA256
• RSA_WITH_AES_256_CBC_SHA256
• DHE_RSA_WITH_AES_128_CBC_SHA256
• DHE_RSA_WITH_AES_256_CBC_SHA256
• TLS_RSA_WITH_AES_128_GCM_SHA256
• TLS_RSA_WITH_AES_256_GCM_SHA384
• TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
A.7 LDAP
By default, supports LDAP encryption SSL version 3 or TLS1.0 up to TLS1.2. The only banned
algorithm is MD5 which is not allowed per NIST 800-131a. In strict mode, the switch supports
encryption with TLS1.2 only with the following supported ciphers:
• DHE-DSS-AES128-SHA256
• DHE-RSA-AES128-SHA256
• DHE-DSS-AES128-GCM-SHA256
• DHE-RSA-AES128-GCM-SHA256
Both modes operate using SSL. The different lies in the connection initialization and the
port used.
Now you can access your Splunk WebUI at http://IP:8000/ or http://hostname:8000/. You need to
make sure that port 8000 is open in your server firewall.
Read-only communities:
public
Summary configuration:
Step 9. Click the TCP or UDP button to choose between a TCP or UDP input, and enter a port num-
ber in the “Port” field.
Step 10. In the “Source name override” field, enter a new source name to override the default source
value, if required.
B.5.2 Configuration
Login to the Splunk WebUI and go to Manager > Add Data > Monitor > SNMP > New, and set
up your input data.
Step 15. You can add to search any value that is relevant for you.
Patterns can be viewed not on real time and you can create alert on most repeatable
events.