| LED | Color | Description |
|---|---|---|
| PWR | Solid green | The AP has received a local IP address from the DHCP server. |
| Slow flashing green | A local network, DHCP, or VLAN issue has been detected. | |
| DIR or CTL | Solid green | The AP is connected to the cloud controller. |
| Fast flashing green | The AP is obtaining updates from the cloud controller. | |
| Slow flashing green | The AP is disconnected from the Internet. Check your network firewall settings. | |
| 2.4G and 5GHz | Solid green | The network is up and at least one wireless client is associated with it. |
| Solid orange | The network is up, but no clients are associated with it. | |
| Off | The network is down. | |
| AIR | Always off | Not used |
| LED | Status | Description |
|---|---|---|
| PWR | Off | No power connected. |
| PWR | Solid Red | Boot up in process. |
| PWR | Flashing Green | System started, no routable IP address detected. |
| PWR | Solid Green | Routable IP address received. |
| CTL | Off | Unleashed Member AP. |
| CTL | Flashing Green (slow, every 2 seconds) | Network problem. Cannot contact Unleashed Master. |
| CTL | Flashing Green (fast, 2x per second) | Receiving configuration or image upgrade. |
| CTL | Solid Green | Unleashed Master AP. |
| AIR | N/A | No upstream mesh connection (Root AP). |
| AIR |  | Upstream mesh connection established (Mesh AP). |
| AIR |  | Upstream mesh connection issue. |
| 2.4G | Off | Radio is down. |
| 2.4G | Amber (solid) | Radio is up, no clients are connected to the 2.4 GHz radio. |
| 2.4G | Solid Green | Radio is up, at least one client is connected to the 2.4 GHz radio. |
| 5G | Off | Radio is down. |
| 5G | Amber (solid) | Radio is up, no clients are connected to the 5 GHz radio. |
| 5G | Solid Green | Radio is up, at least one client is connected to the 5 GHz radio. |
| 5G | Flashing Green | Radio is up, at least one downstream Mesh AP is connected to the 5G radio. |
| ICX7150-C12 Switch>show version Copyright (c) 2017 Ruckus Wireless, Inc. All rights reserved. UNIT 1: compiled on Jul 3 2018 at 21:55:58 labeled as SPS08080 (25940204 bytes) from Primary SPS08080.bin **SW: Version 08.0.80T211** Compressed Boot-Monitor Image size = 786944, Version:10.1.11T225 (mnz10111) Compiled on Wed Dec 13 11:13:34 2017 HW: Stackable ICX7150-C12-POE ========================================================================== UNIT 1: SL 1: ICX7150-C12-2X1G POE 12-port Management Module Serial #:FEK3233P129 Software Package: BASE\_SOFT\_PACKAGE Current License: 2X1G P-ASIC 0: type B160, rev 11 Chip BCM56160\_B0 ========================================================================== UNIT 1: SL 2: ICX7150-2X1GC 2-port 2G Module ========================================================================== UNIT 1: SL 3: ICX7150-2X10GF 2-port 20G Module ========================================================================== 1000 MHz ARM processor ARMv7 88 MHz bus 8192 KB boot flash memory 2048 MB code flash memory 1024 MB DRAM STACKID 1 system uptime is 58 second(s) The system started at 02:15:38 GMT+00 Sat Jan 01 2000 The system : started=warm start reloaded=by "reload" ========================================================================== ========== WARNING: Boot-monitor version mismatch!!! ========== ========== Please use "show boot-monitor" command for details ========== ========================================================================== |
| SSH@ICX7150-24P Switch>ping xxx.xxx.xxx.xxx Sending 1, 16-byte ICMP Echo to xxx.xxx.xxx.xxx, timeout 5000 msec, TTL 64 Type Control-c to abort Reply from xxx.xxx.xxx.xxx : bytes=16 time=13ms TTL=53 Success rate is 100 percent (1/1), round-trip min/avg/max=13/13/13 ms. SSH@ICX7150-24P Switch> |
| SSH@ICX7150-24P Switch>en No password has been assigned yet... SSH@ICX7150-24P Switch#conf t SSH@ICX7150-24P Switch(config)#sz active-list xxx.xxx.xxx.xxx Version 08.0.92 onwards use the command below. SSH@ICX7150-24P Switch(config)#management active-list xxx.xxx.xxx.xxx SSH@ICX7150-24P Switch(config)# |
| ## Single AP Topology All the APs in the zone get their IP from the WAN router and provides the DHCP/NAT service. If H510/H320 is configured as GAP by the manual port selection, then LAN1 and LAN2 configuration will be pushed to eth1 and eth2 ports of H510/H320 APs instead of eth0 and eth1 ports. Each AP in this zone is running it’s own DHCP server instance. Typically configured when APs are at different sites and roaming is not required. | [](https://techblog.jcditservices.com/uploads/images/gallery/2024-08/6PPimage.png) |
| ## Multiple AP (Flat Network) Topology All the APs in the zone get their IP from the WAN router and designated APs to provide the DHCP/NAT service. A maximum of two APs be can select for DHCP service (Primary and Secondary) and ten APs for NAT Gateway. Designated APs in this zone are running the DHCP Server instance. Typically configured when multiple APs are at the same site and roaming across APs is needed. | [](https://techblog.jcditservices.com/uploads/images/gallery/2024-08/HIximage.png) |
| ## Hierarchical AP Topology Designated APs provide the DHCP/NAT service. Gateway APs (GAPs) get the IP address from the WAN router and non-gateway APs get the IP from the Gateway APs. If H510/H320 is configured as GAP by the manual port selection, then LAN1 and LAN2 configuration will be pushed to eth1 and eth2 ports of H510/H320 APs instead of eth0 and eth1 ports. In order to configure eth0 ports of H510/H320, the user needs to configure LAN5/LAN3 Ports respectively for the H510/H320 APs. Designated APs in this zone are running the DHCP Server instance. The DHCP server APs connected to the WAN, the rest of APs get their Private IP address from a local IP Pool with VLAN ID 1 from the DHCP Server AP. | [](https://techblog.jcditservices.com/uploads/images/gallery/2024-08/05Pimage.png) |