|
A server is often equipped with two or more network adapters. When a server connects to a switch, one network adapter is used for server management and the other network adapters are used for traffic forwarding. In this case, there is much idle time on the network adapter used for server management and switch interfaces, and the bandwidth use efficiency is low. To address this issue, upgrade the server software so that the network adapter used for server management can be also used for traffic forwarding. When the switch uses an Eth-Trunk to connect to the server, one Eth-Trunk member interface can be bound to a VLAN for server management. In addition, service VLANs can be configured on the Eth-Trunk so that service traffic is load balanced on all Eth-Trunk member interfaces. The bandwidth use efficiency is therefore improved.
This function applies to the scenario where a switch connects to a server.Before binding an Eth-Trunk member interface to a VLAN, ensure that the Eth-Trunk member interface is added to the VLAN. Otherwise, the configuration does not take effect.In an Eth-Trunk, only one member interface can be bound to a VLAN or VLANs and one member interface can be bound to a maximum of eight VLANs. Member interfaces of multiple Eth-Trunks can be bound to the same VLAN.The switch supports a maximum of 256 bound VLANs. If N Eth-Trunk member interfaces are bound to M VLANs, the maximum value of N multiplied by M is 256.After this command is configured, packets from the bound VLAN can be only forwarded through the bound Eth-Trunk member interface. Non-unicast traffic on the Eth-Trunk can be only forwarded through the bound Eth-Trunk member interface.When an Eth-Trunk member interface is bound to a VLAN or VLANs, VLAN mapping, VLAN stacking, MUX VLAN, or FCoE VLAN cannot be configured.When an Eth-Trunk member interface is bound to a VLAN or VLANs, M-LAG cannot be configured.
|