- Community Home
- >
- Networking
- >
- Wireless
- >
- M and MSM Series
- >
- Re: Teaming two MSM 760 problem
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
11-08-2012 03:44 AM
11-08-2012 03:44 AM
Re: Teaming two MSM 760 problem
Did you manage to solve this problem?
I experience exactly the same!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2014 05:39 AM
02-19-2014 05:39 AM
Re: Teaming two MSM 760 problem
Hello all
An older thread, but the question still pops up regularly.
The root cause of this problem is most often that the Default route of the controller is pointing to a subnet on a VLAN.
When controllers are teamed, the IP addressing and Default route must match. If the Manager controller has a Default route configured to a VLAN, the same VLAN must be created in the Member controller, it needs to have an IP interface in appropriate subnet and the Default route has to be configured.
During team formation the Manager will wipe the member's configuration entirely except for LAN and Internet port IP addresses. All VLANs will be deleted. The Manager will reconfigure the member and re-create the VLAN, but it has no mechanism to provide it an IP interface. Because the VLAN has been removed and recreated, the Member has no longer an IP interface in that subnet. Consequently the route Manager is trying to configure will be invalid for the member.
The recommended way is to configure the devices following insructions in the Implementation and Configuration guides. All the example configurations put the Default route to a subnet either behind untagged LAN or untagged Internet port.
If it's for some reason desirable to have the Default route pointing to a VLAN, it's possible with a workaround:
1. Disable Teaming on Manager and Member
2. Remove the Default route on Manager
3. Configure Member's LAN and Internet port IP addresses
4. Enable Teaming on Manager and Member
5. After team has formed, the Default route to a VLAN can be re-added
Again, I'd recommend following the configuration guidelines described in the manuals.
HTH,
Arimo
HPE Networking Engineer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2014 10:41 PM
08-15-2014 10:41 PM
Re: Teaming two MSM 760 problem
Hi All,
Facing same issue when upgraded firmware from 6.0 to 6.4. Three controllers to form teaming. But after upgradation controller are switching from resetting configuration and uplocading configuration.
On looking at the routes on the Team Member, no routing informaiton is synchronized to team members. VSC and groups are getting synchronized to Team Member
Tried resetting all three controllers to factory default, then formed teaming between the controllers, teaming is formed, the restored the configuration on the Team Manager. Access Points are getting discovered on the Team Manager, but as routing information is not getting synchronized to team members, WAPs are not able to discover the team member.
Please help !!!!
@Arimo wrote:Hello all
An older thread, but the question still pops up regularly.
The root cause of this problem is most often that the Default route of the controller is pointing to a subnet on a VLAN.
When controllers are teamed, the IP addressing and Default route must match. If the Manager controller has a Default route configured to a VLAN, the same VLAN must be created in the Member controller, it needs to have an IP interface in appropriate subnet and the Default route has to be configured.
During team formation the Manager will wipe the member's configuration entirely except for LAN and Internet port IP addresses. All VLANs will be deleted. The Manager will reconfigure the member and re-create the VLAN, but it has no mechanism to provide it an IP interface. Because the VLAN has been removed and recreated, the Member has no longer an IP interface in that subnet. Consequently the route Manager is trying to configure will be invalid for the member.
The recommended way is to configure the devices following insructions in the Implementation and Configuration guides. All the example configurations put the Default route to a subnet either behind untagged LAN or untagged Internet port.
If it's for some reason desirable to have the Default route pointing to a VLAN, it's possible with a workaround:
1. Disable Teaming on Manager and Member
2. Remove the Default route on Manager
3. Configure Member's LAN and Internet port IP addresses
4. Enable Teaming on Manager and Member
5. After team has formed, the Default route to a VLAN can be re-added
Again, I'd recommend following the configuration guidelines described in the manuals.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2014 06:43 AM
09-03-2014 06:43 AM
Re: Teaming two MSM 760 problem
Perhaps the 6.4.1.0 firmware could help.
If I need to add a member to a team I usually factory reset the new member first.
Also I only use LAN for team sync and internet interface for all other communication.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2014 12:11 AM
10-20-2014 12:11 AM
Re: Teaming two MSM 760 problem
try the two below steps:
1. disable system clock from outside NTP and make it local hour on the msm760
2. go to home>network>discovery protocols>untick the generate dynamic system names and click save
this should solve the problem for you because they above steps considered as configuration change so it requires the access points to sync.
best of luck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2016 04:53 PM
03-06-2016 04:53 PM
Re: Teaming two MSM 760 problem
Hi,
Looks like this is discussed earlier also but still need to crosscheck some more thing. We are using one MSM760 version 5.5.3.0-01-10326 and planning to make HA so thought about teaming.
Here are some question
- Instead of teaming can I make two standalone controller and make mobility across. So that AP can connected to any controller. If I do that BYOD will get different IP address according to which controller it’s connected.
- If I teamed I need to configure the IP address on the interface reaming configs will sync once it create teaming. Am I right?
Is any know issues after teaming.
- « Previous
-
- 1
- 2
- Next »