Controllerless Networks

 View Only
last person joined: 23 hours ago 

Instant Mode - the controllerless Wi-Fi solution that's easy to set up, is loaded with security and smarts, and won't break your budget
Back to discussions
Expand all | Collapse all

Replacement Ruckus R510 with new APs 503 ( R8M98A)

This thread has been viewed 13 times

  • 1.  Replacement Ruckus R510 with new APs 503 ( R8M98A)

    Posted Feb 01, 2024 10:26 AM

    Hello,

    We replaced Ruckus AP with new AP103s in a hotel.

    The new AP are placed in the same place as the old Ruckus and now the customer complains that the coverage is less good than with the old AP.

    On some room, there the signal is poor.

     
    We have disabled the channels U-NII-4 enad UNNI-3 to use only U-NII-2 Extended to have the max power transmit allowed by EIRP, so in 5G we have 28dbm and on 2.4 we have 20dBm , There is no Noise between AP.

    Do you have an idea to optimize the signal ?

    This is my configuration :

    version 8.11.2.0-8.11.2
    virtual-controller-country FR
    virtual-controller-key ****
    name "Hotel ***"
    virtual-controller-ip 192.168.99.100
    terminal-access
    ntp-server 8.8.8.8
    clock timezone Paris 01 00
    rf-band all

    allow-new-aps


    allowed-ap 50:e4:e0:****
    ****

    arm
     wide-bands 5ghz
     a-channels 36,40,44,48,52,56,60,64,100,104,108,112,116,120,124,128,132,136,140,100+,108+,116+,124+,132+
     min-tx-power 15
     max-tx-power 127
     band-steering-mode prefer-higher-band
     air-time-fairness-mode default-access
     channel-quality-aware-arm-disable
     client-aware
     scanning
     client-match
     client-match nb-matching 75
     client-match calc-threshold 2
     client-match calc-interval 30

    rf dot11g-radio-profile
     max-tx-power 127
     min-tx-power 127
     smart-antenna

    rf dot11a-radio-profile
     max-tx-power 127
     min-tx-power 127
     smart-antenna

    rf dot11a-secondary-radio-profile
     max-tx-power 127
     min-tx-power 18
     smart-antenna

    rf dot11-6ghz-radio-profile
     max-tx-power 127


    syslog-level warn ap-debug 
    syslog-level warn network 
    syslog-level warn security 
    syslog-level warn system 
    syslog-level warn user 
    syslog-level warn user-debug 
    syslog-level warn wireless 

    extended-ssid
    web-server
     ssl-protocol tlsv1_2

    hash-mgmt-password
    hash-mgmt-user admin password hash ****


    wlan access-rule default_wired_port_profile
     index 0
     rule any any match any any any permit

    wlan access-rule wired-SetMeUp
     index 1
     rule masterip 0.0.0.0 match tcp 80 80 permit
     rule masterip 0.0.0.0 match tcp 4343 4343 permit
     rule any any match udp 67 68 permit
     rule any any match udp 53 53 permit

    wlan access-rule Chtvsr
     index 2
     rule any any match any any any permit

    wlan access-rule "Adm * * "
     index 3
     rule any any match any any any permit

    wlan access-rule "Hotel *.*"
     index 4
     rule any any match any any any permit

    wlan access-rule iptvsr
     index 5
     rule any any match any any any permit

    wlan ssid-profile Chtvsr
     enable
     index 0
     type employee
     essid Chtvsr
     wpa-passphrase ****
     opmode wpa2-psk-aes
     max-authentication-failures 0
     vlan 104
     rf-band all
     captive-portal disable
     hide-ssid
     dtim-period 1
     broadcast-filter arp
     g-min-tx-rate 12
     a-min-tx-rate 12
     dmo-channel-utilization-threshold 90
     local-probe-req-thresh 0
     max-clients-threshold 64
     dot11k
     dot11v

    wlan ssid-profile "Adm hotel"
     enable
     index 1
     type employee
     essid "Adm *.**"
     wpa-passphrase ****
     opmode wpa-psk-tkip,wpa2-psk-aes
     max-authentication-failures 0
     vlan 103
     rf-band all
     rf-band-6ghz
     captive-portal disable
     dtim-period 1
     broadcast-filter arp
     g-min-tx-rate 12
     a-min-tx-rate 12
     dmo-channel-utilization-threshold 90
     local-probe-req-thresh 0
     max-clients-threshold 64
     dot11r
     dot11k
     dot11v

    wlan ssid-profile "Hotel Guest"
     enable
     index 2
     type employee
     essid "Hotel Guest"
     opmode opensystem
     max-authentication-failures 0
     vlan 101
     rf-band all
     captive-portal disable
     dtim-period 1
     broadcast-filter arp
     g-min-tx-rate 12
     dmo-channel-utilization-threshold 90
     local-probe-req-thresh 0
     max-clients-threshold 64
     dot11k
     dot11v

    wlan ssid-profile iptvsr
     enable
     index 3
     type employee
     essid iptvsr
     wpa-passphrase ****
     opmode wpa2-psk-aes
     max-authentication-failures 0
     vlan 104
     rf-band all
     captive-portal disable
     hide-ssid
     dtim-period 1
     broadcast-filter arp
     g-min-tx-rate 12
     a-min-tx-rate 12
     dmo-channel-utilization-threshold 90
     local-probe-req-thresh 0
     max-clients-threshold 64
     dot11r
     dot11k
     dot11v

    auth-survivability cache-time-out 24

    wlan external-captive-portal
     server localhost
     port 80
     url "/"
     auth-text "Authenticated"
     auto-whitelist-disable
     https


    blacklist-time 3600
    auth-failure-blacklist-time 3600


    ids
     wireless-containment none
     infrastructure-detection-level low
     client-detection-level low
     infrastructure-protection-level low
     client-protection-level low

    wired-port-profile wired-SetMeUp
     switchport-mode access
     allowed-vlan all
     native-vlan guest
     no shutdown
     access-rule-name wired-SetMeUp
     speed auto
     duplex auto
     no poe
     type guest
     captive-portal disable
     no dot1x

    wired-port-profile default_wired_port_profile
     switchport-mode trunk
     allowed-vlan all
     native-vlan 1
     shutdown
     access-rule-name default_wired_port_profile
     speed auto
     duplex full
     no poe
     type employee
     captive-portal disable
     no dot1x


    enet0-port-profile default_wired_port_profile

    uplink
     preemption
     enforce none
     failover-internet-pkt-lost-cnt 10
     failover-internet-pkt-send-freq 30
     failover-vpn-timeout 180

    airgroup
     enable

    airgroupservice airplay
     enable

    airgroupservice airprint
     enable

    airgroupservice itunes
     enable

    airgroupservice remotemgmt
     enable

    airgroupservice sharing
     enable

    airgroupservice googlecast
     enable

    airgroupservice AmazonTV
     enable

    airgroupservice DIAL
     enable

    airgroupservice "DLNA Media"
     enable

    airgroupservice "DLNA Print"
     enable

    airgroupservice allowall
     enable

    cluster-security
     allow-low-assurance-devices



  • 2.  RE: Replacement Ruckus R510 with new APs 503 ( R8M98A)

    EMPLOYEE
    Posted Feb 01, 2024 10:55 AM

    When you say "coverage is less good" or "signal is poor", do you have numbers to reference against? Did you run a survey of the environment before and after?

    Where is the AP-503 installed?  Is the AP installed on the ceiling?  At what power is the AP transmitting? What is the size of the area attempting to be covered?



    ------------------------------
    Carson Hulcher, ACEX#110
    ------------------------------

    Original Message


  • 3.  RE: Replacement Ruckus R510 with new APs 503 ( R8M98A)

    Posted Feb 09, 2024 03:35 AM

    In addition to another poster's recommendation to work on actual numbers rather than hearsay:

    Having a transmit power of 28dBm (630mW) in the 5GHz band is asking for trouble. Please reduce that to at most 23dBm (200mW), preferably no more than 20dBm (100mW.) Also, common practice is to have 2.4Ghz signal ~6dB lower than 5GHz to ensure 2.4GHz signal doesn't look artificially good, discouraging clients from roaming to 5GHz radios.

    Most client devices will have a transmit power of <=20dBm. If you have an AP that pushes out 5x-6x more power, the client will think signal level is still great and "stick" to that AP for much longer than it should.

    Appropriate WiFi design would target AP transmit power to match client transmit power and still get appropriate coverage. So if your client devices are primarily mobile phones, optimally you'd target an (EIRP) transmit power of somewhere around 16-18dBm, and design cells such that AP signals overlap at ~-65dBm to -67dBm. This is because popular devices (Apple...) start looking to roam to a new AP when signal level reaches -70dBm, by which time the "new" AP should be 8dB stronger (or better.)

    (Of course, money does tend to come in the way of optimal design sometimes, so you have to make well-considered tradeoffs where needed!)

    In the example above, assuming a client device that can transmit at 16dBm: if your AP is transmitting at 28dBm, by the time the received signal at the client is at -70dBm, the received signal at the AP will be -82dBm which is likely too low for a stable connection and the user's experience would have degraded by that time.

    Anecdotally in my neck of the woods, Ruckus deployments (and certain other vendors who shall go unnamed...) are notorious for configuring transmit power to absolute maximums to make things "look good, but work bad", but it's possible that may just be due to the limited number of integrators that implement the product in my area.

    For reference, here is a list of client devices and their transmit powers that Mike Albano (quite the legend!) has documented over the years: ClientsList - Google Blaaie


    Original Message