Teaming two MSM 760 problem

[gessed]

Hi i have two MSM 760 mobillity controller that i want to join in a team.

I have setup the first controller as the team manager and that seems to go good. After that i join the second controller to the team and after the reboot the status of the second controller is constantly switching from uploading configuration to resetting configuration.

The firmware version of both controller is: 5.7.0.3-11516

In the filtered log i see:

Date Level Program Message Jul 12 14:38:12 err mscconf Detail: <error><errorcode>1009</errorcode><errorinfo>Invalid route parameter</errorinfo></error> Jul 12 14:38:12 err mscconf SOAP FAULT: SOAP-ENV:Client "Invalid configuration" Jul 12 14:38:12 err mscconf [00:21:F7:B0:85:84] Error configuring slave msc Jul 12 14:37:34 err mscconf Detail: <error><errorcode>1009</errorcode><errorinfo>Invalid route parameter</errorinfo></error> Jul 12 14:37:34 err mscconf SOAP FAULT: SOAP-ENV:Client "Invalid configuration" Jul 12 14:37:34 err mscconf [00:21:F7:B0:85:84] Error configuring slave msc Jul 12 14:36:56 err mscconf Detail: <error><errorcode>1009</errorcode><errorinfo>Invalid route parameter</errorinfo></error> Jul 12 14:36:56 err mscconf SOAP FAULT: SOAP-ENV:Client "Invalid configuration" Jul 12 14:36:56 err mscconf [00:21:F7:B0:85:84] Error configuring slave msc Jul 12 14:36:18 err mscconf Detail: <error><errorcode>1009</errorcode><errorinfo>Invalid route parameter</errorinfo></error> Jul 12 14:36:18 err mscconf SOAP FAULT: SOAP-ENV:Client "Invalid configuration" Jul 12 14:36:18 err mscconf [00:21:F7:B0:85:84] Error configuring slave msc Jul 12 14:35:40 err mscconf Detail: <error><errorcode>1009</errorcode><errorinfo>Invalid route parameter</errorinfo></error> Jul 12 14:35:40 err mscconf SOAP FAULT: SOAP-ENV:Client "Invalid configuration" Jul 12 14:35:40 err mscconf [00:21:F7:B0:85:84] Error configuring slave msc Jul 12 14:35:02 err mscconf Detail: <error><errorcode>1009</errorcode><errorinfo>Invalid route parameter</errorinfo></error> Jul 12 14:35:02 err mscconf SOAP FAULT: SOAP-ENV:Client "Invalid configuration" Jul 12 14:35:02 err mscconf [00:21:F7:B0:85:84] Error configuring slave msc

Can someone help me out

Greetings

[cenk sasmaztin]

Hi Two controller country must be usa Please test and say me result

[james555]

we have 765 and its a nightmare with the team enabled. well at least i think that is when most issues occur. normally random access points refuse to give out the dhcp leases and i know the server is fine as lan people and other AP's are fine. i must say the new release is more stable than the beta but still far from perfect

[Ian Vaughan]

Howdy,

Do they both share the same VLAN for their LAN port?

Do they both have the same next-hop default gateway?

Are the clocks synchronized to an external time source?

Seen quite a few thing stopping the team from forming properly. Bit more of a black art than a science I'm afraid.

Cheers

Ian

[Joe_NITEC]

Have you already buily the full configuration on your Team manager?

If so then im afraid i have bad news for you - we are having the same issue and  we have just had feedback from HP that you should only apply a very basic configuration to your controllers and then team them - this means that if you have already fully configured the manager you will need to blow it away.

If you havent then from your error messages it looks like you havent set up the same routes and vlans on the secondary controller - the networking setup need to be the same in regards to routes etc or the config will not take.

Just out of interest what is the purpose of teaming - im assuming redundancy here - and you are aware of the limitations that it imposes on the setup?

Joe

[tschaps]

---

@Joe_NITEC wrote:

Just out of interest what is the purpose of teaming - im assuming redundancy here - and you are aware of the limitations that it imposes on the setup?

---

I am curious what limitations you are referring to. Off the top of my head, with teaming you cannot use the controller(s) for DHCP, and you can't use the GMS (guest mgt software). My vendor set us up teamed, and it's been anything but trouble-free, but I am curious what all I might be missing...

Thanks

[Joe_NITEC]

You also cant use the built in web server  - can be a pain if you already have the config etc built and then want to team and still use HTML login for guest access - you need an external web server.

the DHCP thing caught us out to be honest - and then so did the GMS - particualrly bad as this was a key component that we were planning on using for guest access.

we are having some issues as well which we are currently working through but I am increasingly of the opinion that teaming is not worth the hassle in most cases - that is my personal opinion by the way.

[tschaps]

I am beginning to agree -- though with two controllers for failover, without the teaming I'd have to make changes to two controller configs each time there's a change, right?

[Joe_NITEC]

thats correct - although you could simply make the change, backup the config and then upload it to your backup controller -you couldnt have them both on the LAN at the same time anyway so I dont really see any difficulties in having one powered on and waiting with the same config as the other controller until it fails.

It would be a manual switchover which isnt ideal if you are 24/7/365

Another possible issue is that you would not be able to share the base licences across the 2 controllers which is something good that you get from teaming

[tschaps]

---

@Joe_NITEC wrote:

Another possible issue is that you would not be able to share the base licences across the 2 controllers which is something good that you get from teaming

---

Hmmm.... I think my vendor may have screwed that up. I believe I have two full licenses and I know I have an additional 40 clients for each MSM765 (currently have 61 APs) so each could manage 80. Sounds like we may have spent a bunch of money we didn't need to if the intention was teaming?

[Anthony82]

Did you manage to solve this problem?

I experience exactly the same!

[Arimo]

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.

[maheshndeshpand]

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.

---

[C0LDWiR3D]

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.

[Samir_FMC]

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

[SVP]

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.