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

HP Mellanox SX1018 Mellanox MLNX-OS® User Manualfor SX1018HP Ethernet - Page 83

Header Format, 10.1.4 Congestion Control

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

Page 83 highlights

Rev 1.6.9 The system on the receiving end of the analyzer port must be set to handle the egress traffic. If it is not, it might discard it and indicate this in its statistics (packet too long). 5.10.1.3 Header Format Ingress traffic from the source interface can be manipulated in several ways depending on the network layout using the command header-format. If the analyzer system is directly connected to the destination interface, then the only parameters that can be configured on the port are the MTU, speed and port based flow control. Priority flow control is not supported is this case. However, if the analyzer system is indirectly connected to the destination interface, there are two options for switching the mirrored data to the analyzer system: • A VLAN tag may be added to the Ethernet header of the mirrored traffic • An Ethernet header can be added with include a new destination address and VLAN tag It must be taken into account that adding headers increases packet size. Source Frame DA SA Type/ Len Data Figure 12: Header Format Options Mirror Frame local DA SA Type/ Len Data Source Frame DA SA Type/ Len Data add‐vlan Mirror Frame DA SA 0x8100 VLAN Type/ Len Data Source Frame DA SA Type/ Len Data add‐ethernet‐header Mirror Frame DA SA 0x8949 DA SA Type/ Len Data Source Frame add‐ethernet‐header DA SA Type/ Len Data (+vlan) Mirror Frame DA SA 0x8100 VLAN 0x8949 DA SA Type/ Len Data 5.10.1.4 Congestion Control The destination ports might receive pause frames that lead to congestion in the switch port. In addition, too much traffic directed to the analyzer port (for example 40GbE mirror port is directed into 10G analyzer port) might also lead to congestion. In case of congestion: • When best effort mode is enabled on the analyzer port, SwitchX drops excessive traffic headed to the analyzer port using tail drop mechanism, however, the regular data (mirrored data heading to its original port) does not suffer from a delay or drops due to the analyzer port congestion. • When the best effort mode on the analyzer port is disabled, the SwitchX does not drop the excessive traffic. This might lead to buffer exhaustion and data path packet loss. Mellanox Technologies 83 Mellanox Technologies Confidential

Section	Page
Mellanox MLNX-OS® User Manual for SX1018HP Ethernet Managed Blade Switch	1
Document Revision History	6
About this Manual	7
1 Introduction	10
1.1 MLNX-OS Features	10
2 Getting Started	12
2.1 Configuring the Switch for the First Time	12
2.1.1 Re-Running the Wizard	17
2.2 Starting the Command Line (CLI)	17
2.3 Starting the Web Interface	18
2.4 Licenses	19
2.4.1 Installing MLNX-OS® License (CLI)	20
2.4.2 Installing MLNX-OS License (Web)	20
2.4.3 Retrieving a Lost License Key	23
3 User Interfaces	24
3.1 Command Line Interface (CLI)	24
3.1.1 CLI Modes	24
3.1.2 Syntax Conventions	25
3.1.3 Getting Help	25
3.1.4 Prompt and Response Conventions	26
3.1.5 Using the “no” Form	27
3.1.6 Parameter Key	28
3.2 Web Interface	29
3.2.1 Setup Menu	30
3.2.2 System Menu	31
3.2.3 Security Menu	32
3.2.4 Ports Menu	32
3.2.5 Status Menu	33
3.2.6 IB SM Mgmt	33
3.2.7 Fabric Inspector	34
3.2.8 ETH Mgmt	35
4 System Management	36
4.1 Management Interface	36
4.1.1 Configuring Management Interfaces with Static IP Addresses	36
4.1.2 Configuring IPv6 Address on the Management Interface	36
4.1.3 Dynamic Host Configuration Protocol (DHCP)	36
4.1.4 Default Gateway	37
4.1.5 In-Band Management	37
4.2 Software Management	38
4.2.1 Upgrading MLNX-OS® Software	38
4.2.2 Deleting Unused Images	42
4.2.3 Downgrading MLNX-OS Software	42
4.2.3.1 Downloading Image	43
4.2.3.2 Downgrading Image	43
4.2.3.3 Switching to Partition with Older Software Version	45
4.2.4 Upgrading System Firmware	45
4.2.4.1 After Updating MLNX-OS Software	45
4.2.4.2 Importing Firmware and Changing the Default Firmware	46
4.3 File Management	46
4.3.1 Saving a Configuration File	46
4.3.2 Loading a Configuration File	47
4.3.3 Restoring Factory Default Configuration on a Switch System (Single Management Module)	47
4.4 Managing Configuration Files	47
4.4.1 BIN Configuration Files	48
4.4.2 Text Configuration Files	48
4.5 Logging	49
4.5.1 Monitor	49
4.5.2 Remote Logging	49
4.6 Event Notifications	49
4.6.1 Supported Events	50
4.6.2 SNMP Trap Notifications	51
4.6.3 Terminal Notifications	51
4.6.4 Email Notifications	51
4.7 USB Support	53
4.7.1 Accessing a USB Device for Read/Write	53
4.8 Diagnostics	53
4.8.1 Retrieving Return Codes when Executing Remote Commands	53
4.9 mDNS	53
4.10 User Management and Security	54
4.10.1 Authentication, Authorization and Accounting (AAA)	54
4.10.1.1 RADIUS	54
4.10.1.2 TACACS+	55
4.10.1.3 LDAP	55
4.10.2 Secure Shell (SSH)	56
4.10.2.1 Adding a Host and Providing an SSH Key	56
4.10.3 User Accounts	56
4.11 Network Management Interfaces	57
4.11.1 SNMP	57
4.11.1.1 Standard MIBs	57
4.11.1.2 Private MIB	59
4.11.1.3 Mellanox Private Traps	59
4.11.1.4 Configuring SNMP	60
4.11.1.5 Configuring an SNMPv3 User	60
4.11.1.6 Configuring an SNMP Notification	61
4.11.2 MLNX-OS XML API	62
5 Ethernet Switching	63
5.1 Interface	63
5.1.1 Break-Out Cables	63
5.1.1.1 Changing the Module Type to a Split Mode	65
5.1.1.2 Unsplitting a Split Port	65
5.2 Link Aggregation Group (LAG)	66
5.2.1 Configuring Static Link Aggregation Group (LAG)	66
5.2.2 Configuring Link Aggregation Control Protocol (LACP)	67
5.3 VLANs	67
5.3.1 Configuring Access Mode and Assigning Port VLAN ID (PVID)	68
5.3.2 Configuring Hybrid Mode and Assigning Port VLAN ID (PVID)	68
5.3.3 Configuring Trunk Mode VLAN Membership	69
5.3.4 Configuring Hybrid Mode VLAN Membership	69
5.4 MAC Address Table	70
5.4.1 Configuring Unicast Static MAC Address	70
5.5 Spanning Tree	70
5.5.1 Port Priority and Cost	71
5.5.2 Port Type	71
5.5.3 BPDU Filter	71
5.5.4 Loop Guard	72
5.5.5 Root Guard	72
5.6 IGMP Snooping	72
5.6.1 Configuring IGMP Snooping	73
5.6.2 Defining a Multicast Router Port on a VLAN	73
5.7 Link Layer Discovery Protocol (LLDP)	74
5.7.1 Configuring LLDP	74
5.8 Quality of Service (QoS)	75
5.8.1 Priority Flow Control and Link Level Flow Control	75
5.8.2 Enhanced Transmission Selection (ETS)	77
5.9 Access Control List	79
5.9.1 Configuring Access Control List	79
5.9.2 ACL Actions	80
5.10 Port Mirroring	80
5.10.1 Mirroring Sessions	81
5.10.1.1 Source Interface	81
5.10.1.2 Destination Interface	82
5.10.1.3 Header Format	83
5.10.1.4 Congestion Control	83
5.10.1.5 Truncation	84
5.10.2 Configuring Mirroring Sessions	84
5.10.3 Verifying Mirroring Sessions	85
5.11 sFlow	86
5.11.1 Flow Samples	86
5.11.2 Statistical Samples	87
5.11.3 sFlow Datagrams	87
5.11.4 Sampled Interfaces	87
5.11.5 Configuring sFlow	87

Match case Limit results 1 per page

Rev 1.6.9

Mellanox Technologies

Mellanox Technologies Confidential

The system on the receiving end of the analyzer port must be set to handle the egress traffic. If it

is not, it might discard it and indicate this in its statistics (packet too long).

5.10.1.3 Header Format

Ingress traffic from the source interface can be manipulated in several ways depending on the

network layout using the command

header-format

If the analyzer system is directly connected to the destination interface, then the only parameters

that can be configured on the port are the MTU, speed and port based flow control. Priority flow

control is not supported is this case. However, if the analyzer system is indirectly connected to

the destination interface, there are two options for switching the mirrored data to the analyzer

system:

•

A VLAN tag may be added to the Ethernet header of the mirrored traffic

•

An Ethernet header can be added with include a new destination address and VLAN tag

Figure 12: Header Format Options

Source

Frame

Mirror

Frame

Source

Frame

Mirror

Frame

Source

Frame

Mirror

Frame

Source

Frame

Mirror

Frame

Data

Type/

Len

Data

Type/

Len

Data

Type/

Len

Data

Type/

Len

Data

Type/

Len

Data

Type/

Len

0x8949

Data

Type/

Len

0x8949

0x8100

VLAN

Data

Type/

Len

0x8100

VLAN

local

add

‐

vlan

add

‐

ethernet

‐

header

add

‐

ethernet

‐

header

(+vlan)

5.10.1.4 Congestion Control

The destination ports might receive pause frames that lead to congestion in the switch port. In

addition, too much traffic directed to the analyzer port (for example 40GbE mirror port is

directed into 10G analyzer port) might also lead to congestion.

In case of congestion:

•

When best effort mode is enabled on the analyzer port, SwitchX drops excessive traffic

headed to the analyzer port using tail drop mechanism, however, the regular data (mir-

rored data heading to its original port) does not suffer from a delay or drops due to the

analyzer port congestion.

•

When the best effort mode on the analyzer port is disabled, the SwitchX does not drop

the excessive traffic. This might lead to buffer exhaustion and data path packet loss.

It must be taken into account that adding headers increases packet size.

HP Mellanox SX1018 Mellanox MLNX-OS&#174; User Manualfor SX1018HP Ethernet - Page 83

Header Format, 10.1.4 Congestion Control

Page 83 highlights

HP Mellanox SX1018 Mellanox MLNX-OS® User Manualfor SX1018HP Ethernet - Page 83