I have a lot of the new AP R370's not connecting to Ruckus One and flashing amber. I can get into their SSH and Web Interface and all looks okay, I am trying to refresh/upgrade its firmware however there are no files available or really any troubleshooting help with this new AP! 

Any help, appreciated!

ICX7150-C12P 

FEK3226N1JZ

THANK YOU

SN# FEK3226N1JN

We are managing 16 APs from Ruckus Unleashed, we had configured the management IP and we can access to Unleashed through this management IP.
Now, as soon as I access to Unleashed, this shows me the following message:
"Unleashed portal is now available for cloud remote control. Sign up now"
I went to "Sign up now" and created an account
There, when I tried to bind the network, I get:
"Error. Network´s username or password verification failed"

We would like to use the remote management to access directly from anywhere. How can we solve this?

Thanks in advance.
Regards!

Damián

```
Sep 6 13:10:11 prd-radio syslog: upgrade_debug: pid=5161, insert_field_to_upgrade_ap_list(): firmware_file open failure
Sep 6 13:10:11 prd-radio syslog: upgrade_debug: pid=5161, get_ap_list(): see [/tmp/unleashed_upgrade/upgrade_ap_list_from_election.xml.ready], ap-list ready!
Sep 6 13:10:11 prd-radio syslog: upgrade_debug: pid=5161, get_ap_list(): ap-list loop 0.
```

That's my first problem with it. My second problem is that it won't negotiate 802.3at (POE+) no matter what I try. I'm powering it with a Juniper SRX320-POE, and I have enabled POE negotiation on the source but it still recognizes it as a "802.3af Switch/Injector":

```
ruckus(ap-mode)# get power-mode
PoE Configured Mode : Auto
Power Consumption Status : 802.3af Switch/Injector
USB Status : Disabled
OK
```
Forcing it to use POE+ with `set power-mode at` works, but doesn't persist after reboot.

Finding what the log messages mean has been a big pain as documentation that refers to it is almost non-existent.

Thank you

SCH-ACCESS-101(config)# vlan 10 by port
SCH-ACCESS-101(config-vlan-10)# untag ethernet 1/1/1 to 1/1/4
SCH-ACCESS-101(config-vlan-10)# management-vlan
SCH-ACCESS-101(config-vlan-10)# default-gateway 10.10.10.1 1
SCH-ACCESS-101(config-vlan-10)# default-gateway 10.20.20.1 2

! User VLAN configuration.

SCH-ACCESS-101(config)# vlan 1011
SCH-ACCESS-101(config-vlan-1011)# tagged ethernet 1/1/13 to 1/1/17 ethernet 1/2/2 ethernet 1/2/4 ethernet 2/2/2 ethernet 2/2/4
SCH-ACCESS-101(config-vlan-1011)# untagged ethernet 1/1/12
SCH-ACCESS-101# show vlan 1011
Total PORT-VLAN entries: 14
Maximum PORT-VLAN entries: 64
Legend: [Stk=Stack-Id, S=Slot]
PORT-VLAN 1011, Name data_vlan, Priority level0, Spanning tree On
Untagged Ports: (U1/M1) 12
Tagged Ports: (U1/M1) 13 14 15 16 17
Tagged Ports: (U1/M2) 2 4
Tagged Ports: (U2/M2) 2 4
Uplink Ports: None
DualMode Ports: None
Mac-Vlan Ports: None
Monitoring: Disabled

! Multiple VLANs applied to a single port.

Device(config)#vlan 2 3 5 6 9 12
Device(config-mvlan-2*12)#tagged ethernet 1/1/1
Device(config-mvlan-1*12)#show vlan brief ethernet 1/1/1

Port 1/1/1 is a member of 6 VLANs
VLANs 1 3 5 to 6 9 12
Untagged VLAN   : 1
Tagged   VLANs  : 3 5 to 6 9 12

Fig 1 - Node join validation error

Environment - This example is from a vSZ-E (Essentials) with firmware 6.1.2 and running on VMWare ESXi Hypervisor. However, it is also applicable to vSZ-H (High-Scale) running any firmware version and deployed on any supported Hypervisor platform.

Resolution and Explanation - Make sure that VM Resource level of all the nodes of a vSZ cluster are the same. The Resource level matrix can be found on the respective firmware version's Upgrade Guides. For instance, vSZ-E 6.1.2 version has 1, 1.5, 2  and 3 as the Resource Levels that is dependent on the RAM, Disk size and vCPU per node :-

Fig 2 - Resource Level Matrix of vSZ-E

In this case, it was found that the vSZ node trying to join the Cluster had 21 GB of RAM allocated which brought it to Resource Level 3, while the existing Cluster Node had only14 GB of RAM allocated which means it was running on Resource Level 1. Therefore, a node with Resource Level 1 could not join a Cluster on Resource Level 4. 

Fig 3 - RAM allocation to vSZ node

After shutting down the instance and lowering the Memory to match the resource level of Cluster, the new vSZ node joined without any issue.

Regards,

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. 

Customer Environment
vSZ running on 3.6.2.0.222 loaded in ESXi 6.5

Symptoms
All the APs connected to the vSZ are getting disconnected while migrating vSZ from ESXi 6.5 to 6.7 using vMotion.

Resolution
vMotion is not supported for migration of ESXi as it triggers the S/N of the vSZ change. 

Flashes amber initially after 

After reset, system light amber, power light green. No lights on wireless access points. No network visibility. 

ISP is working good. 

All troubleshooting from forums done, including this link: RUCKUS Forums - How to perform a Software recovery on an ICX7150 s... - CommScope RUCKUS Community Forums (ruckuswireless.com)

I need an RMA please. 

Thank you,

Sean

I wanted to take a moment to touch on the minimum code level to onboard an ICX switch to RUCKUS Cloud. In order for an ICX to begin the onboarding process to RUCKUS Cloud, they must be running a minimum code level of 8090d. To confirm your code level, you can use the "show version" command.  If you happen to be running code older than 8090d, you will need to manually upgrade your ICX. Here are the recommended upgrade paths coming from older code:

-If you are running 8080 flat to 8090c, upgrade directly to 8095ca via UFI image

-If you are running any 8070 patch or older, we will need to do a multi-step upgrade. The upgrade path will be: 8070x or older > 8080f (non-ufi) > 8095ca UFI

Additional details are documented in our FastIron Management Guide here and our Cloud User Guide here 

As always, if you need assistance with an upgrade, please do open a case (see my signature) and our support team would be happy to help. 

Have you ever wondered what code Ruckus recommends you run on your ICX? You are in luck. Each product support page has a built-in recommendation or recommendations. While these recommendations will not cover every scenario or customer, it should be your starting reference when selecting code for ICX devices. The recommendations are updated occasionally and will change over time. We recommend most customers look to our Stability Release if it contains all needed features for your network. As always, you can contact us if you are unsure where to start. 

To find the recommended code, navigate to:

https://support.ruckuswireless.com/product_families/21-ruckus-icx-switches

On the above page, you can see the recommendations for all active models and it will contain a direct link for our recommended code. If needed, you can select the appropriate model to get to additional downloads, documents, etc (ex. ICX8200 Support Page).

I have attached a screenshot from our ICX8200 page highlighting the recommended code field.

NOTE: RUCKUS One (cloud) users should look to the recommendation in their respective web GUI. The recommendations here are generally for non-cloud customers.