Find Technical Content
  • Home
  • Ruckus Support Portal
  • Ruckus Networks
  • Table of Contents
  • Dark Mode

Powered by Titania Delivery

⚠ This cached page may be outdated. Click refresh to get the latest content.
Cached Version You are Offline

You are viewing a cached version of this page.

You are currently offline. This page was loaded from cache.

RUCKUS SmartZone (LT-GA) Alarms and Events Reference Guide, 7.2.0 800-73880-001 Rev A

  • 1 Vistance Legal Statements
  • 2 Ruckus Back Cover
  • Preface Ruckus
    • 3 Contact Information, Resources, and Conventions
      • 3.1 Contacting RUCKUS Customer Services and Support
      • 3.2 Document Feedback
      • 3.3 RUCKUS Product Documentation Resources
      • 3.4 Online Training Resources
      • 3.5 Document Conventions
      • 3.6 Command Syntax Conventions
  • 4 About This Guide
    • 4.1 Introduction
    • 4.2 Terminology
  • 5 Alarm and Event Management
    • 5.1 Overview
    • 5.2 Alarm and Event Management
      • 5.2.1 Event Categories
      • 5.2.2 Event Attributes
      • 5.2.3 Generation of Alarm and Event
      • 5.2.4 Smart Monitor Feature
  • 6 Alarm Types
    • 6.1 Introduction
    • 6.2 Accounting Alarms
      • 6.2.1 Accounting server not reachable
    • 6.3 AFC Alarms
      • 6.3.1 AFC Authentication Required
    • 6.4 AP Authentication Alarms
      • 6.4.1 RADIUS server unreachable
      • 6.4.2 LDAP server unreachable
      • 6.4.3 AD server unreachable
    • 6.5 AP Communication Alarms
      • 6.5.1 AP rejected
      • 6.5.2 AP configuration update failed
      • 6.5.3 AP swap model mismatched
      • 6.5.4 AP pre-provision model mismatched
      • 6.5.5 AP firmware update failed
      • 6.5.6 AP WLAN oversubscribed
    • 6.6 AP LBS Alarms
      • 6.6.1 No LS responses
      • 6.6.2 LS authentication failure
      • 6.6.3 AP failed to connect to LS
    • 6.7 AP State Change Alarms
      • 6.7.1 AP rebooted by system
      • 6.7.2 AP disconnected
      • 6.7.3 AP deleted
      • 6.7.4 AP cable modem interface down
      • 6.7.5 AP DHCP service failure
      • 6.7.6 AP NAT failure
      • 6.7.7 AP on Recovery Partition After Panic
      • 6.7.8 AP DHCP/NAT DWPD Ethernet port configuration override
      • 6.7.9 SZ DHCP/NAT DWPD Ethernet port configuration override
      • 6.7.10 SIM removal
    • 6.8 AP 3rd Radio
    • 6.9 AP Thermal Management
    • 6.10 Authentication Alarms
      • 6.10.1 Authentication server not reachable
      • 6.10.2 Authentication failed over to secondary
      • 6.10.3 Authentication fallback to primary
      • 6.10.4 AD/LDAP connectivity failure
      • 6.10.5 Bind fails with AD/LDAP
      • 6.10.6 Bind success with LDAP, but unable to find clear text password for the user
      • 6.10.7 RADIUS fails to connect to AD NPS server
      • 6.10.8 RADIUS fails to authenticate with AD NPS server
      • 6.10.9 Fails to establish TLS tunnel with AD/LDAP
      • 6.10.10 RAC DNS Resolve Failed
    • 6.11 Control and Data Plane Interface Alarms
      • 6.11.1 GtpManager (DP) disconnected
    • 6.12 Cloud Alarms
      • 6.12.1 Cloud Analytics Service has been Enabled
      • 6.12.2 Cloud Analytics Service has been Disabled
      • 6.12.3 Cloud Analytics Disconnected
    • 6.13 Cluster Alarms
      • 6.13.1 New node failed to join
      • 6.13.2 Node removal failed
      • 6.13.3 Node out of service
      • 6.13.4 Cluster in maintenance state
      • 6.13.5 Cluster backup failed
      • 6.13.6 Cluster restore failed
      • 6.13.7 Cluster upgrade failed
      • 6.13.8 Cluster application stopped
      • 6.13.9 Node bond interface down
      • 6.13.10 Node physical interface down
      • 6.13.11 Cluster node rebooted
      • 6.13.12 Cluster node shut down
      • 6.13.13 Node IP Changed
      • 6.13.14 Disk usage exceed threshold
      • 6.13.15 Cluster out of service
      • 6.13.16 Cluster upload AP firmware failed
      • 6.13.17 Cluster add AP firmware failed
      • 6.13.18 Cluster upload KSP file failed
      • 6.13.19 Configuration backup failed
      • 6.13.20 Configuration restore failed
      • 6.13.21 AP certificate updated
      • 6.13.22 Upgrade SS table failed
      • 6.13.23 Over switch max capacity
      • 6.13.24 AP is connected to Standby Cluster Over The Expiration Date
      • 6.13.25 Active Cluster unable to Connect to other Active Clusters for Cluster Redundancy
      • 6.13.26 External DP Connected to Standby Cluster after Rehome Timeout
      • 6.13.27 Certificate is about to Expire
      • 6.13.28 Certificate is already Expired
    • 6.14 Configuration Alarms
      • 6.14.1 Zone configuration preparation failed
      • 6.14.2 AP configuration generation failed
      • 6.14.3 End-of-life AP model detected
    • 6.15 Data Plane Alarms
      • 6.15.1 Data plane configuration update failed
      • 6.15.2 Data plane disconnected
      • 6.15.3 Data plane physical interface down
      • 6.15.4 Data plane process restarted
      • 6.15.5 Data plane license is not enough
      • 6.15.6 Data plane upgrade failed
      • 6.15.7 Data plane of data center side fails to connect to the CALEA server
      • 6.15.8 Data plane fails to connects to the other data plane
      • 6.15.9 Data plane DHCP IP pool usage rate is 100 percent
    • 6.16 Data Streaming Alarms
      • 6.16.1 Connecting Failure to a Data Streaming Profile
    • 6.17 GR Interface Alarms
      • 6.17.1 Destination not reachable
      • 6.17.2 App server down
      • 6.17.3 App server inactive
      • 6.17.4 Association establishment failed
      • 6.17.5 Association down
      • 6.17.6 Outbound routing failure
      • 6.17.7 Did allocation failure
    • 6.18 IPMI Alarms
      • 6.18.1 ipmiVoltage
      • 6.18.2 ipmiThempBB
      • 6.18.3 ipmiThempFP
      • 6.18.4 ipmiThempIOH
      • 6.18.5 ipmiThempMemP
      • 6.18.6 ipmiThempPS
      • 6.18.7 ipmiThempP
      • 6.18.8 ipmiThempHSBP
      • 6.18.9 ipmiFan
      • 6.18.10 ipmiPower
      • 6.18.11 ipmiCurrent
      • 6.18.12 ipmiFanStatus
      • 6.18.13 ipmiPsStatus
      • 6.18.14 ipmiDrvStatus
    • 6.19 Licensing Alarms
      • 6.19.1 TTG session critical threshold
      • 6.19.2 TTG session license exhausted
      • 6.19.3 License going to expire
      • 6.19.4 Insufficient license capacity
      • 6.19.5 Data plane DHCP IP license insufficient
      • 6.19.6 Data plane NAT session license insufficient
      • 6.19.7 Insufficient license capacity
    • 6.20 PMIPv6 Alarms
      • 6.20.1 Config update failed
      • 6.20.2 DHCP connection lost
    • 6.21 SCI Alarms
      • 6.21.1 Connect to SCI failure
      • 6.21.2 SCI has been disabled
      • 6.21.3 SCI and FTP have been disabled
    • 6.22 Session Alarms
      • 6.22.1 Binding failed
    • 6.23 System Alarms
      • 6.23.1 No LS responses
      • 6.23.2 LS authentication failure
      • 6.23.3 {produce.short.name} failed to connect to LS
      • 6.23.4 Syslog server unreachable
      • 6.23.5 CSV export FTP maximum retry
      • 6.23.6 CSV export disk threshold exceeded
      • 6.23.7 CSV export disk max capacity reached
      • 6.23.8 Process restart
      • 6.23.9 Service unavailable
      • 6.23.10 Keepalive failure
      • 6.23.11 Resource unavailable
      • 6.23.12 HIP failed over
      • 6.23.13 Unconfirmed Program Detection
      • 6.23.14 Diameter initialization error
      • 6.23.15 Diameter peer transport failure
      • 6.23.16 Diameter CER error
      • 6.23.17 Diameter peer add error
      • 6.23.18 Diameter peer remove successful
      • 6.23.19 Diameter realm entry error
      • 6.23.20 Diameter failover to alternate peer
      • 6.23.21 Diameter fail back to peer
      • 6.23.22 Diameter CEA unknown peer
      • 6.23.23 Diameter no common application
      • 6.23.24 Process initiated
      • 6.23.25 PMIPv6 unavailable
      • 6.23.26 Memory allocation failed
      • 6.23.27 API High Latency Detected
    • 6.1 Power supply failure
    • 6.2 Fan failure
    • 6.3 Module insertion
    • 6.4 Module removal
    • 6.5 Stack member unit failure
    • 6.6 PoE power allocation failure
    • 6.7 DHCP_Snooping: DHCP offer dropped message
    • 6.8 Port put into error disable state
    • 6.9 Reject certificate signing request
    • 6.10 Pending certificate signing request
    • 6.24 Threshold Alarms
      • 6.24.1 CPU threshold exceeded
      • 6.24.2 Memory threshold exceeded
      • 6.24.3 Disk usage threshold exceeded
      • 6.24.4 The drop of client count threshold exceeded
      • 6.24.5 License threshold exceeded
      • 6.24.6 HDD Health Degradation
      • 6.24.7 Rate limit for TOR surpassed
      • 6.24.8 The number of users exceeded its limit
      • 6.24.9 The number of devices exceeded its limit
      • 6.24.10 Over AP maximum capacity
      • 6.24.11 Over Device maximum capacity
    • 6.25 Tunnel Alarms - Access Point
      • 6.25.1 AP softGRE gateway not reachable
      • 6.25.2 AP is disconnected from secure gateway
      • 6.25.3 AP secure gateway association failure
  • 7 Events Types
    • 7.1 3rd Party Access Point Events
      • 7.1.1 3rd party AP connected
    • 7.2 Accounting Events
      • 7.2.1 Accounting session disabled
      • 7.2.2 Accounting server not reachable
      • 7.2.3 Accounting failed over to secondary
      • 7.2.4 Accounting fallback to primary
      • 7.2.5 AP accounting message mandatory parameter missing
      • 7.2.6 Unknown realm
      • 7.2.7 AP accounting message decode failed
      • 7.2.8 AP accounting retransmission message dropped
      • 7.2.9 AP accounting response while invalid config
      • 7.2.10 AP account message drop while no accounting start message
      • 7.2.11 Unauthorized COA/DM message dropped
    • 7.3 AFC Events
      • 7.3.1 AFC Proxy Timeout
      • 7.3.2 AFC Proxy Unreachable
      • 7.3.3 AFC Proxy Recovered
      • 7.3.4 AP AFC Communication Fail
      • 7.3.5 AP AFC Communication Fail Recovered
      • 7.3.6 AP AFC Server Fail
      • 7.3.7 AP AFC Server Fail Recovered
      • 7.3.8 AP AFC Goto New Power Channel
      • 7.3.9 AP AFC Goto New Power
    • 7.4 AP Authentication Events
      • 7.4.1 Radius server reachable
      • 7.4.2 Radius server unreachable
      • 7.4.3 LDAP server reachable
      • 7.4.4 LDAP server unreachable
      • 7.4.5 AD server reachable
      • 7.4.6 AD server unreachable
      • 7.4.7 Authentication Attempts
      • 7.4.8 Authentication Unsuccessful
      • 7.4.9 Authentication Re-attempt
      • 7.4.10 Authentication 8021
      • 7.4.11 AP Local Session Timeout
      • 7.4.12 AP Remote Session Timeout
      • 7.4.13 AP Interactive Session Termination
    • 7.5 AP Communication Events
      • 7.5.1 AP discovery succeeded
      • 7.5.2 AP managed
      • 7.5.3 AP rejected
      • 7.5.4 AP firmware updated
      • 7.5.5 AP firmware update failed
      • 7.5.6 Updating AP firmware
      • 7.5.7 Updating AP configuration
      • 7.5.8 AP configuration updated
      • 7.5.9 AP configuration update failed
      • 7.5.10 AP pre-provision model mismatched
      • 7.5.11 AP swap model mismatched
      • 7.5.12 AP WLAN oversubscribed
      • 7.5.13 AP join zone failed
      • 7.5.14 AP illegal to change country code
      • 7.5.15 AP configuration get failed
      • 7.5.16 Rogue AP
      • 7.5.17 Rogue AP disappeared
      • 7.5.18 Classified Rogue AP
      • 7.5.19 AP image signing failed
      • 7.5.20 Jamming attack
      • 7.5.21 Rogue client
      • 7.5.22 Key gen fail
      • 7.5.23 Key dis fail
      • 7.5.24 Key dis fail GTK
      • 7.5.25 IPsecses fail
      • 7.5.26 Fw manual initiation
      • 7.5.27 AP Management TSF data
      • 7.5.28 AP TSF failure
      • 7.5.29 AP Self tests
      • 7.5.30 Firmware initiation update
      • 7.5.31 SSH initiation
      • 7.5.32 SSH termination
      • 7.5.33 SSH failure
      • 7.5.34 IP sec initiation
      • 7.5.35 IP sec termination
      • 7.5.36 IP sec failure
      • 7.5.37 AP AOPP Applied
      • 7.5.38 AP AOPP Not Applied
      • 7.5.39 API High Latency Detected
      • 7.5.40 API High Latency Recovered
      • 7.5.41 API High Latency Alarm Timeout Cleared
    • 7.6 AP LBS Events
      • 7.6.1 No LS responses
      • 7.6.2 LS authentication failure
      • 7.6.3 AP connected to LS
      • 7.6.4 AP failed to connect to LS
      • 7.6.5 AP started location service
      • 7.6.6 AP stopped location service
      • 7.6.7 AP received passive calibration request
      • 7.6.8 AP received passive footfall request
      • 7.6.9 AP received unrecognized request
    • 7.7 AP Mesh Events
      • 7.7.1 EMAP downlink connected to MAP
      • 7.7.2 EMAP downlink disconnected from MAP
      • 7.7.3 EMAP uplink connected to MAP
      • 7.7.4 EMAP uplink disconnected from MAP
      • 7.7.5 MAP disconnected
      • 7.7.6 MAP downlink connected
      • 7.7.7 MAP downlink connected to EMAP
      • 7.7.8 MAP downlink disconnected from EMAP
      • 7.7.9 RAP downlink connected to MAP
      • 7.7.10 MAP uplink connected to EMAP
      • 7.7.11 MAP uplink disconnected from EMAP
      • 7.7.12 MAP uplink connected to RAP
      • 7.7.13 MAP uplink connected to MAP
      • 7.7.14 Mesh state updated to MAP
      • 7.7.15 Mesh state updated to MAP no channel
      • 7.7.16 Mesh state updated to RAP
      • 7.7.17 Mesh state update to RAP no channel
      • 7.7.18 MAP downlink connected to MAP
      • 7.7.19 MAP downlink disconnected from MAP
      • 7.7.20 RAP downlink disconnected from MAP
    • 7.8 AP PoE Events
      • 7.8.1 AP PoE Power Not Enough
    • 7.9 AP Resource Events
      • 7.9.1 AP Certificate Recovery Incident
      • 7.9.2 AP Certificate Backup
      • 7.9.3 AP Serial Number MAC Address Change
    • 7.10 AP State Change Events
      • 7.10.1 AP rebooted by user
      • 7.10.2 AP rebooted by system
      • 7.10.3 AP disconnected
      • 7.10.4 AP IP address updated
      • 7.10.5 AP reset to factory default
      • 7.10.6 AP channel updated
      • 7.10.7 AP country code updated
      • 7.10.8 AP channel updated because dynamic frequency selection (DFS) detected a radar
      • 7.10.9 AP Preamble Puncturing Pattern Updated
      • 7.10.10 AP Recovery Factory Reset
      • 7.10.11 AP change control plane
      • 7.10.12 AP connected
      • 7.10.13 AP deleted
      • 7.10.14 AP heartbeat lost
      • 7.10.15 AP tagged as critical
      • 7.10.16 AP cable modem interface down
      • 7.10.17 AP brownout
      • 7.10.18 AP cable modem power-cycled by user
      • 7.10.19 AP smart monitor turn off WLAN
      • 7.10.20 AP client load balancing limit reached
      • 7.10.21 AP client load balancing limit recovered
      • 7.10.22 AP WLAN state changed
      • 7.10.23 AP capacity reached
      • 7.10.24 AP capacity recovered
      • 7.10.25 AP cable modem interface up
      • 7.10.26 AP cable modem soft-rebooted by user
      • 7.10.27 AP cable modem set to factory default by user
      • 7.10.28 AP health high latency flag
      • 7.10.29 AP health low capacity flag
      • 7.10.30 AP health high connection failure flag
      • 7.10.31 AP health high client count flag
      • 7.10.32 AP health high latency clear
      • 7.10.33 AP health low capacity clear
      • 7.10.34 AP health high connection failure clear
      • 7.10.35 AP health high client count clear
      • 7.10.36 Primary DHCP AP is down
      • 7.10.37 Primary DHCP AP is up
      • 7.10.38 Secondary DHCP AP is down
      • 7.10.39 Secondary DHCP AP is up
      • 7.10.40 Primary or secondary DHCP AP detects 90% of the configured total IPs
      • 7.10.41 Both primary and secondary DHCP server APs are down
      • 7.10.42 AP NAT gateway IP failover detected for particular VLAN pool
      • 7.10.43 AP NAT gateway IP fall back detected for particular VLAN pool
      • 7.10.44 NAT VLAN capacity affected detected by NAT gateway AP at zone due to three (3) consecutive NAT gateway AP IPs are down for particular VLAN pool
      • 7.10.45 NAT VLAN capacity restored detected by NAT gateway AP due to (at least) one out of the three (3) consecutive NAT gateway AP IP were down is now up
      • 7.10.46 AP NAT failure detected by SZ due to three (3) consecutive NAT gateway APs are down
      • 7.10.47 AP health high airtime utilization flag
      • 7.10.48 AP health high airtime utilization clear
      • 7.10.49 AP cluster failover
      • 7.10.50 AP cluster rehome
      • 7.10.51 AP on Recovery Partition
      • 7.10.52 AP on Recovery Partition After Panic
      • 7.10.53 AP MAC OUI violation
      • 7.10.54 Backhaul switched to primary
      • 7.10.55 Backhaul switched to secondary
      • 7.10.56 LTE network connectivity lost
      • 7.10.57 Ethernet network connectivity lost
      • 7.10.58 LTE DHCP timeout
      • 7.10.59 Ethernet link down
      • 7.10.60 Ethernet link up
      • 7.10.61 SIM switch
      • 7.10.62 Remote host blacklisted
      • 7.10.63 SIM removal
      • 7.10.64 LTE network registration status
      • 7.10.65 LTE connection status
      • 7.10.66 AP Temp AF Threshold Exceeded
      • 7.10.67 AP Writable File Threshold Exceeded
      • 7.10.68 AP Operate in BT
      • 7.10.69 AP MDU Port Status Down
    • 7.11 AP Thermal Management
      • 7.11.1 AP Thermal Management
    • 7.12 AP USB Events
      • 7.12.1 AP USB software package downloaded
      • 7.12.2 AP USB software package download failed
    • 7.13 Authentication Events
      • 7.13.1 Authentication server not reachable
      • 7.13.2 Unknown realm
      • 7.13.3 Authentication succeeded
      • 7.13.4 Authentication failed
      • 7.13.5 Pseudonym authentication succeeded
      • 7.13.6 Pseudonym authentication failed
      • 7.13.7 Fast re-authentication succeeded
      • 7.13.8 Fast re-authentication failed
      • 7.13.9 Authentication failed over to secondary
      • 7.13.10 Authentication fallback to primary
      • 7.13.11 AD/LDAP connected successfully
      • 7.13.12 AD/LDAP connectivity failure
      • 7.13.13 Bind fails with AD/LDAP
      • 7.13.14 Bind success with LDAP, but unable to find clear text password for the user
      • 7.13.15 RADIUS fails to connect to AD NPS server
      • 7.13.16 RADIUS fails to authenticate with AD NPS server
      • 7.13.17 Successfully established the TLS tunnel with AD/LDAP
      • 7.13.18 Fails to establish TLS tunnel with AD/LDAP
      • 7.13.19 TLS Establishment Failed between SZ and external AAA Server
      • 7.13.20 RAC DNS Resolve Failed
    • 7.14 Authorization Events
      • 7.14.1 DM received from AAA
      • 7.14.2 DM NACK sent to AAA
      • 7.14.3 DM sent to NAS
      • 7.14.4 DM NACK received from NAS
      • 7.14.5 CoA received from AAA
      • 7.14.6 CoA NACK sent to AAA
      • 7.14.7 CoA sent NAS
      • 7.14.8 CoA NAK received NAS
      • 7.14.9 CoA authorize only access reject
      • 7.14.10 CoA RWSG MWSG notification failure
    • 7.15 Control and Data Plane Interface
      • 7.15.1 DP connected
      • 7.15.2 GtpManager (DP) disconnected
      • 7.15.3 Session updated at DP
      • 7.15.4 Session update at DP failed
      • 7.15.5 Session deleted at DP
      • 7.15.6 Session delete at DP failed
      • 7.15.7 C2d configuration failed
    • 7.16 Client Events
      • 7.16.1 Client authentication failed
      • 7.16.2 Client joined
      • 7.16.3 Client failed to join
      • 7.16.4 Client disconnected
      • 7.16.5 Client connection timed out
      • 7.16.6 Client authorization successfully
      • 7.16.7 Client authorization failed
      • 7.16.8 Client session expired
      • 7.16.9 Client roaming
      • 7.16.10 Client logged out
      • 7.16.11 3rd party client join
      • 7.16.12 3rd party client inactivity timeout
      • 7.16.13 3rd party client authorization
      • 7.16.14 3rd party client authorization failure
      • 7.16.15 3rd party client session expiration
      • 7.16.16 3rd party client roaming
      • 7.16.17 3rd party client session logout
      • 7.16.18 Client roaming disconnected
      • 7.16.19 Client blocked
      • 7.16.20 Client grace period
      • 7.16.21 Onboarding registration succeeded
      • 7.16.22 Onboarding registration failed
      • 7.16.23 Remediation succeeded
      • 7.16.24 Remediation failed
      • 7.16.25 Force DHCP disconnected
      • 7.16.26 WDS device joined
      • 7.16.27 WDS device left
      • 7.16.28 Client is blocked because of barring UE rule
      • 7.16.29 Client is unblocked by barring UE rule
      • 7.16.30 Start CALEA mirroring client
      • 7.16.31 Stop CALEA mirroring client
      • 7.16.32 Client information updated
      • 7.16.33 Wired client joined
      • 7.16.34 Wired client failed to join
      • 7.16.35 Wired client disconnected
      • 7.16.36 Wired client authorization successfully
      • 7.16.37 Wired client session expired
      • 7.16.38 Application identified
      • 7.16.39 Application denied
      • 7.16.40 URL filtering server unreachable
      • 7.16.41 URL filtering server reachable
      • 7.16.42 Packet spoofing detected
      • 7.16.43 Packet spoofing detected
      • 7.16.44 Packet spoofing detected
      • 7.16.45 Packet spoofing detected
      • 7.16.46 Client BTM Request Sent
      • 7.16.47 Client BTM Response Received
      • 7.16.48 Client Disassoc By CLB
    • 7.17 Cloud Events
      • 7.17.1 Cloud Services Enabled
      • 7.17.2 Cloud Services Disabled
      • 7.17.3 Cloud Analytics Enabled
      • 7.17.4 Cloud Analytics Disabled
      • 7.17.5 Cloud Services Token Refreshed
      • 7.17.6 Cloud Analytics Token Renewed
      • 7.17.7 Cloud Analytics Service has been Enabled
      • 7.17.8 Cloud Analytics service has been disabled
      • 7.17.9 Cloud Analytics Disconnected
      • 7.17.10 cloudAPRegistarSyncEnabled
      • 7.17.11 cloudAPRegistarSyncDisabled
      • 7.17.12 cloudAPRegistarSyncSZInfo
      • 7.17.13 cloudAPRegistarSyncAPInfo
    • 7.18 Cluster Events
      • 7.18.1 Cluster created successfully
      • 7.18.2 New node joined successfully
      • 7.18.3 New node failed to join
      • 7.18.4 Node removal completed
      • 7.18.5 Node removal failed
      • 7.18.6 Node out of service
      • 7.18.7 Cluster in maintenance state
      • 7.18.8 Cluster back in service
      • 7.18.9 Cluster backup completed
      • 7.18.10 Cluster backup failed
      • 7.18.11 Cluster restore completed
      • 7.18.12 Cluster restore failed
      • 7.18.13 Cluster node upgrade completed
      • 7.18.14 Entire cluster upgraded successfully
      • 7.18.15 Cluster upgrade failed
      • 7.18.16 Cluster application stopped
      • 7.18.17 Cluster application started
      • 7.18.18 Cluster backup started
      • 7.18.19 Cluster upgrade started
      • 7.18.20 Cluster leader changed
      • 7.18.21 Node bond interface down
      • 7.18.22 Node bond interface up
      • 7.18.23 Node IP address changed
      • 7.18.24 Node physical interface down
      • 7.18.25 Node physical interface up
      • 7.18.26 Cluster node rebooted
      • 7.18.27 NTP time synchronized
      • 7.18.28 Cluster node shutdown
      • 7.18.29 Cluster upload started
      • 7.18.30 Cluster upload completed
      • 7.18.31 Cluster upload failed
      • 7.18.32 SSH tunnel switched
      • 7.18.33 Cluster remove node started
      • 7.18.34 Node back in service
      • 7.18.35 Disk usage exceed threshold
      • 7.18.36 Cluster out of service
      • 7.18.37 Initiated moving APs in node to a new cluster
      • 7.18.38 Cluster upload vSZ-D firmware started
      • 7.18.39 Cluster upload vSZ-D firmware completed
      • 7.18.40 Cluster upload vSZ-D firmware failed
      • 7.18.41 Cluster upload AP firmware started
      • 7.18.42 Cluster upload AP firmware completed
      • 7.18.43 Cluster upload AP firmware failed
      • 7.18.44 Cluster add AP firmware started
      • 7.18.45 Cluster add AP firmware completed
      • 7.18.46 Cluster add AP firmware failed
      • 7.18.47 Cluster name is changed
      • 7.18.48 Unsync NTP Time
      • 7.18.49 Cluster upload KSP file started
      • 7.18.50 Cluster upload KSP file completed
      • 7.18.51 Cluster upload KSP file failed
      • 7.18.52 NTP unreachable server
      • 7.18.53 Configuration backup started
      • 7.18.54 Configuration backup succeeded
      • 7.18.55 Configuration backup failed
      • 7.18.56 Configuration restore succeeded
      • 7.18.57 Configuration restore failed
      • 7.18.58 AP Certificate Expired
      • 7.18.59 AP Certificate Updated
      • 7.18.60 Configuration restore started
      • 7.18.61 Upgrade SSTable failed
      • 7.18.62 Reindex elastic search finished
      • 7.18.63 Initiated APs contact APR
      • 7.18.64 All nodes back in service
      • 7.18.65 Not management service ready
      • 7.18.66 Management service ready
      • 7.18.67 Configuration sync failed
      • 7.18.68 Node IPv6 address added
      • 7.18.69 AP is connected to standby cluster over the expiration date
      • 7.18.70 Node IPv6 address deleted
      • 7.18.71 Sync Configuration Start for Cluster Redundancy
      • 7.18.72 Sync Configuration Success for Cluster Redundancy
      • 7.18.73 Standby Cluster Failed to Restore a Configuration for Cluster Redundancy
      • 7.18.74 Standby Cluster Restores a Configuration for Cluster Redundancy
      • 7.18.75 Standby Cluster Restored a Configuration Success for Cluster Redundancy
      • 7.18.76 Standby Cluster Back to Monitoring Mode for Cluster Redundancy
      • 7.18.77 AP Connected to Standby Cluster after Rehome Timeout
      • 7.18.78 Active Cluster unable to Connect to other Active Clusters for Cluster Redundancy
      • 7.18.79 External DP Connected to Standby Cluster after Rehome Timeout
      • 7.18.80 Certificate is about to Expire
      • 7.18.81 Certificate is already Expired
      • 7.18.82 Result of Renew Certificate
      • 7.18.83 Cluster node Resource Invalid
    • 7.19 Configuration Events
      • 7.19.1 Configuration updated
      • 7.19.2 Configuration update failed
      • 7.19.3 Configuration receive failed
      • 7.19.4 Incorrect flat file configuration
      • 7.19.5 Zone configuration preparation failed
      • 7.19.6 AP configuration generation failed
      • 7.19.7 End-of-life AP model detected
      • 7.19.8 VLAN configuration mismatch on non-DHCP/NAT WLAN
      • 7.19.9 VLAN configuration mismatch on DHCP/NAT WLAN
    • 7.20 Datablade Events
      • 7.20.1 DP integrity test failed
      • 7.20.2 DP CLI enable failed
      • 7.20.3 DP re-authentication
      • 7.20.4 DP password min length updated
      • 7.20.5 DP password changed
      • 7.20.6 DP enable password changed
      • 7.20.7 DP https authentication failed
      • 7.20.8 DP certificate uploaded
      • 7.20.9 DP Scg FQDN updated
      • 7.20.10 DP initial upgrade
      • 7.20.11 DP discontinuous time change NTP server DP Ntp time sync
      • 7.20.12 DP user login
      • 7.20.13 DP user login failed
      • 7.20.14 DP user logout
      • 7.20.15 DP account locked
      • 7.20.16 DP session idle updated
      • 7.20.17 DP session idle terminated
      • 7.20.18 DP SSH tunnel failed
      • 7.20.19 DP https connection failed
      • 7.20.20 DP IPsec tunnel create failed
    • 7.21 Data Plane Events
      • 7.21.1 Data plane discovered
      • 7.21.2 Data plane discovery failed
      • 7.21.3 Data plane configuration updated
      • 7.21.4 Data plane configuration update failed
      • 7.21.5 Data plane rebooted
      • 7.21.6 Data plane heartbeat lost
      • 7.21.7 Data plane IP address updated
      • 7.21.8 Data plane updated to a new control plane
      • 7.21.9 Data plane status update failed
      • 7.21.10 Data plane statistics update failed
      • 7.21.11 Data plane connected
      • 7.21.12 Data plane disconnected
      • 7.21.13 Data plane physical interface down
      • 7.21.14 Data plane physical interface up
      • 7.21.15 Data plane packet pool is under low water mark
      • 7.21.16 Data plane packet pool is under critical low water mark
      • 7.21.17 Data plane packet pool is above high water mark
      • 7.21.18 Data plane core dead
      • 7.21.19 Data plane process restarted
      • 7.21.20 Data plane discovery succeeded
      • 7.21.21 Data plane managed
      • 7.21.22 Data plane deleted
      • 7.21.23 Data plane license is not enough
      • 7.21.24 Data plane upgrade started
      • 7.21.25 Data plane upgrading
      • 7.21.26 Data plane upgrade succeeded
      • 7.21.27 Data plane upgrade failed
      • 7.21.28 Data Plane Upgrade Failed Due to Corrupted RPM
      • 7.21.29 Data plane of data center side successfully connects to the CALEA server
      • 7.21.30 Data plane of data center side fails to connect to the CALEA server
      • 7.21.31 Data Plane of data center side disconnects to CALEA server
      • 7.21.32 Data plane successfully connects to the other data plane
      • 7.21.33 Data plane fails to connect to the other data plane
      • 7.21.34 Data plane disconnects to the other data plane
      • 7.21.35 Start CALEA mirroring client in data plane
      • 7.21.36 Data plane DHCP IP pool usage rate is 100 percent
      • 7.21.37 Data plane DHCP IP pool usage rate is 80 percent
      • 7.21.38 Data plane NAT session capacity usage rate is 80 percent
      • 7.21.39 Data plane NAT session capacity usage rate is 100 percent
      • 7.21.40 Data plane DHCP IP capacity usage rate is 80 percent
      • 7.21.41 Data plane DHCP IP capacity usage rate is 100 percent
      • 7.21.42 Data plane backup success
      • 7.21.43 Data plane backup failed
      • 7.21.44 Data plane restore success
      • 7.21.45 Data plane restore failed
      • 7.21.46 dpIpmiPsStatus
      • 7.21.47 dpIpmiThempIOH
      • 7.21.48 dpIpmiThempMemP
      • 7.21.49 dpIpmiPsStatus
      • 7.21.50 dpIpmiREVoltage
      • 7.21.51 dpIpmiREThempIOH
      • 7.21.52 dpIpmiREThempMemP
      • 7.21.53 dpIpmiRePsStatus
      • 7.21.54 dpSSDHealthDegrade
      • 7.21.55 Remote Administration Start
      • 7.21.56 Remote Administration Stop
      • 7.21.57 Data plane Switchover Failed
    • 7.22 Data Streaming Event
      • 7.22.1 Connected to Data a Streaming Endpoint
      • 7.22.2 Disconnected to Data a Streaming Endpoint
      • 7.22.3 Connected to Data a Streaming Endpoint Failure
    • 7.23 DHCP Events
      • 7.23.1 DHCP inform received
      • 7.23.2 DHCP dcln received
    • 7.24 GA Interface Events
      • 7.24.1 Connection to CGF failed
      • 7.24.2 CGF keepalive not responded
      • 7.24.3 CDR transfer succeeded
      • 7.24.4 CDR generation failed
      • 7.24.5 CDR transfer failed
    • 7.25 Gn/S2a Interface Events
      • 7.25.1 GGSN restarted
      • 7.25.2 GGSN not reachable
      • 7.25.3 Echo response not received
      • 7.25.4 GGSN not resolved
      • 7.25.5 PDP context established
      • 7.25.6 PDP create failed
      • 7.25.7 PDP update by HLR succeeded
      • 7.25.8 PDP update by HLR failed
      • 7.25.9 PDP update by roaming succeeded
      • 7.25.10 PDP update by roaming failed
      • 7.25.11 PDP update by GGSN succeeded
      • 7.25.12 PDP update by GGSN failed
      • 7.25.13 PDP delete by TTG succeeded
      • 7.25.14 PDP delete by TTG failed
      • 7.25.15 PDP delete by GGSN succeeded
      • 7.25.16 PDP delete by GGSN failed
      • 7.25.17 IP assigned
      • 7.25.18 IP not assigned
      • 7.25.19 Unknown UE
      • 7.25.20 PDP update success COA
      • 7.25.21 PDP update fail COA
      • 7.25.22 PDNGW could not be resolved
      • 7.25.23 PDNGW version not supported
      • 7.25.24 Associated PDNGW down
      • 7.25.25 Create session response failed
      • 7.25.26 Decode failed
      • 7.25.27 Modify bearer response failed
      • 7.25.28 Delete session response failed
      • 7.25.29 Delete bearer request failed
      • 7.25.30 Update bearer request failed
      • 7.25.31 CGF server not configured
    • 7.26 Gr Interface Event
      • 7.26.1 Destination not reachable
      • 7.26.2 Destination available
      • 7.26.3 App server down
      • 7.26.4 App server inactive
      • 7.26.5 App server active
      • 7.26.6 Association establishment failed
      • 7.26.7 Association down
      • 7.26.8 Association up
      • 7.26.9 Send auth info success
      • 7.26.10 Auth info sending failed
      • 7.26.11 GPRS location update succeeded
      • 7.26.12 GPRS location update failed
      • 7.26.13 Insert sub data success
      • 7.26.14 Insert sub data failed
      • 7.26.15 Outbound routing failure
      • 7.26.16 Did allocation failure
      • 7.26.17 Restore data success
      • 7.26.18 Restore data failed
    • 7.27 IPMI Events
      • 7.27.1 ipmiThempBB
      • 7.27.2 ipmiThempFP
      • 7.27.3 ipmiThempHSBP
      • 7.27.4 ipmiFan
      • 7.27.5 ipmiFanStatus
      • 7.27.6 ipmiREThempBB
      • 7.27.7 ipmiREThempFP
      • 7.27.8 ipmiREFan
      • 7.27.9 ipmiREFanStatus
    • 7.28 Licensing Interface Events
      • 7.28.1 TTG session warning threshold
      • 7.28.2 TTG session major threshold
      • 7.28.3 TTG session critical threshold
      • 7.28.4 TTG session license exhausted
      • 7.28.5 License sync succeeded
      • 7.28.6 License sync failed
      • 7.28.7 License import succeeded
      • 7.28.8 License import failed
      • 7.28.9 License data changed
      • 7.28.10 License going to expire
      • 7.28.11 Insufficient license capacity
      • 7.28.12 Data plane DHCP IP license insufficient
      • 7.28.13 Data plane NAT session license insufficient
      • 7.28.14 AP number limit exceeded
      • 7.28.15 Insufficient license capacity
      • 7.28.16 Insufficient license capacity
    • 7.29 Location Delivery Events
      • 7.29.1 Unavailable location info requested
      • 7.29.2 Incapable location info requested
      • 7.29.3 Unsupported location delivery request
    • 7.30 Multi-Link Operation
      • 7.30.1 mloClienteMLSREnter
      • 7.30.2 mloClienteMLSRExit
    • 7.31 PMIPv6 Events
      • 7.31.1 Config update failed
      • 7.31.2 LMA ICMP reachable
      • 7.31.3 LMA server unreachable
      • 7.31.4 DHCP connected
      • 7.31.5 DHCP connection lost
    • 7.32 Session Events
      • 7.32.1 Session timeout
      • 7.32.2 Delete all sessions
      • 7.32.3 Binding succeeded
      • 7.32.4 Binding failed
      • 7.32.5 Binding time expired
      • 7.32.6 Binding revoked
      • 7.32.7 Binding released
    • 7.33 STA Interface Events
      • 7.33.1 STA successful authentication
      • 7.33.2 STA session termination {produce.short.name} initiated success
      • 7.33.3 STA session termination AAA initiated success
      • 7.33.4 STA session termination AAA initiated failed
      • 7.33.5 STA re-authorization successful
    • 7.34 System Events
      • 7.34.1 No LS responses
      • 7.34.2 LS authentication failure
      • 7.34.3 {produce.short.name} connected to LS
      • 7.34.4 {produce.short.name} failed to connect to LS
      • 7.34.5 {produce.short.name} received passive request
      • 7.34.6 {produce.short.name} sent controller information report
      • 7.34.7 {produce.short.name} received management request
      • 7.34.8 {produce.short.name} sent AP info by venue report
      • 7.34.9 {produce.short.name} sent query venues report
      • 7.34.10 {produce.short.name} sent associated client report
      • 7.34.11 {produce.short.name} forwarded calibration request to AP
      • 7.34.12 {produce.short.name} forwarded footfall request to AP
      • 7.34.13 {produce.short.name} received unrecognized request
      • 7.34.14 Syslog server reachable
      • 7.34.15 Syslog server unreachable
      • 7.34.16 Syslog server switched
      • 7.34.17 System service failure
      • 7.34.18 Generate AP config for plane load rebalance succeeded
      • 7.34.19 Generate AP config for plane load rebalance failed
      • 7.34.20 FTP transfer
      • 7.34.21 FTP transfer error
      • 7.34.22 File upload
      • 7.34.23 Email sent successfully
      • 7.34.24 Email sent failed
      • 7.34.25 SMS sent successfully
      • 7.34.26 SMS sent failed
      • 7.34.27 Process restart
      • 7.34.28 Service unavailable
      • 7.34.29 Keepalive failure
      • 7.34.30 Resource unavailable
      • 7.34.31 All data planes in the zone affinity profile are disconnected
      • 7.34.32 CALEA UE Matched
      • 7.34.33 Diameter peer transport failure
      • 7.34.34 Diameter CER error
      • 7.34.35 Diameter CER success
      • 7.34.36 Diameter invalid version
      • 7.34.37 Diameter peer add successful
      • 7.34.38 ZD AP migrating
      • 7.34.39 ZD AP migrated
      • 7.34.40 ZD AP rejected
      • 7.34.41 ZD AP migration failed
      • 7.34.42 Database error
      • 7.34.43 Process initiated
      • 7.34.44 PMIPv6 unavailable
      • 7.34.45 Memory allocation failed
      • 7.34.46 Process stopped
      • 7.34.47 SZ Login Fail
      • 7.34.48 SZ Login
      • 7.34.49 SZ Logout
      • 7.34.50 Password expiration
      • 7.34.51 Admin account lockout
      • 7.34.52 Admin session expired
      • 7.34.53 Disable inactive admins
      • 7.34.54 Two factor auth failed
      • 7.34.55 Unconfirmed program detection
      • 7.34.56 Admin account lockout after failed attempts
      • 7.34.57 Discontinuous time change
      • 7.34.58 Mesh network connectivity lost
      • 7.34.59 Failure of Key Generation
      • 7.34.60 Failure of IPsec
      • 7.34.61 Failure Certificate
      • 7.34.62 IPsec KE is Up
      • 7.34.63 IPsec IKE is Down
      • 7.34.64 Discontinuous Time Change
      • 7.34.65 szAuthAction
    • 7.35 Switch Events
      • 7.35.1 Switch critical message
      • 7.35.2 Switch alert message
      • 7.35.3 Switch warning message
      • 7.35.4 Switch CPU critical threshold exceed
      • 7.35.5 Switch memory warning threshold exceed
      • 7.35.6 Switch memory major threshold exceed
      • 7.35.7 Switch memory critical threshold exceed
      • 7.35.8 Switch custom warning threshold exceed
      • 7.35.9 Switch custom critical threshold exceed
      • 7.35.10 GetCACert Request
      • 7.35.11 Certificate signing request
      • 7.35.12 Accept certificate signing request
      • 7.35.13 Reject certificate signing request
      • 7.35.14 Pending certificate signing request
      • 7.35.15 Switch is Offline for 15 Minutes
      • 7.35.16 Over Switch Max Capacity
      • 7.35.17 Switch Duplicated
      • 7.35.18 Switch Firmware Upgrade
      • 7.35.19 Switch Firmware Upgrade Failed
      • 7.35.20 Switch Configuration Update
      • 7.35.21 Switch Configuration Update Failed
      • 7.35.22 Switch Reboot
      • 7.35.23 Switch Delete
      • 7.35.24 Switch Disconnected from the Controller
      • 7.35.25 Switch is Connected to the Controller
      • 7.35.26 Switch Discovered by the Controller
      • 7.35.27 scheduleZoneFirmwareUpgrade
    • 7.36 Threshold Events
      • 7.36.1 CPU threshold exceeded
      • 7.36.2 Memory threshold exceeded
      • 7.36.3 Disk usage threshold exceeded
      • 7.36.4 CPU threshold back to normal
      • 7.36.5 Memory threshold back to normal
      • 7.36.6 Disk threshold back to normal
      • 7.36.7 License threshold exceeded
      • 7.36.8 The drop of client count threshold exceeded
      • 7.36.9 Rate limit threshold surpassed
      • 7.36.10 Rate limit threshold restored
      • 7.36.11 Rate limit for TOR surpassed
      • 7.36.12 The number of users exceed its limit
      • 7.36.13 The number of devices exceeded its limit
      • 7.36.14 Over AP maximum capacity
      • 7.36.15 Over Device Maximum Capacity
      • 7.36.16 Device Capacity Threshold Back to Normal
    • 7.37 Tunnel Events - Access Point (AP)
      • 7.37.1 Data plane accepted a tunnel request
      • 7.37.2 Data plane rejected a tunnel request
      • 7.37.3 Data plane terminated a tunnel
      • 7.37.4 AP created a tunnel
      • 7.37.5 AP tunnel disconnected
      • 7.37.6 AP softGRE tunnel fails over primary to secondary
      • 7.37.7 AP softGRE tunnel fails over secondary to primary
      • 7.37.8 AP softGRE gateway reachable
      • 7.37.9 AP softGRE gateway not reachable
      • 7.37.10 Data plane set up a tunnel
      • 7.37.11 AP secure gateway association success
      • 7.37.12 AP is disconnected from secure gateway
      • 7.37.13 AP secure gateway association failure
    • 7.38 Tunnel Events - Data Plane
      • 7.38.1 DP sGRE GW unreachable
      • 7.38.2 DP sGRE keep alive timeout
      • 7.38.3 DP sGRE GW inactive
      • 7.38.4 DP DHCPRelay no response
      • 7.38.5 DP DHCPRelay failover
      • 7.38.6 DP sGRE new tunnel
      • 7.38.7 DP sGRE del tunnel
      • 7.38.8 DP sGRE keepalive recovery
      • 7.38.9 DP DHCPRelay response recovery
      • 7.38.10 DP sGRE GW reachable
      • 7.38.11 DP sGRE GW active
      • 7.38.12 DP sGRE GW failover
      • 7.38.13 DP switchover
    • 7.39 AP Ethernet Phy Error Count
    • 7.40 AP Ethernet PHY Down Shift
    • 7.41 AP BAND Change
      • 7.41.1 apIllegalToChange3rdRadioBand
      • 7.41.2 apIllegal6gVAPCreation
      • 7.41.3 ap6gWLANCfgDone

AP BAND Change

In this section:

  1. apIllegalToChange3rdRadioBand
  2. apIllegal6gVAPCreation
  3. ap6gWLANCfgDone
Parent topic: Events Types

Did you find what you were looking for?

Thanks!

Ruckus Wireless

© 2026 Ruckus Wireless LLC All rights reserved.

  • Accessibility
  • Privacy & Cookies
  • Do Not Sell My Information
  • Trademarks
  • Terms
  • Feedback