- Community Home
- >
- Networking
- >
- Wireless
- >
- M and MSM Series
- >
- Who Me Too'd this topic
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
Who Me Too'd this topic
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2011 10:42 AM
09-17-2011 10:42 AM
MSM760 Teaming with Internet port
I have a working MSM760 Mobility controller with serveral VSC's, once of which is a captive portal used by guests. I want to add a second controller for redundancy and make it into a team.
Currently, the LAN IP of the controller is the default gateway, and traffic exits through the Internet port. NAT is not used, and our core network routes the VSC's subnet back to the Internet port address.
I understand that teaming creates a virtual LAN IP and I would change the default gateway for the clients to point to it. What I can't figure out is if there is a virtual IP for the Internet port. Obviously, routing all the traffic to the actual IP of one controller defeats the purpose of teaming.
I'm not totally against the idea of changing the VSC to use NAT, but I'm concerned about port exhaustion when scaling 1000 users behind a single IP, so I'd prefer to stay with a routed solution. Has anybody implemented something similar who can point me in the right direction?