- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- Bidirectional load balancing using HP 6127XLG Blad...
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
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
05-25-2017 08:29 AM
05-25-2017 08:29 AM
Bidirectional load balancing using HP 6127XLG Blade Switch
I plan to install a traffic management software on HPE Proliant blades. They are in the middle of the traffic path, (the traffic path being: clients + access network + HPE blades + NAT + Internet). I need to load balance the traffic with layer-4 flow affinity: all traffic with the same IP addresses and ports will go through the same blade in both directions.
I was thinking to use HP 6127XLG Blade Switch, which has a flow-sharing functionality. There seems to be a command to do just that. From page 118 of Layer 3 - IP Services Configuration Guide:
ip load-sharing mode per-flow [ tunnel { inner | outer } | algorithm algorithm-number | [ dest-ip | dest-port | ingress-port | ip-pro | src-ip | src-port ] * ] [ slot slot-number ]
Has anyone used this switch in this scenario?
To keep the affinity on both directions, do I need two switches (one with rules based on destination address/port and the other one with rules based on source address/port)? or can it be done with one single switch playing with the undocumented algorithm-number?
An finally, how will that work in the event of a blade failure? Will the traffic be distributed to the remaining blades?
Thanks in advance!
Luis