RUCKUS Technical Family

Announcement: FastIron 10.0.10c_cd3 Software & Product Guide Published on RUCKUS Support Portal

The FastIron 10.0.10c_cd3 software image and release notes have been published on the RUCKUS Support Portal.The PM can share the links below as needed for release announcements.RUCKUS ICX FastIron 10.0.10c_cd3 Softwarehttps://support.ruckuswireless.com/software/4032RUCKUS FastIron 10.0.10c_cd3 Release Notes, v1.0https://support.ruckuswireless.com/documents/4765 Note: HTML and PDF versions of the product guides are available in the document portal (https://docs.commscope.com).

Announcement: RUCKUS SmartZone 7.0.0 Streamlined Product Guides Published on RUCKUS Support Portal

The following RUCKUS SmartZone 7.0.0 *streamlined* product guides have been published on the RUCKUS Support Portal.The PM can share the links below as needed for release announcements.RUCKUS SmartZone (ST-GA) Access and Security Services Guide, 7.0.0RUCKUS SmartZone (ST-GA) Troubleshooting and Diagnostics, 7.0.0RUCKUS SmartZone (ST-GA) Tunnel and Data Plane, 7.0.0RUCKUS SmartZone (ST-GA) Network Administration Guide, 7.0.0RUCKUS SmartZone (ST-GA) Controller Administration Guide, 7.0.0Streamlined RUCKUS Administration SmartZone Guides: Enhancing User ExperienceBased on user feedback and internal review, we have redesigned the RUCKUS SmartZone set of Administration Guides to improve usability and streamline information. This strategic revamp is geared towards offering a more intuitive experience for both internal and external users. Now, let's explore the significant changes: Grouped Topics for Clarity and Efficiency:o RUCKUS SmartZone (ST-GA) Network Administration Guide, 7.0.0: Explore wireless network configuration, wireless traffic policies, and the administration of APs and switches.o RUCKUS SmartZone (ST-GA) Controller Administration Guide, 7.0.0: Discover controller setup, management, and system network services..o RUCKUS SmartZone (ST-GA) Access and Security Services Guide, 7.0.0: Gain insights into wireless user access control, authentication, and security protocols.o RUCKUS SmartZone (ST-GA) Tunnel and Data Plane, 7.0.0: Grasp tunneling concepts and configuration, as well as data plane deployment.o RUCKUS SmartZone (ST-GA) Troubleshooting and Diagnostics, 7.0.0: Enhance your understanding to address known issues and access troubleshooting steps for the resolution process. Furthermore, explore CLI commands for controllers, APs, Switches, and wireless environment issues. Improved Flow of Information: By consolidating content from eleven separate books into five comprehensive guides, we have simplified the process for users to find relevant information in one location.Whether you're configuring a network or troubleshooting an issue, the streamlined structure guarantees that you can quickly access the necessary details.The previously issued product guides from the SmartZone 7.0.0 release will not be available after May 17th from the RUCKUS Support Portal and CommScope Technical Content Portal.RUCKUS SmartZone (ST-GA) AP Management Guide, 7.0.0RUCKUS SmartZone (ST-GA)Basic Controller Settings, 7.0.0RUCKUS SmartZone (ST-GA) Client Management Guide,7.0.0RUCKUS SmartZone (ST-GA) Guest Access Guide,7.0.0RUCKUS SmartZone (ST-GA) Monitoring Guide,7.0.0RUCKUS SmartZone (ST-GA) Management Guide, 7.0.0RUCKUS SmartZone (ST-GA) Security Guide,7.0.0RUCKUS SmartZone (ST-GA) Switch Management Guide, 7.0.0RUCKUS SmartZone (ST-GA) Traffic Management Guide, 7.0.0RUCKUS SmartZone (ST-GA) User Management Guide, 7.0.0RUCKUS SmartZone (ST-GA) WLAN Management Guide, 7.0.0The above summary serves as an educational resource, bridging the gap between the old and new structures. As we upload this to the RUCKUS Support Portal and CommScope Technical Content Portal, we invite you to explore the revamped guides and provide further feedback. Your insights are invaluable as we continue to refine our documentation.

Optical Monitoring not working ICX7450/ ICX7550

 Hi,I have two switches, ICX7450 and ICX7550. Below is a table with switch models and tested image SW versions. On both switches, I could not get Digital Optical Monitoring to work on Ruckus vendor-provided part numbers: 33211-100 & 33210-100, but can get Digital Optical Monitoring to work on Brocade vendor-provided part numbers: 33211-100 & 33210-100 not matter the image versions . Global DOM settingsoptical-monitoroptical-monitor down-port-enableoptical-monitor non-ruckus-optic-enableShow OpticSTBD_SAS#sh optic 1/1/4Port Temperature Voltage Tx Power Rx Power Tx Bias Current+-----+-------------+-------------+-------------+-------------+---------------+1/1/4 29.9140 C 3.3328 volts -005.0196 dBm -026.3827 dBm 6.392 mANormal Normal Normal Low-Alarm NormalSTBD_SAS#sh optic 1/1/61G M-SX on port 1/1/6 is not capable of optical monitoring.Show MediaNote: 1/1/4 is the Brocade vendor-provided SFPNote: 1/1/6 is the Ruckus vendor-provided SFPSTBD_SAS#sh media eth 1/1/4Port 1/1/4: Type : 1GE M-SX(SFP) Vendor: RUCKUS Version: A Part# : 33210-100 Serial#: TAF217060000DV4STBD_SAS#sh media eth 1/1/6Port 1/1/6: Type : 1GE M-SX(SFP) Vendor: RUCKUS Version: A Part# : 33210-100 Serial#: TAU121110000188Show Media ValidationSTBD_SAS>sh media validationPort Supported Vendor Type --------------------------------------------------------------------- 1/1/4 Yes RUCKUS Type : 1GE M-SX(SFP)1/1/6 Yes RUCKUS Type : 1GE M-SX(SFP) SyslogLog on both switches suggest that the Ruckus-provided SFP is not Brocade qualifiedEnabling Port defined Optical Monitoringenconfig tint ethe 1/1/6optical-monitor1G M-SX(SFP) on port 1/1/XX is not capable of optical monitoringModelSW VersionSFP Vendor 1 SFP Part NumberDOMSupportedDOM Works?SFP Vendor 2SFP Part NumberDOMSupportedDOM Works?ICX745008.0.70dRuckus33211-100/ 33210-100YesNoBrocade33211-100/ 33210-100YesNoICX745008.0.80fRuckus33211-100/ 33210-100YesNoBrocade33211-100/ 33210-100YesNoICX745008.0.95dRuckus33211-100/ 33210-100YesNoBrocade33211-100/ 33210-100YesYesICX745008.0.95nRuckus33211-100/ 33210-100YesNoBrocade33211-100/ 33210-100YesYesICX755008.0.95fRuckus33211-100/ 33210-100YesNoBrocade33211-100/ 33210-100YesYesICX755008.0.95nRuckus33211-100/ 33210-100YesNoBrocade33211-100/ 33210-100YesYes

Issue with Stacking new unit in stack existant. ICX7150 (08095F UFI)

Hello everybody,I have a problem when a try to add a new unit in an existing stack of ICX7150. (08095F)Of course, the active stack and the unit have the same version.The stack mount well, but the active controller request a reboot of my new unit everytime the stack mount.I have try to add with static and dynamic methods.Here the logs of my issue :____________________ ON ACTIVE CONTROLLER_________________SSH@SW_EMERAUDE_253#sh stackT=3h30m53.1: alone: standalone, 😧 dynamic cfg, S: staticID Type Role Mac Address Pri State Comment1 S ICX7150-48PF active fc5c.4532.3988 200 local Ready2 S ICX7150-48 standby 3845.3b2f.5238 190 remote Ready3 D ICX7150-48P member 903a.7216.d3a8 0 remote Reset: vlan: U1 1024, U3 4active standby +---+ +---+ +---+-3/3| 1 |3/1--3/3| 2 |3/1--3/3| 3 |3/1-| +---+ +---+ +---+ || ||-------------------------------------------|Will assign standby in 78 sec due to electionStandby u2 - protocols ready, can failoverCurrent stack management MAC is fc5c.4532.3988_______________________ON NEW UNIT (CLI)_________________________________________Success - Enable stacking. This unit actively participates in stackingRSA Key pair is successfully created[MEMBER]local-3@ICX7150-48P Switch>[MEMBER]local-3@ICX7150-48P Switch>PS 1, Internal Power supply detected.PS 1, Internal Power supply is up.PoE: Stack unit 3 PS 1, Internal Power supply with 370000 mwatts capacity is upCreating certificate, please wait...SSL Client Certificate is successfully createdUNIT3:System initialization completed...console going online.Copyright (c) Ruckus Networks, Inc. All rights reserved.UNIT 3: compiled on Dec 16 2021 at 03:40:25 labeled as SPS08095f(31457280 bytes) from Primary SPS08095f.bin (UFI)SW: Version 08.0.95fT211Compressed Primary Boot Code size = 786944, Version:10.1.21T225 (mnz10121)Compiled on Wed Aug 25 06:27:49 2021HW: Stackable ICX7150-48-POE==========================================================================UNIT 3: SL 1: ICX7150-48P-2X10G_2X1G POE 48-port Management ModuleSerial #:Software Package: BASE_SOFT_PACKAGECurrent License: 2X10GP-ASIC 4: type B160, rev 11 Chip BCM56160_B0==========================================================================UNIT 3: SL 2: ICX7150-2X1GC 2-port 2G Module==========================================================================UNIT 3: SL 3: ICX7150-4X10GF 4-port 40G Module==========================================================================1000 MHz ARM processor ARMv7 88 MHz bus8 MB boot flash memory2 GB code flash memory1 GB DRAMSTACKID 3 system uptime is 25 second(s)The system started at 03:54:57 GMT+00 Thu Dec 16 2021The system : started=warm start reloaded=by "reload"My stack unit ID = 3, bootup role = member[MEMBER]local-3@ICX7150-48P Switch>UNIT3:In szAgent_save_initial_runningConfigTimestamp(), 0T=32.0: Election, I 903a.7216.d3a8 was member, no change, ID=3, pri=0, 3U(1-3), A=u1, nbr#=2 2,reason: u2: port-up,T=34.9: Election, I 903a.7216.d3a8 was member, no change, ID=3, pri=0, 3U(1-3), A=u1, nbr#=2 2,reason: u1: stk-po-chg,T=38.4: Boot request from u1 mac=fc5c.4532.3988, my ID=3, reason: vlan: U1 1024, U3 4, flash: Primary, jumbo=0,_______________________________________________________________________________________Has somenone knowledge of this issue ? I've try some technics but this issues occur everytime.Thank you very much. Kevin

R850 won't connect to Virtual Smart Zone 5.2.0

Hi! We recently purchased a R850, but it won't show up in our Virtual Smart Zone 5.2.0. We already tried the following:set scg ipdownloading the firmware from our vsz 5.2.0disable cert check on controlleruploading AP patch 5.2.0.0.5527 to our vsz 5.2.0.0.699set discovery-agent enablethe controller can ping the AP. the AP can ping the controller.there is enough AP capacity license in controllerThese are the results of the debug mode log from get syslog log:May 3 10:24:02 RuckusAP daemon.info cubic[685]: util_cmd_proc:1574 Execute CMD type: [1][GET_BASE_INFO].May 3 10:24:02 RuckusAP daemon.warn cubic[685]: apcfg_general_get_base_info:513 ret:[6]/[bad key: device-gps-coordinates] No GPS dataMay 3 10:24:02 RuckusAP daemon.info cubic[685]: apcfg_general_get_sz_list:352 Server list[10.158.31.12,10.158.31.11] from DHCP..May 3 10:24:02 RuckusAP daemon.warn cubic[685]: apcfg_general_get_base_info:565 ret:[34]/[file missing for RSM services] No server cert validation setting.May 3 10:24:02 RuckusAP daemon.debug cubic[685]: apcfg_general_get_radio_info:153 background scan wifi0: en:0, timer:20, channel num:13.May 3 10:24:02 RuckusAP daemon.debug cubic[685]: apcfg_general_get_radio_info:153 background scan wifi1: en:0, timer:20, channel num:24.May 3 10:24:02 RuckusAP daemon.debug cubic[685]: cub_conn_get_addr_state_action:635 Current server list:[10.158.31.12,10.158.31.11], target address:[10.158.31.11], remaining address:[(null)], pending retry:[0].May 3 10:24:02 RuckusAP daemon.info cubic[685]: cub_state_action:2285 Start [DISC_REQ_STATE].May 3 10:24:02 RuckusAP daemon.info cubic[685]: cub_state_action:2289 [CONN_GET_ADDR_STATE] -> [DISC_REQ_STATE]; reason: [CUB_RESULT_CONN_GET_ADDR_SUCCESS].May 3 10:24:02 RuckusAP daemon.info cubic[685]: json_cmd_proc:558 Data type : [1][GENERATE_DISCOVER].May 3 10:24:02 RuckusAP daemon.debug cubic[685]: apcfg_general_get_radio_info:153 background scan wifi0: en:0, timer:20, channel num:13.May 3 10:24:02 RuckusAP daemon.debug cubic[685]: apcfg_general_get_radio_info:153 background scan wifi1: en:0, timer:20, channel num:24.May 3 10:24:02 RuckusAP daemon.warn cubic[685]: apcfg_general_get_base_info:513 ret:[6]/[bad key: device-gps-coordinates] No GPS dataMay 3 10:24:02 RuckusAP daemon.info cubic[685]: apcfg_general_get_sz_list:352 Server list[10.158.31.12,10.158.31.11] from DHCP..May 3 10:24:02 RuckusAP daemon.warn cubic[685]: apcfg_general_get_base_info:565 ret:[34]/[file missing for RSM services] No server cert validation setting.May 3 10:24:02 RuckusAP daemon.err cubic[685]: apcfg_general_get_wan_ipv6:1119 Get IP error. stop rsm config get/set, please check the config key and valueMay 3 10:24:02 RuckusAP daemon.debug cubic[685]: curl_https_request:1332 curl_https_request, msg_type:[0][MSG_TYPE_DISC], via ssh:[no], send_data:[{ "protocolVersion": "0.50", "mac": "2C:AB:46:14:B7:B0", "serial": "342322022009", "deviceName": "RuckusAP", "model": "R850", "timeStamp": 1714731842, "fwVersion": "114.0.0.0.5585", "gpsInfo": "", "deviceIpMode": 3, "ip": "10.158.31.58", "ipv6": "fc00::1", "countryCode": "PH", "provisionTag": "", "location": "", "devSupportUsb": "1", "meshRole": 0, "radio": [[{ "channel": "1,2,3,4,5,6,7,8,9,10,11,12,13" }], [{ "channel": "36,40,44,48,52,56,60,64,100,104,108,112,116,120,124,128,132,136,140,149,153,157,161,165" }]] }].May 3 10:24:02 RuckusAP daemon.info cubic[685]: util_cmd_proc:1574 Execute CMD type: [5][GET_DOMAIN_SUFFIX_INFO].May 3 10:24:02 RuckusAP daemon.debug cubic[685]: need_append_suffix:450 Check whether addr is numeric IP. buf:10.158.31.11.May 3 10:24:02 RuckusAP daemon.debug cubic[685]: wrap_getaddrinfo:1187 getaddrinfo with address [10.158.31.11] returns success.May 3 10:24:02 RuckusAP daemon.debug cubic[685]: resolve_addrinfo:1236 wrap_getaddrinfo with addr [10.158.31.11] returns success.May 3 10:24:02 RuckusAP daemon.debug cubic[685]: do_curl:968 No SZ public key from APR, skip verification..May 3 10:24:02 RuckusAP daemon.info cubic[685]: do_curl:1069 Send HTTP request to URL:[https://10.158.31.11:443/wsg/ap/discovery/2C:AB:46:14:B7:B0].May 3 10:24:03 RuckusAP daemon.info cubic[685]: util_cmd_proc:1574 Execute CMD type: [30][SET_TIMESTAMP].May 3 10:24:03 RuckusAP daemon.debug cubic[685]: http_timestamp_parser:1250 Received Timestamp: Fri, 03 May 2024 10:24:04 GMT^M .May 3 10:24:03 RuckusAP daemon.debug cubic[685]: apcfg_set_timestamp:1332 SCG: 1714731844 Delta: 1 Current: 1714731843 LastSync: 1714731792 SyncDelta: 51.May 3 10:24:03 RuckusAP daemon.info cubic[685]: curl_https_request:1414 curl_easy_perform success. http response code:[502].May 3 10:24:03 RuckusAP daemon.info cubic[685]: cub_disc_req_state_action:684 DISC request http return code:[502]..May 3 10:24:03 RuckusAP daemon.info cubic[685]: cub_state_action:2285 Start [CONN_GET_ADDR_STATE].May 3 10:24:03 RuckusAP daemon.info cubic[685]: cub_state_action:2289 [DISC_REQ_STATE] -> [CONN_GET_ADDR_STATE]; reason: [CUB_RESULT_DISC_REQ_FAIL].What could be the issue? Thank you in advance!

SZ NAT Design - Can some APs use internal IP while others use External NAT IP?

I've been following the old Smartzone Network-Design-with-NAT guide and something I'm trying to wrap my head around is the AP Connection behaviour when both internal and NAT addresses are reachable.Preferably, we'd like to have new APs out of the box, reach out over the public internet to download firmware and initial configurations. Their Zone/APGroup config should inform them to switch management to another VLAN which has access to the internal IPs of the SZs in the cluster.Is this possible?