Web Management Guide-R04

Table Of Contents
Chapter 4
| Interface Configuration
Port Configuration
– 114 –
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
The 1000BASE-T standard does not support forced mode. Auto-negotiation
should always be used to establish a connection over any 1000BASE-T port or
trunk. If not used, the success of the link process cannot be guaranteed when
connecting to other types of switches.
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.
When auto-negotiation is enabled
1
, the only attributes which can be
advertised include speed, duplex mode, flow control and symmetric pause
frames.
Although not covered in the 1000BASE-T standard, auto-negotiation on
1000BASE-T ports must be disabled before you can force an RJ-45 interface to
use the Speed/Duplex mode or Flow Control options. Note that Speed/Duplex
mode is fixed at 100full for 100BASE-FX transceivers, 1000full for Gigabit
transceivers, and 10Gfull for 10 Gigabit transceivers.
Using Jumbo Frames
Use the jumbo frame attribute on the System > Capability page to enable or
disable jumbo frames for all 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 packets 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.
1. Support for auto-negotiation depends on port or transceiver type, such as 1000BASE-T or 1G SFP.