Edge-Core ECS4660-28F, Management Manual, Page: 182 / 2020

C
HAPTER
5
| Interface Configuration
Port Configuration
– 182 –
P
ORT
C
ONFIGURATION
This section describes how to configure port connections, mirror traffic
from one port to another, and run cable diagnostics.
C
ONFIGURING BY
P
ORT
L
IST
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.
CLI R
EFERENCES
◆
"Interface Commands" on page 1187
C
OMMAND
U
SAGE
◆
Auto-negotiation must be disabled before you can configure or force an
RJ-45 interface to use the Speed/Duplex mode or Flow Control options.
◆
When using auto-negotiation, the optimal settings will be negotiated
between the link partners based on their advertised capabilities. To set
the speed, duplex mode, or flow control under auto-negotiation, the
required operation modes must be specified in the capabilities list for
an interface.
◆
The Speed/Duplex mode is fixed at 1000full on the Gigabit SFP ports,
and at 10Gfull on the 10 Gigabit ports. When auto-negotiation is
enabled, the attributes which can be advertised include speed, duplex
mode, 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 Gigabit and 10 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 switch), and the payload. This should all be