Ruckus R320 cannot join with mapping ip address

[fahrizal_zulqif]

Dear Master,

we have ap ruckus r320 will register to vsz with mapping ip model, but cannot register, any idea for solution that???.

Thanks.

[syamantakomer]

Hi Fahrizal,

Are you using batch provisioning to add the APs or using AP registration rules?

• Make sure vSZ and AP Zone firmware supports the R320 AP.
• Make sure batch provisioning template file (if you are using batch provisioning method) which you are uploading to vSZ for batch provisioning has correct data and file format and encoding do not gets changed.
• Make sure that AP is getting the IP on correct range, which is defined in your registration rule.
  
• Does other AP models are able to get registered? or only R320 facing this issue?

Regards,
Syamantak Omer

[fahrizal_zulqif]

Hi Syamantak,

thanks for respons, no i question abaout registering AP to virtual AP, maybe you can see our image as network diagram, i try to connect with virtual ip the result is cannot register to controller.

Regards,
Fahrizal

[fahrizal_zulqif]

Status AP SCG

rkscli: get scg

------ SCG Information ------
SCG Service is enabled.
AP is not managed by SCG.
State: CONN_GET_ADDR_STATE
Server List: 192.168.1.206
No SSH tunnel exists
Failover List: Not found
Failover Max Retry: 2
DHCP Opt43 Code: 6
Server List from DHCP (Opt43/Opt52): Not found
SCG default URL: RuckusController
SCG config|heartbeat intervals: 30|30
SCG gwloss|serverloss timeouts: 1800|7200
Controller Cert Validation : disable
-----------------------------
OK

[syamantakomer]

Hi Fahrizal,

Sorry for late response as I was on medical for past few weeks.

So as per my understanding, your AP is not joining vSZ controller.

Try below to troubleshoot the issue:

1- Is the controller on same site as firewall or on different site?
2- I can see in network diagram that controller has an IP 192.168.0.2, may I know why you are pointing AP to firewall IP?
3- If AP and vSZ and firewall on same site, than to make things easy, enable the interVLAN routing between AP and vSZ VLAN, so that AP can directly reach controller.
4- Is there any IP mapping (NAT) on your firewall for vSZ?
5- Make sure APs has network connectivity with vSZ IP. Try pinging controller IP from AP.
6- Make sure port 22 and 443 is not blocked between AP to controller network path, in firewall.
7- Is the AP even discovering on controller?
8- Check and make sure you have enough AP licenses on vSZ.

Regards,
Syamantak Omer