Je souhaiterai mettre en place le mode "trunking" à l'aide des deux interfaces réseau et de mon Switch Netgear (GS724T). Côté serveur, la team a bien été créée, mais ensuite je ne sais pas quelle option choisir (le mode automatique ne fonctionne pas) toutes les données passent par une seule interface... :/
§ Automatic (Recommended). Default setting. The system automatically selects the best team type or combination of team features based on the configuration of the adapters in the team. 802.3ad will be used to place team members into port trunks/channels, if possible. All transmit packets are load balanced among all team members based on a Load Balancing algorithm in the teaming device driver. The receive packets are load balanced among all team members by the switch. If a failure of any team member occurs, the packets are load balanced among the remaining adapters. If a team contains an iSCSI-enabled adapter, you cannot use the Automatic setting. § 802.3ad Dynamic Dual Channel Load Balancing (INP). Available in the ProLiant Essentials Intelligent Networking Pack only. There must be a minimum of two adapters in a dual channel team. All team members within each group are dynamically placed into a port-trunk/channel by dynamic protocol agreement (LACP) with the switch. A failure of a team member to synchronize joining a port-trunk or channel with the switch is treated as an error and that team member is considered failed. All transmit packets are load balanced among all team members based on a Load Balancing algorithm in the teaming device driver. The receive packets are load balanced among all team members by the switch. If a failure of any team member occurs, the packets are load balanced among the remaining adapters. If a team contains an iSCSI-enabled adapter, you cannot use the 802.3ad Dynamic Dual Channel Load Balancing (INP) setting. § Switch-assisted Dual Channel Load Balancing (INP). Available in the ProLiant Essentials Intelligent Networking Pack only. There must be a minimum of two adapters in a dual channel team and a minimum of one adapter per group. One group of team members is treated as an SLB group to one switch, and a second group of team members is treated as an SLB group to a second switch. All transmit packets are load balanced among all team members based on a Load Balancing algorithm in the teaming device driver. The receive packets are load balanced among all team members by the switch. If a failure of any team member occurs, the packets are load balanced among the remaining adapters. Only Gigabit adapters can be used for Switch-assisted Dual Channel Load Balancing. When you select Switch-assisted Dual Channel Load Balancing, the Team Members window becomes Team Members Grouping and displays two windows labeled Group A and Group B. The up and down arrows are used to assign the members to be in Group A and Group B. If a team contains an iSCSI-enabled adapter, you cannot use the Switch-assisted Dual Channel Load Balancing (INP) setting. § 802.3ad Dynamic with Fault Tolerance. All team members are dynamically placed into a port-trunk/channel by dynamic protocol agreement (LACP) with the switch. A failure of a team member to synchronize joining a port-trunk or channel with the switch is treated as an error and that team member is considered failed. All transmit packets are load balanced among all team members based on a Load Balancing algorithm in the teaming device driver. The receive packets are load balanced among all team members by the switch. If a failure of any team member occurs, the packets are load balanced among the remaining adapters. If a team contains an iSCSI-enabled adapter, you cannot use the 802.3ad Dynamic with Fault Tolerance setting. § Switch-assisted Load Balancing with Fault Tolerance (SLB). All transmit packets are load balanced among all team members based on a Load Balancing algorithm in the teaming device driver. The receive packets are load balanced among all team members by the switch. If a failure of any team member occurs, the packets are load balanced among the remaining adapters. There is no Primary adapter in a Switch-assisted Load Balancing team. § Transmit Load Balancing with Fault Tolerance (TLB). All transmit IP packets are load balanced among all team members based on a Load Balancing algorithm in the teaming device driver. The Current Primary adapter transmits all non-IP packets, and receives all frames for the team. If a failover event occurs, one of the non-Primary adapters assumes the role of Current Primary adapter, and transmit IP packets are load balanced among all remaining team members. If a failure occurs in any of the non-Primary adapters, the packets are load balanced among all remaining team members. § Transmit Load Balancing with Fault Tolerance and Preference Order. All transmitted IP packets are load balanced among all team members based on a Load Balancing algorithm in the teaming device driver. The Current Primary adapter transmits all non-IP packets, and receives all frames for the team. If a failover event occurs, one of the non-Primary adapters assumes the role of Current Primary adapter, and transmitted IP packets are load balanced among all remaining team members. If a failure occurs in any of the non-Primary adapters, the packets are load balanced among all remaining team members. The user sets the priority of the adapters relative to each other within the team. The priority of the adapters is an additional consideration when determining the Primary adapter. § Network Fault Tolerance Only (NFT). NFT provides the safety of an additional backup link between the server and hub/switch. NFT is implemented with a Primary adapter and a Secondary (backup) adapter(s). During normal operations, if the Primary adapter fails, the link to the Secondary adapter automatically takes over. § Network Fault Tolerance only (NFT) with Preference Order. NFT provides the safety of an additional backup link between the server and hub/switch. NFT is implemented with a Primary adapter and a Secondary (backup) adapter(s). During normal operations, if the Primary adapter fails, the link to the Secondary adapter automatically takes over. The user sets the priority of the adapters relative to each other within the team. The priority of the adapters is an additional consideration when determining the Primary adapter. · Transmit Load Balancing Method. Select or change the Transmit Balancing Method for the team. If the team type is Network Fault Tolerance Only with Preference Order or Network Fault Tolerance Only (NFT), this control is disabled and Automatic is selected. § Automatic. (Recommended) Default setting. Teaming driver selects the load balancing mechanism based on the packet type. § TCP Connection. Load balances transmit TCP packets using the TCP connection. § Destination IP Address. Load balances transmit IP packets using the last four bits of the destination IP Address. § Destination MAC Address. Load balances transmit IP packets using the last four bits of the destination MAC Address. § Round Robin (Packet order not guaranteed). Load balances transmit IP packets among all team members. A packet is sent on one team member then the next packet is sent out on the next team member and so on. When the last team member is utilized, the rotation begins again.Au niveau du switch j'ai activé le "trunking" sur les ports 13 & 14.