We've moved to a brand new modern platform which sets us up for growth and innovation over the next few years. Our aim is to revitalize the Community as a place to get help from RUCKUS Team members as well as your peers. But coming soon we'll be adding many features and capabilities to make Community a destination for product discussions and ideas, specialty groups, vertical market solutions and event announcements.

At the risk of repeating ourselves:

• Please be sure to read the Community Guidelines before posting.
• Please visit the Community Help and FAQs for tips on using Vanilla features.
• Lennar SmartHome Customers: Please visit our Lennar Knowledge Base for quick answers to common issues before posting to the forum.

Happy posting!

https://community.ruckuswireless.com/t5/ICX-Switches/DHCP-server-icx-7750/m-p/101495#M7109 

SW version is 08.0.95pT203

I have created 2 VLANS. For example vlan 100 and vlan 101
For vlan 100 I have used the dhcp pool created on ICX7750 and For Vlan 101 I used the TP-link router to provide DHCP. Both PC+ Mobile working fine with VLAN101 in SSID101 but VLAN 100 has SSID 100 in AP on which only PC get connects.

On checking VSZ6.1.2 it shows in AP clients i can see the DHCP ip received by the PC but the DHCP from the mobile phone reaches to VSZ but it shows 0.0.0.0:: and it donot request the dhcp to switch but incase of PC it does with the same SSID.

On checking via Wireshark:

--On Laptop (Wi-Fi)
--Receives DHCP Pool Address
DHCP Request:
*Option:(50) Requested IP address (192.168.92.4)
DHCP ACK:
*Option:(54) DHCP Server Identifier(192.168.92.1)

--On Mobile (Same Wi-Fi)
--Do not lease IP address, no Request and ACK, Only Discover is seen in Wireshark
*Option:(53) DHCP Message Type (Discover)
DHCP: Discover (1)
*Option:(61) Client Identifier
Client Mac Address:<------>
*OPtion:(12) Hostname
Hostname: <Redmi-12-5G>
*option:(55) Parameter Request list
Length:12
Parameter Request List Item: (1) Subnet mask
Parameter Request List Item: (3) Router
Parameter Request List Item: (6) Domain name Server
Parameter Request List Item: (15) Domain name
Parameter Request List Item: (26) Interface MTU
Parameter Request List Item: (28) Broadcast Address
Parameter Request List Item: (51) IP Address lease time
Parameter Request List Item: (58) Renewal time value
Parameter Request List Item: (43) vendor-specific Information
Parameter Request List Item:(114) DHCP Captive-Portal
Parameter Request List Item: (108) IPv6-Only Preferred

switch configuration:
ip dhcp-server pool vlan100
excluded-address 192.168.92.1
!
excluded-address 192.168.92.100 192.168.92.254
lease 1 0 0
network 192.168.92.0 255.255.255.0
option 3 ip 192.168.92.1
deploy
ip helper-use-responder-ip

interface ve 100
vrf forwarding abc
ip address 192.168.92.1 255.255.255.0
ip helper-address 1 192.168.92.1

also globally i have enabled
ip dhcp-server enable
ip dhcp-server relay-agent-echo enable

Unleashed Overview

In an Unleashed network, a RUCKUS Unleashed 'Master' Access Point acts similarly to a controller, managing all control functions. These settings are then propagated to the other APs in the network. If the Master AP go offline, a 'Member' AP will automatically take on the role of the Unleashed Master, assuming control and maintaining network operations.

Unleashed Support

-Bridge mode 128 APs and 2,048 clients.

-Gateway mode supports up to 25 APs and 512 clients.

-Dedicated Master

Overview Limitations from Zone Director

-IPv6 is not supported.

-No interface to communicate with SmartCell Insight analytics engine or SPoT location.

-No Northbound Interface to pass client authentication responsibility to an external entity.

-No WLAN groups.

What are the necessary conditions or prerequisites for an access point to successfully connect to an existing Unleashed network?

Connect the Member Access Point (AP) to the network, ensuring it is on the same VLAN as the Master AP. Upon powering up, the Member AP will engage in an election to determine if a Master already exists. It's important that the Member AP either matches or has a lower firmware version than the Master.

Additionally, it must be able to ping the Master AP and share the same country code setting.

Commands to check if a member Access Point is not joining to the Unleashed Network.

•  ping < Master_AP>
•  get version 
•  get boarddata : Display hardware version and system board information
•  get discovery-agent: Check if LLWAP protocol is enable.
• get countrycode :
• get director : show Master AP information.
• get election: shows the status of all Unleashed APs
• get syslog log

The same information can be collected on the Master AP.

• Ping <Member_IP>
• get version 
• get countrycode 
• get boarddata 
• get election 

Ruckus CLI on unleashed when SSH to the Access Points.

The 'ruckus>' CLI prompt indicates you are logged into the 'Master' Access Point. From here, you can navigate through various configuration modes to manage settings and preferences.

Enable:

ruckus#

Under enable mode we can go to different modes example:

ap-mode: Note under this mode you can run set-get commands.

ruckus(ap-mode)#

Config

ruckus(config)#

Under config there are some different modes

+Admin:

ruckus(config-admin)#

+System:

ruckus(config-sys)#

+Using the Mac-address of the AP: 

ruckus(config)# ap d4:bd:4f:01:bc:10
The AP 'd4:bd:4f:01:bc:10' has been loaded. To save the AP, type 'end' or 'exit'.
ruckus(config-ap)#

The 'rkscli:' prompt indicates that you are logged into a 'Member' Access Point. In this CLI, you can execute 'get' or 'set' commands to retrieve or configure the Access Point settings. For example:

Best Regards 

Fernando Vasquez 

I got a T610 AP from my friend and I cannot acces it. When i plug it in POE it gets ip adress from DHCP                         (169.254.62.226). I cannot acces it at all. My configure.me (xxx) is locked and the password is S/N from AP. When I connect nothing happens.  Probably the AP was somewhere before configured. Is there any way to HARD reset it so the AP got his default ip 192.168.0.1 so i can configure it? If not, is there any way someone could explain a bit how to put new firmaware over tftp ( dunno if this will work cause i can't get it's ip)

Thanks a lot!

In this article, I will explains an issue with customer DHCP configuration (related to DNS Domain name) which can potentially cause AP connectivity issue with RUCKUS Cloud.

Symptoms

• If you hit this issue, AP may show online but as soon as you make any configuration changes on venue, AP, WLAN, it will result AP state changing to "Never contacted Cloud".

• AP will not show any new event, since the time of its last successful connection to Cloud.
  In some cases AP will also show in "Operational -  applying configuration" state on Cloud UI and will never complete applying configuration.

• AP will still serve clients with last known configuration (if AP was not rebooted).

How to troubleshoot?

• Run a capture on switch port where AP is connected and reboot the AP.
  Note: This will not help if AP is configured with static IP configuration.
• Check the uplink packet capture and analyze (look at the DHCP Offer frame) the DHCP packets for the DHCP process.
• You will see DHCP server sending DNS domain name information.

• When Domain Name is added to the DHCP and configured on AP, AP will append the AP-Cloud discovery URL which is device.ruckus.cloud to device.ruckus.cloud.xyz.com. Because of this change in Cloud URL, AP will not be able to reach the correct controller IP (usually DNS resolution will fail) and will eventually fail to connect to Cloud.
• In case domain specific URL (in this case "device.ruckus.cloud.xyz.com") has a valid DNS entry on customer/public DNS server, it will further result in connection failure as resulted IP address will not match with the correct Cloud controller IP address.
• You can also factory reset one AP and then SSH into it (with default credentials super/sp-admin), run below commands to confirm if AP is getting the DNS Domain name configuration from DHCP.
• Run and review the output of "get dns" command.
• Output when DNS Domain name is received from DHCP server.
  

  rkscli:
  rkscli: get dns
  Allow DNS from DHCP: Enabled
  Ethernet DNS servers:
  DNS 1 : 8.8.8.8
  DNS 2 : 8.8.4.4

  IPv6 DNS Setting

  DNS Domain
  <None>

  DNS Search List
  <None>
  OK

• Output when DNS Domain name is received from DHCP server

  rkscli:
  rkscli: get dns
  Allow DNS from DHCP: Enabled
  Ethernet DNS servers:
  DNS 1 : 8.8.8.8
  DNS 2 : 8.8.4.4

  IPv6 DNS Setting

  DNS Domain
  xyz.com

  DNS Search List
  <None>
  OK

Resolution

While issue is impacting RUCKUS APs, this is completely an issue caused by customer DNS and/or DHCP server configuration.

Follow below steps to fix the issue.

• Check and remove the domain name configuration from DHCP IP pool which is used for RUCKUS Access points.
• Just updating the configuration on DHCP server may not fix APs as APs will still hold old IP which has valid lease time. In this case you may reboot the AP so that AP can get the fresh IP lease from DHCP server without DNS domain name. Also clearing the IP lease from DHCP server can help.
• Even after rebooting or re-requesting IP from DHCP if issue is not solved, remove the AP from the Cloud and re-add.
• If you continue seeing issue even after fixing the DHCP configuration, please contact RUCKUS Support and report the issue.

I hope this will help!

Got any queries? Start the conversation!

Does any of you have a solution for this?  

 This communication is intended for our Partners/Customers who rely on Device Registrar Service (DRS) to onboard devices (AP/Switch) onto Smart Zone Controller.

Please be aware of an upcoming change to the Device Registrar Service (DRS) Public Certificate Issuer. The Public Certificate Issuer is scheduled to be migrated from Entrust to GoDaddy, on March 27, 2024. 

Action Required:

Customers who onboard devices through DRS discovery should whitelist http://ocsp.godaddy.com in their firewalls, so that the devices can OCSP-validate the DRS certificate before performing Controller discovery.

Impact on Customers:

This activity impacts only those Customers who have outbound firewall rules blocking OCSP validation. In such environments devices would fail to discover a controller through DRS service.

FAQs:

• What is the downtime of this activity?
• There is no downtime expected.

• What happens to my devices which are in production?
• There is no impact on devices which are in production or until the devices are rebooted.

• Who and what does it affect?
• Customers who are about to deploy devices already registered or about to be registered in DRS should whitelist http://ocsp.godaddy.com.

If you have any urgent concerns or require immediate assistance, please do not hesitate to reach out to our support team at https://support.ruckuswireless.com/contact-us

Thank you for your continued support.

Sincerely,

Ruckus NOC

Customer Environment

APs and Switches deployed behind a firewall and inbound/outbound traffic needs to be allowed for successful communication between RUCKUS network devices and RUCKUS One.

Symptoms

Newly added APs and switches are in Never Contacted Cloud state, not joining RUCKUS One.

Resolution

To allow RUCKUS One to function properly, please configure your firewall to allow for outbound connectivity according to the following guidelines:
 

Outbound HTTPS (TCP 443) from APs and Switches to:

https://ap-registrar.ruckuswireless.com
https://sw-registrar.ruckuswireless.com
https://ocsp.comodoca.com
https://ocsp.entrust.net
https://ruckus.cloud
https://eu.ruckus.cloud
https://asia.ruckus.cloud
https://device.ruckus.cloud
https://device.eu.ruckus.cloud
https://device.asia.ruckus.cloud
https://storage.googleapis.com
http://ocsp.godaddy.com

Outbound SSH (TCP 22) from APs and Switches to:

device.ruckus.cloud
device.eu.ruckus.cloud
device.asia.ruckus.cloud

Network Requirements

The following list of firewall ports is required to allow APs to enable Cloud discovery and continued connection with the Cloud

Checking the firewall ports is the first step of troubleshooting if an AP is unable to connect to the Cloud or disconnects from the Cloud.

https://docs.cloud.ruckuswireless.com/ruckusone/userguide/GUID-D00EA4CC-7B8A-4F99-969B-2A5FB5DDB178-low.png 

If these information helped you in any way, please click on "KUDOs", so you can help other users.

Very basically I've tried to follow the AP Setup guide on the ruckus website but haven't been able to complete it. 

I'm using a POE Injector ( TRENDnet TPE-319GI capable of POE++ and 10G) and new 1ft cat 6a cables. 

First set up I tried. 

AP -> POE Port on injector, Laptop -> POE Data Port. In this situation The AP will power on and the LED indicator will go from Solid RED -> Solid Amber -> Flashing Amber. And no matter how long i wait (up to 6 hrs) the LED will never turn to solid green and even when setting static IP address on Laptop to suggested 192.168.0.22 , I cannot access 192.168.0.1 in any web browser(chrome,firefox,brave,edge)

Next Set up i tried was 

AP-> poe port on injector, POE Data Port -> Switch and Laptop to Switch. Same exact result. 

I then tried factory reseting by holding the reset button until the light went from red-> red with green to solid red). I then again tried the above scenarios exhibiting the same behavior. 

At this point , I don't know what else to try and some help would be greatly appreciated. Thanks. 

This is an announcement about this know issue we are currently working on Please check this information if you run into it.

Issue: iPhone with IOS 16 can't reach "unleashed.ruckuswireless.com" after connected to Unleashed network

Error message: "Not connected to the Unleashed network"

PLEASE NOTE: This is a known issue on which we are working with our Engineering Team internally. And This issue is expected to be fixed in the upcoming Unleashed version 200.14 software release and the App Release.  

The estimated Time of Arrival (ETA) for the release is Mid of July 2023.

For now, please refer to the workaround, that will be using the IP Address of Master AP as described in the below process.

If you haven’t tried Accessing Unleashed on a web browser via the IP address of the Access Points, could you please try to find the Master IP address of the Access Point and try to check it on a browser? Please refer to the below guide to find the IP address.

How to find my Ruckus “Devices IP address” using free applications:

https://community.ruckuswireless.com/t5/RUCKUS-Support-for-Lennar-Homes/How-to-find-my-Ruckus-Device...

You should see the below Unleashed dashboard after finding the IP Address of the AP. Try to log in

Refer to the below screenshot to know your MASTER IP Address on the Web Unleashed system.

Once you find and can log in via the IP Address of the Unleashed Master Access Point, please try the below steps.

1. Make sure you are connected to the RUCKUS Access Point Wi-Fi Network.

2. Click on ‘change login destination’. (Please refer to the below screenshot)

 3. Put your Unleashed MASTER Access Point IP Address as ‘Destination IP’ and save it. (Please refer to the below screenshot and 0.0.0.0 is just an example)

4. Now try to log in to Unleashed App using your credentials.

Please follow ALL 4 STEPS as explained above.

If you have any questions about the Steps for the workaround please open a new post using this as reference.

Best regards,

David Chavarria  | Technical Support Manager.

In this article we are going to share information about ports, which should be open on firewall for RUCKUS Access Points, Switches and other services/server to v/SmartZone communication.

For each major release port requirement may differ, so it is advised to refer the Administrator guide of respective release.

Refer the below documents major release wise.

• 6.x.x
• 5.x.x
• 3.6.x
• 3.5.x refer the page #349
• 3.4.x refer the page #416
• 3.2.x refer the page #410

If your controller is running on 6.1.0 or later version, you can also go to "Network > Data and Control Plane > Cluster", select any of the controller nodes from the left side pan, then click on the "Network Settings" under "Details" section. It lists up all the required ports under "Inbound ports' 

For exact release related information, please go to v/SmartZone documentation at our support site and refer the administrator guide for your specific v/SmartZone version.

This may require when customer doesn’t know the access credentials for admin web console due to change in ownership of the device or lost password due to any other reason.

What is the problem?

If you have more than 1 AP in Unleashed network and want to reset entire network, this can be difficult due to redundancy feature on Unleashed.

If you factory reset current master, election process will quickly elect new master from any available AP in the network and old master AP will again join the Unleashed network as a member of it.

Then what is the solution?

There are three ways to factory reset entire Unleashed network.

Method-1

1. Disconnect all the APs physically from wired network, except the master AP.
2. Factory reset master AP by pushing and holding the reset button or using master AP CLI (ap-mode) and then run the command “set factory”.
3. Now reconfigure master as per requirement.
4. Reset other member APs one by one (one at a time), by powering up on a isolated network (member APs should not be able to reach master AP over the network) or using POE injector or power adapter.
5. Once all member APs factory defaulted, plug them back to the network so that they can be discovered by master and get the fresh configuration.

Note:

• Above procedure needs physical access to the devices, so cannot be done remotely.
• A power injector or POE switch (in isolated network) or a power adapter is required.

Method-2 

1. If all APs are connected to a managed switch, you can shut the switch ports of all the member APs.
2. Then factory reset master AP using CLI (set factory).
3. Now shut down the port for master and turn up other member APs (one at a time) and follow the same for rest of the APs.
4. Once all the APs are done, keep last AP online, configure as master and then un shut the all switch ports for other APs.

Note:

• For the above procedure you must have access to switch(es) where APs are connected.
• To run "set factory" CLI command on master AP you have to first go to "enable" mode >> "ap-mode" and then run the "set factory" command followed by "reboot".

Method-3

1. SSH into each AP or use master AP CLI (remote AP CLI option) to hardcode member APs role as “member only”. This way none of the member APs can become master, if original master factory reset or unreachable/unavailable.
   
   Command (from master AP):
   
   Please login: admin
   Password:
   Welcome to Ruckus Unleashed Network Command Line Interface
   ruckus> enable
   ruckus# debug
   You have all rights in this mode.
   ruckus(debug)# remote_ap_cli <AP_MAC_ADDRESS>"set election role 1"
   
   Command Usage: set election role
                    -> role <0=Clear 1=Member>
   
   Command (from member AP):
   
   rkscli> set election role 1
   
   Command Usage: set election role
                    -> role <0=Clear 1=Member>
2. Now factory reset master, followed by member APs. Once all are done, configure master AP again, and all member will join it.

Note: This procedure requires access to Unleashed AP CLI (member and master both), so if admin login credentials are not available, this cannot be done.

Got questions? Start the conversation!