Web Management Guide

Table Of Contents
Chapter 4
| Interface Configuration
Port Configuration
– 104
Port Configuration
This section describes how to configure port connections, mirror traffic from one
port to another, and run cable diagnostics.
Configuring by Port
List
Use the Interface > Port > General (Configure by Port List) page to enable/disable
an interface, set auto-negotiation and the interface capabilities to advertise, or
manually fix the speed, duplex mode, and flow control.
Command Usage
10GBASE-SFP+ connections are fixed at 10G - full duplex, and 40GBASE-QSFP+
connections at 40G - full duplex. Auto-negotiation must be disabled before you
can configure or force an RJ-45 interface to use the Flow Control option.
When using auto-negotiation
1
, the optimal settings will be negotiated
between the link partners based on their advertised capabilities. To set flow
control and symmetric pause frames under auto-negotiation, the required
operation modes must be specified in the capabilities list for an interface.
The Speed/Duplex mode is fixed at 100full for 100BASE-FX transceivers,
1000full for Gigabit transceivers, and 10Gfull for 10 Gigabit transceivers. When
auto-negotiation is enabled
1
, the only attributes which can be advertised
include flow control and symmetric pause frames.
Using Jumbo Frames
Use the jumbo frame attribute on the System > Capability page to enable or
disable jumbo frames for all 10 Gigabit and 40 Gigabit Ethernet ports. Then
specify the required MTU size for a specific interface on the port configuration
page.
The comparison of packet size against the configured port MTU considers only
the incoming packet size, and is not affected by the fact that an ingress port is a
tagged port or a QinQ ingress port. In other words, any additional size (for
example, a tagged field of 4 bytes added by the chip) will not be considered
when comparing the egress packet’s size against the configured MTU.
When pinging the switch from an external device, information added for the
Ethernet header can increase the packet size by at least 42 bytes for an
untagged packet, and 46 bytes for a tagged packet. If the adjusted frame size
exceeds the configured port MTU, the switch will not respond to the ping
message.
For other traffic types, calculation of overall frame size is basically the same,
including the additional header fields SA(6) + DA(6) + Type(2) + VLAN-Tag(4)
(for tagged packets, for untaqged packets, the 4-byte field will not be added by
1. Support for auto-negotiation depends on transceiver type, such as 1G SFP.