- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Networking
- >
- Teaming behavior
Networking
1753701
Members
4994
Online
108799
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2008 09:33 PM
тАО09-28-2008 09:33 PM
Teaming behavior
Hello,
recently we configured to one of our client DL380 (win2k3 se)with teaming that includes 2 nic's HP NC373i type.
the nic's are configured with 802.3ad Dynamic with fault tolerance , the switch that they attached support IEEE 802.3ad the LACP is shown to work correctly.
Next we have been requested to test the teaming throughput to show 2Gbit link, we picked another DL380 with same Teaming and used IPERF utility to simulate TCP stream
from one to destination only send the results are showing 110MBytes/s that corresponds to 1Gbit link.
also using second DL380 both iperf send to teamed DL380 server we get about 52_+ MByte/s each.
But when we open second instance of IPERF( using only one source server) with both iperf dual send receive in same time to destination we get about 210Mbytes/s
My question is how especially teaming (802.3ad Dynamic with fault tolerance)behave and load/scale balance, is per session or process? this is not clear to me.
Please Advise
Thanks in advanced
recently we configured to one of our client DL380 (win2k3 se)with teaming that includes 2 nic's HP NC373i type.
the nic's are configured with 802.3ad Dynamic with fault tolerance , the switch that they attached support IEEE 802.3ad the LACP is shown to work correctly.
Next we have been requested to test the teaming throughput to show 2Gbit link, we picked another DL380 with same Teaming and used IPERF utility to simulate TCP stream
from one to destination only send the results are showing 110MBytes/s that corresponds to 1Gbit link.
also using second DL380 both iperf send to teamed DL380 server we get about 52_+ MByte/s each.
But when we open second instance of IPERF( using only one source server) with both iperf dual send receive in same time to destination we get about 210Mbytes/s
My question is how especially teaming (802.3ad Dynamic with fault tolerance)behave and load/scale balance, is per session or process? this is not clear to me.
Please Advise
Thanks in advanced
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-29-2008 05:52 AM
тАО09-29-2008 05:52 AM
Re: Teaming behavior
Default, Load Balancing should be done by session, you can check the info below to get more info on Cisco LACP load balancing and the transmit methods supported by hp.
http://www.cisco.com/en/US/docs/ios/cether/configuration/guide/ce_lnkbndl.html#wp1053763
http://h18004.www1.hp.com/products/servers/networking/whitepapers.html
rgds,
lmm
http://www.cisco.com/en/US/docs/ios/cether/configuration/guide/ce_lnkbndl.html#wp1053763
http://h18004.www1.hp.com/products/servers/networking/whitepapers.html
rgds,
lmm
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-04-2008 01:55 AM
тАО10-04-2008 01:55 AM
Re: Teaming behavior
Balancing network traffic on a server can increase the throughput on the server and the network, enhancing performance in addition to providing basic fault tolerance. HP's load balancing distributes network traffic among the members of a network adapter (NIC) team to utilize all available network paths. The HP Network Configuration Utility provides a user-friendly method to configure load balancing and to view the resulting distribution of network traffic. HP makes this technology available to all HP ProLiant customers running Microsoft Windows operating systems. This paper describes the load balancing options available through the HP Network Configuration Utility
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP