layerbreak
Enthusiast
- Mitglied seit
- 30.12.2010
- Beiträge
- 590
Also LevelOne sagt mir die Hilfe bei Trunk:
und bei LACP:
Ich hab jetzt mal spaßeshalber Port 6+7 (meinPC) und Port 10+11 (Server) aktiviert bei Key-Value nichts eingetragen, am ESXi nichts verändert. Dann bricht die Durchsatzrate beim Kopieren zusammen.
Wenn ich am ESXi umstelle auf "Anhand des ip-Hashes routen", dann pendelt er sich zusammen gerechnet auf etwas mehr wie 100 Mib/s ein.
Ohne LACP Änderung komm ich aber zusammen schon auf ca. 120 MiB/s.
Ich weis jetzt nicht was besser ist.
---------- Post added at 19:02 ---------- Previous post was at 18:52 ----------
Ich hab ja auch in meinem PC eine Dualport Nic drinne und die ist inzwischen ja auch geteamt und jetzt will ich vnic4 und vnic5 am ESXi auch teamen.
Was meinst du jetzt mit "entsprechendem Client"?
Mein PC ist halt Win7Pro, Server ESXi 5.1 und VM ist Openindiana.
Die Kopieraktion habe ich mit zwei mal gestartetem SpeedCommander durchgeführt. Ob das jetzt eine Verbindung ist oder zwei - keine Ahnung.
Was bremst ist mein PC da sicherlich die HD, IMHO nicht Openindiana, da der Pool aus 5 Mirrors besteht.
This page allows you to create a maximum of eight trunks of up to eight ports each. The Membership Table has one row for each port and ten columns. Each row contains nine radio buttons which are used to indicate which trunk (if any) the port belongs to. Each radio button is in a column of its own. The columns are:
Port - The front-panel port-number of the port.
Not a Trunk Member - If the radio button in this column is selected, the port is not a member of any trunks. This is the default state.
Columns Trunk T1 through Trunk T8 - These columns correspond to the eight trunks that are supported by the Switch. Clicking on the radio button in any one of these columns causes the port to become a member of the corresponding trunk.
When a trunk is first created it is given the following, default configuration:
Speed/Duplex is set to Auto Speed (see TRUNKS > Settings)
Flow Control is turned off (see TRUNKS > Settings)
Rate Limiting is turned off (see TRUNKS > Rate Limiting)
The trunk is a member of VLAN 1 with a PVID of 1. The trunk will accept both tagged and untagged packets (see VLANS > VLAN Settings)
Ports that are removed from the trunk, retain the configuration that they had when members of the trunk. Ports that are added to the trunk after its creation, inherit the current configuration of the trunk.
There are three main buttons associated with this page:
HELP - Displays this window.
APPLY - Updates the Switch configuration. No changes are made to the configuration until this button is pressed.
CANCEL - All changes made to the page are discarded and the Switch configuration remains unchanged.
Port - The front-panel port-number of the port.
Not a Trunk Member - If the radio button in this column is selected, the port is not a member of any trunks. This is the default state.
Columns Trunk T1 through Trunk T8 - These columns correspond to the eight trunks that are supported by the Switch. Clicking on the radio button in any one of these columns causes the port to become a member of the corresponding trunk.
When a trunk is first created it is given the following, default configuration:
Speed/Duplex is set to Auto Speed (see TRUNKS > Settings)
Flow Control is turned off (see TRUNKS > Settings)
Rate Limiting is turned off (see TRUNKS > Rate Limiting)
The trunk is a member of VLAN 1 with a PVID of 1. The trunk will accept both tagged and untagged packets (see VLANS > VLAN Settings)
Ports that are removed from the trunk, retain the configuration that they had when members of the trunk. Ports that are added to the trunk after its creation, inherit the current configuration of the trunk.
There are three main buttons associated with this page:
HELP - Displays this window.
APPLY - Updates the Switch configuration. No changes are made to the configuration until this button is pressed.
CANCEL - All changes made to the page are discarded and the Switch configuration remains unchanged.
This page enables you to setup the configuration of LACP on all or some ports. LACP (IEEE 802.3ad Link Aggregation Protocol) provides a way to set up aggregation automatically between switches. The LACP Setup table has one row for each port and three columns. The columns are:
Port - The front-panel port-number of the port. This cannot be changed.
Enabled - Enable LACP on the associated port.
Key Value - Setup key value for each port.
There are three main buttons associated with this page:
HELP - Displays this window.
Apply - Updates the configuration. No changes are made to the configuration until this button is pressed.
Refresh - Refreshes the page with the current configurations.
LACP Introduction
LACP (IEEE 802.3ad Link Aggregation Protocol) provides a way to set up aggregation automatically between switches. LACP configured ports can automatically negotiate a trunked link with LACP-configured ports on another device. You can configure any number of ports on the switch as LACP, as long as they are not already configured as part of a static trunk. If ports on another device are also configured as LACP, the switch and the other device will negotiate a trunk link between them. On the other hand, static trunks have to be manually configured at both ends of the link.
Enabled
To avoid creating a loop in the network, be sure you enable LACP before connecting the ports, and also disconnect the ports before disabling LACP.
If the target switch has also enabled LACP on the connected ports, the trunk will be activated automatically.
All ports on both ends of an LACP trunk must be configured for full duplex, either by forced mode or auto-negotiation.
Trunks dynamically established through LACP will also be shown in the LACP Status.
Key Value
Key value must be between 1 - 255. Auto means autogenerated key.
The LACP key must be set to the same value for ports that belong to the same LACP group.
Port - The front-panel port-number of the port. This cannot be changed.
Enabled - Enable LACP on the associated port.
Key Value - Setup key value for each port.
There are three main buttons associated with this page:
HELP - Displays this window.
Apply - Updates the configuration. No changes are made to the configuration until this button is pressed.
Refresh - Refreshes the page with the current configurations.
LACP Introduction
LACP (IEEE 802.3ad Link Aggregation Protocol) provides a way to set up aggregation automatically between switches. LACP configured ports can automatically negotiate a trunked link with LACP-configured ports on another device. You can configure any number of ports on the switch as LACP, as long as they are not already configured as part of a static trunk. If ports on another device are also configured as LACP, the switch and the other device will negotiate a trunk link between them. On the other hand, static trunks have to be manually configured at both ends of the link.
Enabled
To avoid creating a loop in the network, be sure you enable LACP before connecting the ports, and also disconnect the ports before disabling LACP.
If the target switch has also enabled LACP on the connected ports, the trunk will be activated automatically.
All ports on both ends of an LACP trunk must be configured for full duplex, either by forced mode or auto-negotiation.
Trunks dynamically established through LACP will also be shown in the LACP Status.
Key Value
Key value must be between 1 - 255. Auto means autogenerated key.
The LACP key must be set to the same value for ports that belong to the same LACP group.
Ich hab jetzt mal spaßeshalber Port 6+7 (meinPC) und Port 10+11 (Server) aktiviert bei Key-Value nichts eingetragen, am ESXi nichts verändert. Dann bricht die Durchsatzrate beim Kopieren zusammen.
Wenn ich am ESXi umstelle auf "Anhand des ip-Hashes routen", dann pendelt er sich zusammen gerechnet auf etwas mehr wie 100 Mib/s ein.
Ohne LACP Änderung komm ich aber zusammen schon auf ca. 120 MiB/s.
Ich weis jetzt nicht was besser ist.
---------- Post added at 19:02 ---------- Previous post was at 18:52 ----------
Das stimmt so ohne weiteres aber nicht für das was er eigentlich vorhatte: Teaming/Bonding/Trunking - ich hatte auf meiner alten Workstation ne Intel Dualport geteamt und von einem Server (ebenfalls geteamt) auf ein RAID10 (mit schnellen SAS HDDs, später ein RAID1 mit SSDs) regelmäßig recht große Daten gezogen. Da war deutlich mehr als die ~125MB drin die theoretisch möglich wären über 1Gbit - es waren halt 2 gebündelte Gbit Kanäle. Das braucht also bei entsprechendem Client nicht zwangsweise auch 2 Verbindungen. Und die hätte er ja auch wenn er seinen PC mit 2 NICs ebenfalls Teamen kann. Das seine HDD limitiert ist ja was anderes
Ich hab ja auch in meinem PC eine Dualport Nic drinne und die ist inzwischen ja auch geteamt und jetzt will ich vnic4 und vnic5 am ESXi auch teamen.
Was meinst du jetzt mit "entsprechendem Client"?
Mein PC ist halt Win7Pro, Server ESXi 5.1 und VM ist Openindiana.
Die Kopieraktion habe ich mit zwei mal gestartetem SpeedCommander durchgeführt. Ob das jetzt eine Verbindung ist oder zwei - keine Ahnung.
Was bremst ist mein PC da sicherlich die HD, IMHO nicht Openindiana, da der Pool aus 5 Mirrors besteht.