micron_support's profile

4 Messages

 • 

100 Points

Wed, Jun 2, 2021 11:17 AM

VoIP WLAN with Ruckus GRE Tunnel

Hello,

We are trying to tunnel VoIP over WLAN using the Ruckus GRE with a virtual Data-Plane. The DP is hosted in the cloud along with the PBX and controllers, all accessible via a VPLS connection. However cannot seem to get this working. When activating the tunnel, clients cannot see the network, effectively no network. Phones will work without the tunnel, but roaming often disconnects calls, hence why trying to tunnel

DP data interface is on the same subnet as the PBX.

Struggled to find any real good guides on setting up Ruckus GRE, and there doesn't appear to be much to it in terms of settings.

Any help appreciated.

Responses

Official Rep

 • 

1.2K Messages

 • 

16.6K Points

4 m ago

Hi Micron support,

Check below points.

  • Can AP reach vDP IP address and vice-versa?
  • Run "get tunnelmgr" on AP and check the vDP tunnel status.
  • What is the path MTU between AP to vDP network path?

(edited)

4 Messages

 • 

100 Points

Hi @syamantak_omer 

thank you for the reply.

  • Yes the AP can ping the vDP and visa versa.
  • tunnelmgr appears all good, I do notice under the "SCG-D IP list:" the WAN IP is listed as well as the data interface. Not sure if this means anything
  • MTU is set to Auto, however I have tried 1200, and 850 as a test, still nothing.

I am using just GRE, not GRE+UDP if that helps as well.

Thanks.

Official Rep

 • 

1.2K Messages

 • 

16.6K Points

Could you post get tunnelmgr and get wlanlist output from the AP CLI.

I think opening a case with support will be best and fastest way to get this checked and fixed.

Regards,

Syamantak Omer

4 Messages

 • 

100 Points

HI,

rkscli: get tunnelmgr

 

------ TUNNELMGR Information ------

tunnelmgr Service:      Enabled

Tunnel Establishment:   Enabled

Tunnel IPSec:           Disabled

Tunnel Authentication:  Enabled

Tunnel Cipher:          Disabled

Tunnel Cipher Key Len:

Tunnel Forward Bcast:   Enabled

PMTU:                   Auto

PMTU Discovery:         Enabled

Node Affinity:          Disabled

Force Fragmentation:    Disabled

Offload:                Enabled

Tunnel Type: Ruckus-GRE

SCG-D IP List:       +1@[<WAN-IP>]:23233,[<DATA-INT-IP>]:0

SCG-D Subject List:       <redacted>

Internal Subnet:        10.255.0.0

No GRE over UDP

Keep Alive Interval/Retry-limit: 10/6

Keep Alive Interval2: N/A

Keep Alive Count: N/A

Force Primary Interval: N/A

------- Run Time Status (Debug) -------

Current tunnel ID: 12763

Current failover mode: 0

Current connected SCG-D: [<DATA-INT-IP>]:0

Current Session UpTime: 3 mins 6 secs

Current Keep Alive retry:0  sent:19  lost: 0

Keep Alive Average Round Trip Time: 0.002577 seconds

Number of tunnel (re)establishment: 12

FIPS mode: Disable

Reason on last re-establishment: can't connect to SCG-D

Suggested action: check connectivity between AP and SCG-D

Ipsec state : IPSEC_BEGIN

Ping default gateway from last disconnection:

 

        Wed Jun  2 16:18:56 UTC 2021

        PING <LOCAL-GATEWAY> (<LOCAL-GATEWAY>: 56 data bytes

        64 bytes from <LOCAL-GATEWAY>: seq=0 ttl=254 time=2.918 ms

        64 bytes from <LOCAL-GATEWAY>: seq=1 ttl=254 time=2.625 ms

 

        --- <LOCAL-GATEWAY> ping statistics ---

        2 packets transmitted, 2 packets received, 0% packet loss

        round-trip min/avg/max = 2.625/2.771/2.918 ms

        PING <WAN-IP> (<WAN-IP>): 56 data bytes

        64 bytes from <WAN-IP>: seq=0 ttl=250 time=4.262 ms

        64 bytes from <WAN-IP>: seq=1 ttl=250 time=4.057 ms

 

        --- <WAN-IP> ping statistics ---

        2 packets transmitted, 2 packets received, 0% packet loss

        round-trip min/avg/max = 4.057/4.159/4.262 ms

 

------ Logging parameters ------

Log Console:  Disable

Log Level:  3

----------- gre1 status -----------

gre1: RX packets 0 errors:0 dropped:0

gre1: TX packets 1 errors:0 dropped:0

gre1: RX idle time: 1073741.822000 seconds

OK

rkscli: get wlanlist

name          status   type   wlanID   radioID  bssid             ssid

--------------------------------------------------------------------------------------------------

wlan0         up       AP     wlan0    0        1c:3a:60:09:7a:98 .voip

wlan1         up       AP     wlan1    0        1c:3a:60:49:7a:98 .priv

wlan2         up       AP     wlan2    0        1c:3a:60:89:7a:98 .av

wlan3         up       AP     wlan3    0        1c:3a:60:c9:7a:98 Guest

wlan4         down     AP     wlan4    0        00:00:00:00:00:00 Wireless4

wlan5         down     AP     wlan5    0        00:00:00:00:00:00 Wireless5

wlan6         down     AP     wlan6    0        00:00:00:00:00:00 Wireless7

wlan7         down     AP     wlan7    0        00:00:00:00:00:00 Wireless8

wlan8         down     AP     wlan8    0        00:00:00:00:00:00 Wireless 8

wlan9         down     AP     wlan9    0        00:00:00:00:00:00 Wireless 9

wlan10        down     AP     wlan10   0        00:00:00:00:00:00 Wireless 10

wlan11        down     AP     wlan11   0        00:00:00:00:00:00 Wireless 11

wlan12        down     AP     wlan12   0        00:00:00:00:00:00 Wireless 12

wlan13        down     AP     wlan13   0        00:00:00:00:00:00 Wireless 13

wlan14        down     AP     wlan14   0        00:00:00:00:00:00 Wireless 14

recovery-ssid down     AP     wlan102  0        00:00:00:00:00:00 Recover.Me-097A90

wlan32        up       AP     wlan32   1        1c:3a:60:09:7a:9c .voip

wlan33        up       AP     wlan33   1        1c:3a:60:49:7a:9c .priv

wlan34        up       AP     wlan34   1        1c:3a:60:89:7a:9c .av

wlan35        up       AP     wlan35   1        1c:3a:60:c9:7a:9c Guest

wlan36        down     AP     wlan36   1        00:00:00:00:00:00 Wireless36

wlan37        down     AP     wlan37   1        00:00:00:00:00:00 Wireless37

wlan38        down     AP     wlan38   1        00:00:00:00:00:00 Wireless15

wlan39        down     AP     wlan39   1        00:00:00:00:00:00 Wireless16

wlan40        down     AP     wlan40   1        00:00:00:00:00:00 Wireless 40

wlan41        down     AP     wlan41   1        00:00:00:00:00:00 Wireless 41

wlan42        down     AP     wlan42   1        00:00:00:00:00:00 Wireless 42

wlan43        down     AP     wlan43   1        00:00:00:00:00:00 Wireless 43

wlan44        down     AP     wlan44   1        00:00:00:00:00:00 Wireless 44

wlan45        down     AP     wlan45   1        00:00:00:00:00:00 Wireless 45

wlan46        down     AP     wlan46   1        00:00:00:00:00:00 Wireless 46

wlan47        down     AP     wlan47   1        00:00:00:00:00:00 Wireless 47

Tried logging a case, but support has ran out, and customer is yet to re-sign :(

Thanks.

Official Rep

 • 

1.2K Messages

 • 

16.6K Points

I think tunnel is flapping.

Current Session UpTime: 3 mins 6 secs

Current Keep Alive retry:0  sent:19  lost: 0

Keep Alive Average Round Trip Time: 0.002577 seconds

Number of tunnel (re)establishment: 12

FIPS mode: Disable

Reason on last re-establishment: can't connect to SCG-D

Suggested action: check connectivity between AP and SCG-D

Ipsec state : IPSEC_BEGIN

As per the get wlanlist output, voip WLAN is up on both the bands so clients should be able to see it, but if tunnel is flapping, tunneled WLAN will get disabled.

You can also check the SZ event logs for AP tunnel flaps.

Regards,

Syamantak Omer

4 Messages

 • 

100 Points

Hi @syamantak_omer 

The tunnel looks flapping as I am enabling and disabling it to test with. If i leave it on, the wireless VoIP handsets don't work, so have to disable it to give them service.

Thanks

(edited)

Important Announcement