topic RE: mobility tunnel in ExtremeWireless (Identifi)

mobility tunnel

Salvador_Gallo — Wed, 10 May 2017 05:42:00 GMT

I have two controllers WC-35 with version 10.31.01.0048, and C4110 with version 09.21.10.0005, and i would like configure mobility tunnel between tow controllers, the controller´s dont have HA, this is possible?

RE: mobility tunnel

Ronald_Dvorak — Wed, 10 May 2017 11:57:00 GMT

Yes

RE: mobility tunnel

Salvador_Gallo — Wed, 10 May 2017 22:18:00 GMT

But is necessary create a HA?

RE: mobility tunnel

StephanH — Thu, 11 May 2017 01:05:00 GMT

Hello Salvador,

you don't need HA!

Regards
Stephan

RE: mobility tunnel

Salvador_Gallo — Thu, 11 May 2017 01:05:00 GMT

i tryed and the tunnel does not up, i have differents segment of network on interface of register 10.10.1.0/24 and 10.10.3.0/24. is necesary that the inferfaces have the same network segment?

RE: mobility tunnel

Ronald_Dvorak — Thu, 11 May 2017 01:05:00 GMT

No, they don't need to be on the same VLAN/subnet.

Is a route configured on the controller so they could reach each other - you could try a ping from controller#1 to controller#2 to see whether routing works.

RE: mobility tunnel

StephanH — Thu, 11 May 2017 03:34:00 GMT

Mybe there is a firewall between your networks?
Visit the release notes for the necessary ports.

RE: mobility tunnel

Salvador_Gallo — Thu, 11 May 2017 03:40:00 GMT

The two controllers are in the same LAN conect at the core

RE: mobility tunnel

StephanH — Thu, 11 May 2017 10:11:00 GMT

Are you using NTP and do you have the same time on both controllers?
What do you see in the Reports->Mobility->Mobility Tunnel Matrix?
What do you see in the Logs for Mobility?

RE: mobility tunnel

Umut_Aydin — Thu, 11 May 2017 20:16:00 GMT

I assume but if not..add the mobility agents statically in the list?

RE: mobility tunnel

Salvador_Gallo — Thu, 11 May 2017 23:36:00 GMT

i cal see this logs:
manager: Mobility tunnel establishment failed with Peer 10.15.2.254. Please verify peer's reachability
agent: Mobility tunnels with Peers reset due to membership credentials change on current controller

RE: mobility tunnel

Ronald_Dvorak — Thu, 11 May 2017 23:52:00 GMT

I'm sorry but it's hard to help if you don't provide exact information.....

1) what is the IP of controller#1&2 interface that you'd like to use for mobility and how are the interface topologies are configured = physical or bridge@EWC

2) could you ping the IP this IP from controller#1 and vice-versa

RE: mobility tunnel

Salvador_Gallo — Thu, 11 May 2017 23:52:00 GMT

this is the information of controllers:

controller 1: interface physical 10.10.2.254/ 24 with Ap registrering, version 09.21.10.0005
controller 2: interface physical 10.10.3.254/ 24 with Ap registrering, version 10.31.01.0048

and ping is successfull in both directions.

but controller 1 have 61 VNS configured and other controller have 3 VNS.

RE: mobility tunnel

Ronald_Dvorak — Thu, 11 May 2017 23:52:00 GMT

That IPs don't match with the IPs in the error message that you've provided...

"manager: Mobility tunnel establishment failed with Peer 10.15.2.254."

RE: mobility tunnel

Salvador_Gallo — Thu, 11 May 2017 23:52:00 GMT

sorry, the Second octet is 15 for both segment of network, 10.15.2.254/24 and 10.15.3.254/24