- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- ProCurve LAG load balancing methods.
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
04-20-2016 09:38 PM
04-20-2016 09:38 PM
ProCurve LAG load balancing methods.
Hello there.
I got 2 ProCurve 6120XG switches (hp c7000 onboard). I`m currently reading user guide http://h10032.www1.hp.com/ctg/Manual/c01868095.pdf and I am confused about load balancing methods within a trunk group.
I see there are few methods:
ProCurve 6120XG Switch Right(config)# trunk-load-balance L2-based Load balance based on Layer 2 information. L3-based Load balance based on Layer 3 information (if present) or Layer 2 information; this is the default. L4-based Load balance based on Layer 4 information (if present), or Layer 3 (if present), or Layer 2. source-mac-based Load balance based on source MAC address information.
And this is quote from the user guide (about L3 method):
When an IP address is available, the calculation includes the last five bits of the IP source address and IP destination address, otherwise the MAC addresses are used.
How can it be? I mean IP address is always available, but mac address is not, e.g. if the destination host resides behind the gateway. In this case the source knows the destination IP, but the destination MAC address is available only to gateway. So the method should work like "if the mac address available - use it, if not - use IP address", isn`t it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2016 09:32 AM
04-21-2016 09:32 AM
Re: ProCurve LAG load balancing methods.
Ethernet frames always contain ethernet source/dest mac addresses.
But not all ethernet frames contain IPv4 addresses: Bot only relics from the past like IPX adn BETBUI, but als loopdetection, spanning tree....and ipv6