Ruckus SZ™ 100 And VSZ E™ Alarm Event Reference Guide For SmartZone 3.4.1 Smart Zone (MR) (SZ100/v SZ E) Sz100Vsze 341 Rev B 20170427
SmartZone 3.4.1 (MR) Alarm and Event Reference Guide (SZ100/vSZ-E) Sz100Vsze-341-AlarmEventReferenceGuide-revB-20170427
2017-06-18
User Manual: Ruckus SmartZone 3.4.1 (MR) Alarm and Event Reference Guide (SZ100/vSZ-E)
Open the PDF directly: View PDF 
.
Page Count: 291
| Download | |
| Open PDF In Browser | View PDF |
Ruckus Wireless
SmartZone 100 and
Virtual SmartZone Essentials
™
™
™
Alarm and Event Reference Guide for
SmartZone 3.4.1
Part Number 800-71374-001 Rev B
Published April 2017
www.ruckuswireless.com
Copyright Notice and Proprietary Information
Copyright 2017. Ruckus Wireless, Inc. All rights reserved.
No part of this documentation may be used, reproduced, transmitted, or translated, in any form or by any means,
electronic, mechanical, manual, optical, or otherwise, without prior written permission of Ruckus Wireless, Inc.
(“Ruckus”), or as expressly provided by under license from Ruckus.
Destination Control Statement
Technical data contained in this publication may be subject to the export control laws of the United States of America.
Disclosure to nationals of other countries contrary to United States law is prohibited. It is the reader’s responsibility to
determine the applicable regulations and to comply with them.
Disclaimer
THIS DOCUMENTATION AND ALL INFORMATION CONTAINED HEREIN (“MATERIAL”) IS PROVIDED FOR GENERAL
INFORMATION PURPOSES ONLY. RUCKUS AND ITS LICENSORS MAKE NO WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, WITH REGARD TO THE MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE, OR THAT THE
MATERIAL IS ERROR-FREE, ACCURATE OR RELIABLE. RUCKUS RESERVES THE RIGHT TO MAKE CHANGES OR
UPDATES TO THE MATERIAL AT ANY TIME.
Limitation of Liability
IN NO EVENT SHALL RUCKUS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL OR CONSEQUENTIAL DAMAGES, OR DAMAGES FOR LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY YOU OR ANY
THIRD PARTY, WHETHER IN AN ACTION IN CONTRACT OR TORT, ARISING FROM YOUR ACCESS TO, OR USE
OF, THE MATERIAL.
Trademarks
Ruckus Wireless, Ruckus, the bark logo, ZoneFlex, FlexMaster, ZoneDirector, SmartMesh, Channelfly, Smartcell,
Dynamic PSK, and Simply Better Wireless are trademarks of Ruckus Wireless, Inc. in the United States and other
countries. All other product or company names may be trademarks of their respective owners.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
2
Contents
About This Guide
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Online Training Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1
Revision History
SmartZone Version 3.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
SmartZone Version 3.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
New Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Displayed on the Web Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
New Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
SmartZone Version 3.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
New Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
New Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Event on Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
SmartZone Version 3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
New Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Attribute Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Renamed Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
New Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Severity Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Attribute Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Renamed Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Auto Clearance of Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
SmartZone Version 3.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
New Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
New Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Re-added Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Renamed Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Deprecated Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
RuckOS Version 3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
3
Contents
New Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Deprecated Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Renamed Alarm Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Renamed Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
New Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Renamed Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2
Alarm and Event Management
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Alarm and Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Event Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Event Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Generation of Alarm and Event. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3
Alarm Types
Accounting Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Accounting server not reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
AP Authentication Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
RADIUS server unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
LDAP server unreachable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
AD server unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
WeChat ESP authentication server unreachable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
WeChat ESP authentication server unresolvable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
WeChat ESP DNAT server unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
WeChat ESP DNAT server unresolvable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
AP Communication Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
AP rejected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
AP configuration update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
AP swap model mismatched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
AP pre-provision model mismatched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
AP firmware update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
AP WLAN oversubscribed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
AP LBS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
No LS responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
LS authentication failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
AP failed to connect to LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
AP State Change Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
AP rebooted by system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
AP disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
4
Contents
AP deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
AP cable modem interface down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Authentication Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Authentication server not reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Authentication failed over to secondary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Authentication fallback to primary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
AD/LDAP connectivity failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Bind fails with AD/LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Bind success with LDAP, but unable to find clear text password for the user . . . . . . . . 63
RADIUS fails to connect to AD NPS server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
RADIUS fails to authenticate with AD NPS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Control and Data Plane Interface Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
GtpManager (DP) disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Cluster Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
New node failed to join. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Node removal failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Node out of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Cluster in maintenance state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Cluster backup failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Cluster restore failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Cluster upgrade failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Cluster application stopped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Node bond interface down. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Node physical interface down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Cluster node rebooted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Cluster node shut down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Disk usage exceed threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Resync NTP time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Cluster out of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Cluster upload AP firmware failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Cluster add AP firmware failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Configuration backup failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Configuration restore failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
AP Certificate Expired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Configuration Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Zone configuration preparation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
AP configuration generation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
End-of-life AP model detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Data Plane Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
5
Contents
Data plane configuration update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Data plane disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Data plane physical interface down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Data plane process restarted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Data plane license is not enough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Data plane upgrade failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
IPMI Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
ipmiThempBB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
ipmiThempP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
ipmiFan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
ipmiFanStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Licensing Interface Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
License going to expire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Insufficient license capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
System Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
No LS responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
LS authentication failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
{produce.short.name} failed to connect to LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Syslog server unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Process restart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Service unavailable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Keepalive failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Resource unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
HIP failed over . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Threshold Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
CPU threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Memory threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Disk usage threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
License threshold exceeded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Rate limit for TOR surpassed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
The number of users exceeded its limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
The number of devices exceeded its limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Tunnel Alarms - Access Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
AP softGRE gateway not reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
AP is disconnected from secure gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
AP secure gateway association failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
4
Events Types
Accounting Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
6
Contents
Accounting server not reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
AP accounting response while invalid config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
AP account message drop while no accounting start message . . . . . . . . . . . . . . . . . 113
Unauthorized COA/DM message dropped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
AP Communication Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
AP discovery succeeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
AP managed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
AP rejected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
AP firmware updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
AP firmware update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Updating AP firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Updating AP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
AP configuration updated. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
AP configuration update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
AP pre-provision model mismatched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
AP swap model mismatched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
AP WLAN oversubscribed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
AP illegal to change country code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Rogue AP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
SSID-spoofing rogue AP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Mac-spoofing rogue AP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Same-network rogue AP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Ad-hoc network device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Rogue AP disappeared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
AP LBS Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
No LS responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
LS authentication failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
AP connected to LS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
AP failed to connect to LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
AP started location service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
AP stopped location service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
AP received passive calibration request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
AP received passive footfall request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
AP received unrecognized request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
AP Mesh Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
EMAP downlink connected to MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
EMAP downlink disconnected from MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
EMAP uplink connected to MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
EMAP uplink disconnected from MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
7
Contents
MAP disconnected. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
MAP downlink connected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
MAP downlink connected to EMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
MAP downlink disconnected from EMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
RAP downlink connected to MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
MAP uplink connected to EMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
MAP uplink disconnected from EMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
MAP uplink connected to RAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
MAP uplink connected to MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Mesh state updated to MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Mesh state updated to MAP no channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Mesh state updated to RAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Mesh state update to RAP no channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
MAP downlink connected to MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
MAP downlink disconnected from MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
RAP downlink disconnected from MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
AP State Change Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
AP rebooted by user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
AP rebooted by system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
AP disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
AP IP address updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
AP reset to factory default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
AP channel updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
AP country code updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
AP channel updated because dynamic frequency selection (DFS) detected a radar . . 144
AP change control plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
AP connected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
AP deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
AP heartbeat lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
AP tagged as critical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
AP cable modem interface down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
AP brownout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
AP cable modem power-cycled by user. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
AP smart monitor turn off WLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
AP client load balancing limit reached . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
AP client load balancing limit recovered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
AP WLAN state changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
AP capacity reached . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
AP capacity recovered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
8
Contents
AP cable modem interface up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
AP cable modem soft-rebooted by user. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
AP cable modem set to factory default by user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
AP Authentication Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Radius server reachable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Radius server unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
LDAP server reachable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
LDAP server unreachable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
AD server reachable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
AD server unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Wechat ESP authentication server reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
WeChat ESP authentication server unreachable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
WeChat ESP authentication server resolvable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
WeChat ESP authentication server unresolvable . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
WeChat ESP DNAT server reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
WeChat ESP DNAT server unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
WeChat ESP DNAT server resolvable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
WeChat ESP DNAT server unresolvable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
AP USB Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
AP USB software package downloaded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
AP USB software package download failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Authentication Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Authentication server not reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Authentication failed over to secondary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Authentication fallback to primary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
AD/LDAP connected successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
AD/LDAP connectivity failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Bind fails with AD/LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Bind success with LDAP, but unable to find clear text password for the user . . . . . . . 165
RADIUS fails to connect to AD NPS server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
RADIUS fails to authenticate with AD NPS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Authorization Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
DM received from AAA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
DM NACK sent to AAA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
DM sent to NAS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
DM NACK received from NAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
CoA received from AAA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
CoA NACK sent to AAA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
CoA sent NAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
9
Contents
CoA NAK received NAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
CoA authorize only access reject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
CoA RWSG MWSG notification failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Control and Data Plane Interface Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
DP connected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
GtpManager (DP) disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Session updated at DP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Session update at DP failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Session deleted at DP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Session delete at DP failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
C2d configuration failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Client Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Client authentication failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Client joined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Client failed to join . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Client disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Client connection timed out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Client authorization successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Client authorization failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Client session expired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Client roaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Client logged out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Client roaming disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Client blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Client grace period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Onboarding registration succeeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Onboarding registration failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Remediation succeeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Remediation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Force DHCP disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
WDS device joined. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
WDS device left . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Cluster Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Cluster created successfully. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
New node joined successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
New node failed to join. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Node removal completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Node removal failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Node out of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
10
Contents
Cluster in maintenance state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Cluster back in service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Cluster backup completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Cluster backup failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Cluster restore completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Cluster restore failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Cluster node upgrade completed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Entire cluster upgraded successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Cluster upgrade failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Cluster application stopped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Cluster application started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Cluster backup started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Cluster upgrade started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Cluster leader changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Node bond interface down. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Node bond interface up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Node IP address changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Node physical interface down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Node physical interface up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Cluster node rebooted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
NTP time synchronized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Cluster node shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Cluster upload started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Cluster upload completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Cluster upload failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
SSH tunnel switched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Cluster remove node started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Node back in service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Resync NTP time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Disk usage exceed threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Cluster out of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Initiated moving APs in node to a new cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Cluster upload vSZ-D firmware started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Cluster upload vSZ-D firmware completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Cluster upload vSZ-D firmware failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Cluster upload AP firmware started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Cluster upload AP firmware completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Cluster upload AP firmware failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Cluster add AP firmware started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
11
Contents
Cluster add AP firmware completed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Cluster add AP firmware failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Cluster name is changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Configuration backup started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Configuration backup succeeded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Configuration backup failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Configuration restore succeeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Configuration restore failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
AP Certificate Expired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
AP Certificate Updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Node IPv6 address added . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Node IPv6 address deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Configuration Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Configuration updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Configuration update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Configuration receive failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Incorrect flat file configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Zone configuration preparation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
AP configuration generation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
End-of-life AP model detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Data Plane Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Data plane discovered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Data plane discovery failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Data plane configuration updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Data plane configuration update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Data plane rebooted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Data plane heartbeat lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Data plane IP address updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Data plane updated to a new control plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Data plane status update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Data plane statistics update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Data plane connected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Data plane disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Data plane physical interface down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Data plane physical interface up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Data plane packet pool is under low water mark . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Data plane packet pool is under critical low water mark . . . . . . . . . . . . . . . . . . . . . . . 230
Data plane packet pool is above high water mark . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Data plane core dead. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
12
Contents
Data plane process restarted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Data plane discovery succeeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Data plane managed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Data plane deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Data plane license is not enough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Data plane upgrade started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Data plane upgrading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Data plane upgrade succeeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Data plane upgrade failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
IPMI Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
ipmiThempBB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
ipmiThempP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
ipmiFan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
ipmiFanStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
ipmiREThempBB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
ipmiREThempP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
ipmiREFan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
ipmiREFanStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Licensing Interface Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
License sync succeeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
License sync failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
License import succeeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
License import failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
License data changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
License going to expire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Insufficient license capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Session Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Delete all sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
System Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
No LS responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
LS authentication failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
{produce.short.name} connected to LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
{produce.short.name} failed to connect to LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
{produce.short.name} received passive request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
{produce.short.name} sent controller information report. . . . . . . . . . . . . . . . . . . . . . . 250
{produce.short.name} received management request . . . . . . . . . . . . . . . . . . . . . . . . 250
{produce.short.name} sent AP info by venue report . . . . . . . . . . . . . . . . . . . . . . . . . . 251
{produce.short.name} sent query venues report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
{produce.short.name} sent associated client report . . . . . . . . . . . . . . . . . . . . . . . . . . 252
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
13
Contents
{produce.short.name} forwarded calibration request to AP . . . . . . . . . . . . . . . . . . . . 252
{produce.short.name} forwarded footfall request to AP . . . . . . . . . . . . . . . . . . . . . . . 253
{produce.short.name} received unrecognized request . . . . . . . . . . . . . . . . . . . . . . . . 253
Syslog server reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Syslog server unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Syslog server switched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Generate AP config for plane load rebalance succeeded . . . . . . . . . . . . . . . . . . . . . . 255
Generate AP config for plane load rebalance failed. . . . . . . . . . . . . . . . . . . . . . . . . . . 255
FTP transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
FTP transfer error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
File upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Email sent successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Email sent failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
SMS sent successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
SMS sent failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Process restart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Service unavailable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Keepalive failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Resource unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
ZD AP migrating. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
ZD AP migrated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
ZD AP rejected. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
ZD AP migration failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Database error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Database error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Threshold Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
CPU threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Memory threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Disk usage threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
CPU threshold back to normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Memory threshold back to normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Disk threshold back to normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
License threshold exceeded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Rate limit threshold surpassed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Rate limit threshold restored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Rate limit for TOR surpassed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
The number of users exceed its limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
The number of devices exceeded its limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Tunnel Events - Access Point (AP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
14
Contents
Data plane accepted a tunnel request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Data plane rejected a tunnel request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Data plane terminated a tunnel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
AP created a tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
AP tunnel disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
AP SoftGRE tunnel fails over primary to secondary . . . . . . . . . . . . . . . . . . . . . . . . . . 274
AP SoftGRE tunnel fails over secondary to primary . . . . . . . . . . . . . . . . . . . . . . . . . . 274
AP SoftGRE gateway reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
AP SoftGRE gateway not reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Data plane set up a tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
AP secure gateway association success . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
AP is disconnected from secure gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
AP secure gateway association failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Tunnel Events - Data Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
DP sGRE GW unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
DP sGRE keep alive timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
DP sGRE GW inactive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
DP DHCPRelay no response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
DP DHCPRelay failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
DP sGRE new tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
DP sGRE keepalive recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
DP DHCPRelay response recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
DP sGRE GW reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
DP sGRE GW active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Index
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
15
About This Guide
This SmartZone™ Alarm and Event Reference Guide describes the various types
of alarms and events that the controller (SZ-100 or vSZ-E) generates. For each alarm
and event this guide provides the code, type, attributes, and description.
This guide is written for service operators and system administrators who are
responsible for managing, configuring, and troubleshooting Ruckus Wireless
devices. Consequently, it assumes a basic working knowledge of local area
networks, wireless networking, and wireless devices.
NOTE If release notes are shipped with your product and the information there
differs from the information in this guide, follow the instructions in the release notes.
Most user guides and release notes are available in Adobe Acrobat Reader Portable
Document Format (PDF) or HTML on the Ruckus Wireless Support Web site at
https://support.ruckuswireless.com/contact-us.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
16
About This Guide
Document Conventions
Document Conventions
Table 1 and Table 2 list the text and notice conventions that are used throughout
this guide.
Table 1.
Text conventions
Convention
Description
monospace
Represents information as it [Device name]>
appears on screen
monospace bold
Represents information that [Device name]> set
you enter
ipaddr 10.0.0.12
default font bold
Keyboard keys, software
buttons, and field names
On the Start menu, click All
Programs.
italics
Screen or page names
Click Advanced Settings. The
Advanced Settings page
appears.
Table 2.
Example
Notice conventions
Notice Type
Description
NOTE
Information that describes important features or instructions
CAUTION!
Information that alerts you to potential loss of data or potential
damage to an application, system, or device
WARNING!
Information that alerts you to potential personal injury
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
17
About This Guide
Terminology
Terminology
Table 3 lists the terms used in this guide.
Table 3.
Terms used
Term
Description
AAA
Authentication, Authorization, and Accounting
AP
Access Point
APN
Access Point Name
CDR
A formatted collection of information on chargeable events
used for accounting and billing. For example, call set-up,
call duration and amount of data transferred.
CLB
Client Load Balance
CNN
Configuration Change Notifier
CNR
Configuration Notification Receiver
CoA
Change of Authorization
Controller
Refers to either SZ-100 or vSZ-E as the case may be.
CPE
Customer-Premises Equipment
DHCP
Dynamic Host Configuration Protocol
DM
Dynamic Multipoint
DNS
Domain Name System
EAP
Extensible Authentication Protocol
EMAP
Ethernet Mesh AP
EPS
Evolved Packet System
FTP
File Transfer Protocol
GGSN
Gateway GPRS Support Node
GTP
GPRS Tunneling Protocol
GTPv1-U
GTP version 1, user plane
GTPv2-C
GTP version 2, control plane
HIP
Host Identity Protocol
MAP
Mobile Application Part
MOR
Maximum Outstanding Request
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
18
About This Guide
Related Documentation
Table 3.
Terms used
Term
Description
MTU
Maximum Transmission Unit
MWSG
Metro Wireless Security Gateway
NAS
Network Access Server
NTP
Network Time Protocol)
PDP
Packet Data Protocol
produce.short.name
Refers to either SZ-100 or vSZ-E
RAC
Radio Access Controller
RAP
Root Access Point
RSSI
Received Signal Strength Indicator
SSID
Service Set Identifier (SSID)
TCP
Transmission Control Protocol
TEID
Tunnel End Point Identifier
UE
User Equipment
UI
The SmartZone Web User Interface
USB
Universal Serial Bus
WDS
Wireless Distribution System
Related Documentation
For a complete list of documents that accompany this release, refer to the Release
Notes.
Online Training Resources
To access a variety of online Ruckus Wireless training modules, including free
introductory courses to wireless networking essentials, site surveys, and Ruckus
Wireless products, visit the Ruckus Wireless Training Portal at:
https://training.ruckuswireless.com
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
19
About This Guide
Documentation Feedback
Documentation Feedback
Ruckus Wireless is interested in improving its documentation and welcomes your
comments and suggestions. You can email your comments to Ruckus Wireless at:
docs@ruckuswireless.com
When contacting us, please include the following information:
• Document title
• Document part number (on the cover page)
• Page number (if appropriate)
For example:
• SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1
• Part number: 800-71374-001
• Page 60
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
20
Revision History
1
This chapter contains revision history for:
• SmartZone Version 3.4.1
• SmartZone Version 3.4
• SmartZone Version 3.2.1
• SmartZone Version 3.2
• SmartZone Version 3.1.1
• RuckOS Version 3.1
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
21
Revision History
SmartZone Version 3.4.1
SmartZone Version 3.4.1
No changes to this version.
SmartZone Version 3.4
The following are the changes for version 3.4.
New Alarm
Alarm Code
Alarm
850
clusterUploadAPFirmwareFailed
853
clusterAddAPFirmwareFailed
1021
zoneCfgPrepareFailed
1022
apCfgGenFailed
1023
cfgGenSkippedDueToEolAp
Displayed on the Web Interface
Alarm Code
Attribute
Attribute Change
107
Added failure
reason
AP [{apName&&apMac}] failed to update its
firmware from [{fromVersion}] to [{toVersion}]
failure reason [{reason}]
New Event
2
Event Code
Event
848
clusterUploadAPFirmwareStart
849
clusterUploadAPFirmwareSuccess
850
clusterUploadAPFirmwareFailed
851
clusterAddAPFirmwareStart
852
clusterAddAPFirmwareSuccess
853
clusterAddAPFirmwareFailed
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
22
Revision History
SmartZone Version 3.4
Event Code
Event
854
clusterNameChanged
1021
zoneCfgPrepareFailed
1022
apCfgGenFailed
1023
cfgGenSkippedDueToEolAp
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
23
Revision History
SmartZone Version 3.2.1
SmartZone Version 3.2.1
The following are the changes for version 3.2.1.
New Alarm
Alarm Code
Alarm
865
apCertificateExpire
New Event
2
Event Code
Event
226
wdsDeviceJoin
227
wdsDeviceLeave
865
apCertificateExpire
866
apCertificateExpireClear
3011
recoverCassandraError
Event on Web Interface
Event
Code
Existing Display
New Display
513
Data plane [{dpName&&dpKey}]
disconnected from
{produce.short.name}
[{cpName||wsgIP}].
Data plane [{dpName&&dpKey}]
disconnected from
{produce.short.name}
[{cpName||wsgIP}], Reason:
[{reason}].
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
24
Revision History
SmartZone Version 3.2
SmartZone Version 3.2
The following are the changes for version 3.2.
New Alarm
Alarm Code
Alarm
538
dpLicenseInsufficient
553
dpUpgradeFailed
661
ipsecTunnelDisassociated
662
ipsecTunnelAssociateFailed
751
syslogServerUnreachable
835
resyncNTPTime
1752
racADLDAPFail
1753
racADLDAPBindFail
1754
racLDAPFailToFindPassword
1755
racADNPSFail
1756
racADNPSFailToAuthenticate
2102
radiusServerUnreachable
2122
ldapServerUnreachable
2142
adServerUnreachable
2152
espAuthServerUnreachable
2154
espAuthServerUnResolvable
2162
espDNATServerUnreachable
2164
espDNATServerUnresolvable
Attribute Change
Table 4.
Module
Attribute
Attribute Change
DataPlane
dpMac
dpKey
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
25
Revision History
SmartZone Version 3.2
Renamed Alarm
Alarm
Code
Alarm Name
Renamed To
1202
DP Disconnected
GtpManager (DP) disconnected
7003
The number of users exceeded it's limit
The number of users exceeded
its limit
7004
The number of devices exceeded it's limit The number of devices
exceeded its limit
New Event
2
Event Code
Event
370
apUsbSoftwarePackageDownloaded
371
apUsbSoftwarePackageDownloadFailed
516
dpPktPoolLow
517
dpPktPoolCriticalLow
518
dpPktPoolRecover
519
dpCoreDead
530
dpDiscoverySuccess
532
dpStatusManaged
537
dpDeleted
538
dpLicenseInsufficient
550
dpUpgradeStart
551
dpUpgrading
552
dpUpgradeSuccess
553
dpUpgradeFailed
615
dpSgreGWUnreachable
616
dpSgreKeepAliveTimeout
617
dpSgreGWInact
620
dpSgreNewTunnel
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
26
Revision History
SmartZone Version 3.2
Event Code
Event
622
dpSgreKeepAliveRecovery
624
dpSgreGWReachable
625
dpSgreGWAct
750
syslogServerReachable
751
syslogServerUnreachable
752
syslogServerSwitched
770
planeLoadingRebalancingSucceeded
771
planeLoadingRebalancingFailed
845
clusterUploadVDPFirmwareStart
846
uploadClusterVDPFirmwareSuccess
847
uploadClusterVDPFirmwareFailed
1255
licenseGoingToExpire
1256
apConnectionTerminatedDueToInsufficientLicense
1751
racADLDAPSuccess
1752
racADLDAPFail
1753
racADLDAPBindFail
1754
racLDAPFailToFindPassword
1755
racADNPSFail
1756
racADNPSFailToAuthenticate
2151
espAuthServerReachable
2152
espAuthServerUnreachable
2153
espAuthServerResolvable
2154
espAuthServerUnResolvable
2161
espDNATServerReachable
2162
espDNATServerUnreachable
2163
espDNATServerResolvable
2164
espDNATServerUnresolvable
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
27
Revision History
SmartZone Version 3.2
Severity Change
Event Code and Event
Severity Changed From Severity Changed To
837 - resyncNTPTime
Informational
Major
2102 radiusServerUnreachable
Informational
Major
2122 ldapServerUnreachable
Informational
Major
2142 - adServerUnreachable Informational
Major
Attribute Change
Module
Attribute
Attribute Change
Data Plane
dpMac
dpKey
AP Communication “model"="ZF7343"
Events
"model"="R700”
System Events
System Events
"model"="ZF7962",
"model"="R700", “firmware”=“3.2.0.0.x”
“firmware”=“3.0.0.0.0”
Renamed Event
Event
Code
Event Name
Renamed To
320
AP CLB limit reached
AP client load balancing limit
reached
321
AP CLB limit recovered
AP client load balancing limit
recovered
619
DP DHCPRelay failOver
DP DHCPRelay failover
1202
DP Disconnected
GtpManager (DP) disconnected
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
28
Revision History
SmartZone Version 3.1.1
Auto Clearance of Event
Event Code Event Name
2102
This event triggers the alarm 2102, which is auto cleared by the
event code 2101
2122
This event triggers the alarm 2122, which is auto cleared by the
event code 2121
2142
This event triggers the alarm 2142, which is auto cleared by the
event code 2141.
SmartZone Version 3.1.1
The following are the changes for version 3.1.1.
New Alarm
Alarm Code
Alarm
661
ipsecTunnelDisassociated
662
ipsecTunnelAssociateFailed
New Event
Event Code
Event
326
cmResetByUser
327
cmResetFactoryByUser
660
ipsecTunnelAssociated
661
ipsecTunnelDisAssociated
662
ipsecTunnelAssociateFailed
844
clusterInitiatedMovingAp
2101
radiusServerReachable
2102
radiusServerUnreachable
2121
ldapServerReachable
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
29
Revision History
SmartZone Version 3.1.1
Event Code
Event
2122
ldapServerUnreachable
2141
adServerReachable
2142
adServerUnreachable
2201
zoneInitiatedMovingAp
2501
nodeIPv6Added
2502
nodeIPv6Deleted
Re-added Event
Event Code
Event
101
apDiscoverySuccess
Renamed Event
Event
Code
Event Name
Renamed To
318
AP cable modem rebooted by user
AP cable modem power-cycled
by user
Deprecated Event
Event Code
Event Name
1604
authSuccess
1605
authFailed
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
30
Revision History
RuckOS Version 3.1
RuckOS Version 3.1
The following are the changes for version 3.1.
New Alarm
Alarm Code
Alarm
520
dpProcessRestart
862
clusterCfgBackupFailed
864
clusterCfgRestoreFailed
902
ipmiThempBB
1651
authFailedOverToSecondary
1652
authFallbackToPrimary
7003
tooManyUsers
7004
tooManyDevices
Deprecated Alarm
Alarm Code
Alarm
1008
cfgUpdFailed
1909
apAcctRespWhileInvalidConfig
Renamed Alarm Type
Alarm Code
Alarm Type
Renamed To
843
clusterOutofService
clusterOutOfService
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
31
Revision History
RuckOS Version 3.1
Renamed Alarm
Alarm Code
Alarm Type
Renamed To
701
No LS Responses
No LS responses
721
No LS Responses
No LS responses
1302
Rate Limit for TOR surpassed
Rate limit for TOR surpassed
New Event
Event Code
Event
223
remediationSuccess
224
remediationFailure
325
cableModemUp
520
dpProcessRestart
627
dpSetUpTunnel
860
clusterCfgBackupStart
861
clusterCfgBackupSuccess
862
clusterCfgBackupFailed
863
clusterCfgRestoreSuccess
864
clusterCfgRestoreSuccess
902
ipmiThempBB
927
ipmiREThempBB
932
ipmiREThempP
934
ipmiREFan
937
ipmiREFanStatus
953
cpuThresholdBackToNormal
954
memoryThresholdBackToNormal
955
diskUsageThresholdBackToNormal
1651
authFailedOverToSecondary
1652
authFallbackToPrimary
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
32
Revision History
RuckOS Version 3.1
Event Code
Event
7001
tooManyUsers
7002
tooManyDevices
Renamed Event
Event
Code
Event Name
Renamed To
181
Ssid-spoofing rogue AP
SSID-spoofing rogue AP
209
Client Roaming
Client roaming
220
Client Grace Period
Client grace period
308
AP channel updated because Dynamic
Frequency Selection (DFS) detected a
radar event
AP channel updated because
dynamic frequency selection
(DFS) detected a radar event
317
AP Brownout
AP brownout
323
AP capacity Reached
AP capacity reached
405
eMAP downlink connected to MAP
EMAP downlink connected to
MAP
406
eMAP downlink disconnected from MAP EMAP downlink disconnected
from MAP
407
eMAP uplink connected to MAP
EMAP uplink connected to MAP
408
eMAP uplink disconnected from MAP
EMAP uplink disconnected from
MAP
422
Mesh state updated to MAP No Channel Mesh state updated to MAP no
channel
424
Mesh state update to RAP No Channel
Mesh state update to RAP no
channel
515
Data plane physical Interface Up
Data plane physical interface up
615
DP SoftgreGW Unreachable
DP softGRE GW unreachable
618
DP DhcpRelay No Resp
DP DHCPRelay no response
619
DP DhcpRelay FailOver
DP DHCPRelay failOver
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
33
Revision History
RuckOS Version 3.1
Event
Code
Event Name
Renamed To
623
DP DhcpRelay Resp Recovery
DP DHCPRelay response
recovery
701
No LS Responses
No LS responses
707
AP received Passive Calibration Request AP received passive calibration
request
708
AP received Passive Footfall Request
AP received passive footfall
request
709
AP received Unrecognized Request
AP received unrecognized
request
721
No LS Responses
No LS responses
725
SCG received Passive Request
SCG received passive request
727
SCG sent Controller Information report
SCG sent controller information
report
728
SCG received Management Request
SCG received management
request
729
SCG sent AP Info by Venue Report
SCG sent AP info by venue
report
730
SCG sent Query Venues Report
SCG sent query venues report
731
SCG sent Associated Client Report
SCG sent associated client
report
732
SCG forwarded Calibration Request to AP SCG forwarded calibration
request to AP
733
SCG forwarded Footfall Request to AP
SCG forwarded footfall request
to AP
734
SCG received Unrecognized Request
SCG received unrecognized
request
833
SSH Tunnel Switched
SSH tunnel switched
837
Resync NTP Time
Resync NTP time
970
FTP Transfer
FTP transfer
971
FTP Transfer Error
FTP transfer error
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
34
Revision History
RuckOS Version 3.1
Event
Code
Event Name
Renamed To
980
File Upload
File upload
981
Email Sent Successfully
Email sent successfully
982
Email Sent Failed
Email sent failed
983
SMS Sent Successfully
SMS sent successfully
984
SMS Sent Failed
SMS sent failed
1012
Incorrect Flat File Configuration
Incorrect flat file configuration
1647
CoA Sent NAS
CoA sent NAS
1648
CoA NAK Received NAS
CoA NAK received NAS
1649
CoA Authorize Only Access Reject
CoA authorize only access reject
1650
CoA RWSG MWSG Notification Failure
CoA RWSG MWSG notification
failure
2001
ZD AP Migrating
ZD AP migrating
2002
ZD AP Migrated
ZD AP migrated
2003
ZD AP Rejected
ZD AP rejected
2004
ZD AP Migration Failed
ZD AP migration failed
1302
Rate Limit for TOR surpassed
Rate limit for TOR surpassed
1911
Unauthorized CoA/DM message dropped Unauthorized COA/DM
message dropped
1641
DM Received from AAA
DM received from AAA
1643
DM Sent to NAS
DM sent to NAS
1644
DM NACK Received from NAS
DM NACK received from NAS
1645
CoA Received from AAA
CoA received from AAA
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
35
Alarm and Event Management
2
In this chapter:
• Overview
• Alarm and Event Management
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
36
Alarm and Event Management
Overview
Overview
This guide lists and describes the various types of alarm and event that the controller
generates. For each alarm and event, this guide provides the code, type, attributes,
and description.
NOTE: Refer to About This Guide for the conventions used in this guide.
Alarm and Event Management
This subsystem contains set of functions that help users to detect, isolate, and
eventually correct malfunctions in the managed network. This section covers:
• Event Categories
• Event Attributes
• Generation of Alarm and Event
Event Categories
Events are used for many different purposes, mainly for notifying users of certain
conditions in the system components as well as the managed network. They can
be classified into the following categories:
• Alarms: These are unexpected events indicating a condition that typically
requires management attention
• Configuration Change Events: Configuration change events are events that
inform of a configuration change effect on the device.
• Threshold Crossing Alerts: These are events that inform of a performance-related
state variable that has exceeded a certain value. These events point to conditions
that might require management attention to prevent network and service degradation.
• Logging Events: These are events that occur regularly and are expected to occur
during the operation of a network, that indicate what is currently going on in the
network. Some examples of these events include:
• Activity on the network and service
• Operator activity
• System activity
• Informational events – Any other kind of event.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
37
Alarm and Event Management
Alarm and Event Management
• Debug and Informational events - All the debug and informational events
pertaining to TTG modules like RADIUS proxy, HIP, CIP and AUT are not
displayed on the controller web interface. This is because it reduces the
performance of the system since its large in numbers. Enabling display of
these events on the controller web interface is possible through CLI but it is
not recommended.
Event Attributes
An event always includes the following attributes:
• Event Source: The identifier of the source component that generates the event
• Timestamp: The time when the event occurred
• Event Severity: Severity is classified as critical, major, minor, warning, informational or debug
• Event Type: The type of event that has occurred
• Event Information: Contains detail attribute fields in a key-value pair, where a list
of field names is provided
Generation of Alarm and Event
The following are the steps of how the controller generates alarm and event.
1 Alarm
a An alarm is a persistent indication of a fault that clears only when the triggering
condition had been resolved.
b An alarm can be filtered in the controller web interface based on:
-
Acknowledge Time: The time when the alarm is acknowledged
-
Date and Time - Date and time when the alarm is acknowledged
-
Severity: Severity is classified as critical, major or minor
-
Status - Could either be cleared or outstanding
-
Type - Alarm type
c To view the below alarm information in the controller web interface navigate
to Monitor > Alarms
-
Date and Time
-
Code
-
Alarm Type
-
Severity
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
38
Alarm and Event Management
Alarm and Event Management
-
Status
-
Acknowledged on
-
Cleared By
-
Cleared On
-
Comments
-
Activity
-
Actions
d On an alarm generation, the controller web interface Monitor > Alarms
provides the following information as seen in Figure 1.
-
Alarm console, which displays the cleared and outstanding alarms visible
to the user who is currently logged on
-
Alarm summary, which lists various information such as outstanding alarm
counts and unacknowledged alarm counts.
-
Filtering features based on the alarm attributes.
-
You may clear an alarm or a set of alarms to let other administrators know
that you have already resolved the issue. When you select a group of
alarms, the Clear Alarms button is activated. Click this button. A text box
appears where you can enter comments or notes about the resolved
issue. Click Apply when done. To view the cleared alarms, select the
cleared option.
Figure 1. Alarm
2 Event - On an event generation the:
a Controller collects, receives, and maintains the raw events from the managed
entities (control plane, data plane and access points). These raw events are
kept in the controller database, and is automatically purged.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
39
Alarm and Event Management
Alarm and Event Management
b The controller allows users to enable/disable certain event types from the
managed entities.
-
Disabled events are filtered at the source whenever possible to minimize
resources for processing events
-
Threshold events are triggered at the source whenever possible.
c The controller provides event log window as seen in Figure 2 for users to
visualize and analyze the events. Users are able to perform various operations
on the events, such as filtration, aggregation and counting. To view the below
event information in the controller web interface navigate to Monitor >
Events .
-
Date and Time
-
Code
-
Type
-
Severity
-
Activity
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
40
Alarm and Event Management
Alarm and Event Management
Figure 2. Event
NOTE: Refer to Alarm Types and Events Types for the list of alarm and event that
the controller generates.
NOTE: Refer to SNMP MIB Reference Guide for the list of SNMP alarm traps that
the controller generates.
NOTE: Refer to Administrator Guide for Viewing of Alarms and Events.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
41
Alarm Types
3
This chapter provides information on the various types of alarms that the controller
100 generates. Alarms are a subset of the events defined. Categories are inherited
from the event.
In this chapter:
• Accounting Alarms
• AP Authentication Alarms
• AP Communication Alarms
• AP LBS Alarms
• AP State Change Alarms
• Authentication Alarms
• Control and Data Plane Interface Alarms
• Cluster Alarms
• Configuration Alarms
• Data Plane Alarms
• IPMI Alarms
• Licensing Interface Alarms
• System Alarms
• Threshold Alarms
• Tunnel Alarms - Access Point
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
42
Alarm Types
Accounting Alarms
Accounting Alarms
Following are the alarms related to accounting.
• Accounting server not reachable
Accounting server not reachable
Table 5.
Accounting server not reachable alarm
Alarm
Accounting server not reachable
Alarm Type
accSrvrNotReachable
Alarm Code
1602
Severity
Major
Aggregation Policy
An alarm is raised for every event from the event code 1602. A single
event triggers a single alarm.
Attribute
“mvnoId”=12, “ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”
“srcProcess”=”radiusd”, “realm”=”wlan.3gppnetwork.org"
“radProxyIp”=”7.7.7.7”, “accSrvrIp"=”30.30.30.30”
" {produce.short.name}"="2.2.2.2"
Displayed on the web
interface
Accounting Server [{accSrvrIp}] not reachable from Radius Proxy
[{radProxyIp}] on {produce.short.name} [{SZMgmtIp}]
Description
This alarm is triggered when the accounting server cannot be reached.
Recommended Actions Manual intervention is required. Check the web interface for the SZ
connection to the AAA interface. Also, check if the RADIUS server can
reach the AAA server interface.
NOTE: Refer to Accounting Events.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
43
Alarm Types
AP Authentication Alarms
AP Authentication Alarms
Following are the alarms related to AP authentication.
• RADIUS server unreachable
• LDAP server unreachable
• AD server unreachable
• WeChat ESP authentication server unreachable
• WeChat ESP authentication server unresolvable
• WeChat ESP DNAT server unreachable
• WeChat ESP DNAT server unresolvable
RADIUS server unreachable
Table 6.
RADIUS server unreachable alarm
Alarm
RADIUS server unreachable
Alarm Type
radiusServerUnreachable
Alarm Code
2102
Severity
Major
Aggregation Policy
From the event code 2102 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“apMac="xx:xx:xx:xx:xx:xx","ip"="17.0.0.12","fwVersion"="3.2.0.0.x","
model"="ZF7982","zoneUUID"="f77a8816-3049-40cd-848482919275ddc3","zoneName"="Default Zone","apLocation"=""
Auto Clearance
The alarm is auto cleared with the event code 2101.
Displayed on the web
interface
AP [{apName&&apMac}] is unable to reach radius server [{ip}].
Description
This alarm is triggered when AP is unable to reach RADIUS server.
Recommended Actions Check the network connectivity between AP and RADIUS server.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
44
Alarm Types
AP Authentication Alarms
LDAP server unreachable
Table 7.
LDAP server unreachable alarm
Alarm
LDAP server unreachable
Alarm Type
ldapServerUnreachable
Alarm Code
2122
Severity
Major
Aggregation Policy
From the event code 2122 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“apMac="xx:xx:xx:xx:xx:xx","ip"="17.0.0.12","fwVersion"="3.2.0.0.x","
model"="ZF7982","zoneUUID"="f77a8816-3049-40cd-848482919275ddc3","zoneName"="Default Zone","apLocation"=""
Auto Clearance
The alarm is auto cleared with the event code 2121.
Displayed on the web
interface
AP [{apName&&apMac}] is unable to reach LDAP server [{ip}].
Description
This alarm is triggered when AP is unable to reach LDAP server.
Recommended Actions Check the network connectivity between AP and LDAP server.
AD server unreachable
Table 8.
AD server unreachable alarm
Alarm
AD server unreachable
Alarm Type
adServerUnreachable
Alarm Code
2142
Severity
Major
Aggregation Policy
From the event code 2142 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“apMac="xx:xx:xx:xx:xx:xx","ip"="17.0.0.12","fwVersion"="3.2.0.0.x","
model"="ZF7982","zoneUUID"="f77a8816-3049-40cd-848482919275ddc3","zoneName"="Default Zone","apLocation"=""
Auto Clearance
The alarm is auto cleared with the event code 2141.
Displayed on the web
interface
AP [{apName&&apMac}] is unable to reach AD server [{ip}].
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
45
Alarm Types
AP Authentication Alarms
Table 8.
AD server unreachable alarm
Description
This alarm is triggered when AP is unable to reach AD server.
Recommended Actions Check the network connectivity between AP and AD server.
WeChat ESP authentication server unreachable
Table 9.
WeChat ESP authentication server unreachable alarm
Alarm
WeChat ESP authentication server unreachable
Alarm Type
espAuthServerUnreachable
Alarm Code
2152
Severity
Major
Aggregation Policy
From the event code 2152 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
"apMac"="xx:xx:xx:xx:xx:xx","ip"="17.0.0.12","profileId"="1","fwVersio
n"="3.2.0.0.x","model"="ZF7982","zoneUUID"="f77a8816-304940cd-8484-82919275ddc3","zoneName"="Default
Zone","apLocation"=""
Auto Clearance
The alarm is auto cleared with the event code 2151
Displayed on the web
interface
AP [{apName&&apMac}] is unable to reach WeChat ESP authentication
server [{ip}]
Description
This alarm is triggered when AP is unable to reach WeChat ESP
authentication server.
Recommended Actions Check the network connectivity between controller web interface and
WeChat ESP authentication server.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
46
Alarm Types
AP Authentication Alarms
WeChat ESP authentication server unresolvable
Table 10. WeChat ESP authentication server unresolvable alarm
Alarm
WeChat ESP authentication server unresolvable
Alarm Type
espAuthServerUnResolvable
Alarm Code
2154
Severity
Major
Aggregation Policy
From the event code 2154 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
"apMac"="xx:xx:xx:xx:xx:xx","dn"="www.test.com","profileId"="1","fw
Version"="3.2.0.0.x","model"="ZF7982","zoneUUID"="f77a88163049-40cd-8484-82919275ddc3","zoneName"="Default
Zone","apLocation"=""
Auto Clearance
The alarm is auto cleared with the event code 2153.
Displayed on the web
interface
AP [{apName&&apMac}] is unable to resolve WeChat ESP
authentication server domain name [{dn}] to IP
Description
This alarm is triggered when AP is unable to resolve WeChat ESP
authentication server domain name.
Recommended Actions Check the DNS server configuration settings in the controller web
interface.
WeChat ESP DNAT server unreachable
Table 11. WeChat ESP DNAT server unreachable alarm
Alarm
WeChat ESP DNAT server unreachable
Alarm Type
espDNATServerUnreachable
Alarm Code
2162
Severity
Major
Aggregation Policy
From the event code 2162 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
"apMac"="xx:xx:xx:xx:xx:xx","ip"="17.0.0.12","profileId"="1","fwVersio
n"="3.2.0.0.x","model"="ZF7982","zoneUUID"="f77a8816-304940cd-8484-82919275ddc3","zoneName"="Default
Zone","apLocation"=""
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
47
Alarm Types
AP Authentication Alarms
Table 11. WeChat ESP DNAT server unreachable alarm
Auto Clearance
The alarm is auto cleared with the event code 2161.
Displayed on the web
interface
AP [{apName&&apMac}] is unable to reach WeChat ESP DNAT server
[{ip}].
Description
This alarm is triggered when the AP is unable to reach WeChat ESP
DNAT server.
Recommended Actions Check the network connectivity between controller web interface and
WeChat ESP DNAT server.
WeChat ESP DNAT server unresolvable
Table 12. WeChat ESP DNAT server unresolvable alarm
Alarm
WeChat ESP DNAT server unresolvable
Alarm Type
espDNATServerUnresolvable
Alarm Code
2164
Severity
Major
Aggregation Policy
From the event code 2164 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
"apMac"="xx:xx:xx:xx:xx:xx","dn"="www.test.com","profileId"="1","fw
Version"="3.2.0.0.x","model"="ZF7982","zoneUUID"="f77a88163049-40cd-8484-82919275ddc3","zoneName"="Default
Zone","apLocation"=""
Auto Clearance
The alarm is auto cleared with the event code 2163.
Displayed on the web
interface
AP [{apName&&apMac}] is unable to resolve WeChat ESP DNAT server
domain name [{dn}] to IP
Description
This alarm is triggered when the AP is unable to resolve WeChat ESP
DNAT server domain name.
Recommended Actions Check the DNS server configuration settings in the controller web
interface.
NOTE: Refer to AP Authentication Events.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
48
Alarm Types
AP Communication Alarms
AP Communication Alarms
Following are the alarms related to access point communications.
• AP rejected
• AP configuration update failed
• AP swap model mismatched
• AP pre-provision model mismatched
• AP firmware update failed
• AP WLAN oversubscribed
AP rejected
Table 13. AP rejected alarm
Alarm
AP rejected
Alarm Type
apStatusRejected
Alarm Code
101
Severity
Minor
Aggregation Policy
From the event code 105 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm is auto cleared with the event code 103.
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”, “wsgIP"=”xxx.xxx.xxx.xxx”,
“reason”=”xxx”
Displayed on the web
interface
{produce.short.name} [{wsgIP}] rejected AP [{apName&&apMac}]
because of [{reason}].
Description
This alarm is triggered when the AP is rejected by the controller.
Recommended Actions Check if the number of licenses has exceeded the limit. You would need
to purchase additional licenses, in case of insufficient licenses.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
49
Alarm Types
AP Communication Alarms
AP configuration update failed
Table 14. AP configuration update failed alarm
Alarm
AP configuration update failed
Alarm Type
apConfUpdateFailed
Alarm Code
102
Severity
Major
Aggregation Policy
From the event code 111 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm is auto cleared with the event code 110.
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”, “configID”=”23456781234”
Displayed on the web
interface
AP [{apName&&apMac}] failed to update to configuration [{configID}].
Description
This alarm is triggered when the controller is unable to update the AP
configuration details.
Recommended Actions Retrieve the AP support text. Reboot the AP and trigger another
configuration change for upgrading the AP. If it fails revert to the previous
zone firmware.
AP swap model mismatched
Table 15. AP swap model mismatched alarm
Alarm
AP swap model mismatched
Alarm Type
apModelDiffWithSwapOutAP
Alarm Code
104
Severity
Major
Aggregation Policy
From the event code 113 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "wsgIP"="xxx.xxx.xxx.xxx"
“configModel”=”xxx.xxx.xxx.xxx”, “model”=”xxx.xxx.xxx.xxx
Displayed on the web
interface
AP [{apName&&apMac}] model [{model}] is different from swap
configuration model [{configModel}]
Description
This alarm is triggered when the AP model differs from the swapped
configuration model.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
50
Alarm Types
AP Communication Alarms
Table 15. AP swap model mismatched alarm
Recommended Actions If the model is incorrect delete and rejoin the AP.
AP pre-provision model mismatched
Table 16. AP pre-provision model mismatched alarm
Alarm
AP pre-provision model mismatched
Alarm Type
apModelDiffWithPreProvConfig
Alarm Code
105
Severity
Major
Aggregation Policy
From the event code 112 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”, “wsgIP"=”xxx.xxx.xxx.xxx”,
“configModel”=”xxx.xxx.xxx.xxx”. “model”=”xxx.xxx.xxx.xxx”
Displayed on the web
interface
AP [{apName&&apMac}] model [{model}] is different from per-provision
configuration model [{configModel}]
Description
This alarm is triggered when the AP model differs from the per-provision
configuration model.
Recommended Actions If the model is incorrect delete the AP for the AP to rejoin to get the
proper AP configuration.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
51
Alarm Types
AP Communication Alarms
AP firmware update failed
Table 17. AP firmware update failed alarm
Alarm
AP firmware update failed
Alarm Type
apFirmwareUpdateFailed
Alarm Code
107
Severity
Major
Aggregation Policy
From the event code 107 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm is auto cleared with the event code 106.
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "wsgIP"="xxx.xxx.xxx.xxx"
Displayed on the web
interface
AP [{apName&&apMac}] failed to update its firmware from
[{fromVersion}] to [{toVersion}] [{reason}]
Description
This alarm is triggered when the AP fails to update the firmware details
on the controller.
Recommended Actions Retrieve the AP support text. Reboot the AP and trigger another
configuration change for upgrading the AP. If it fails revert to the previous
zone firmware.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
52
Alarm Types
AP Communication Alarms
AP WLAN oversubscribed
Table 18. AP WLAN oversubscribed alarm
Alarm
AP WLAN oversubscribed
Alarm Type
apWlanOversubscribed
Alarm Code
108
Severity
Major
Aggregation Policy
From the event code 114 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
"apMac"=”xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
AP [{apName&&apMac}] does not have enough capacity to deploy all
wlans. Only maximum wlan number of the AP can be deployed
Description
This alarm is triggered when the AP exceeds the maximum capacity for
deploying all WLANs. Only a maximum number of WLAN APs can be
deployed.
Recommended Actions Any of the following are the recommended actions.
• Create a new WLAN group with WLANs. Ensure that it is not more
than the AP's WLAN capacity. Apply the new WLAN group to either
the AP or the AP's AP Group.
• Find the WLAN group used by the AP and reduce the number of
WLAN
NOTE: Refer to AP Communication Events.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
53
Alarm Types
AP LBS Alarms
AP LBS Alarms
Following are the alarms related to AP Location Based Service.
• No LS responses
• LS authentication failure
• AP failed to connect to LS
No LS responses
Table 19. No LS responses alarm
Alarm
No LS responses
Alarm Type
apLBSNoResponses
Alarm Code
701
Severity
Major
Aggregation Policy
From the event code 701 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“apMac”=“xx:xx:xx:xx:xx:xx“, “url”=““,”port”=““
Displayed on the web
interface
AP [{apName&&apMac}] no response from LS: url=[{url}], port=[{port}]
Description
This alarm is triggered when the AP does not get a response when trying
to connect to the location based service.
Recommended Actions This alarm is triggered when the location server fails to respond to the
AP request due to an error or the server is an maintenance mode. Report
this to the location server owner.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
54
Alarm Types
AP LBS Alarms
LS authentication failure
Table 20. LS authentication failure alarm
Alarm
LS authentication failure
Alarm Type
apLBSAuthFailed
Alarm Code
702
Severity
Major
Aggregation Policy
From the event code 702 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“apMac”=“xx:xx:xx:xx:xx:xx“, “url”=““,”port”=““
Displayed on the web
interface
AP [{apName&&apMac}] LBS authentication failed: url=[{url}],
port=[{port}]
Description
This alarm is triggered due to the authentication failure on connecting
to the location based service.
Recommended Actions The password needs to be corrected in the LBS service page.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
55
Alarm Types
AP LBS Alarms
AP failed to connect to LS
Table 21. AP failed to connect to LS alarm
Alarm
AP failed to connect to LS
Alarm Type
apLBSConnectFailed
Alarm Code
704
Severity
Major
Aggregation Policy
From the event code 704 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm is auto cleared with the event code 703.
Attribute
“apMac”=“xx:xx:xx:xx:xx:xx“, “url”=““,”port”=““
Displayed on the web
interface
AP [{apName&&apMac}] connection failed to LS: url=[{url}],
port=[{port}]
Description
This alarm is triggered when the AP fails to connect to the location based
service.
Recommended Actions This alarm is triggered either when the location server is unreachable or
the network connection is unstable or the domain name system (DNS)
configuration is incorrect. It is recommended to check all the three
possible error codes 701, 702 and 704.
NOTE: Refer to AP LBS Events.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
56
Alarm Types
AP State Change Alarms
AP State Change Alarms
Following are the alarms related to access point state changes.
• AP rebooted by system
• AP disconnected
• AP deleted
• AP cable modem interface down
AP rebooted by system
Table 22. AP rebooted by system alarm
Alarm
AP rebooted by system
Alarm Type
apRebootBySystem
Alarm Code
302
Severity
Major
Aggregation Policy
From the event code 302 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”, “reason”=”xxxxx”
Displayed on the web
interface
AP [{apName&&apMac}] rebooted by the system because of [{reason}]
Description
This alarm is triggered when the system reboots the AP.
Recommended Actions Check the reasons for the reboot. If the reason is unknown, retrieve the
AP support text and send it to Ruckus support.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
57
Alarm Types
AP State Change Alarms
AP disconnected
Table 23. AP disconnected alarm
Alarm
AP disconnected
Alarm Type
apConnectionLost
Alarm Code
303
Severity
Major
Aggregation Policy
From the event code 303 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm is auto cleared with the event code 312
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
AP [{apName&&apMac}] disconnected
Description
This alarm is triggered when the AP disconnects from the controller.
Recommended Actions Check the network and the communicator process on the controller. Try
rebooting the AP locally.
AP deleted
Table 24. AP deleted alarm
Alarm
AP deleted
Alarm Type
apDeleted
Alarm Code
306
Severity
Major
Aggregation Policy
From the event code 313 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
AP [{apName&&apMac}] deleted
Description
This alarm is triggered when the AP is deleted.
Recommended Actions This is a user action and to confirm check the user audit.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
58
Alarm Types
AP State Change Alarms
AP cable modem interface down
Table 25. AP cable modem interface down alarm
Alarm
AP cable modem interface down
Alarm Type
cableModemDown
Alarm Code
308
Severity
Major
Aggregation Policy
From the event code 316 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm is auto cleared with the event code 325.
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
AP [{apName&&apMac}] cable modem interface is down
Description
This alarm is triggered when the AP cable modem interface is down.
Recommended Actions Check cable modem. Try rebooting the cable modem.
NOTE: Refer to AP State Change Events.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
59
Alarm Types
Authentication Alarms
Authentication Alarms
The following are the alarms related to authentication.
• Authentication server not reachable
• Authentication failed over to secondary
• Authentication fallback to primary
• AD/LDAP connectivity failure
• Bind fails with AD/LDAP
• Bind success with LDAP, but unable to find clear text password for the user
• RADIUS fails to connect to AD NPS server
• RADIUS fails to authenticate with AD NPS server
Authentication server not reachable
Table 26. Authentication server not reachable alarm
Alarm
Authentication server not reachable
Alarm Type
authSrvrNotReachable
Alarm Code
1601
Severity
Major
Aggregation Policy
From the event code 1601 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“mvnoId”=12 “ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”
“srcProcess”=”radiusd” “realm”=
”wlan.mnc080.mcc405.3gppnetwork.org" “radProxyIp”=”7.7.7.7”
“authSrvrIp"=”20.20.20.20” "SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
Authentication Server [{authSrvrIp}] not reachable from Radius Proxy
[{radProxyIp}] on {produce.short.name} [{SZMgmtIp}]
Description
This alarm is triggered when the authentication fails since the primary or
secondary servers are not reachable.
Recommended Actions Manual intervention is required. Check the web interface for the interface
from the controller to AAA server. Also check if the AAA server can be
reached from the RADIUS server. Ensure that the AAA server is UP.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
60
Alarm Types
Authentication Alarms
Authentication failed over to secondary
Table 27. Authentication failed over to secondary alarm
Alarm
Authentication failed over to secondary
Alarm Type
authFailedOverToSecondary
Alarm Code
1651
Severity
Major
Aggregation Policy
From the event code 1651 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“mvnoId”=12 “ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”,
srcProcess”=”radiusd” “realm”=
”wlan.mnc080.mcc405.3gppnetwork.org" “radProxyIp”=”7.7.7.7”
“primary"=”20.20.20.20” “secondary”=”30.30.30.30”
"SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
Radius Server Failed Over from Primary [{primary}] to Secondary
[{secondary}] on Radius Proxy [{radProxyIp}] on {produce.short.name}
[{SZMgmtIp}]
Description
This alarm is triggered when the secondary RADIUS server is available
after the primary server becomes zombie or dead.
Recommended Actions No operator action is required.
Authentication fallback to primary
Table 28. Authentication fallback to primary alarm
Alarm
Authentication fallback to primary
Alarm Type
authFallbackToPrimary
Alarm Code
1652
Severity
Major
Aggregation Policy
From the event code 1652 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“mvnoId”=12 “ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”
“srcProcess”=”radiusd” “realm”=
”wlan.mnc080.mcc405.3gppnetwork.org" “radProxyIp”=”7.7.7.7”
“primary"=”20.20.20.20” “secondary”=”30.30.30.30”
"SZMgmtIp"="2.2.2.2"
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
61
Alarm Types
Authentication Alarms
Table 28. Authentication fallback to primary alarm
Displayed on the web
interface
Radius Server Fallback to Primary [{primary}] from Secondary
[{secondary}] on Radius Proxy [{radProxyIp}] on {produce.short.name}
[{SZMgmtIp}]
Description
This alarm is triggered when automatic fallback is enable. Consequently,
the authentication failover to secondary server occurs and the revival
timer for the primary server expires, and the requests falls back to the
primary server.
Recommended Actions No action is required.
AD/LDAP connectivity failure
Table 29. AD/LDAP connectivity failure alarm
Alarm
AD/LDAP connectivity failure
Alarm Type
racADLDAPFail
Alarm Code
1752
Severity
Major
Aggregation Policy
From the event code 1752 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “mvnoId”=12,
“srcProcess”=”RAC”, “authSrvrIp”=“1.1.1.1”, "SZMgmtIp"="2.2.2.2"
“desc”= "Connection to AD/LDAP fails"
Displayed on the web
interface
[{srcProcess}] Connect to AD/LDAP[{authSrvrIp}] fails from
{produce.short.name}[{SZMgmtIp}]
Description
This alarm is triggered when RADIUS server fails to connect with AD/
LDAP server.
Recommended Actions • Check whether AD/LDAP server instance is running on the target
machine
• Check whether the AD/LDAP server can be reached from the
controller
• Verify if AD/LDAP server instances are listening on ports 3268 and
389
• Verify if the requests are reaching AD/LDAP servers by any packet
capture tool (tcpdump, wireshark)
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
62
Alarm Types
Authentication Alarms
Bind fails with AD/LDAP
Table 30. Bind fails with AD/LDAP alarm
Alarm
Bind fails with AD/LDAP
Alarm Type
racADLDAPBindFail
Alarm Code
1753
Severity
Major
Aggregation Policy
From the event code 1753 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “mvnoId”=12,
“srcProcess”=”RAC”, “authSrvrIp”= “1.1.1.1”, “username”=“testuser’
"SZMgmtIp"="2.2.2.2", “desc”=”Bind to AD/LDAP fails”
Displayed on the web
interface
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “mvnoId”=12,
“srcProcess”=”RAC”, “authSrvrIp”= “1.1.1.1”, “username”=“testuser’
"SZMgmtIp"="2.2.2.2", “desc”=”Bind to AD/LDAP fails”
Description
This alarm is triggered when RADIUS server binding fails to AD/LDAP
server.
Recommended Actions • Verify the base and administrator domain names as configured in the
controller web interface
• Verify the administrator user name and password as configured in the
controller web interface
• Verify whether the configured administrator user name and password
is authenticated by the AD/LDAP servers
Bind success with LDAP, but unable to find clear text
password for the user
Table 31. Bind success with LDAP, but unable to find clear text password for the user alarm
Alarm
Bind success with LDAP, but unable to find clear text password for the
user
Alarm Type
racLDAPFailToFindPassword
Alarm Code
1754
Severity
Major
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
63
Alarm Types
Authentication Alarms
Table 31. Bind success with LDAP, but unable to find clear text password for the user alarm
Aggregation Policy
From the event code 1754 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “mvnoId”=12,
“srcProcess”=”RAC”, “authSrvrIp”=“1.1.1.1”, “username”= “testuser’
"SZMgmtIp"="2.2.2.2", “desc”=”Fail to find password”
Displayed on the web
interface
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “mvnoId”=12
“srcProcess”=”RAC”, “authSrvrIp”=“1.1.1.1”, “username”= “testuser’
"SZMgmtIp"="2.2.2.2", “desc”=”Fail to find password”]
Description
This alarm is triggered when binding is successful with LDAP server
using root credentials but it is unable to retrieve the clear text password
for the user.
Recommended Actions Verify whether the given username and clear text password are
configured in the LDAP server.
RADIUS fails to connect to AD NPS server
Table 32. RADIUS fails to connect to AD NPS server alarm
Alarm
RADIUS fails to connect to AD NPS server
Alarm Type
racADNPSFail
Alarm Code
1755
Severity
Major
Aggregation Policy
From the event code 1755 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “mvnoId”=12
“srcProcess”=”RAC”, “authSrvrIp”=“1.1.1.1”, “username”=“testuser’
"SZMgmtIp"="2.2.2.2", “desc”= ”Fails to connect to AD NPS server”
Displayed on the web
interface
[{srcProcess}] Fails to connect to AD NPS[{authSrvrIp}] from
{produce.short.name} [{SZMgmtIp}
Description
This alarm is triggered RADIUS server fails to connect to AD NPS server.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
64
Alarm Types
Authentication Alarms
Table 32. RADIUS fails to connect to AD NPS server alarm
Recommended Actions • Verify if the configured NPS server instance is up and running
(Network Policy Server)
• Verify if the NPS server instance is communicating on the standard
RADIUS port 1812
• Ensure that Windows server where AD/NPS server is provisioned can
be reached from the controller web interface
RADIUS fails to authenticate with AD NPS server
Table 33. RADIUS fails to authenticate with AD NPS server alarm
Alarm
RADIUS fails to authenticate with AD NPS server
Alarm Type
racADNPSFailToAuthenticate
Alarm Code
1756
Severity
Major
Aggregation Policy
From the event code 1756 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “mvnoId”=12,
“srcProcess”=”RAC”, “authSrvrIp”=“1.1.1.1”, “username”=“testuser’
"SZMgmtIp"="2.2.2.2", “desc”=”Fails to authenticate with AD NPS”
Displayed on the web
interface
[{srcProcess}] Fails to authenticate AD NPS[{authSrvrIp}] on
{produce.short.name}[{SZMgmtIp}] for User[{userName}
Description
This alarm is triggered when RADIUS server fails to authenticate with
AD NPS server.
Recommended Actions • The shared secret for NPS server should be same as that of
administrator password provisioned in the controller web interface for
AD server
• NPS should be configured to accept request (CHAP and MSCHAPv2)
from the controller
• For CHAP authentication to work the AD server should store the
password in reversible encryption format
• Ensure that NPS is registered with AD server
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
65
Alarm Types
Authentication Alarms
NOTE: Refer to Authentication Events.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
66
Alarm Types
Control and Data Plane Interface Alarms
Control and Data Plane Interface Alarms
NOTE: This section is not applicable for vSZ-E.
Following alarm relates to control and data plane.
• GtpManager (DP) disconnected
GtpManager (DP) disconnected
v
Table 34. GtpManager (DP) disconnected alarm
Alarm
GtpManager (DP) disconnected
Alarm Type
lostCnxnToDblade
Alarm Code
1202
Severity
Major
Aggregation Policy
From the event code 1202 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 1201.
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess”=”aut” “realm”=”NA”
“ctrlBladeIp”=”1.1.1.1” "dataBladeIp"="3.3.3.3" "SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
The connectivity between Control plane [{ctrlBladeIp}] and Data plane
[{dataBladeIp}] is lost at {produce.short.name} [{SZMgmtIp}]
Description
This alarm is triggered due to transmission control protocol (TCP)
connection loss or when control plane is unable to complete the
configuration procedure successfully.
Recommended Actions A manual intervention is required. Refer to Control and Data Plane
Interface Events event 1201.
NOTE: Refer to Control and Data Plane Interface Events.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
67
Alarm Types
Cluster Alarms
Cluster Alarms
Following are alarms related to cluster.
• New node failed to join
• Node removal failed
• Node out of service
• Cluster in maintenance state
• Cluster backup failed
• Cluster restore failed
• Cluster upgrade failed
• Cluster application stopped
• Node bond interface down
• Node physical interface down
• Cluster node rebooted
• Cluster node shut down
• Disk usage exceed threshold
• Resync NTP time
• Cluster out of service
• Cluster upload AP firmware failed
• Cluster add AP firmware failed
• Configuration backup failed
• Configuration restore failed
• AP Certificate Expired
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
68
Alarm Types
Cluster Alarms
New node failed to join
Table 35. New node failed to join alarm
Alarm
New node failed to join
Alarm Type
newNodeJoinFailed
Alarm Code
801
Severity
Critical
Aggregation Policy
From the event code 803 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 802.
Attribute
“clusterName”=”xxx”, “nodeName”=”xxx”,
“nodeMac”=” xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
New node [([{nodeName}]) failed to join cluster [{clusterName}]
Description
This alarm is triggered when a node fails to join a cluster session. The
controller web Interface displays the error message.
Recommended Actions When the operation fails, the user can run the join process. If it continues
to fail, please send the complete log files to Ruckus support. Download
the system log file by logging to the controller system. Navigate to
Administration >> Diagnostics >> Application Logs & Status. Possible
causes are:
• The joining node is unable to complete the syncing of data in time.
This could be due to the existing node performing compaction/repair
etc.
• The communication between the nodes may be broken. This could
cause the operation to timeout such as IP address change or due to
other events, which affects the network. Usually, it does not last for
a long period of time.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
69
Alarm Types
Cluster Alarms
Node removal failed
Table 36. Node removal failed alarm
Alarm
Node removal failed
Alarm Type
removeNodeFailed
Alarm Code
802
Severity
Major
Aggregation Policy
From the event code 805 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 804.
Attribute
“clusterName”=”xxx”, “nodeName”=”xxx”,
“nodeMac”=” xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Node [{nodeName}] failed to remove from cluster [{clusterName}].
Description
This alarm is triggered when it is unable to remove a node from the
cluster.
Recommended Actions In general, this alarm should rarely occur. If it occurs, restore to the
previous backup file. Please send the complete log files to Ruckus
support. Download the system log file by logging to the controller
system. Navigate to Administration > Diagnostics > Application Logs &
Status.
Node out of service
Table 37. Node out of service alarm
Alarm
Node out of service
Alarm Type
nodeOutOfService
Alarm Code
803
Severity
Critical
Aggregation Policy
From the event code 806 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 835.
Attribute
“clusterName”=”xxx”, “nodeName”=”xxx”,
“nodeMac”=” xx:xx:xx:xx:xx:xx”
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
70
Alarm Types
Cluster Alarms
Table 37. Node out of service alarm
Displayed on the web
interface
Node [{nodeName}] in cluster [{clusterName}] is out of service.
Reason:[{reason}].
Description
This alarm is triggered when a node is out of service.
Recommended Actions The operator/user needs to check the application/interface state.
Cluster in maintenance state
Table 38. Cluster in maintenance state alarm
Alarm
Cluster in maintenance state
Alarm Type
clusterInMaintenanceState
Alarm Code
804
Severity
Critical
Aggregation Policy
From the event code 807 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 808.
Attribute
“clusterName”=”xxx”
Displayed on the web
interface
Cluster [{clusterName}] is in maintenance state
Description
This alarm is triggered when a cluster is in a maintenance state.
Recommended Actions Possible causes:
• The entire system backup is in process.
• In a two-node cluster, the remove-node process is working.
For any other cause, please send the complete log files to Ruckus
support. Download the system log file by logging to the controller
system. Navigate to Administration > Diagnostics > Application Logs &
Status.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
71
Alarm Types
Cluster Alarms
Cluster backup failed
Table 39. Cluster backup failed alarm
Alarm
Cluster backup failed
Alarm Type
backupClusterFailed
Alarm Code
805
Severity
Major
Aggregation Policy
From the event code 810 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 809.
Attribute
“clusterName”=”xxx”
Displayed on the web
interface
Cluster [{clusterName}] backup failed. Reason:[{reason}].
Description
This alarm is triggered when a cluster backup fails.
Recommended Actions Check the disk usage. Try restoring the communication between nodes
for a few more times. If the backup continues to fail or if you encounter
Python script errors, please send the complete log files to Ruckus
support. Download the system log file by logging to the controller
system. Navigate to Administration > Diagnostics > Application Logs &
Status. Possible causes:
• Insufficient disk space.
• Communication between nodes may be broken.
• Errors due to the underlying Python script.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
72
Alarm Types
Cluster Alarms
Cluster restore failed
Table 40. Cluster restore failed alarm
Alarm
Cluster restore failed
Alarm Type
restoreClusterFailed
Alarm Code
806
Severity
Major
Aggregation Policy
From the event code 812 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 811.
Attribute
“clusterName”=”xxx”
Displayed on the web
interface
Cluster [{clusterName}] restore failed. Reason:[{reason}].
Description
This alarm is triggered when a cluster restore fails.
Recommended Actions Try a few more times. If the backup restore continues failing, please send
the complete log files to Ruckus support. Download the system log file
by logging to the controller system. Navigate to Administration >
Diagnostics > Application Logs & Status.
The possible cause could be that the command for all nodes in the
cluster failed. This could be due to a broken communication link
between the nodes.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
73
Alarm Types
Cluster Alarms
Cluster upgrade failed
Table 41. Cluster upgrade failed alarm
Alarm
Cluster upgrade failed
Alarm Type
upgradeClusterFailed
Alarm Code
807
Severity
Major
Aggregation Policy
From the event code 815 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 814.
Attribute
"clusterName”=”xxx”, “nodeName”=”xxx”,
“nodeMac”=” xx:xx:xx:xx:xx:xx”, “fromVersion”="x.x",
“toVersion”="x.x"
Displayed on the web
interface
Cluster [{clusterName}] could not be upgraded from [{fromVersion}] to
[{toVersion}]. Reason:[{reason}].
Description
This alarm is triggered when a version upgrade of a cluster fails.
Recommended Actions Check the disk usage. Try restoring the communication between nodes
for a few times. If the backup continues to fail or if you encounter Python
script errors, please send the complete log files to Ruckus support.
Download the system log file by logging to the controller system.
Navigate to Administration > Diagnostics > Application Logs & Status.
Possible causes:
• Insufficient disk space
• Communication between nodes might be broken.
• Errors due to the underlying Python script.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
74
Alarm Types
Cluster Alarms
Cluster application stopped
Table 42. Cluster application stopped alarm
Alarm
Cluster application stopped
Alarm Type
clusterAppStop
Alarm Code
808
Severity
Critical
Aggregation Policy
From the event code 816 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 817.
Attribute
“appName”=”xxxx”, “nodeName”=”xxx”, “nodeMac”=”
xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Application [{appName}] on node [{nodeName}] stopped
Description
This alarm is triggered when the application on a node stops.
Recommended Actions This could happen to any application for various reasons. Please send
the complete log files to Ruckus support. Download the system log file
by logging to the controller system. Navigate to Administration >
Diagnostics > Application Logs & Status.
Node bond interface down
Table 43. Node bond interface down alarm
Alarm
Node bond interface down
Alarm Type
nodeBondInterfaceDown
Alarm Code
809
Severity
Major
Aggregation Policy
From the event code 821 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 822.
Attribute
"nodeName”=”xxx”, “nodeMac”=”xxx”, “ifName”=”xxxx”
Displayed on the web
interface
Network interface [{networkInterface||ifName}] on node [{nodeName}]
is down.
Description
This alarm is triggered when the network interface of a node is down.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
75
Alarm Types
Cluster Alarms
Table 43. Node bond interface down alarm
Recommended Actions Check if the network cables of both the physical interfaces are broken.
Alternatively, check if the physical interfaces for this bond interface is
broken. Please send the complete log files to Ruckus support.
Download the system log file by logging to the controller system.
Navigate to Administration > Diagnostics > Application Logs & Status.
Node physical interface down
Table 44. Node physical interface down alarm
Alarm
Node physical interface down
Alarm Type
nodePhyInterfaceDown
Alarm Code
810
Severity
Critical
Aggregation Policy
From the event code 824 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 825.
Attribute
“nodeName”=”xxx”, “nodeMac”=” xx:xx:xx:xx:xx:xx”,
“ifName”=”xxxx”
Displayed on the web
interface
Physical network interface [{networkInterface||ifName}] on node
[{nodeName}] is down.
Description
This alarm is triggered when the physical interface of a node is down.
Recommended Actions Check if the network cables of both the physical interfaces are broken.
Alternatively, check if the physical interfaces for this bond interface is
broken. Please send the complete log files to Ruckus support.
Download the system log file by logging to the controller system.
Navigate to Administration >> Diagnostics >> Application Logs &
Status.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
76
Alarm Types
Cluster Alarms
Cluster node rebooted
Table 45. Cluster node rebooted alarm
Alarm
Cluster node rebooted
Alarm Type
nodeRebooted
Alarm Code
811
Severity
Major
Aggregation Policy
From the event code 826 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
"nodeName”=”xxx”, “nodeMac”=”xxx”
Displayed on the web
interface
Node [{nodeName}] in cluster [{clusterName}] rebooted
Description
This alarm is triggered when the node is rebooted.
Recommended Actions Usually, this occurs due to user actions like manual reboot of a node,
upgrade or restoration of a cluster. Please send the complete log files
to Ruckus support. Download the system log file by logging to the
controller system. Navigate to Administration >> Diagnostics >>
Application Logs & Status.
Cluster node shut down
Table 46. Cluster node shut down alarm
Alarm
Cluster node shut down
Alarm Type
nodeShutdown
Alarm Code
813
Severity
Major
Aggregation Policy
From the event code 828 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 826.
Attribute
"nodeName"="xxx", "nodeMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
Node [{nodeName}] has been shut down
Description
This alarm is triggered when the node shutdowns.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
77
Alarm Types
Cluster Alarms
Table 46. Cluster node shut down alarm
Recommended Actions This usually occurs due to a user action. Please send the complete log
files to Ruckus support. Download the system log file by logging to the
controller system. Navigate to Administration >> Diagnostics >>
Application Logs & Status.
Disk usage exceed threshold
Table 47. Disk usage exceed threshold alarm
Alarm
Disk usage exceed threshold
Alarm Type
diskUsageExceed
Alarm Code
834
Severity
Critical
Aggregation Policy
From the event code 838 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
"nodeName"="xx", "status"="xx"
Displayed on the web
interface
The disk usage of node [{nodeName}] is over {status}%.
Description
This alarm is triggered when the disk usage has reached the threshold
limit.The disk usage percentage can be configured from 60% to 90%.
Recommended Actions It is recommended that the user moves the backup files to the file
transfer protocol (FTP) server and deletes the moved backup files.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
78
Alarm Types
Cluster Alarms
Resync NTP time
Table 48. Resync NTP time alarm
Alarm
Resync NTP time
Alarm Type
resyncNTPTime
Alarm Code
835
Severity
Major
Aggregation Policy
From the event code 837 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
"nodeName"="xx", "reason"="xx", "status"="xx"
Displayed on the web
interface
Node [{nodeName}] resyncs time from [{reason}]. The time difference is
[{status}] seconds.
Description
This alarm is triggered when the cluster time is not synchronized.
Recommended Actions The trigger points of NTP time resync alarm are:
• Change in system time setting in the controller web interface
• Detection of current system time is more than 5 seconds when
compared to the NTP server
• Reboot a node
• Change roles of cluster nodes
If this alarm is not triggered by any of the conditions above, the operator
or user needs to check the current system time to ensure it is accurate.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
79
Alarm Types
Cluster Alarms
Cluster out of service
Table 49. Cluster out of service alarm
Alarm
Cluster out of service
Alarm Type
clusterOutOfService
Alarm Code
843
Severity
Critical
Aggregation Policy
From the event code 843 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 808.
Attribute
"clusterName"="xx"
Displayed on the web
interface
Cluster [{clusterName}] is out of service.
Description
This alarm is triggered when cluster is out of service.
Recommended Actions It is recommended that the operator/user checks the out of service node
to locate the reason.
Cluster upload AP firmware failed
Table 50. Cluster upload AP firmware failed alarm
Alarm
Cluster upload AP firmware failed
Alarm Type
clusterUploadAPFirmwareFailed
Alarm Code
850
Severity
Major
Aggregation Policy
From the event code 850 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 849
Attribute
"clusterName"="xx"
Displayed on the web
interface
Cluster [{clusterName}] upload AP firmware failed.
Description
This alarm is triggered when the cluster upload to AP firmware fails.
Recommended Actions It is recommended that the operator uploads the AP patch.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
80
Alarm Types
Cluster Alarms
Cluster add AP firmware failed
Table 51. Cluster add AP firmware failed alarm
Alarm
Cluster add AP firmware failed
Alarm Type
clusterAddAPFirmwareFailed
Alarm Code
853
Severity
Major
Aggregation Policy
From the event code 853 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 852
Attribute
"clusterName"="xx"
Displayed on the web
interface
Cluster [{clusterName}] add AP firmware failed.
Description
This alarm is triggered when the cluster upload to AP firmware fails.
Recommended Actions It is recommended that the operator applies the AP patch.
Configuration backup failed
Table 52. Configuration backup failed alarm
Alarm
Configuration backup failed
Alarm Type
clusterCfgBackupFailed
Alarm Code
862
Severity
Major
Aggregation Policy
From the event code 862 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 861.
Attribute
"clusterName"="xxx"
Displayed on the web
interface
Cluster [{clusterName}] configuration backup failed.
Description
This alarm is triggered when the configuration backup fails.
Recommended Actions Download the web log file from the controller web interface to check for
errors.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
81
Alarm Types
Cluster Alarms
Configuration restore failed
Table 53. Configuration restore failed alarm
Alarm
Configuration restore failed
Alarm Type
clusterCfgRestoreFailed
Alarm Code
864
Severity
Major
Aggregation Policy
From the event code 864 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 863.
Attribute
"clusterName"="xxx"
Displayed on the web
interface
Cluster [{clusterName}] configuration restore failed.
Description
This alarm is triggered when the cluster restoration fails.
Recommended Actions Download the web log file from the controller web interface to check for
errors.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
82
Alarm Types
Cluster Alarms
AP Certificate Expired
Table 54. AP Certificate Expired alarm
Alarm
AP Certificate Expired
Alarm Type
apCertificateExpire
Alarm Code
865
Severity
Critical
Aggregation Policy
From the event code 865 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 866.
Attribute
"count"="XXX"
Displayed on the web
interface
[{count}] APs need to update their certificates.
Description
This alarm is triggered when the AP certificate is not valid.
Recommended Actions AP certificates need to be refreshed. Navigate to Administration > AP
Certificate Replacement page to verify and follow the certificate refresh
process.
NOTE: Refer to Cluster Events.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
83
Alarm Types
Configuration Alarms
Configuration Alarms
Following are the alarms related to configuration.
• Zone configuration preparation failed
• AP configuration generation failed
• End-of-life AP model detected
Zone configuration preparation failed
Table 55. Zone configuration preparation failed alarm
Alarm
Zone configuration preparation failed
Alarm Type
zoneCfgPrepareFailed
Alarm Code
1021
Severity
Major
Aggregation Policy
From the event code 1021 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
"nodeMac"="50:A7:33:24:E7:90","zoneName"="openZone"
Displayed on the web
interface
Failed to prepare zone [{zoneName}] configuration required by ap
configuration generation
Description
This alarm is triggered when the controller is unable to prepare a zone
configuration required by the AP.
Recommended Actions APs under these zone stay functional but are unable to receive new
settings. Contact Ruckus support to file an error bug along with the log
file.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
84
Alarm Types
Configuration Alarms
AP configuration generation failed
Table 56. AP configuration generation failed alarm
Alarm
AP configuration generation failed
Alarm Type
apCfgGenFailed
Alarm Code
1022
Severity
Major
Aggregation Policy
From the event code 1022 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
"nodeMac"="50:A7:33:24:E7:90","zoneName"="openZone",
"apCfgGenFailedCount"="25"
Displayed on the web
interface
Failed to generate configuration for [{apCfgGenFailedCount}] AP(s)
under zone[{zoneName}]
Description
This alarm is triggered when the controller fails to generate the AP
configuration under a particular zone.
Recommended Actions APs under these zone stay functional but are unable to receive the new
settings. Contact Ruckus support to file an error bug along with the log
file.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
85
Alarm Types
Configuration Alarms
End-of-life AP model detected
Table 57. End-of-life AP model detected alarm
Alarm
End-of-life AP model detected
Alarm Type
cfgGenSkippedDueToEolAp
Alarm Code
1023
Severity
Major
Aggregation Policy
From the event code 1023 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“nodeMac”="50:A7:33:24:E7:90","zoneName"="openZone","model"=
"R300,T300"
Displayed on the web
interface
Detected usage of end-of-life ap model(s)[{model}] while generating
configuration for AP(s) under zone[{zoneName}]
Description
This alarm is triggered when the controller detects the AP model’s endof-life under a certain zone.
Recommended Actions These obsoleted APs occupies licensed AP space. Disconnect these
unsupported AP models from the given zone by:
• Reset the APs to a factory setting using the AP command line
Delete these APs through the controller Web Interface >
Configuration AP List
NOTE: Refer to Configuration Events.
show upgrade-state
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
86
Alarm Types
Data Plane Alarms
Data Plane Alarms
Following are the alarms related to data plane.
• Data plane configuration update failed
• Data plane disconnected
• Data plane physical interface down
• Data plane process restarted
• Data plane license is not enough
• Data plane upgrade failed
Data plane configuration update failed
Table 58. Data plane configuration update failed alarm
Alarm
Data plane configuration update failed
Alarm Type
dpConfUpdateFailed
Alarm Code
501
Severity
Major
Aggregation Policy
From the event code 505 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 504
Attribute
“dpKey”=”xx:xx:xx:xx:xx:xx”, “configID”=” 123456781234567”
Displayed on the web
interface
Data plane [{dpName||dpKey}] failed to update to configuration
[{configID}].
Description
This alarm is triggered when the data plane configuration update fails
since it was unable to transfer the configuration update from the control
plane to the data plane.
Recommended Actions Check the data plane configuration and the CPU utilization of the control
plane. The possible cause could be of the server being busy at that
particular moment. Check to see if the event is persistent.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
87
Alarm Types
Data Plane Alarms
Data plane disconnected
Table 59. Data plane disconnected alarm
Alarm
Data plane disconnected
Alarm Type
dpDisconnected
Alarm Code
503
Severity
Critical
Aggregation Policy
From the event code 513 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 512.
Attribute
“dpKey”=”xx:xx:xx:xx:xx:xx”, “wsgIP"=”xxx.xxx.xxx.xxx”
Displayed on the web
interface
Data plane [{dpName||dpKey}] disconnected from
{produce.short.name} [{cpName||wsgIP}]
Description
This alarm is triggered when the data plane gets disconnected from the
controller since it fails to update the status to the control plane.
Recommended Actions Check if the communicator is still alive and if the cluster interface is
working.
Data plane physical interface down
Table 60. Data plane physical interface down alarm
Alarm
Data plane physical interface down
Alarm Type
dpPhyInterfaceDown
Alarm Code
504
Severity
Critical
Aggregation Policy
From the event code 514 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 515.
Attribute
“portID”=”xx”, “dpKey”=”xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Network link of port [{portID}] on data plane [{dpName||dpKey}] is down
Description
This alarm is triggered when the physical interface link of the data plane
is down due to the fiber cable connection.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
88
Alarm Types
Data Plane Alarms
Table 60. Data plane physical interface down alarm
Recommended Actions Check if the fiber cable between the data plane and the switch is firmly
connected.
Data plane process restarted
Table 61. Data plane process restarted alarm
Alarm
Data plane process restarted
Alarm Type
dpProcessRestart
Alarm Code
520
Severity
Major
Aggregation Policy
From the event code 520 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
dpKey="xx:xx:xx:xx:xx:xx", processName="xxxx"
Displayed on the web
interface
[{processName}] process got re-started on data plane
[{dpName&&dpKey}]
Description
This alarm is triggered when a process in data plane restarts since it fails
to pass the health check.
Recommended Actions No action required.
Data plane license is not enough
NOTE: Alarm 538 is applicable only for vSZ-E
Table 62. Data plane license is not enough alarm
Alarm
Data plane license is not enough
Alarm Type
dpLicenseInsufficient
Alarm Code
538
Severity
Major
Aggregation Policy
From the event code 538 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
"count"=
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
89
Alarm Types
Data Plane Alarms
Table 62. Data plane license is not enough alarm
Displayed on the web
interface
DP license is not enough, [{count}] instance of DP will be deleted.
Description
This alarm is triggered when the number of data plane licenses are
insufficient.
Recommended Actions Check if the number of data plane licenses has exceeded the limit. You
would need to purchase additional licenses, in case of insufficient
licenses and synchronize the licenses.
Data plane upgrade failed
NOTE: Alarm 553 is applicable only for vSZ-E
Table 63. Data plane upgrade failed alarm
Alarm
Data plane upgrade failed
Alarm Type
dpLicenseInsufficient
Alarm Code
553
Severity
Major
Aggregation Policy
From the event code 553 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“dpKey”=“xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Data plane [{dpName&&dpKey}] failed to upgrade.
Description
This alarm is triggered when the data plane upgrade fails.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
90
Alarm Types
Data Plane Alarms
Table 63. Data plane upgrade failed alarm
Recommended Actions There are several possible reasons to trigger alarm 553. The operator
has to ensure the accuracy of network connectivity and version
availability. For advanced process, check the debug log for reason of
upgrade failure. Note: Debug file includes the upgrade log file. The
operator can get the debug log from vSZ web interface or through vSZD CLI.
The operator can use the following vSZ-D CLI commands to:
• View the previous upgrade status and reason in case of a failure ruckus# show upgrade-state / ruckus# show upgradehistory
• Save the debug file for viewing - ruckus(debug)# save-log
• Check the connection status between vSZ and vSZ-D ruckus# show status
• Check the current vSZ-D software version ruckus# show version
Note: Refer to the vSZ-D CLI Reference Guide for details on the CLI
commands mentioned above.
NOTE: Refer to Data Plane Events.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
91
Alarm Types
IPMI Alarms
IPMI Alarms
NOTE: This section is not applicable for vSZ-E.
Following are the alarms related to IPMIs.
• ipmiThempBB
• ipmiThempP
• ipmiFan
• ipmiFanStatus
ipmiThempBB
Table 64. ipmiThempBB alarm
Alarm
ipmiThempBB
Alarm Type
ipmiThempBB
Alarm Code
902
Severity
Major
Aggregation Policy
From the event code 902 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 927.
Attribute
"id"="x", "status"="xxxxx", "nodeMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
Baseboard temperature [{status}] on control plane [{nodeMac}]
Description
This alarm is triggered due to the increase/decrease of the baseboard
temperature status of the control plane. Baseboard threshold
temperatures are in the range of 100 Celsius to 610 Celsius. The default
threshold is 610C.
Recommended Actions Check the fan module. Decrease the ambient temperature if the fan
module is working.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
92
Alarm Types
IPMI Alarms
ipmiThempP
Table 65. ipmiThempP alarm
Alarm
ipmiThempP
Alarm Type
ipmiThempP
Alarm Code
907
Severity
Major
Aggregation Policy
From the event code 907 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 932.
Attribute
"id"="x", "status"="xxxxx", "nodeMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
Processor [{id}] temperature [{status}] on control plane [{nodeMac}]
Description
This alarm is triggered when the reading surpasses threshold value is
<= 550 Celsius. The default threshold is 550C.
Recommended Actions Check and replace the CPU fan module if required. Decrease the
ambient temperature if the fan module is working.
ipmiFan
Table 66. ipmiFan alarm
Alarm
ipmiFan
Alarm Type
ipmiFan
Alarm Code
909
Severity
Major
Aggregation Policy
From the event code 909 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 934.
Attribute
"id"="x", "status"="xxxxx", "nodeMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
System fan [{id}] module [{status}] on control plane [{nodeMac}]
Description
This alarm is triggered when the control plane’s fan module status is
shown.
Recommended Actions Replace the fan module.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
93
Alarm Types
IPMI Alarms
ipmiFanStatus
Table 67. ipmiFanStatus alarm
Alarm
ipmiFanStatus
Alarm Type
ipmiFanStatus
Alarm Code
912
Severity
Major
Aggregation Policy
From the event code 912 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 937.
Attribute
"id"="x", "status"="xxxxx", "nodeMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
Fan module [{id}] [{status}] on control plane [{nodeMac}]
Description
This alarm is triggered when the control plane’s fan module shows the
status as not working.
Recommended Actions Replace the fan module.
NOTE: Refer to IPMI Events.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
94
Alarm Types
Licensing Interface Alarms
Licensing Interface Alarms
The following are the alarms related to licensing.
• License going to expire
• Insufficient license capacity
License going to expire
Table 68. License going to expire alarm
Alarm
License going to expire
Alarm Type
licenseGoingToExpire
Alarm Code
1255
Severity
Major
Aggregation Policy
From the event code 1255 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“nodeName”=“xxx”, “licenseType”=“ xxx”
Displayed on the web
interface
The [{licenseType}] on node [{nodeName}] will expire on
[{associationTime}].
Description
This alarm is triggered when the validity of the license is going to expire.
Recommended Actions Check the validity of licenses. You would need to purchase additional
licenses if validity expires.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
95
Alarm Types
Licensing Interface Alarms
Insufficient license capacity
Table 69. Insufficient license capacity alarm
Alarm
Insufficient license capacity
Alarm Type
apConnectionTerminatedDueToInsufficientLicense
Alarm Code
1256
Severity
Major
Aggregation Policy
From the event code 1256 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
"licenseType”=“ xxx”
Displayed on the web
interface
Insufficient [{licenseType}] license is detected and it will cause existing
AP connections to terminate.
Description
This alarm is triggered when connected APs are rejected due to
insufficient licenses.
Recommended Actions Check the number of licenses. You would need to purchase additional
licenses due to insufficient number of licenses.
NOTE: Refer to Licensing Interface Events.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
96
Alarm Types
System Alarms
System Alarms
NOTE: {produce.short.name} refers to SZ or vSZ-E.
Following are the alarms with the system log severity.
• No LS responses
• LS authentication failure
• {produce.short.name} failed to connect to LS
• Syslog server unreachable
• Process restart
• Service unavailable
• Keepalive failure
• Resource unavailable
• HIP failed over
No LS responses
Table 70. No LS responses alarm
Alarm
No LS responses
Alarm Type
scgLBSNoResponse
Alarm Code
721
Severity
Major
Aggregation Policy
From the event code 721 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”, “url”=““, “port”=““, “SZMgmtIp”=““
Displayed on the web
interface
{produce.short.name} [{SZMgmtIp}] no response from LS: url=[{url}],
port=[{port}]
Description
This alarm is triggered when the controller does not get a response while
connecting to the location based service.
Recommended Actions Check if the location server is working properly.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
97
Alarm Types
System Alarms
LS authentication failure
Table 71. LS authentication failure alarm
Alarm
LS authentication failure
Alarm Type
scgLBSAuthFailed
Alarm Code
722
Severity
Major
Aggregation Policy
From the event code 722 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”, “url”=““, “port”=““, “SZMgmtIp”=““
Displayed on the web
interface
{produce.short.name} [{SZMgmtIp}] authentication failed: url=[{url}],
port=[{port}]
Description
This alarm is triggered due to the authentication failure on connecting
to the location based service.
Recommended Actions Check the location server password.
{produce.short.name} failed to connect to LS
Table 72. {produce.short.name} failed to connect to LSalarm
Alarm
{produce.short.name} failed to connect to LS
Alarm Type
scgLBSConnectFailed
Alarm Code
724
Severity
Major
Aggregation Policy
From the event code 724 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm is auto cleared with the event code 723.
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”, “url”=““, “port”=““, “SZMgmtIp”=““
Displayed on the web
interface
{produce.short.name} [{SZMgmtIp}] connection failed to LS: url=[{url}],
port=[{port}]
Description
This alarm is triggered when the controller fails to connect to the location
based service.
Recommended Actions Check the location service configuration. Also check the network
connectivity between the controller and location server.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
98
Alarm Types
System Alarms
Syslog server unreachable
Table 73.
Syslog server unreachable alarm
Alarm
Syslog server unreachable
Alarm Type
syslogServerUnreachable
Alarm Code
751
Severity
Major
Aggregation Policy
From the event code 751 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm is auto cleared with the event code 750.
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”,
“syslogServerAddress"="xxx.xxx.xxxx.xxx"
Displayed on the
Syslog server [{syslogServerAddress}] is unreachable on
SmartZone web interface {produce.short.name}.
Description
This alarm is triggered when the syslog server is unreachable.
Recommended Actions Check the network between the controller and the syslog server.
Process restart
Table 74. Process restart alarm
Alarm
Process restart
Alarm Type
processRestart
Alarm Code
1001
Severity
Major
Aggregation Policy
From the event code 1001 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “srcProcess”=”nc”,
“realm”=”NA”, “processName”=”aut”, "
{produce.short.name}MgmtIp"="2.2.2.2"
Displayed on the web
interface
[{processName}] process got re-started on {produce.short.name}
[{SZMgmtIp}]
Description
This alarm is triggered when any process crashes and restarts.
Recommended Actions Download the process log file from the controller web Interface to
understand the cause of the error.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
99
Alarm Types
System Alarms
Service unavailable
Table 75. Service unavailable alarm
Alarm
Service unavailable
Alarm Type
serviceUnavailable
Alarm Code
1002
Severity
Critical
Aggregation Policy
From the event code 1002 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “srcProcess”=”nc”,
“realm”=”NA”, “processName”=”aut”, "
{produce.short.name}MgmtIp"="2.2.2.2"
Displayed on the web
interface
[{processName}] process is not stable on {produce.short.name}
[{SZMgmtIp}]
Description
This alarm is triggered when the process repeatedly restarts and is
unstable.
Recommended Actions A manual intervention is required. Download the process log file from
the controller web Interface to find the cause of the error.
Keepalive failure
Table 76. Keepalive failure alarm
Alarm
Keepalive failure
Alarm Type
keepAliveFailure
Alarm Code
1003
Severity
Major
Aggregation Policy
From the event code 1003 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “srcProcess”=”nc”,
“realm”=”NA”, “processName”=”aut”, "
{produce.short.name}MgmtIp"="2.2.2.2"
Displayed on the web
interface
[{srcProcess}] on Smart Zone [{SZMgmtIp}] restarted [{processName}]
process
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
100
Alarm Types
System Alarms
Table 76. Keepalive failure alarm
Description
This alarm is triggered when the mon/nc restarts the process due to a
keep alive failure.
Recommended Actions Download the process log file from the controller web Interface to locate
the cause of the error.
Resource unavailable
Table 77. Resource unavailable alarm
Alarm
Resource unavailable
Alarm Type
resourceUnavailable
Alarm Code
1006
Severity
Critical
Aggregation Policy
From the event code 1006 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “srcProcess”=“radiusd”,
“realm”=”NA”, ” {produce.short.name}MgmtIp”=“3.3.3.3’,
“cause”=“xx”
Displayed on the web
interface
System resource [{cause}] not available in [{srcProcess}] process at
{produce.short.name} [{SZMgmtIp}]
Description
This alarm is generated due to unavailability of any other system
resource, such as memcached.
Recommended Actions A manual intervention is required. Check the memcached process. Also
check if the br1 interface is running.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
101
Alarm Types
System Alarms
HIP failed over
NOTE: This alarm is not applicable for vSZ-E.
Table 78. HIP failed over alarm
Alarm
HIP failed over
Alarm Type
hipFailover
Alarm Code
1016
Severity
Major
Aggregation Policy
Alarm is raised for every event from event code 1016. A single event
triggers a single alarm.
Attribute
"ctrlBladeMac"="50:A7:33:24:E7:90", "srcProcess"="HIP",
"realm"="NA", "processName"="HIP", "SZMgmtIp"="100.13.0.102"
Displayed on the web
interface
[{srcProcess}] Node transitioned to Active on
{produce.short.name}[{SZMgmtIp}]
Description
This alarm is logged when the standby host identity protocol (HIP)
transits to an active node and is included in control plane identifier of
the newly active HIP.
Recommended Actions A manual intervention is required.
NOTE: Refer to System Events.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
102
Alarm Types
Threshold Alarms
Threshold Alarms
Following are the alarms related to threshold system set.
• CPU threshold exceeded
• Memory threshold exceeded
• Disk usage threshold exceeded
• License threshold exceeded
• Rate limit for TOR surpassed
• The number of users exceeded its limit
• The number of devices exceeded its limit
CPU threshold exceeded
Table 79. CPU threshold exceeded alarm
Alarm
CPU threshold exceeded
Alarm Type
cpuThresholdExceeded
Alarm Code
950
Severity
Critical
Aggregation Policy
From the event code 950 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 953.
Attribute
“nodeName”=”xxx”, “nodeMac”=”xx:xx:xx:xx:xx:xx”, “perc”=”XX”
Displayed on the web
interface
CPU threshold [{perc}%] exceeded on control plane [{nodeName}-C].
Description
This alarm is triggered when the CPU usage exceeds the threshold limit.
The CPU usage percentage threshold can be configured as 60% to
90%.
Recommended Actions Check CPU/memory/disk information for any unexpected value. Keep
monitoring the CPU for higher values than the threshold or set it to only
one peak value. If the CPU value is high, please take a snapshot log,
containing the information and send it to Ruckus Wireless support.
Alternatively, if an application is abnormal, restart the service or restart
the controller. This may resolve the issue.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
103
Alarm Types
Threshold Alarms
Memory threshold exceeded
Table 80. Memory threshold exceeded alarm
Alarm
Memory threshold exceeded
Alarm Type
memoryThresholdExceeded
Alarm Code
951
Severity
Critical
Aggregation Policy
From the event code 951 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 954.
Attribute
“nodeName”=”xxx”, “nodeMac”=”xx:xx:xx:xx:xx:xx”, “perc”=”XX”
Displayed on the web
interface
Memory threshold [{perc}%] exceeded on control plane [{nodeName}C].
Description
This alarm is triggered when the memory usage exceeds the threshold
limit. The disk threshold value for SZ-100 is 85% and 90% for vSZ-E.
Recommended Actions Check CPU/memory/disk information for any unexpected value. Keep
monitoring the CPU for higher values than the threshold or set it to only
one peak value. If the CPU value is high, please take a snapshot log,
containing the information and send it to Ruckus Wireless support.
Alternatively, if an application is abnormal, restart the service or restart
the controller. This may resolve the issue.
Disk usage threshold exceeded
Table 81. Disk usage threshold exceeded alarm
Alarm
Disk usage threshold exceeded
Alarm Type
diskUsageThresholdExceeded
Alarm Code
952
Severity
Critical
Aggregation Policy
From the event code 952 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 955.
Attribute
“nodeName”=”xxx”, “nodeMac”=”xx:xx:xx:xx:xx:xx”, “perc”=”XX”
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
104
Alarm Types
Threshold Alarms
Table 81. Disk usage threshold exceeded alarm
Displayed on the web
interface
Disk usage threshold [{perc}%] exceeded on control plane
[{nodeName}-C].
Description
This alarm is triggered when the disk usage exceeds the threshold limit.
The disk threshold value is 80%.
Recommended Actions Check the backup files for disk usage. Each backup file may occupy a
large disk space based on the database size. If there are multiple backup
files/versions in the controller, it is recommended to delete the older
backup files to free disk usage. If the problem persists, please take a
screen shot and send it to Ruckus Wireless support.
License threshold exceeded
Table 82. License threshold exceeded alarm
Alarm
License threshold exceeded
Alarm Type
licenseThresholdExceeded
Alarm Code
960
Severity
Critical 90%
Major 80%
Aggregation Policy
From the event code 960 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
“perc”=”xxx”, "nodeMac"="xx:xx:xx:xx:xx:xx”, "nodeName"="box1",
"licenseType"="SG00"
Displayed on the web
interface
[{licenseType}] limit reached at [{perc}%].
Description
This alarm is triggered when maximum number of licenses is utilized.
Recommended Actions Check the license purchase and usage numbers. Alternatively, you
would need to buy new licenses.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
105
Alarm Types
Threshold Alarms
Rate limit for TOR surpassed
Table 83. Rate limit for TOR surpassed alarm
Alarm
Rate limit for TOR surpassed
Alarm Type
rateLimitMORSurpassed
Alarm Code
1302
Severity
Critical
Aggregation Policy
From the event code 1302 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 1301.
Attribute
"mvnoId”=”12”, “wlanId”=”1”, “zoneId”=”10”,
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “srcProcess”=”radiusd”,
“UserName”=abc@xyz.com, “realm”=”wlan.3gppnetwor"
"SZMgmtIp"="2.2.2.2", “aaaSrvrIp”=”1.1.1.1”
“AAAServerType”=”Auth/Acct”, “ueMacAddr”=”aa:bb:cc:gg:hh:ii”
“MOR”=1000, “THRESHOLD”=”500”, “TOR”=”501”
Displayed on the web
interface
Maximum Outstanding Requests(MOR) surpassed for AAA Server
[{aaaSrvrIp}] and ServerType [{AAAServerType}]. Dropping requests to
be proxied to AAA.
Description
This alarm is triggered when maximum outstanding requests (MOR) is
surpassed.
Recommended Actions Download the SM log file from the controller web Interface to check the
error cause.
The number of users exceeded its limit
Table 84. The number of users exceeded its limit
Alarm
The number of users exceeded its limit
Alarm Type
tooManyUsers
Alarm Code
7003
Severity
Major
Aggregation Policy
From the event code 7001 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
This alarm has no attributes.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
106
Alarm Types
Threshold Alarms
Table 84. The number of users exceeded its limit
Displayed on the web
interface
The number of users exceeds the specified limit
Description
This alarm is triggered when the number of users exceeds the specified
limit.
Recommended Actions No action is required.
The number of devices exceeded its limit
Table 85. The number of devices exceeded its limit alarm
Alarm
The number of devices exceeded its limit
Alarm Type
tooManyDevices
Alarm Code
7004
Severity
Major
Aggregation Policy
From the event code 7002 an alarm is raised for every event. A single
event triggers a single alarm.
Attribute
This alarm has no attributes.
Displayed on the web
interface
Displayed on the web interface. The number of devices exceeded its limit
Description
This alarm is triggered the number of devices exceeds the specified limit.
Recommended Actions No action is required.
NOTE: Refer toThreshold Events.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
107
Alarm Types
Tunnel Alarms - Access Point
Tunnel Alarms - Access Point
Following are the alarms related to tunnel.
• AP softGRE gateway not reachable
• AP is disconnected from secure gateway
• AP secure gateway association failure
AP softGRE gateway not reachable
Table 86. AP softGRE gateway not reachable alarm
Alarm
AP softGRE gateway not reachable
Alarm Type
apSoftGREGatewayNotReachable
Alarm Code
614
Severity
Major
Aggregation Policy
From the event code 614 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 613.
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”,
“softGREGatewayList”=”xxx.xxx.xxx.xxx”
Displayed on the web
interface
AP [{apName&&apMac}] is unable to reach the following gateways:
[{softGREGatewayList}]
Description
This alarm is triggered when AP fails to build a soft GRE tunnel either
on the primary or the secondary GRE.
Recommended Actions Check the primary and secondary soft-GRE gateway.
AP is disconnected from secure gateway
Table 87. AP is disconnected from secure gateway alarm
Alarm
AP is disconnected from secure gateway
Alarm Type
ipsecTunnelDisassociated
Alarm Code
661
Severity
Major
Aggregation Policy
From the event code 661 an alarm is raised for every event. A single
event triggers a single alarm.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
108
Alarm Types
Tunnel Alarms - Access Point
Table 87. AP is disconnected from secure gateway alarm
Attribute
apMac="xx:xx:xx:xx:xx:xx","ipsecGWAddress"="x.x.x.x"
Displayed on the web
interface
AP [{apName&&apMac}] is disconnected from secure gateway
[{ipsecGWAddress}].
Description
This alarm is triggered when the AP is disconnected from the secure
gateway.
Recommended Actions No action required.
AP secure gateway association failure
Table 88. AP secure gateway association failure alarm
Alarm
AP secure gateway association failure
Alarm Type
ipsecTunnelAssociateFailed
Alarm Code
662
Severity
Major
Aggregation Policy
From the event code 662 an alarm is raised for every event. A single
event triggers a single alarm.
Auto Clearance
The alarm code is auto cleared with the event code 660
Attribute
apMac="xx:xx:xx:xx:xx:xx","ipsecGWAddress"="x.x.x.x"
Displayed on the web
interface
AP [{apName&&apMac}] is unable to establish secure gateway with
[{ipsecGWAddress}
Description
This alarm is triggered when the AP is unable to connect with the secure
gateway.
Recommended Actions No action required.
NOTE: Refer toTunnel Events - Access Point (AP) and Tunnel Events - Data Plane
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
109
Events Types
4
This chapter provides information on the following types of events that the controller
generates:
• Accounting Events
• AP Communication Events
• AP LBS Events
• AP Mesh Events
• AP State Change Events
• AP Authentication Events
• AP USB Events
• Authentication Events
• Authorization Events
• Control and Data Plane Interface Events
• Client Events
• Cluster Events
• Configuration Events
• Data Plane Events
• IPMI Events
• Licensing Interface Events
• Session Events
• System Events
• Threshold Events
• Tunnel Events - Access Point (AP)
• Tunnel Events - Data Plane
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
110
Events Types
Accounting Events
Accounting Events
Following are the events related to accounting.
• Accounting server not reachable
• AP accounting response while invalid config
• AP account message drop while no accounting start message
• Unauthorized COA/DM message dropped
Accounting server not reachable
Table 89. Accounting server not reachable event
Event
Accounting server not reachable
Event Type
accSrvrNotReachable
Event Code
1602
Severity
Major
Attribute
“mvnoId”=12 “ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”
“srcProcess”=”radiusd” “realm”=
”wlan.mnc080.mcc405.3gppnetwork.org" “radProxyIp”=”7.7.7.7”
“accSrvrIp"=”30.30.30.30” "SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
Accounting Server [{accSrvrIp}] not reachable from Radius Proxy
[{radProxyIp}] on {produce.short.name} [{SZMgmtIp}].
Description
This event occurs when the controller is unable to connect to either the
primary or secondary accounting server.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
111
Events Types
Accounting Events
AP accounting response while invalid config
Table 90. AP accounting response while invalid config event
Event
AP accounting response while invalid config
Event Type
apAcctRespWhileInvalidConfig
Event Code
1909
Severity
Debug
Attribute
mvnoId"=12 "wlanId"=1,"zoneId"="10",
“ctrlBladeMac"="aa:bb:cc:dd:ee:ff", "srcProcess"="aut"
"realm"="wlan.3gppnetwork.org", “userName”=”abc@xyz.com",
" {produce.short.name}MgmtIp"="2.2.2.2",“apIpAddress”=”10.1.4.11”
Displayed on the web
interface
[{srcProcess}] sending dummy response for Accounting Packet
received from AP [{apIpAddress}] on {produce.short.name}
[{SZMgmtIp}], with username [{userName}]. Configuration is incorrect
in {produce.short.name} to forward received message nor to generate
CDR
Description
This event occurs when the controller sends a dummy response to the
AP accounting message since the configuration in the controller is
incorrect. The event could either occur when forwarding received
messages or when generating call detail records.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
112
Events Types
Accounting Events
AP account message drop while no accounting start
message
Table 91. AP account message drop while no accounting start message event
Event
AP account message drop while no accounting start message
Event Type
apAcctMsgDropNoAcctStartMsg
Event Code
1910
Severity
Critical
Attribute
mvnoId"=12 "wlanId"=1,"zoneId"="10"
"ctrlBladeMac"="aa:bb:cc:dd:ee:ff" "srcProcess"="aut"
"realm"="wlan.3gppnetwork.org", “userName”=”abc@xyz.com","
{produce.short.name}MgmtIp"="2.2.2.2",“apIpAddress”=”10.1.4.11”
Displayed on the web
interface
[{srcProcess}] Dropped Accounting Packet received from AP
[{apIpAddress}] on {produce.short.name} [{SZMgmtIp}], with username
[{userName}]. Accounting session timer expired, stop or interim
message not received, as Account Start not received from NAS/AP
Description
This event occurs when the accounting session timer expires. Stop or
interim messages are not received since the account start is not received
from the network access server (NAS) or access point (AP).
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
113
Events Types
Accounting Events
Unauthorized COA/DM message dropped
Table 92.
Unauthorized COA/DM message dropped event
Event
Unauthorized COA/DM message dropped
Event Type
unauthorizedCoaDmMessageDropped
Event Code
1911
Severity
Critical
Attribute
mvnoId"=12 "wlanId"=1,"zoneId"="10"
"ctrlBladeMac"="aa:bb:cc:dd:ee:ff" "srcProcess"="aut"
"realm"="wlan.3gppnetwork.org" “userName”=”abc@xyz.com",
“radSrvrIp”=”7.7.7.7”,"SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
[{srcProcess}] Dropped CoA/DM Packet received from AAA [{radSrvrIp}]
on {produce.short.name} [{SZMgmtIp}], with username [{userName}].
Received message from unauthorized AAA
Description
This event occurs when the controller receives a change of authorization
(CoA) or dynamic multipoint (DM) messages from an unauthorized AAA
server.
NOTE: Refer to Accounting Alarms.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
114
Events Types
AP Communication Events
AP Communication Events
All events from AP are appended with firmware, model name, zone ID (if there is no
zone ID, the key will not be present) at the end. Following are the events related to
AP communications.
AP discovery succeeded
AP managed
AP rejected
AP firmware updated
AP firmware update failed
Updating AP firmware
Updating AP configuration
AP configuration updated
AP configuration update failed
AP pre-provision model
mismatched
AP swap model mismatched
AP WLAN oversubscribed
AP illegal to change country
code
Rogue AP
SSID-spoofing rogue AP
Mac-spoofing rogue AP
Same-network rogue AP
Ad-hoc network device
Rogue AP disappeared
AP discovery succeeded
Table 93.
AP discovery succeeded event
Event
AP discovery succeeded
Event Type
apDiscoverySuccess
Event Code
101
Severity
Informational
Attribute
"apMac"="xxx.xxx.xxx.xxx,, "wsgIP"="xxx.xxx.xxx.xxx"
Displayed on the web
interface
AP [{apName&&apMac}] sent a discovery request to
{produce.short.name} [{wsgIP}]
Description
This event occurs when the AP sends a discovery request to the
{produce.short.name} successfully.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
115
Events Types
AP Communication Events
AP managed
Table 94. AP managed event
Event
AP managed
Event Type
apStatusManaged
Event Code
103
Severity
Informational
Attribute
"apMac"="xxx.xxx.xxx.xxx", "wsgIP"="xxx.xxx.xxx.xxx"
Displayed on the web
interface
AP [{apName&&apMac}] approved by {produce.short.name} [{wsgIP}].
Description
This event occurs when the AP is approved by the controller.
AP rejected
Table 95. AP rejected event
Event
AP rejected
Event Type
apStatusRejected
Event Code
105
Severity
Minor
Attribute
"apMac"="xxx.xxx.xxx.xxx", "wsgIP"="xxx.xxx.xxx.xxx",
"reason"="xxxxxx"
Displayed on the web
interface
{produce.short.name} [{wsgIP}] rejected AP [{apName&&apMac}]
because of [{reason}].
Description
This event occurs when the AP is rejected by the controller.
Auto Clearance
This event triggers the alarm 101, which is auto cleared by the event
code 103.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
116
Events Types
AP Communication Events
AP firmware updated
Table 96. AP firmware updated event
Event
AP firmware updated
Event Type
apFirmwareUpdated
Event Code
106
Severity
Informational
Attribute
“apMac”=“xxx.xxx.xxx.xxx” , “configID”=“23456781234”,
"toVersion"="3.2.0.0.539", "fromVersion"="3.2.0.0.x"
Displayed on the web
interface
AP [{apName&&apMac}] updated its firmware from [{fromVersion}] to
[{toVersion}].
Description
This event occurs when the AP successfully updates the firmware details
to the controller.
AP firmware update failed
Table 97. AP firmware update failed event
Event
AP firmware update failed
Event Type
apFirmwareUpdateFailed
Event Code
107
Severity
Major
Attribute
“apMac”=“xxx.xxx.xxx.xxx” , “configID”=“23456781234”,
"toVersion"="3.2.0.0.x", "fromVersion"="3.2.0.0.x"
Displayed on the web
interface
AP [{apName&&apMac}] failed to update its firmware from
[{fromVersion}] to [{toVersion}].
Description
This event occurs when the AP fails to update the firmware details to
the controller.
Auto Clearance
This event triggers the alarm 107, which is auto cleared by the event
code 106.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
117
Events Types
AP Communication Events
Updating AP firmware
Table 98. Updating AP firmware event
Event
Updating AP firmware
Event Type
apFirmwareApplying
Event Code
108
Severity
Informational
Attribute
“apMac”=“xxx.xxx.xxx.xxx” , “configID”=“23456781234”,
"toVersion"="3.2.0.0.x", "fromVersion"="3.2.0.0.x"
Displayed on the web
interface
AP [{apName&&apMac}] firmware is being updated from [{fromVersion}]
to [{toVersion}].
Description
This event occurs when AP updates its firmware.
Updating AP configuration
Table 99.
Updating AP configuration event
Event
Updating AP configuration
Event Type
apConfApplying
Event Code
109
Severity
Informational
Attribute
"apMac"="xxx.xxx.xxx.xxx", "configID"="23456781234"
Displayed on the web
interface
AP [{apName&&apMac}] is being updated to new configuration ID
[{configID}]
Description
This event occurs when the AP updates its configuration.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
118
Events Types
AP Communication Events
AP configuration updated
Table 100. AP configuration updated event
Event
AP configuration updated
Event Type
apConfUpdated
Event Code
110
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "configID"="23456781234"
Displayed on the web
interface
AP [{apName&&apMac}] updated to configuration [{configID}]
Description
This event occurs when the AP successfully updates the existing
configuration details to the controller.
AP configuration update failed
Table 101. AP configuration update failed event
Event
AP configuration update failed
Event Type
apConfUpdateFailed
Event Code
111
Severity
Major
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "configID"="23456781234"
Displayed on the web
interface
AP [{apName&&apMac}] failed to update to configuration [{configID}].
Description
This event occurs when the AP fails to update the configuration details
to the controller.
Auto Clearance
This event triggers the alarm 102, which is auto cleared by the event
code 110.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
119
Events Types
AP Communication Events
AP pre-provision model mismatched
Table 102. AP pre-provision model mismatched event
Event
AP pre-provision model mismatched
Event Type
apModelDiffWithPreProvConfig
Event Code
112
Severity
Major
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "wsgIP"="xxx.xxx.xxx.xxx",
"configModel"="xxx.xxx.xxx.xxx" "model"="R700"
Displayed on the web
interface
AP [{apName&&apMac}] model [{model}] is different from per-provision
configuration model [configModel]
Description
This event occurs when the AP model differs from the configuration
model.
AP swap model mismatched
Table 103. AP swap model mismatched event
Event
AP swap model mismatched
Event Type
apModelDiffWithSwapOutAP
Event Code
113
Severity
Major
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "wsgIP"="xxx.xxx.xxx.xxx",
"configModel"="xxx.xxx.xxx.xxx" "model"="R700"
Displayed on the web
interface
AP [{apName&&apMac}] model [{model}] is different from swap
configuration model [{configModel}].
Description
This event occurs when the AP model differs from the swap
configuration model.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
120
Events Types
AP Communication Events
AP WLAN oversubscribed
Table 104. AP WLAN oversubscribed event
Event
AP WLAN oversubscribed
Event Type
apWlanOversubscribed
Event Code
114
Severity
Major
Attribute
"apMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
AP [{apName&&apMac}] does not have enough capacity to deploy all
wlans. Only maximum wlan number of the AP can be deployed
Description
This event occurs when the AP exceeds the maximum capacity for
deploying all WLANs.
AP illegal to change country code
Table 105. AP illegal to change country code event
Event
AP illegal to change country code
Event Type
apIllgalToChangeCountryCode
Event Code
116
Severity
Informational
Attribute
“apMac”=“xxx.xxx.xxx.xxx” , “configID”=“23456781234”
Displayed on the web
interface
AP [{apName&&apMac}] does not support country code change.
Description
This event occurs when attempting to change the country code for an
AP. Changing of country code is not allowed.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
121
Events Types
AP Communication Events
Rogue AP
Table 106. Rogue AP event
Event
Rogue AP
Event Type
genericRogueAPDetected
Event Code
180
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "rogueMac"="xxx.xxx.xxx.xxx",
"ssid"="xxxxxxxxxx", "channel"="xx"
Displayed on the web
interface
Rogue AP[{rogueMac}] with SSID[{ssid}] is detected by
[{apName&&apMac}] on channel[{channel}]
Description
This event occurs when the AP detects a rogue AP.
SSID-spoofing rogue AP
Table 107. SSID-spoofing rogue AP event
Event
SSID-spoofing rogue AP
Event Type
ssid-spoofingRogueAPDetected
Event Code
181
Severity
Warning
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "rogueMac"="xxx.xxx.xxx.xxx",
"ssid"="xxxxxxxxxx", "channel"="xx"
Displayed on the web
interface
Ssid-spoofing rogue [{rogueMac}] with [{ssid}] is detected by
[{apName&&apMac}] on channel [{channel}]
Description
This event occurs when the AP detects a rogue AP with the same service
set identifier (SSID).
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
122
Events Types
AP Communication Events
Mac-spoofing rogue AP
Table 108. Mac-spoofing rogue AP event
Event
Mac-spoofing rogue AP
Event Type
mac-spoofingRogueAPDetected
Event Code
182
Severity
Warning
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "rogueMac"="xxx.xxx.xxx.xxx",
"ssid"="xxxxxxxxxx", "channel"="xx"
Displayed on the web
interface
MAC-spoofing AP [{rogueMac}] with SSID[{ssid}] is detected by
[{apName&&apMac}] on channel[{channel}]
Description
This event occurs when the AP detects a rogue AP having the same
basic service set identifier (BSSID).
Same-network rogue AP
Table 109. Same-network rogue AP event
Event
Same-network rogue AP
Event Type
same-networkRogueAPDetected
Event Code
183
Severity
Warning
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "rogueMac"="xxx.xxx.xxx.xxx",
"ssid"="xxxxxxxxxx", "channel"="xx"
Displayed on the web
interface
Same-network AP [{rogueMac}] with SSID[{ssid}] is detected by
[{apName&&apMac}] on channel[{channel}]
Description
This event occurs when the AP detects a rogue AP which has the same
network.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
123
Events Types
AP Communication Events
Ad-hoc network device
Table 110. Ad-hoc network device event
Event
Ad-hoc network device
Event Type
ad-hoc-networkRogueAPDetecte
Event Code
184
Severity
Warning
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "rogueMac"="xxx.xxx.xxx.xxx",
"ssid"="xxxxxxxxxx", "channel"="xx"
Displayed on the web
interface
Ad-hoc network rogue {rogueMac} with {ssid} is detected by
[{apName&&apMac}] on channel [{channel}]
Description
This event occurs when the AP detects a rogue AP which has the same
ad-hoc network.
Rogue AP disappeared
Table 111. Rogue AP disappeared event
Event
Rogue AP disappeared
Event Type
maliciousRogueAPTimeout
Event Code
185
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "rogueMac"="xxx.xxx.xxx.xxx"
Displayed on the web
interface
Malicious rogue [{rogueMac}] detected by [{apName&&apMac}] goes
away.
Description
This event occurs when the rogue AP disappears.
NOTE: Refer to AP Communication Alarms.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
124
Events Types
AP LBS Events
AP LBS Events
Following are the events related to AP Location Based Service.
• No LS responses
• LS authentication failure
• AP connected to LS
• AP failed to connect to LS
• AP started location service
• AP stopped location service
• AP received passive calibration request
• AP received passive footfall request
• AP received unrecognized request
No LS responses
Table 112. No LS responses event
Event
No LS responses
Event Type
apLBSNoResponses
Event Code
701
Severity
Major
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", “url”=””, “port”=””
Displayed on the web
interface
AP [{apName&&apMac}] no response from LS: url= [{url}], port= [{port}]
Description
This event occurs when the AP does not get a response when trying to
connect to the location based service.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
125
Events Types
AP LBS Events
LS authentication failure
Table 113. LS authentication failure event
Event
LS authentication failure
Event Type
apLBSAuthFailed
Event Code
702
Severity
Major
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", “url”=””, “port”=””
Displayed on the web
interface
AP [{apName&&apMac}] LBS authentication failed: url= [{url}], port=
[{port}]
Description
This event occurs due to the authentication failure on connecting to the
location based service.
AP connected to LS
Table 114. AP connected to LS event
Event
AP connected to LS
Event Type
apLBSConnectSuccess
Event Code
703
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", “url”=””, “port”=””
Displayed on the web
interface
AP [{apName&&apMac}] connected to LS: url= [{url}], port= [{port}]
Description
This event occurs when the AP successfully connects to the location
based service.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
126
Events Types
AP LBS Events
AP failed to connect to LS
Table 115. AP failed to connect to LS event
Event
AP failed to connect to LS
Event Type
apLBSConnectFailed
Event Code
704
Severity
Major
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", “url”=””, “port”=””
Displayed on the web
interface
AP [{apName&&apMac}] connection failed to LS: url= [{url}], port=
[{port}]
Description
This event occurs when the AP fails to connect to the location based
service.
Auto Clearance
This event triggers the alarm 704, which is auto cleared by the event
code 703.
AP started location service
Table 116. AP started location service event
Event
AP started location service
Event Type
apLBSStartLocationService
Event Code
705
Severity
Informational
Attribute
"apMac”=”xx:xx:xx:xx:xx:xx”, "venue"=""
Displayed on the web
interface
AP [{apName&&apMac}] Start Ruckus Location Service: venue=
[{venue}], band= [{band}]
Description
This event occurs when the AP starts to get the location data.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
127
Events Types
AP LBS Events
AP stopped location service
Table 117. AP stopped location service event
Event
AP stopped location service
Event Type
apLBSStopLocationService
Event Code
706
Severity
Informational
Attribute
"apMac”=”xx:xx:xx:xx:xx:xx”, "venue"=""
Displayed on the web
interface
AP [{apName&&apMac}] Stop Ruckus Location Service: venue=
[{venue}], band= [{band}]
Description
This event occurs when the AP stops getting the location data.
AP received passive calibration request
Table 118. AP received passive calibration request event
Event
AP received passive calibration request
Event Type
apLBSRcvdPassiveCalReq
Event Code
707
Severity
Informational
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”, “venue”=””, “interval”=””, “duration, =””,
“band”=””, “count”=””
Displayed on the web
interface
AP [{apName&&apMac}] received Passive Calibration Request:
interval=[{interval}s], duration=[{duration}m], band=[{band}]
Description
This event occurs when the AP receives the passive calibration request.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
128
Events Types
AP LBS Events
AP received passive footfall request
Table 119. AP received passive footfall request event
Event
AP received passive footfall request
Event Type
apLBSRcvdPassiveFFReq
Event Code
708
Severity
Informational
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”, “venue”=””, “interval”=””, “duration, =””,
“band”=””
Displayed on the web
interface
AP [{apName&&apMac}] received Passive Footfall Request:
interval=[{interval}s], duration=[{duration}m], band=[{band}]]
Description
This event occurs when the AP receives the passive footfall request.
AP received unrecognized request
Table 120. AP received unrecognized request event
Event
AP received unrecognized request
Event Type
apLBSRcvdUnrecognizedRequest
Event Code
709
Severity
Warning
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”, “type”=””, “length”=””, "
{produce.short.name}MgmtIp"=""
Displayed on the web
interface
AP [{apName&&apMac}] received Unrecognized Request: type =
[{type}], length = [{length}]
Description
This event occurs when the AP receives an unrecognized request.
NOTE: Refer to AP LBS Alarms.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
129
Events Types
AP Mesh Events
AP Mesh Events
Following are the events related to access point (AP) mesh.
EMAP downlink connected to EMAP downlink disconnected from EMAP uplink connected to
MAP
MAP
MAP
EMAP uplink disconnected
from MAP
MAP disconnected
MAP downlink connected
MAP downlink connected to
EMAP
MAP downlink disconnected from RAP downlink connected to
EMAP
MAP
MAP uplink connected to
EMAP
MAP uplink disconnected from
EMAP
MAP uplink connected to RAP
MAP uplink connected to
MAP
Mesh state updated to MAP
Mesh state updated to MAP
no channel
Mesh state updated to RAP
Mesh state update to RAP no
channel
MAP downlink connected to
MAP
MAP downlink disconnected RAP downlink disconnected from
from MAP
MAP
EMAP downlink connected to MAP
Table 121. EMAP downlink connected to MAP event
Event
EMAP downlink connected to MAP
Event Type
emapDlinkConnectWithMap
Event Code
405
Severity
Informational
Attribute
"emapMac"="xx:xx:xx:xx:xx:xx", "mapMac="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
eMAP [{apName&&apMac}] accepted connection from MAP
[{mapName&&mapMac}].
Description
This event occurs when the mobile application part (MAP) to Ethernet
Mesh AP (EMAP) connection is successful.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
130
Events Types
AP Mesh Events
EMAP downlink disconnected from MAP
Table 122. EMAP downlink disconnected from MAP event
Event
EMAP downlink disconnected from MAP
Event Type
emapDlinkDisconnectWithMap
Event Code
406
Severity
Informational
Attribute
"emapMac"="xx:xx:xx:xx:xx:xx", "mapMac="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
MAP [{mapName&&mapMac}] disconnects from eMAP
[{apName&&apMac}].
Description
This event occurs when the MAP disconnects from EMAP.
EMAP uplink connected to MAP
Table 123. EMAP uplink connected to MAP event
Event
EMAP uplink connected to MAP
Event Type
emapUlinkConnectWithMap
Event Code
407
Severity
Informational
Attribute
"emapMac"="xx:xx:xx:xx:xx:xx","mapMac="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
eMAP [{apName&&apMac}] uplink connected to MAP
[{mapName&&mapMac}]
Description
This event occurs when the EMAP uplink connection to MAP is
successful.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
131
Events Types
AP Mesh Events
EMAP uplink disconnected from MAP
Table 124. EMAP uplink disconnected from MAP event
Event
EMAP uplink disconnected from MAP
Event Type
emapUlinkDisconnectWithMap
Event Code
408
Severity
Informational
Attribute
"emapMac"="xx:xx:xx:xx:xx:xx", "mapMac="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
eMAP [{apName&&apMac}] uplink disconnected from MAP
[{mapName&&mapMac}]
Description
This event occurs when the EMAP uplink disconnects from MAP.
MAP disconnected
Table 125. MAP disconnected event
Event
MAP disconnected
Event Type
mapDisconnected
Event Code
411
Severity
Informational
Attribute
"emapMac"="xx:xx:xx:xx:xx:xx", "mapMac="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
MAP [{xapName&&xapMac}] disconnected from AP
[{apName&&apMac}]
Description
This event occurs when the MAP disconnects from the AP.
MAP downlink connected
Table 126. MAP downlink connected event
Event
MAP downlink connected
Event Type
mapDlinkConnected
Event Code
412
Severity
Informational
Attribute
"mapMac="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
MAP [{apName&&apMac}] downlink connected
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
132
Events Types
AP Mesh Events
Table 126. MAP downlink connected event
Description
This event occurs when the MAP downlink connects to the AP.
MAP downlink connected to EMAP
Table 127. MAP downlink connected to EMAP event
Event
MAP downlink connected to EMAP
Event Type
mapDlinkConnectWitheMap
Event Code
413
Severity
Informational
Attribute
"mapMac"="xx:xx:xx:xx:xx:xx", "emapMac="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
MAP [{apName&&apMac}] accepted connection from eMAP
[{emapName&&emapMac}]
Description
This event occurs when the MAP accepts the connection from Ethernet
Mesh AP.
MAP downlink disconnected from EMAP
Table 128. MAP downlink disconnected from EMAP event
Event
MAP downlink disconnected from EMAP
Event Type
mapDlinkDisconnectWitheMap
Event Code
414
Severity
Informational
Attribute
"mapMac"="xx:xx:xx:xx:xx:xx", "emapMac="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
eMAP [{emapName&&emapMac}] disconnected from MAP
[{apName&&apMac}]
Description
This event occurs when the Ethernet Mesh AP disconnects from MAP.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
133
Events Types
AP Mesh Events
RAP downlink connected to MAP
Table 129. RAP downlink connected to MAP event
Event
RAP downlink connected to MAP
Event Type
rmapDlinkConnectWithMap
Event Code
416
Severity
Informational
Attribute
"rapMac"="xx:xx:xx:xx:xx:xx", "mapMac="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
RAP [{apName&&apMac}] accepted connection from MAP
[{mapName&&mapMac}]
Description
This event occurs when the root access point (RAP) accepts the MAP
connection.
MAP uplink connected to EMAP
Table 130. MAP uplink connected to EMAP event
Event
MAP uplink connected to EMAP
Event Type
mapUlinkConnectToeMap
Event Code
417
Severity
Informational
Attribute
"mapMac"="xx:xx:xx:xx:xx:xx", "emapMac="xx:xx:xx:xx:xx:xx",
"rssi"="xx", "meshDepth"="x"
Displayed on the web
interface
MAP [{apName&&apMac}] connected to eMAP
[{emapName&&emapMac}] with RSSI [{rssi}] across [{meshDepth}] links
Description
This event occurs when MAP successfully connects to EMAP with
received signal strength indicator (RSSI) (across links).
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
134
Events Types
AP Mesh Events
MAP uplink disconnected from EMAP
Table 131. MAP uplink disconnected from EMAP event
Event
MAP uplink disconnected from EMAP
Event Type
mapUlinkDisconnectToeMap
Event Code
418
Severity
Informational
Attribute
"mapMac"="xx:xx:xx:xx:xx:xx", "emapMac="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
MAP [{apName&&apMac}] disconnected from eMAP
[{emapName&&emapMac}]
Description
This event occurs when the MAP disconnects from EMAP.
MAP uplink connected to RAP
Table 132. MAP uplink connected to RAP event
Event
MAP uplink connected to RAP
Event Type
mapUlinkConnectToRap
Event Code
419
Severity
Informational
Attribute
"mapMac"="xx:xx:xx:xx:xx:xx", "rootMac="xx:xx:xx:xx:xx:xx",
"rssi"="xx", "meshDepth"="x"
Displayed on the web
interface
MAP [{apName&&apMac}] connected to RAP [{rootName&&rootMac}]
with RSSI [{rssi}] across [{meshDepth}] links
Description
This event occurs when the MAP connects to RAP with RSSI (across
links).
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
135
Events Types
AP Mesh Events
MAP uplink connected to MAP
Table 133. MAP uplink connected to MAP event
Event
MAP uplink connected to MAP
Event Type
mapUlinkConnectToMap
Event Code
420
Severity
Informational
Attribute
"mapMac"="xx:xx:xx:xx:xx:xx", "secondMapMac="xx:xx:xx:xx:xx:xx",
"rssi"="xx", "meshDepth"="x"
Displayed on the web
interface
MAP [{apName&&apMac}] connected to MAP
[{secondMapName&&secondMapMac}] with RSSI [{rssi}] across
[{meshDepth}] links
Description
This event occurs when the MAP connects to a second MAP with RSSI
(across links).
Mesh state updated to MAP
Table 134. Mesh state updated to MAP event
Event
Mesh state updated to MAP
Event Type
meshStateUpdateToMap
Event Code
421
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "newState"="xx",,
"mapMac"="xx:xx:xx:xx:xx:xx", "numHop"="x", "channel"="xx",
"downlinkState"="xx", "radio"
Displayed on the web
interface
AP [{apName&&apMac}] state set to [{newState}] uplinks to
[{mapName&&mapMac}] across [{numHop}] hops on channel
[{channel}] at [{radio}] with downlink [{downlinkState}]
Description
This event occurs when the AP is set to MAP uplinks across hops on
channel radio (with downlink).
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
136
Events Types
AP Mesh Events
Mesh state updated to MAP no channel
Table 135. Mesh state updated to MAP no channel event
Event
Mesh state updated to MAP no channel
Event Type
meshStateUpdateToMapNoChannel
Event Code
422
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx",
"newState"="xx",,"mapMac"="xx:xx:xx:xx:xx:xx", "numHop"="x”,
"downlinkState"="xx"
Displayed on the web
interface
AP [{apName&&apMac}] state set to [{newState}] uplinks to
[{mapName&&mapMac}] across [{numHop}] hops with downlink
[{downlinkState}]
Description
This event occurs when the AP is set to MAP links across hops (with
downlink).
Mesh state updated to RAP
Table 136. Mesh state updated to RAP event
Event
Mesh state updated to RAP
Event Type
meshStateUpdateToRap
Event Code
423
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "newState"="xx", "channel"="xx",
"downlinkState"="xx", "radio"
Displayed on the web
interface
AP [{apName&&apMac}] state set to [{newState}] on channel [{channel}]
at [{radio}] with downlink [{downlinkState}]
Description
This event occurs when the AP is set to channel radio (with downlink).
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
137
Events Types
AP Mesh Events
Mesh state update to RAP no channel
Table 137. Mesh state update to RAP no channel event
Event
Mesh state update to RAP no channel
Event Type
meshStateUpdateToRapNoChannel
Event Code
424
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "newState"="xx", "downlinkState"="xx"
Displayed on the web
interface
AP [{apName&&apMac}] state set to [{newState}] with downlink
[{downlinkState}]
Description
This event occurs when the AP is set to downlink.
MAP downlink connected to MAP
Table 138. MAP downlink connected to MAP event
Event
MAP downlink connected to MAP
Event Type
mapDlinkConnectWithMap
Event Code
425
Severity
Informational
Attribute
"mapMac"=" xx:xx:xx:xx:xx:xx", "apMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
MAP [{apName&&apMac}] accepted connection from MAP
[{mapName&&mapMac}]
Description
This event occurs when the MAP accepts a connection from another
MAP.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
138
Events Types
AP Mesh Events
MAP downlink disconnected from MAP
Table 139. MAP downlink disconnected from MAP event
Event
MAP downlink disconnected from MAP
Event Type
mapDlinkDisconnectWithMap
Event Code
426
Severity
Informational
Attribute
"secondMapMac"=" xx:xx:xx:xx:xx:xx", "apMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
MAP [{secondMapName&&secondMapMac}] disconnected from MAP
[{apName&&apMac}]
Description
This event occurs when the MAP disconnects from a second MAP.
RAP downlink disconnected from MAP
Table 140. RAP downlink disconnected from MAP event
Event
RAP downlink disconnected from MAP
Event Type
rapDlinkDisconnectWithMap
Event Code
427
Severity
Informational
Attribute
"secondMapMac"=" xx:xx:xx:xx:xx:xx", "apMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
MAP [{secondMapName&&secondMapMac}] disconnected from RAP
[{apName&&apMac}]
Description
This event occurs when the MAP disconnects from RAP.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
139
Events Types
AP State Change Events
AP State Change Events
Following are the events related to access point state changes.
AP rebooted by user
AP rebooted by system
AP disconnected
AP IP address updated
AP reset to factory default
AP channel updated
AP country code updated
AP channel updated because
AP change control plane
dynamic frequency selection (DFS)
detected a radar
AP connected
AP deleted
AP heartbeat lost
AP tagged as critical
AP cable modem interface down
AP brownout
AP cable modem powercycled by user
AP smart monitor turn off WLAN
AP client load balancing limit
reached
AP client load balancing limit AP WLAN state changed
recovered
AP capacity reached
AP capacity recovered
AP cable modem softrebooted by user
AP cable modem interface up
AP cable modem set to
factory default by user
AP rebooted by user
Table 141. AP rebooted by user event
Event
AP rebooted by user
Event Type
apRebootByUser
Event Code
301
Severity
Informational
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”, "reason"="xxxxx"
Displayed on the web
interface
AP [{apName&&apMac}] rebooted because of [{reason}]
Description
This event occurs when AP reboots.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
140
Events Types
AP State Change Events
AP rebooted by system
Table 142. AP rebooted by system event
Event
AP rebooted by system
Event Type
apRebootBySystem
Event Code
302
Severity
Major
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”, "reason"="xxxxx"
Displayed on the web
interface
AP [{apName&&apMac}] rebooted by the system because of [{reason}]
Description
This event occurs when the system reboots the AP.
AP disconnected
Table 143. AP disconnected event
Event
AP disconnected
Event Type
apConnectionLost (detected on the server)
Event Code
303
Severity
Major
Attribute
“apMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
AP [{apName&&apMac}] disconnected
Description
This event occurs when the AP disconnects from the controller.
Auto Clearance
This event triggers the alarm 303, which is auto cleared by the event
code 312.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
141
Events Types
AP State Change Events
AP IP address updated
Table 144. AP IP address updated event
Event
AP IP address updated
Event Type
apIPChanged
Event Code
304
Severity
Informational
Attribute
“apMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
AP [{apName&&apMac}] reset because of an IP address change
Description
This event occurs when the AP is reset due to a change in the IP address.
AP reset to factory default
Table 145. AP reset to factory default event
Event
AP reset to factory default
Event Type
apFactoryReset
Event Code
305
Severity
Informational
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
AP [{apName&&apMac}] reset to factory default settings
Description
This event occurs when the AP is reset to factory default settings.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
142
Events Types
AP State Change Events
AP channel updated
Table 146. AP channel updated event
Event
AP channel updated
Event Type
apChannelChanged
Event Code
306
Severity
Informational
Attribute
“apMac"="xx:xx:xx:xx:xx:xx", “radio”="xxx", “fromChannel”="xx",
“toChannel”="xx"
Displayed on the web
interface
AP [{apName&&apMac}] detected interference on radio [{radio}] and
has switched from channel [{fromChannel}] to channel [{toChannel}]
Description
This event occurs when the AP detects an interference on the radio and
switches to another channel.
AP country code updated
Table 147. AP country code updated event
Event
AP country code updated
Event Type
apCountryCodeChanged
Event Code
307
Severity
Informational
Attribute
“apMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
AP [{apName&&apMac}] reset because of a country code change
Description
This event occurs when a change in country code causes the AP to
reset.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
143
Events Types
AP State Change Events
AP channel updated because dynamic frequency
selection (DFS) detected a radar
Table 148. AP channel updated because dynamic frequency selection (DFS) detected a radar
event
Event
AP channel updated because dynamic frequency selection (DFS)
detected a radar
Event Type
apDfsRadarEvent
Event Code
308
Severity
Informational
Attribute
“apMac"="xx:xx:xx:xx:xx:xx", “radio”="xxx", “channel”="xx"
Displayed on the web
interface
AP [{apName&&apMac}] detected radar burst on radio [{radio}] and
channel [{channel}] went into non-occupancy period
Description
This event occurs when the AP detects a radar burst on the radio and
the channel moves to a non-occupancy mode.
AP change control plane
Table 149. AP change control plane event
Event
AP change control plane
Event Type
apChangeControlBlade
Event Code
311
Severity
Informational
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”, “oldwsgIP”=”xxx.xxx.xxx.xxx”,
“newwsgIP”=”xxx.xxx.xxx.xxx”
Displayed on the web
interface
AP [{apName&&apMac}] switched from {produce.short.name}
[{oldCpName||oldwsgIP}] to {produce.short.name}
[{cpName||newwsgIP}].
Description
This event occurs when the AP switches from an existing controller
connection to a new connection.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
144
Events Types
AP State Change Events
AP connected
Table 150. AP connected event
Event
AP connected
Event Type
apConnected
Event Code
312
Severity
Informational
Attribute
“apMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
AP [{apName&&apMac}] connected because of [{reason}].
Description
This event occurs when the AP is connected.
AP deleted
Table 151. AP deleted event
Event
AP deleted
Event Type
apDeleted (detected on the server)
Event Code
313
Severity
Major
Attribute
“apMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
AP [{apName&&apMac}] deleted
Description
This event occurs when the AP is deleted on the server side.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
145
Events Types
AP State Change Events
AP heartbeat lost
Table 152. AP heartbeat lost event
Event
AP heartbeat lost
Event Type
apHeartbeatLost
Event Code
314
Severity
Informational
Attribute
“apMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
AP [{apName&&apMac}] heartbeat lost.
Description
This event occurs when the AP is deleted due to a lost heartbeat.
AP tagged as critical
Table 153. AP tagged as critical event
Event
AP tagged as critical
Event Type
apTaggedAsCritical
Event Code
315
Severity
Informational
Attribute
“apMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
AP [{apName&&apMac}] tagged as critical
Description
This event occurs when the AP is tagged critical.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
146
Events Types
AP State Change Events
AP cable modem interface down
Table 154. AP cable modem interface down event
Event
AP cable modem interface down
Event Type
cableModemDown
Event Code
316
Severity
Major
Attribute
“apMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
AP [{apName&&apMac}] cable modem interface is down
Description
This event occurs when the AP cable modem interface is down.
Auto Clearance
This event triggers the alarm 308, which is auto cleared by the event
code 325.
AP brownout
Table 155. AP brownout event
Event
AP brownout
Event Type
apBrownout
Event Code
317
Severity
Major
Attribute
“apMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
AP [{apMac}] voltage deviation on [{cause}] port
Description
This event occurs due to a voltage deviation on the AP port.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
147
Events Types
AP State Change Events
AP cable modem power-cycled by user
Table 156. AP cable modem power-cycled by user event
Event
AP cable modem power-cycled by user
Event Type
cmRebootByUser
Event Code
318
Severity
Informational
Attribute
“apMac"="xx:xx:xx:xx:xx:xx", "reason"="xxxxx"
Displayed on the web
interface
AP [{apName&&apMac}] cable modem power-cycled because of
[{reason}].]
Description
This event occurs when AP cable modem is power-cycled because the
user executes the power-cycle CLI command.
AP smart monitor turn off WLAN
Table 157. AP smart monitor turn off WLAN event
Event
AP smart monitor turn off WLAN
Event Type
smartMonitorTurnOffWLAN
Event Code
319
Severity
Warning
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "turnOffTime"="" , "turnOnTime"=""
Displayed on the web
interface
AP [{apName&&apMac}] turned off WLANs by Smart Monitor on
[{time(turnOffTime)}] and turn on WLANs on [{time(turnOnTime)}]
Description
This event occurs when the smart monitor of the AP turns off the WLAN.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
148
Events Types
AP State Change Events
AP client load balancing limit reached
Table 158. AP client load balancing limit reached event
Event
AP client load balancing limit reached
Event Type
apCLBlimitReached
Event Code
320
Severity
Warning
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "bssid"="xx:xx:xx:xx:xx:xx", "clb-loadlimit"="", "cur-load"="", "min-clbpartner-bssid"="", "min-clbpartnerload"="", "num-clbpartners"="", "low-clbpartners"=""
Displayed on the web
interface
AP [{apname@apMac}] reached client load limit, [{cur-load}] / [{clb-loadlimit}], on WLAN [{ssid}]
Description
This event occurs when the AP reaches the client loading balance (CLB)
limit. The adjacent threshold limit value is 50 for 2.4GHz radio and 43
for 5GHz radio.
AP client load balancing limit recovered
Table 159. AP client load balancing limit recovered event
Event
AP client load balancing limit recovered
Event Type
apCLBlimitRecovered
Event Code
321
Severity
Informational
Attribute
“apMac”=“xx:xx:xx:xx:xx:xx”,”bssid”=“xx:xx:xx:xx:xx:xx”, “clb-loadlimit”=““, “cur-load”=““,
Displayed on the web
interface
AP[{apname@apMac}] recovered from client load limit, [{cur-load}] /
[{clb-load-limit}], on WLAN [{ssid}]
Description
This event occurs when the AP is recovered from client load balance
(CLB) limit. The adjacent threshold limit value is 50 for 2.4GHz radio and
43 for 5GHz radio.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
149
Events Types
AP State Change Events
AP WLAN state changed
Table 160. AP WLAN state changed event
Event
AP WLAN state changed
Event Type
apWLANStateChanged
Event Code
322
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx" "state"="enable | disable" "ssid"="xxxxx"
"apTime"="Tue Apr 22 12:15:00 2014" "reason"="State changed
according to service schedule | State changed by adminstrator"
Displayed on the web
interface
AP [{apName&&apMac}] {state} WLAN [{ssid}] on [{apTime}]. Reason:
[{reason}].
Description
This event occurs when the WLAN state changes as per the service
schedule or as per the service type setting.
AP capacity reached
Table 161. AP capacity reached event
Event
AP capacity reached
Event Type
apCapacityReached
Event Code
323
Severity
Warning
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", “radio”:"",
Displayed on the web
interface
AP [{{apName&&apMac}] radio [{radio}] stopped accepting clients
because the client association threshold has been reached.
Description
This event occurs when an AP rejects a client due to the threshold limit
reached by the client.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
150
Events Types
AP State Change Events
AP capacity recovered
Table 162. AP capacity recovered event
Event
AP capacity recovered
Event Type
apCapacityRecovered
Event Code
324
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", “radio”:"",
Displayed on the web
interface
AP [{{apName&&apMac}] radio [{radio}] started accepting clients again
because current client association is now below the threshold.
Description
This event occurs when the AP starts accepting clients again because
the current client association is below the threshold limit.
AP cable modem interface up
Table 163. AP cable modem interface up event
Event
AP cable modem interface up
Event Type
cableModemUp
Event Code
325
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
AP [{apName&&apMac}] cable modem interface is up.
Description
This event occurs when the AP cable modem interface is up.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
151
Events Types
AP State Change Events
AP cable modem soft-rebooted by user
Table 164. AP cable modem soft-rebooted by user event
Event
AP cable modem soft-rebooted by user
Event Type
cmResetByUser
Event Code
326
Severity
Informational
Attribute
”apMac”=“xx:xx:xx:xx:xx:xx”,”reason”=“xxxxx”
Displayed on the web
interface
AP [{apName&&apMac}] cable modem soft-reboot because of
[{reason}].
Description
This event occurs when the AP cable modem is softly rebooted because
the user executes the soft-reboot CLI command.
AP cable modem set to factory default by user
Table 165. AP cable modem set to factory default by user event
Event
AP cable modem set to factory default by user
Event Type
cmResetFactoryByUser
Event Code
327
Severity
Informational
Attribute
”apMac”=“xx:xx:xx:xx:xx:xx”,”reason”=“xxxxx”
Displayed on the web
interface
AP [{apName&&apMac}] cable modem set to factory default because
of [{reason}].
Description
This event occurs when AP cable modem is reset to factory default
because the user executes the set factory CLI command.
NOTE: Refer to AP State Change Alarms.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
152
Events Types
AP Authentication Events
AP Authentication Events
Following are the events related to AP authentication.
• Radius server reachable
• Radius server unreachable
• LDAP server reachable
• LDAP server unreachable
• AD server reachable
• AD server unreachable
• Wechat ESP authentication server reachable
• WeChat ESP authentication server unreachable
• WeChat ESP authentication server resolvable
• WeChat ESP authentication server unresolvable
• WeChat ESP DNAT server reachable
• WeChat ESP DNAT server unreachable
• WeChat ESP DNAT server resolvable
• WeChat ESP DNAT server unresolvable
Radius server reachable
Table 166. Radius server reachable event
Event
Radius server reachable
Event Type
radiusServerReachable
Event Code
2101
Severity
Informational
Attribute
apMac="xx:xx:xx:xx:xx:xx","ip"="17.0.0.12","fwVersion"="3.2.0.0.x","
model"="ZF7982","zoneUUID"="f77a8816-3049-40cd-848482919275ddc3","zoneName"="Default Zone","apLocation"=""
Displayed on the web
interface
AP [{apName&&apMac}] is able to reach radius server [{ip}] successfully.
Description
This event occurs when the AP is able to reach the RADIUS server
successfully.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
153
Events Types
AP Authentication Events
Radius server unreachable
Table 167. Radius server unreachable event
Event
Radius server unreachable
Event Type
radiusServerUnreachable
Event Code
2102
Severity
Major
Attribute
apMac="xx:xx:xx:xx:xx:xx","ip"="17.0.0.12","fwVersion"="3.2.0.0.x","
model"="ZF7982","zoneUUID"="f77a8816-3049-40cd-848482919275ddc3","zoneName"="Default Zone","apLocation"=""
Displayed on the web
interface
AP [{apName&&apMac}] is unable to reach radius server [{ip}].
Description
This event occurs when AP is unable to reach the RADIUS server.
Auto Clearance
This event triggers the alarm 2102, which is auto cleared by the event
code 2101.
LDAP server reachable
Table 168. LDAP server reachable event
Event
LDAP server reachable
Event Type
ldapServerReachable
Event Code
2121
Severity
Informational
Attribute
apMac="xx:xx:xx:xx:xx:xx","ip"="17.0.0.12","fwVersion"="3.2.0.0.x","
model"="ZF7982","zoneUUID"="f77a8816-3049-40cd-848482919275ddc3","zoneName"="Default Zone","apLocation"=""
Displayed on the web
interface
AP [{apName&&apMac}] is able to reach LDAP server [{ip}] successfully.
Description
This event occurs when the AP is able to reach the lightweight directory
access protocol (LDAP) server successfully.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
154
Events Types
AP Authentication Events
LDAP server unreachable
Table 169. LDAP server unreachable event
Event
LDAP server unreachable
Event Type
ldapServerUnreachable
Event Code
2122
Severity
Major
Attribute
apMac="xx:xx:xx:xx:xx:xx","ip"="17.0.0.12","fwVersion"="3.2.0.0.x","
model"="ZF7982","zoneUUID"="f77a8816-3049-40cd-848482919275ddc3","zoneName"="Default Zone","apLocation"=""
Displayed on the web
interface
AP [{apName&&apMac}] is unable to reach LDAP server [{ip}].
Description
This event occurs when the AP is unable to reach the LDAP server.
Auto Clearance
This event triggers the alarm 2122, which is auto cleared by the event
code 2121.
AD server reachable
Table 170. AD server reachable event
Event
AD server reachable
Event Type
adServerReachable
Event Code
2141
Severity
Informational
Attribute
apMac="xx:xx:xx:xx:xx:xx","ip"="17.0.0.12","fwVersion"="3.2.0.0.x","
model"="ZF7982","zoneUUID"="f77a8816-3049-40cd-848482919275ddc3","zoneName"="Default Zone","apLocation"=""
Displayed on the web
interface
AP [{apName&&apMac}] is able to reach AD server [{ip}].
Description
This event occurs when AP is able to reach the active directory
successfully.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
155
Events Types
AP Authentication Events
AD server unreachable
Table 171. AD server unreachable event
Event
AD server unreachable
Event Type
adServerUnreachable
Event Code
2142
Severity
Major
Attribute
apMac="xx:xx:xx:xx:xx:xx","ip"="17.0.0.12","fwVersion"="3.2.0.0.x","
model"="ZF7982","zoneUUID"="f77a8816-3049-40cd-848482919275ddc3","zoneName"="Default Zone","apLocation"=""
Displayed on the web
interface
AP [{apName&&apMac}] is unable to reach AD server [{ip}].
Description
This event occurs when AP is unable able to reach the active directory.
Auto Clearance
This event triggers the alarm 2142, which is auto cleared by the event
code 2141.
Wechat ESP authentication server reachable
Table 172. Wechat ESP authentication server reachable event
Event
Wechat ESP authentication server reachable
Event Type
espAuthServerReachable
Event Code
2151
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx","ip"="17.0.0.12","profileId"="1","fwVersio
n"="3.2.0.0.x","model"="ZF7982","zoneUUID"="f77a8816-304940cd-8484-82919275ddc3","zoneName"="Default
Zone","apLocation"=""
Displayed on the web
interface
AP [{apName&&apMac}] is able to reach WeChat ESP authentication
server [{ip}] successfully.
Description
This event occurs when AP successfully reaches WeChat ESP
authentication server.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
156
Events Types
AP Authentication Events
WeChat ESP authentication server unreachable
Table 173. WeChat ESP authentication server unreachable event
Event
WeChat ESP authentication server unreachable
Event Type
espAuthServerUnreachable
Event Code
2152
Severity
Major
Attribute
"apMac"="xx:xx:xx:xx:xx:xx","ip"="17.0.0.12","profileId"="1","fwVersio
n"="3.2.0.0.x","model"="ZF7982","zoneUUID"="f77a8816-304940cd-8484-82919275ddc3","zoneName"="Default
Zone","apLocation"=""
Displayed on the web
interface
AP [{apName&&apMac}] is unable to reach WeChat ESP authentication
server [{ip}]
Description
This event occurs when AP fails to reach WeChat ESP authentication
server.
Auto Clearance
This event triggers the alarm 2152, which is auto cleared by the event
code 2151.
WeChat ESP authentication server resolvable
Table 174. WeChat ESP authentication server resolvable event
Event
WeChat ESP authentication server resolvable
Event Type
espAuthServerResolvable
Event Code
2153
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx","dn"="www.test.com","ip"="17.0.0.12","
profileId"="1","fwVersion"="3.2.0.0.x","model"="ZF7982","zoneUUID"
="f77a8816-3049-40cd-8484-82919275ddc3","zoneName"="Default
Zone","apLocation"=""
Displayed on the web
interface
AP [{apName&&apMac}] is able to resolve WeChat ESP authentication
server domain name [{dn}] to [{ip}] successfully.
Description
This event occurs when AP successfully resolves WeChat ESP
authentication server domain name.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
157
Events Types
AP Authentication Events
WeChat ESP authentication server unresolvable
Table 175. WeChat ESP authentication server unresolvable event
Event
WeChat ESP authentication server unresolvable
Event Type
espAuthServerUnResolvable
Event Code
2154
Severity
Major
Attribute
"apMac"="xx:xx:xx:xx:xx:xx","dn"="www.test.com","profileId"="1","fw
Version"="3.2.0.0.x","model"="ZF7982","zoneUUID"="f77a88163049-40cd-8484-82919275ddc3","zoneName"="Default
Zone","apLocation"=""
Displayed on the web
interface
AP [{apName&&apMac}] is unable to resolve WeChat ESP
authentication server domain name [{dn}] to IP.
Description
This event occurs when AP fails to resolves WeChat ESP authentication
server domain name.
Auto Clearance
This event triggers the alarm 2154, which is auto cleared by the event
code 2153.
WeChat ESP DNAT server reachable
Table 176. WeChat ESP DNAT server reachable event
Event
WeChat ESP DNAT server reachable
Event Type
espDNATServerReachable
Event Code
2161
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx","ip"="17.0.0.12","profileId"="1","fwVersio
n"="3.2.0.0.x","model"="ZF7982","zoneUUID"="f77a8816-304940cd-8484-82919275ddc3","zoneName"="Default
Zone","apLocation"=""
Displayed on the web
interface
AP [{apName&&apMac}] is able to reach WeChat ESP DNAT server [{ip}]
successfully.
Description
This event occurs when AP successfully able to reach WeChat ESP
DNAT server.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
158
Events Types
AP Authentication Events
WeChat ESP DNAT server unreachable
Table 177. WeChat ESP DNAT server unreachable event
Event
WeChat ESP DNAT server unreachable
Event Type
espDNATServerUnreachable
Event Code
2162
Severity
Major
Attribute
"apMac"="xx:xx:xx:xx:xx:xx","ip"="17.0.0.12","profileId"="1","fwVersio
n"="3.2.0.0.x","model"="ZF7982","zoneUUID"="f77a8816-304940cd-8484-82919275ddc3","zoneName"="Default
Zone","apLocation"=""
Displayed on the web
interface
AP [{apName&&apMac}] is unable to reach WeChat ESP DNAT server
[{ip}].
Description
This event occurs when AP fails to reach WeChat ESP DNAT server.
Auto Clearance
This event triggers the alarm 2162, which is auto cleared by the event
code 2161.
WeChat ESP DNAT server resolvable
Table 178. WeChat ESP DNAT server resolvable event
Event
WeChat ESP DNAT server resolvable
Event Type
espDNATServerResolvable
Event Code
2163
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx","dn"="www.test.com","ip"="17.0.0.12","
profileId"="1","fwVersion"="3.2.0.0.x","model"="ZF7982","zoneUUID"
="f77a8816-3049-40cd-8484-82919275ddc3", "zoneName"="Default
Zone","apLocation"=""
Displayed on the web
interface
AP [{apName&&apMac}] is able to resolve WeChat ESP DNAT server
domain name [{dn}] to [{ip}] successfully.
Description
This event occurs when AP successfully resolve WeChat ESP DNAT
server domain name.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
159
Events Types
AP Authentication Events
WeChat ESP DNAT server unresolvable
Table 179. WeChat ESP DNAT server unresolvable event
Event
WeChat ESP DNAT server unresolvable
Event Type
espDNATServerUnresolvable
Event Code
2164
Severity
Major
Attribute
"apMac"="xx:xx:xx:xx:xx:xx","dn"="www.test.com","profileId"="1","fw
Version"="3.2.0.0.x","model"="ZF7982","zoneUUID"="f77a88163049-40cd-8484-82919275ddc3","zoneName"="Default
Zone","apLocation"=""
Displayed on the web
interface
AP [{apName&&apMac}] is unable to resolve WeChat ESP DNAT server
domain name [{dn}] to IP.
Description
This event occurs when AP fails to resolve WeChat ESP DNAT server
domain name.
Auto Clearance
This event triggers the alarm 2164, which is auto cleared by the event
code 2163.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
160
Events Types
AP USB Events
AP USB Events
Following are the events related to AP USB (Universal Serial Bus).
• AP USB software package downloaded
• AP USB software package download failed
AP USB software package downloaded
Table 180. AP USB software package downloaded event
Event
AP USB software package downloaded
Event Type
apUsbSoftwarePackageDownloaded
Event Code
370
Severity
Informational
Attribute
“apMac="xx:xx:xx:xx:xx:xx", “usbSoftwareName="19d2-fff5(v1.0)"
Displayed on the web
interface
AP [{apName&&apMac}] downloaded USB software package
[{usbSoftwareName}] successfully.
Description
This event occurs when AP successfully downloads its USB software
package.
AP USB software package download failed
Table 181. AP USB software package download failed event
Event
AP USB software package download failed
Event Type
apUsbSoftwarePackageDownloadFailed
Event Code
371
Severity
Major
Attribute
apMac="xx:xx:xx:xx:xx:xx", usbSoftwareName="19d2-fff5(v1.0)"
Displayed on the web
interface
AP [{apName&&apMac}] failed to download USB software package
[{usbSoftwareName}]
Description
This event occurs when the AP fails to download its USB software
package.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
161
Events Types
Authentication Events
Authentication Events
The following are the events related to authentication.
• Authentication server not reachable
• Authentication failed over to secondary
• Authentication fallback to primary
• AD/LDAP connected successfully
• AD/LDAP connectivity failure
• Bind fails with AD/LDAP
• Bind success with LDAP, but unable to find clear text password for the user
• RADIUS fails to connect to AD NPS server
• RADIUS fails to authenticate with AD NPS server
Authentication server not reachable
Table 182. Authentication server not reachable event
Event
Authentication server not reachable
Event Type
authSrvrNotReachable
Event Code
1601
Severity
Major
Attribute
“mvnoId”=12 “ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”
“srcProcess”=”radiusd” “realm”=
”wlan.mnc080.mcc405.3gppnetwork.org" “radProxyIp”=”7.7.7.7”
“authSrvrIp"=”20.20.20.20” "SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
Authentication Server [{authSrvrIp}] not reachable from Radius Proxy
[{radProxyIp}] on {produce.short.name} [{SZMgmtIp}]
Description
This event occurs when the authentication fails since the primary or
secondary servers is not reachable.
Authentication failed over to secondary
Table 183. Authentication failed over to secondary event
Event
Authentication failed over to secondary
Event Type
authFailedOverToSecondary
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
162
Events Types
Authentication Events
Table 183. Authentication failed over to secondary event
Event Code
1651
Severity
Major
Attribute
“mvnoId”=12 “ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”
“srcProcess”=”radiusd” “realm”=
”wlan.mnc080.mcc405.3gppnetwork.org" “radProxyIp”=”7.7.7.7”
“primary"=”20.20.20.20” “secondary”=”30.30.30.30”
"SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
Radius Server Failed Over from Primary [{primary}] to Secondary
[{secondary}] on Radius Proxy [{radProxyIp}] on {produce.short.name}
[{SZMgmtIp}]
Description
This event occurs when the secondary authentication RADIUS server is
available after the primary server becomes zombie or dead.
Authentication fallback to primary
Table 184. Authentication fallback to primary event
Event
Authentication fallback to primary
Event Type
authFallbackToPrimary
Event Code
1652
Severity
Major
Attribute
“mvnoId”=12 “ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”
“srcProcess”=”radiusd” “realm”=
”wlan.mnc080.mcc405.3gppnetwork.org" “radProxyIp”=”7.7.7.7”
“primary"=”20.20.20.20” “secondary”=”30.30.30.30”
"SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
Radius Server Fallback to Primary [{primary}] from Secondary
[{secondary}] on Radius Proxy [{radProxyIp}] on {produce.short.name}
[{SZMgmtIp}]
Description
This event occurs when the automatic fallback is enabled. The
authentication failover to secondary server has occurred, the revival
timer for primary server has expired and the requests falls back to the
primary server.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
163
Events Types
Authentication Events
AD/LDAP connected successfully
Table 185. AD/LDAP connected successfully event
Event
AD/LDAP connected successfully
Event Type
racADLDAPSuccess
Event Code
1751
Severity
Debug
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “mvnoId”=12,
“srcProcess”=”RAC”, “authSrvrIp”= “1.1.1.1”
"SZMgmtIp"="2.2.2.2", “desc”=”Successful connection to AD/LDAP”
Displayed on the web
interface
[{srcProcess}] Connect to AD/LDAP[{authSrvrIp}] successfully from
SCG[{SZMgmtIp}]
Description
This event occurs when RADIUS connection to AD/LDAP server is
successful.
AD/LDAP connectivity failure
Table 186. AD/LDAP connectivity failure event
Event
AD/LDAP connectivity failure
Event Type
racADLDAPFail
Event Code
1752
Severity
Major
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “mvnoId”=12,
“srcProcess”=”RAC”, “authSrvrIp”=“1.1.1.1”, "SZMgmtIp"="2.2.2.2"
“desc”= "Connection to AD/LDAP fails"
Displayed on the web
interface
[{srcProcess}] Connect to AD/LDAP[{authSrvrIp}] fails from
SCG[{SZMgmtIp}]
Description
This event occurs when RADIUS fails to connect to AD/LDAP server.
Bind fails with AD/LDAP
Table 187. Bind fails with AD/LDAP event
Event
Bind fails with AD/LDAP
Event Type
racADLDAPBindFail
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
164
Events Types
Authentication Events
Table 187. Bind fails with AD/LDAP event
Event Code
1753
Severity
Major
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “mvnoId”=12,
“srcProcess”=”RAC”, “authSrvrIp”= “1.1.1.1”, “username”=“testuser’
"SZMgmtIp"="2.2.2.2", “desc”=”Bind to AD/LDAP fails”
Displayed on the web
interface
[{srcProcess}] Bind to AD/LDAP[{authSrvrIp}] fails from
SCG[{SZMgmtIp}] for User[{userName}]
Description
This event occurs when RADIUS binding fails to AD/LDAP server.
Bind success with LDAP, but unable to find clear text
password for the user
Table 188. Bind success with LDAP, but unable to find clear text password for the user event
Event
Bind success with LDAP but unable to find clear text password for the
user
Event Type
racLDAPFailToFindPassword
Event Code
1754
Severity
Major
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “mvnoId”=12,
“srcProcess”=”RAC”, “authSrvrIp”=“1.1.1.1”, “username”= “testuser’
"SZMgmtIp"="2.2.2.2", “desc”=”Fail to find password”
Displayed on the web
interface
[{srcProcess}] failed to find password from LDAP [{authSrvrIp}] for
SCG[{SZMgmtIp}] for User[{userName}]
Description
This event occurs when binding is successful with LDAP using root
credential but is unable to retrieve the clear text password for the user.
RADIUS fails to connect to AD NPS server
Table 189. RADIUS fails to connect to AD NPS server event
Event
RADIUS fails to connect to AD NPS server
Event Type
racADNPSFail
Event Code
1755
Severity
Major
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
165
Events Types
Authentication Events
Table 189. RADIUS fails to connect to AD NPS server event
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “mvnoId”=12,
“srcProcess”=”RAC”, “authSrvrIp”=“1.1.1.1”, “username”=“testuser’
"SZMgmtIp"="2.2.2.2", “desc”= ”Fails to connect to AD NPS server”
Displayed on the web
interface
[{srcProcess}] Fails to connect to AD NPS [{authSrvrIp}] from
SCG[{SZMgmtIp}]
Description
This event occurs when RADIUS fails to connect to AD NPS server.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
166
Events Types
Authentication Events
RADIUS fails to authenticate with AD NPS server
Table 190. RADIUS fails to authenticate with AD NPS server event
Event
RADIUS fails to authenticate with AD NPS server
Event Type
racADNPSFailToAuthenticate
Event Code
1756
Severity
Major
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “mvnoId”=12,
“srcProcess”=”RAC”, “authSrvrIp”=“1.1.1.1”, “username”=“testuser’
"SZMgmtIp"="2.2.2.2", “desc”=”Fails to authenticate with AD NPS”
Displayed on the web
interface
[{srcProcess}] Fails to authenticate AD NPS[{authSrvrIp}] on SCG
[{SZMgmtIp}] for User[{userName}]
Description
This event occurs when RADIUS fails to authenticate with AD NPS
server.
NOTE: Refer to Authentication Alarms.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
167
Events Types
Authorization Events
Authorization Events
Following are the events related to authorization (DM/CoA).
• DM received from AAA
• DM NACK sent to AAA
• DM sent to NAS
• DM NACK received from NAS
• CoA received from AAA
• CoA NACK sent to AAA
• CoA sent NAS
• CoA NAK received NAS
• CoA authorize only access reject
• CoA RWSG MWSG notification failure
DM received from AAA
Table 191. DM received from AAA event
Event
DM received from AAA
Event Type
dmRcvdAAA
Event Code
1641
Severity
Debug
Attribute
"mvnoId"="2" "ctrlBladeMac"="aa:bb:cc:dd:ee:ff"
"srcProcess"="radius" "userName"="user name" "radSrvrIp"="7.7.7.7"
"rmtRadSrvrIp"="40.40.40.40" "
{produce.short.name}MgmtIp"="2.2.2.2"
Displayed on the web
interface
RADIUS DM received by RAC [{radSrvrIp}] from AAA [{rmtRadSrvrIp}]
for [{userName}]
Description
This event occurs when the radio access controller (RAC) receives a
disconnected message from the AAA server.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
168
Events Types
Authorization Events
DM NACK sent to AAA
Table 192. DM NACK sent to AAA event
Event
DM NACK sent to AAA
Event Type
dmNackSntAAA
Event Code
1642
Severity
Debug
Attribute
“mvnoId”=”2” “ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”
“srcProcess”=”radius” “userName”=”user name" “radSrvrIp”=”7.7.7.7”
"rmtRadSrvrIp"="40.40.40.40" "SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
RADIUS DM NACK sent by RAC [{radSrvrIp}] to AAA [{rmtRadSrvrIp}]
for [{userName}]
Description
This event occurs when RAC sends a disconnected not acknowledged
message to the AAA server.
DM sent to NAS
Table 193. DM sent to NAS event
Event
DM sent to NAS
Event Type
dmSntNAS
Event Code
1643
Severity
Debug
Attribute
“mvnoId”=”2” “ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”
“srcProcess”=”radius” “userName”=”user name" “radSrvrIp”=”7.7.7.7”
"nasIp"="40.40.40.40" "SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
RADIUS DM sent to NAS [{rmtRadSrvrIp}] by RAC [{radSrvrIp}] for
[{userName}]
Description
This event occurs when RAC sends a disconnected message to the
network access server [proxy of received disconnected message or the
disconnected message as initiated by the controller].
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
169
Events Types
Authorization Events
DM NACK received from NAS
Table 194. DM NACK received from NAS event
Event
DM NACK received from NAS
Event Type
dmNackRcvdNAS
Event Code
1644
Severity
Debug
Attribute
“mvnoId”=”2” “ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”
“srcProcess”=”radius” “userName”=”user name" “radSrvrIp”=”7.7.7.7”
"nasIp"="40.40.40.40" "SZMgmtIp"="2.2.2.2", “cause”=””
Displayed on the web
interface
RADIUS DM NACK received by RAC [{radSrvrIp}] from NAS [{nasIp}] for
[{userName}]
Description
This event occurs when the radio access control receives disconnect
message, which is not acknowledged from the NAS server.
CoA received from AAA
Table 195. CoA received from AAA event
Event
CoA received from AAA
Event Type
coaRcvdAAA
Event Code
1645
Severity
Debug
Attribute
“mvnoId”=”2” “ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”
“srcProcess”=”radius” “userName”=”user name" “radSrvrIp”=”7.7.7.7”
"rmtRadSrvrIp"="40.40.40.40" "SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
RADIUS CoA received by RAC [{radSrvrIp}] from AAA [{rmtRadSrvrIp}]
for [{userName}]
Description
This event occurs when radio access control receives a change of
authorization message from the AAA server.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
170
Events Types
Authorization Events
CoA NACK sent to AAA
Table 196. CoA NACK sent to AAA event
Event
CoA NACK sent to AAA
Event Type
coaNackSntAAA
Event Code
1646
Severity
Debug
Attribute
“mvnoId”=”2” “ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”
“srcProcess”=”radius” “userName”=”user name" “radSrvrIp”=”7.7.7.7”
"rmtRadSrvrIp"="40.40.40.40" "SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
RADIUS CoA NACK sent by RAC [{radSrvrIp}] to AAA [{rmtRadSrvrIp}]
for [{userName}]
Description
This event occurs when radio access control sends a change of
authorization, not acknowledged to the AAA server.
CoA sent NAS
Table 197. CoA sent NAS event
Event
CoA sent NAS
Event Type
coaSentNas
Event Code
1647
Severity
Debug
Attribute
“mvnoId”=”12” “ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”
“srcProcess”=”radiusd” “userName”=”abc@xyz.com”
“radSrvrIp”=”1.1.1.1” “nasIp”=”3.3.3.3” "SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
CoA requests proxied/forwarded to NAS(AP) [{nasIp}].
Description
This event occurs when the controller forwards/proxy of change of
authorization to the NAS server.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
171
Events Types
Authorization Events
CoA NAK received NAS
Table 198. CoA NAK received NAS event
Event
CoA NAK received NAS
Event Type
coaNakRcvdNas
Event Code
1648
Severity
Debug
Attribute
“mvnoId”=”12” “ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”
“srcProcess”=”radiusd” “userName”=”abc@xyz.com”
“radSrvrIp”=”1.1.1.1” “nasIp”=”3.3.3.3” "SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
CoA NAK received from NAS(AP) for forwarded/proxied CoA
[{radSrvrIp}]
Description
This event occurs when a change of authorization, not acknowledged
is received from the NAS server.
CoA authorize only access reject
Table 199. CoA authorize only access reject event
Event
CoA authorize only access reject
Event Type
coaAuthorizeOnlyAccessReject
Event Code
1649
Severity
Critical
Attribute
“mvnoId”=”12” “wlanId”=”1” “zoneId”=”10”
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess”=”radiusd”
“userName”=”abc@xyz.com” “realm”=
”wlan.mnc080.mcc405.3gppnetwork.org" "SZMgmtIp"="2.2.2.2"
“apType” = “” “ueMacAddr”=”aa:bb:cc:gg:hh:ii”
"rmtRadSrvrIp"="40.40.40.40"
Displayed on the web
interface
CoA Authorize Only unsuccessful for AAA Server [rmtRadSrvrIp] for UE
[ueMacAddr]
Description
This event occurs when the change of authorization is rejected.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
172
Events Types
Authorization Events
CoA RWSG MWSG notification failure
Table 200. CoA RWSG MWSG notification failure event
Event
CoA RWSG MWSG notification failure
Event Type
coaRWSGMWSGNotifFailure
Event Code
1650
Severity
Major
Attribute
mvnoId”=12 “wlanId”=1 “zoneId”=”10”
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess”=”radiusd”
“userName”=abc@xyz.com
“realm”=”wlan.mnc080.mcc405.3gppnetwork.org"
"SZMgmtIp"="2.2.2.2" “apType” = “ “ueMacAddr”=”aa:bb:cc:gg:hh:ii”
Displayed on the web
interface
Session Modify MWSG-RWSG Notification Failure/No response
received
Description
This event occurs when the change of authorization in RADIUS /metro
wireless service gateway notification fails.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
173
Events Types
Control and Data Plane Interface Events
Control and Data Plane Interface Events
Following are the events related to control and data plane events.
• DP connected
• GtpManager (DP) disconnected
• Session updated at DP
• Session update at DP failed
• Session deleted at DP
• Session delete at DP failed
• C2d configuration failed
DP connected
Table 201. DP connected event
Event
DP connected
Event Type
connectedToDblade
Event Code
1201
Severity
Informational
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess”=”aut” “realm”=”NA”
“ctrlBladeIp”=”1.1.1.1” "dataBladeIp"="3.3.3.3" "SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
The connectivity between Control plane [{ctrlBladeIp}] and Data plane
[{dataBladeIp}] is established at {produce.short.name} [{SZMgmtIp}]
Description
This event occurs when data plane successfully completes the
configuration procedure.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
174
Events Types
Control and Data Plane Interface Events
GtpManager (DP) disconnected
Table 202. GtpManager (DP) disconnected event
Event
GtpManager (DP) disconnected
Event Type
lostCnxnToDblade
Event Code
1202
Severity
Major
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess”=”aut” “realm”=”NA”
“ctrlBladeIp”=”1.1.1.1” "dataBladeIp"="3.3.3.3" "SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
The connectivity between Control plane [{ctrlBladeIp}] and Data plane
[{dataBladeIp}] is lost at {produce.short.name} [{SZMgmtIp}]
Description
This event occurs when either the transmission control protocol
connection is lost or when the control plane is unable to complete the
configuration procedure.
Auto Clearance
This event triggers the alarm 1202, which is auto cleared by the event
code 1201.
Session updated at DP
Table 203. Session updated at DP event
Event
Session updated at DP
Event Type
sessUpdatedAtDblade
Event Code
1205
Severity
Debug
Attribute
“mvnoId”=”12” “wlanId”=”1” “zoneId”=”10”
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess”=”aut” “realm”=”realm
sent by UE” “ctrlBladeIp”=”1.1.1.1” "dataBladeIp"="3.3.3.3"
"SZMgmtIp"="2.2.2.2" “ueMacAddr”=”aa:bb:cc:gg:hh:ii”
“ueImsi”=”12345” “ueMsisdn”=”98787”
Displayed on the web
interface
TTG/PDG session for UE with IMSI [{ueImsi}] and MSISDN [{ueMsisdn}]
has been updated at Data plane [{dataBladeIp}] by Control plane
[{ctrlBladeIp}] at {produce.short.name} [{SZMgmtIp}]
Description
This event occurs when the session updates the request (C-D-SESSUPD-REQ) successfully.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
175
Events Types
Control and Data Plane Interface Events
Session update at DP failed
Table 204. Session update at DP failed event
Event
Session update at DP failed
Event Type
sessUpdateErrAtDblade
Event Code
1206
Severity
Debug
Attribute
“mvnoId”=”12”, “wlanId”=”1”, “ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”,
“srcProcess”=”aut”, “zoneId”=”10”, “realm”=”realm sent by UE”,
“ctrlBladeIp”=”1.1.1.1”, "dataBladeIp"="3.3.3.3", "
{produce.short.name}MgmtIp"="2.2.2.2",
“ueMacAddr”=”aa:bb:cc:gg:hh:ii”,
“ueImsi”=”12345”, “ueMsisdn”=”98787”
Displayed on the web
interface
TTG/PDG session for UE with IMSI [{ueImsi}] and MSISDN [{ueMsisdn}]
has failed to update at Data plane [{dataBladeIp}] by Control plane
[{ctrlBladeIp}] at {produce.short.name} [{SZMgmtIp}]
Description
This event occurs when the session update request fails (C-D-SESSUPD-REQ). This is either due to a request timeout or a failed response.
Session deleted at DP
Table 205. Session deleted at DP event
Event
Session deleted at DP
Event Type
sessDeletedAtDblade
Event Code
1207
Severity
Debug
Attribute
“mvnoId”=”12” “wlanId”=”1” “zoneId”=”10”
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess”=”aut” “realm”=”realm
sent by UE” “ctrlBladeIp”=”1.1.1.1” "dataBladeIp"="3.3.3.3"
"SZMgmtIp"="2.2.2.2" “ueMacAddr”=”aa:bb:cc:gg:hh:ii”
“ueImsi”=”12345” “ueMsisdn”=”98787”
Displayed on the web
interface
TTG/PDG session for UE with IMSI [{ueImsi}] and MSISDN [{ueMsisdn}]
has been deleted from Data plane [{dataBladeIp}] by Control plane
[{ctrlBladeIp}] at {produce.short.name} [{SZMgmtIp}]
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
176
Events Types
Control and Data Plane Interface Events
Table 205. Session deleted at DP event
Description
This event occurs when the session deletes request (C-D-SESS-DELREQ) is successfully acknowledged.
Session delete at DP failed
Table 206. Session delete at DP failed event
Event
Session delete at DP failed
Event Type
sessDeleteErrAtDblade
Event Code
1208
Severity
Debug
Attribute
“mvnoId”=”12” “wlanId”=”1” “zoneId”=”10”
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess”=”aut” “realm”=”realm
sent by UE” “ctrlBladeIp”=”1.1.1.1” "dataBladeIp"="3.3.3.3"
"SZMgmtIp"="2.2.2.2" “ueMacAddr”=”aa:bb:cc:gg:hh:ii”
“ueImsi”=”12345” “ueMsisdn”=”98787”
Displayed on the web
interface
TTG/PDG session for UE with IMSI [{ueImsi}] and MSISDN [{ueMsisdn}]
has failed to delete from Data plane [{dataBladeIp}] by Control plane
[{ctrlBladeIp}] at {produce.short.name} [{SZMgmtIp}]
Description
This event occurs when the session delete request (C-D-SESS-DELREQ) results in a timeout or a failed response.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
177
Events Types
Control and Data Plane Interface Events
C2d configuration failed
Table 207. C2d configuration failed event
Event
C2d configuration failed
Event Type
c2dCfgFailed
Event Code
1209
Severity
Warning
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess”=”aut” “realm”=”NA"
“ctrlBladeIp”=”1.1.1.1” "dataBladeIp"="3.3.3.3" "SZMgmtIp"="2.2.2.2"
“cause”=””
Displayed on the web
interface
Configuration [{cause}] from Control plane [{ctrlBladeIp}] failed to apply
on Data plane [{dataBladeIp}] at {produce.short.name} [{SZMgmtIp}]
Description
This event occurs when the configuration request (C-D-CFG-REQ)
results in a timeout or a failed response.
NOTE: Refer to Control and Data Plane Interface Alarms.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
178
Events Types
Client Events
Client Events
All client events from the AP will be appended with tenant ID ("tenantUUID":"xxxxx").
Following are the events related to clients.
• Client authentication failed
• Client joined
• Client failed to join
• Client disconnected
• Client connection timed out
• Client authorization successfully
• Client authorization failed
• Client session expired
• Client roaming
• Client logged out
• Client roaming disconnected
• Client blocked
• Client grace period
• Onboarding registration succeeded
• Onboarding registration failed
• Remediation succeeded
• Remediation failed
• Force DHCP disconnected
• WDS device joined
• WDS device left
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
179
Events Types
Client Events
Client authentication failed
Table 208. Client authentication failed event
Event
Client authentication failed
Event Type
clientAuthFailure
Event Code
201
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "clientMac"="xx:xx:xx:xx:xx:xx",
"ssid"="xxxxx", "wlanId"="xxxxx", "userName"="xxxxx",“userId”=”uuid"
Displayed on the web
interface
Client [{userName||IP||clientMac}] failed to join WLAN [{ssid}] from AP
[{apName&&apMac}] due to authentication failure.
Description
This event occurs when the client fails to join WLAN on the AP due to
an authentication failure.
Client joined
Table 209. Client joined event
Event
Client joined
Event Type
clientJoin
Event Code
202
Severity
Informational
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”, “clientMac”=”xx:xx:xx:xx:xx:xx”,
“ssid”=”xxxxx”, “wlanId”=”xxxxx”, “userName”=”xxxxx”,
“clientIP”=”x.x.x.x”, “userId”=”uuid"
Displayed on the web
interface
Client [{userName||IP||clientMac}] joined WLAN [{ssid}] from AP
[{apName&&apMac}].
Description
This event occurs when the client session joins the WLAN on AP.
Client failed to join
Table 210. Client failed to join event
Event
Client failed to join
Event Type
clientJoinFailure
Event Code
203
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
180
Events Types
Client Events
Table 210. Client failed to join event
Severity
Informational
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”, “clientMac”=”xx:xx:xx:xx:xx:xx”,
“ssid”=”xxxxx”, “wlanId”=”xxxxx”, “userName”=”xxxxx”,
“userId”=”uuid"
Displayed on the web
interface
Client [{userName||IP||clientMac}] failed to join WLAN [{ssid}] from AP
[{apName&&apMac}].
Description
This event occurs when the client fails to connect to the WLAN on the AP.
Client disconnected
Table 211. Client disconnected event
Event
Client disconnected
Event Type
clientDisconnect
Event Code
204
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "clientMac"="xx:xx:xx:xx:xx:xx",
“ssid”=”xxxxx”, “assoicationTime"="600", “wlanId”=”xxxxx”,
“userName”=”xxxxx”, “clientIP”=”x.x.x.x”, “apName”=””,
“apLocation”=””, “username”=””, “osType”=””, “radio”=””, “vlanId”=””,
“sessionDuration”=””, “txBytes”=””, “rxBytes”=””, “rssi”=””,
“receivedSignalStrength”=””, “apGps”=””, “hostname”=””,
“encryption”=””, “disconnectReason”=””, “bssid”=””, “userId”=”uuid"
Displayed on the web
interface
Client [{userName||IP||clientMac}] disconnected from WLAN [{ssid}] on
AP [{apName&&apMac}]
Description
This event occurs when the client disconnects from WLAN on AP.
Client connection timed out
Table 212. Client connection timed out event
Event
Client connection timed out
Event Type
clientInactivityTimeout
Event Code
205
Severity
Informational
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
181
Events Types
Client Events
Table 212. Client connection timed out event
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "clientMac"="xx:xx:xx:xx:xx:xx",
"ssid"="xxxxx", "assoicationTime"="600",
"wlanId"="xxxxx","userName"="xxxxx", "clientIP"="x.x.x.x",
"apName"="", "apLocation"="", "username"="", "osType"="",
"radio"="", "vlanId"=, "sessionDuration"=, "txBytes"=, "rxBytes"=,
"rssi"="", "receivedSignalStrength"="", "apGps"="","hostname"="",
"encryption"="",, “userId”=”uuid"
Displayed on the web
interface
Remediation of type [{remediationType}] failed on client
[{clientIP||clientMac}] for user [{userName}].
Description
This event occurs when client disconnects from WLAN on AP due to
inactivity.
Client authorization successfully
Table 213. Client authorization successfully event
Event
Client authorization successfully
Event Type
clientAuthorization
Event Code
206
Severity
Informational
Attribute
""apMac"="xx:xx:xx:xx:xx:xx",
"clientMac"="xx:xx:xx:xx:xx:xx",“ssid”=”xxxxx”, “wlanId”=”xxxxx”,
“userName”=”xxxxx”,“clientIP”=”x.x.x.x”, “userId”=”uuid"
Displayed on the web
interface
Client [{userName||IP||clientMac}] of WLAN [{ssid}] from AP
[{apName&&apMac}] was authorized.
Description
This event occurs when the client on WLAN AP is authorized.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
182
Events Types
Client Events
Client authorization failed
Table 214. Client authorization failed event
Event
Client authorization failed
Event Type
clientAuthorizationFailure
Event Code
207
Severity
Informational
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”,
“clientMac”=”xx:xx:xx:xx:xx:xx”,“ssid”=”xxxxx”, “wlanId”=”xxxxx”,
“userName”=”xxxxx”,“clientIP”=”x.x.x.x” “userId”=”uuid"
Displayed on the web
interface
Client [{userName||IP||clientMac}] of WLAN [{ssid}] from AP
[{apName&&apMac}] was not authorized.
Description
This event occurs when the client on WLAN AP authorization fails.
Client session expired
Table 215. Client session expired event
Event
Client session expired
Event Type
clientSessionExpiration
Event Code
208
Severity
Informational
Attribute
“apMac"="xx:xx:xx:xx:xx:xx", "clientMac"="xx:xx:xx:xx:xx:xx",
“ssid”=”xxxxx”, “assoicationTime"="600", “wlanId”=”xxxxx”,
“userName”=”xxxxx”, “clientIP”=”x.x.x.x”,“apName”=””,
“apLocation”=””,“username”=””, “osType”=””,“radio”=””,“vlanId”="",
“sessionDuration”="", “txBytes”=””, “rxBytes”=””, “rssi”=””,
“receivedSignalStrength”=””, “apGps”=””, “hostname”=””,
“encryption”=””, “disconnectReason”=””, “bssid”=”” “userId”=”uuid"
Displayed on the web
interface
Client [{userName||IP||clientMac}] exceeded the session time limit.
Session terminated.
Description
This event occurs when the client exceeds the session time limit resulting
in a session termination.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
183
Events Types
Client Events
Client roaming
Table 216. Client roaming event
Event
Client roaming
Event Type
clientRoaming
Event Code
209
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "clientMac"="xx:xx:xx:xx:xx:xx",
“ssid”=”xxxxx”, “wlanId”=”xxxxx”,
“userName”=”xxxxx”,“clientIP”=”x.x.x.x” “userId”=”uuid"
Displayed on the web
interface
AP [{apName&&apMac}] radio [{toRadio}] detected client
[{userName||IP||clientMac}] in WLAN [{ssid}] roam from AP
[{fromApName&&fromApMac}].
Description
This event occurs when the AP radio detects a client.
Client logged out
Table 217. Client logged out event
Event
Client logged out
Event Type
clientSessionLogout
Event Code
210
Severity
Informational
Attribute
“apMac"="xx:xx:xx:xx:xx:xx", "clientMac"="xx:xx:xx:xx:xx:xx",
“ssid”=”xxxxx”, “assoicationTime"="600", “wlanId”=”xxxxx”,
“userName”=”xxxxx”, “clientIP”=”x.x.x.x”, “apName”=””,
“apLocation”=””, “username”=””, “osType”=””, “radio”=””, “vlanId”="",
“sessionDuration”="", “txBytes”=””, “rxBytes”=””, “rssi”=””,
“receivedSignalStrength”=””, “apGps”=””, “hostname”=””,
“encryption”=””, “disconnectReason”=””, “bssid”=”” “userId”=”uuid"
Displayed on the web
interface
Client [{userName||IP||clientMac}] session logout.
Description
This event occurs when a client session is logged out.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
184
Events Types
Client Events
Client roaming disconnected
Table 218. Client roaming disconnected event
Event
Client roaming disconnected
Event Type
smartRoamDisconnect
Event Code
218
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", “clientMac"="xx:xx:xx:xx:xx:xx",
"ssid"="xxxxx", "assoicationTime"="600", "wlanId"="xxxxx",
"userName"="xxxxx", "clientIP"="x.x.x.x","apName"="",
"apLocation"="", "username"="","osType"="", "radio"="",
"vlanId"=””,"sessionDuration"=””,"txBytes"=””, "rxBytes"=””, "rssi"="",
"receivedSignalStrength"="", "apGps"="", "hostname"="",
"encryption"="", "disconnectReason"="", "bssid"="",
"ni_rx_rssilo_cnt"="" , "ni_rx_tot_cnt"="" , "ns_rx_rssilo_cnt"="" ,
"ns_rx_tot_cnt"="" , "ni_tx_xput_lo_cnt"="" , "ni_tx_xput_lo_dur"="" ,
"Instantaneous rssi"="" , "Xput"="",“userId”=””uuid"
Displayed on the web
interface
Client [{userName||IP||clientMac}] disconnected from WLAN [{ssid}] on
AP [{apName&&apMac}] due to SmartRoam policy.
Description
This event occurs when the client disconnects from the WLAN due to
a smart roam policy.
Client blocked
Table 219. Client blocked event
Event
Client blocked
Event Type
clientBlockByDeviceType
Event Code
219
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "clientMac"="xx:xx:xx:xx:xx:xx",
"deviceType"="xxxxx", "ssid"="xxxxx", "wlanId"="xxxxx",
Displayed on the web
interface
Client [{clientMac}] was recognized as [{deviceType}], and blocked by a
device policy in AP [{apMac}]
Description
This event occurs when a client is blocked by a device policy.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
185
Events Types
Client Events
Client grace period
Table 220. Client grace period event
Event
Client grace period
Event Type
clientGracePeriod
Event Code
220
Severity
Informational
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”, “clientMac”=”xx:xx:xx:xx:xx:xx”,
“ssid”=”xxxxx”, “wlanId”=”xxxxx”, “userName”=”xxxxx”,
“clientIP”=”x.x.x.x”
Displayed on the web
interface
Client [{userName||clientIP||clientMac}] reconnects WLAN [{ssid}] on AP
[{apName&&apMac}] within grace period. No additional authentication
is required.
Description
This event occurs when the when the STa interface reconnects and
authorizes due to the grace period.
Onboarding registration succeeded
Table 221. Onboarding registration succeeded event
Event
Onboarding registration succeeded
Event Type
onboardingRegistrationSuccess
Event Code
221
Severity
Informational
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”, “clientMac”=”xx:xx:xx:xx:xx:xx”,
“ssid”=”xxxxx”, “wlanId”=”xxxxx”, “userName”=”xxxxx”,
“clientIP”=”x.x.x.x”, “userId”=”uuid", “apLocation”=”xxxx”,
“groupName”=”xxxx”, “vlanId”=”xxxx”, “osType”=”xxxx”,
“userAgent”=”xxxx”
Displayed on the web
interface
Client [{userName||clientIP||clientMac}] of WLAN [{ssid}] on AP
[{apName&&apMac}] on boarding registration succeeded.
Description
This event occurs when the client on boarding registration is successful.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
186
Events Types
Client Events
Onboarding registration failed
Table 222. Onboarding registration failed event
Event
On boarding registration failed
Event Type
onboardingRegistrationFailure
Event Code
222
Severity
Informational
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”, “clientMac”=”xx:xx:xx:xx:xx:xx”,
“ssid”=”xxxxx”, “wlanId”=”xxxxx”, “userName”=”xxxxx”,
“clientIP”=”x.x.x.x”, “userId”=”uuid",“apLocation”=”xxxx”,
“groupName”=”xxxx”, “vlanId”=”xxxx”,
“osType”=”xxxx”,“userAgent”=”xxxx”,“reason”=”xxxxx”
Displayed on the web
interface
Client [{userName||clientIP||clientMac}] of WLAN [{ssid}] on AP
[{apName&&apMac}] on boarding registration failed because of
[{reason}].
Description
This event occurs when the client on boarding registration fails.
Remediation succeeded
Table 223. Remediation succeeded event
Event
Remediation succeeded
Event Type
remediationSuccess
Event Code
223
Severity
Informational
Attribute
“remediationType”=“xxxxx”,“clientMac”=“xx:xx:xx:xx:xx:xx”,
“userName”=“xxxxx”, “userId”=“uuid”,“reason”=“xxxxx”
Displayed on the web
interface
Remediation of type [{remediationType}] finished successfully on client
[{clientIP||clientMac}] for user [{userName}].
Description
This event occurs when the client remediation is successful.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
187
Events Types
Client Events
Remediation failed
Table 224. Remediation failed event
Event
Remediation failed
Event Type
remediationFailure
Event Code
224
Severity
Informational
Attribute
“remediationType”=“xxxxx”,“clientMac”=“xx:xx:xx:xx:xx:xx”,
“userName”=“xxxxx”, “userId”=“uuid”
Displayed on the web
interface
Client [{userName||clientIP||clientMac}] of WLAN [{ssid}] on AP
[{apName&&apMac}] on boarding registration failed because of
[{reason}].
Description
This event occurs when the client remediation fails.
Force DHCP disconnected
Table 225. Force DHCP disconnected event
Event
Force DHCP disconnected
Event Type
ForceDHCPDisconnect
Event Code
225
Severity
Informational
Attribute
“apMac”=“xx:xx:xx:xx:xx:xx”, “clientMac”=“xx:xx:xx:xx:xx:xx”,
“ssid”=“xxxxx”, “bssid”=“”, “wlanId”=“xxxxx”,
"tenantUUID"="xxxxx",“clientIP”=“x.x.x.x”,”apName”=““,”vlanId”=,
"radio"="", “encryption”=““,
Displayed on the web
interface
Client [{userName||IP||clientMac}] disconnected from WLAN [{ssid}] on
AP [{apName&&apMac}] due to force-dhcp.
Description
This event occurs when the client disconnects by force dynamic host
configuration protocol (DHCP).
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
188
Events Types
Client Events
WDS device joined
Table 226. WDS device joined event
Event
WDS device joined
Event Type
wdsDeviceJoin
Event Code
226
Severity
Informational
Attribute
“apName”=“xxxxx”, “apMac”=“xx:xx:xx:xx:xx:xx”,
“clientMac”=“xx:xx:xx:xx:xx:xx”, “wdsDevicetMac”=“xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Device [{wdsDeviceMac}] sends traffic via Client [{clientMac}] in AP
[{apName&&apMac}].
Description
This event occurs when a subscriber device joins the network provided
by a Customer-Premises Equipment (CPE) of a client associated AP
through a wireless distribution system (WDS) mode.
WDS device left
Table 227. WDS device left event
Event
WDS device left
Event Type
wdsDeviceLeave
Event Code
227
Severity
Informational
Attribute
“apName”=“xxxxx”, “apMac”=“xx:xx:xx:xx:xx:xx”,
“clientMac”=“xx:xx:xx:xx:xx:xx”, “wdsDevicetMac”=“xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Device [{wdsDeviceMac}] stops traffic via Client [{clientMac}] in AP
[{apName&&apMac}].
Description
This event occurs when a subscriber device leaves the network provided
by a CPE client associated to an AP through WDS.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
189
Events Types
Cluster Events
Cluster Events
Following are the events related to clusters.
Cluster created successfully
New node joined successfully
New node failed to join
Node removal completed
Node removal failed
Node out of service
Cluster in maintenance state
Cluster back in service
Cluster backup completed
Cluster backup failed
Cluster restore completed
Cluster restore failed
Cluster node upgrade
completed
Entire cluster upgraded successfully Cluster upgrade failed
Cluster application stopped
Cluster application started
Cluster backup started
Cluster upgrade started
Cluster leader changed
Node bond interface down
Node bond interface up
Node IP address changed
Node physical interface down
Node physical interface up
Cluster node rebooted
NTP time synchronized
Cluster node shutdown
Cluster upload started
Cluster upload completed
Cluster upload failed
SSH tunnel switched
Cluster remove node started
Node back in service
Resync NTP time
Disk usage exceed threshold
Cluster out of service
Initiated moving APs in node to a new Cluster upload vSZ-D firmware
cluster
started
Cluster upload vSZ-D firmware Cluster upload vSZ-D firmware failed Cluster upload AP firmware
completed
started
Cluster upload AP firmware
completed
Cluster upload AP firmware failed
Cluster add AP firmware started
Cluster add AP firmware
completed
Cluster add AP firmware failed
Cluster name is changed
Configuration backup started
Configuration backup succeeded
Configuration backup failed
Configuration restore
succeeded
Configuration restore failed
AP Certificate Expired
AP Certificate Updated
Node IPv6 address added
Node IPv6 address deleted
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
190
Events Types
Cluster Events
Cluster created successfully
Table 228. Cluster created successfully event
Event
Cluster created successfully
Event Type
clusterCreatedSuccess
Event Code
801
Severity
Informational
Attribute
“clusterName”=”xxx”, “nodeName”=”xxx”, “nodeMac”=”
xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Cluster [{clusterName}] created with node [{nodeName}]
Description
This event occurs when a cluster and a node are created.
New node joined successfully
Table 229. New node joined successfully event
Event
New node joined successfully
Event Type
newNodeJoinSuccess
Event Code
802
Severity
Informational
Attribute
“clusterName”=”xxx”, “nodeName”=”xxx”, “nodeMac”=”
xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
New node [{nodeName}] joined cluster [{clusterName}]
Description
This event occurs when a node joins a cluster session.
New node failed to join
Table 230. New node failed to join event
Event
New node failed to join
Event Type
newNodeJoinFailed
Event Code
803
Severity
Critical
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
191
Events Types
Cluster Events
Table 230. New node failed to join event
Attribute
“clusterName”=”xxx”, “nodeName”=”xxx”, “nodeMac”=”
xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
New node [{nodeName}] failed to join cluster [{clusterName}]
Description
This event occurs when a node fails to join a cluster session. The
controller web Interface displays the error message.
Auto Clearance
This event triggers the alarm 801, which is auto cleared by the event
code 802.
Node removal completed
Table 231. Node removal completed event
Event
Node removal completed
Event Type
removeNodeSuccess
Event Code
804
Severity
Informational
Attribute
“clusterName”=”xxx”, “nodeName”=”xxx”, “nodeMac”=”
xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Node [{nodeName}] removed from cluster [{clusterName}]
Description
This event occurs when a node is removed from the cluster session.
Node removal failed
Table 232. Node removal failed event
Event
Node removal failed
Event Type
removeNodeFailed
Event Code
805
Severity
Major
Attribute
“clusterName”=”xxx”, “nodeName”=”xxx”, “nodeMac”=”
xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Node [{nodeName}] failed to remove from cluster [{clusterName}].
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
192
Events Types
Cluster Events
Table 232. Node removal failed event
Description
This event occurs when a node cannot be removed from the cluster.
Auto Clearance
This event triggers the alarm 802, which is auto cleared by the event
code 804.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
193
Events Types
Cluster Events
Node out of service
Table 233. Node out of service event
Event
Node out of service
Event Type
nodeOutOfService
Event Code
806
Severity
Critical
Attribute
“clusterName”=”xxx”, “nodeName”=”xxx”, “nodeMac”=”
xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Node [{nodeName}] in cluster [{clusterName}] is out of service. Reason
[{reason}].
Description
This event occurs when a node is out of service.
Auto Clearance
This event triggers the alarm 803, which is auto cleared by the event
code 835.
Cluster in maintenance state
Table 234. Cluster in maintenance state event
Event
Cluster in maintenance state
Event Type
clusterInMaintenanceState
Event Code
807
Severity
Critical
Attribute
“clusterName”=”xxx”
Displayed on the web
interface
[{clusterName}] is in maintenance state
Description
This event occurs when a node is in a maintenance state.
Auto Clearance
This event triggers the alarm 804, which is auto cleared by the event
code 808.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
194
Events Types
Cluster Events
Cluster back in service
Table 235. Cluster back in service event
Event
Cluster back in service
Event Type
clusterBackToInService
Event Code
808
Severity
Informational
Attribute
“clusterName”=”xxx”
Displayed on the web
interface
[{clusterName}] is now in service
Description
This event occurs when a cluster is back in service.
Cluster backup completed
Table 236. Cluster backup completed event
Event
Cluster backup completed
Event Type
backupClusterSuccess
Event Code
809
Severity
Informational
Attribute
“clusterName”=”xxx”
Displayed on the web
interface
Cluster [{clusterName}] backup completed
Description
This event occurs when a cluster backup is complete.
Cluster backup failed
Table 237. Cluster backup failed event
Event
Cluster backup failed
Event Type
backupClusterFailed
Event Code
810
Severity
Major
Attribute
“clusterName”=”xxx”
Displayed on the web
interface
Cluster [{clusterName}] backup failed. Reason [{reason}].
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
195
Events Types
Cluster Events
Table 237. Cluster backup failed event
Description
This event occurs when a cluster backup fails.
Auto Clearance
This event triggers the alarm 805, which is auto cleared by the event
code 809.
Cluster restore completed
Table 238. Cluster restore completed event
Event
Cluster restore completed
Event Type
restoreClusterSuccess
Event Code
811
Severity
Informational
Attribute
"nodeName”=”xxx”, "clusterName"="xxx",
Displayed on the web
interface
Node [{nodeName}] in cluster [{clusterName}] restore completed
Description
This event occurs when restoration of a node to a cluster is successful.
Cluster restore failed
Table 239. Cluster restore failed event
Event
Cluster restore failed
Event Type
restoreClusterFailed
Event Code
812
Severity
Major
Attribute
“clusterName”=”xxx”
Displayed on the web
interface
Cluster [{clusterName}] restore failed. Reason [{reason}].
Description
This event occurs when restoration of a node in a cluster fails.
Auto Clearance
This event triggers the alarm 806, which is auto cleared by the event
code 811.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
196
Events Types
Cluster Events
Cluster node upgrade completed
Table 240. Cluster node upgrade completed event
Event
Cluster node upgrade completed
Event Type
upgradeClusterNodeSuccess
Event Code
813
Severity
Informational
Attribute
clusterName”=”xxx”, “nodeName”=”xxx”, “nodeMac”=”
xx:xx:xx:xx:xx:xx”, "fromVersion"="x.x", "toVersion"="x.x"
Displayed on the web
interface
Node [{nodeName}] in cluster [{clusterName}] upgraded from
[{fromVersion}] to [{toVersion}]
Description
This event occurs when version upgrade of a node is successful.
Entire cluster upgraded successfully
Table 241. Entire cluster upgraded successfully event
Event
Entire cluster upgraded successfully
Event Type
upgradeEntireClusterSuccess
Event Code
814
Severity
Informational
Attribute
clusterName”=”xxx”, "fromVersion"="x.x", "toVersion"="x.x"
Displayed on the web
interface
Cluster [{clusterName}] upgraded from [{fromVersion}] to [{toVersion}].
Description
This event occurs when version upgrade of a cluster is successful.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
197
Events Types
Cluster Events
Cluster upgrade failed
Table 242. Cluster upgrade failed event
Event
Cluster upgrade failed
Event Type
upgradeClusterFailed
Event Code
815
Severity
Major
Attribute
“clusterName”=”xxx”, “nodeName”=”xxx”, “nodeMac”=”
xx:xx:xx:xx:xx:xx”, "fromVersion"="x.x", "toVersion"="x.x"
Displayed on the web
interface
Cluster [{clusterName}] could not be upgraded from [{fromVersion}] to
[{toVersion}] Reason [{reason}].
Description
This event occurs when the version upgrade of a cluster fails.
Auto Clearance
This event triggers the alarm 807, which is auto cleared by the event
code 814.
Cluster application stopped
Table 243. Cluster application stopped event
Event
Cluster application stopped
Event Type
clusterAppStop
Event Code
816
Severity
Critical
Attribute
“appName”=”xxxx”, “nodeName”=”xxx”, “nodeMac”=”
xx:xx:xx:xx:xx:xx”,
Displayed on the web
interface
Application [{appName}] on node [{nodeName}] stopped
Description
This event occurs when an application on node is stopped.
Auto Clearance
This event triggers the alarm 808, which is auto cleared by the event
code 817.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
198
Events Types
Cluster Events
Cluster application started
Table 244. Cluster application started event
Event
Cluster application started
Event Type
clusterAppStart
Event Code
817
Severity
Informational
Attribute
“appName”=”xxxx”, “nodeName”=”xxx”, “nodeMac”=”
xx:xx:xx:xx:xx:xx”,
Displayed on the web
interface
Application [{appName}] on node [{nodeName}] started
Description
This event occurs when an application on node starts.
Cluster backup started
Table 245. Cluster backup started event
Event
Cluster backup started
Event Type
clusterBackupStart
Event Code
818
Severity
Informational
Attribute
“clusterName”=”xxx”, “nodeName”=”xxx”, “nodeMac”=”
xx:xx:xx:xx:xx:xx”,
Displayed on the web
interface
Starting backup in cluster[{clusterName}]...
Description
This event occurs when a backup for a node commences.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
199
Events Types
Cluster Events
Cluster upgrade started
Table 246. Cluster upgrade started event
Event
Cluster upgrade started
Event Type
clusterUpgradeStart
Event Code
819
Severity
Informational
Attribute
“clusterName”=”xxx”, “nodeName”=”xxx”, “nodeMac”=”
xx:xx:xx:xx:xx:xx”,
Displayed on the web
interface
Starting upgrade in cluster[{clusterName}]...
Description
This event occurs when an upgrade for a node commences.
Cluster leader changed
Table 247. Cluster leader changed event
Event
Cluster leader changed
Event Type
clusterLeaderChanged
Event Code
820
Severity
Informational
Attribute
“clusterName”=”xxx”, “nodeName”=”xxx”, “nodeMac”=”
xx:xx:xx:xx:xx:xx”,
Displayed on the web
interface
Node [{nodeName}] in cluster [{clusterName}] promoted to leader
Description
This event occurs when a node is changed to a lead node.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
200
Events Types
Cluster Events
Node bond interface down
Table 248. Node bond interface down event
Event
Node bond interface down
Event Type
nodeBondInterfaceDown
Event Code
821
Severity
Major
Attribute
“nodeName”=”xxx”, “nodeMac”=” xx:xx:xx:xx:xx:xx”, “ifName”=”xxxx”
Displayed on the web
interface
Network interface [{networkInterface||ifName}] on node [{nodeName}]
is down.
Description
This event occurs when the network interface of a node is down.
Auto Clearance
This event triggers the alarm 809, which is auto cleared by the event
code 822.
Node bond interface up
Table 249. Node bond interface up event
Event
Node bond interface up
Event Type
nodeBondInterfaceUp
Event Code
822
Severity
Informational
Attribute
“nodeName”=”xxx”, “nodeMac”=” xx:xx:xx:xx:xx:xx”, “ifName”=”xxxx”
Displayed on the web
interface
Network interface [{networkInterface||ifName}] on node [{nodeName}]
is up.
Description
This event occurs when the network interface of a node is up.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
201
Events Types
Cluster Events
Node IP address changed
Table 250. Node IP address changed event
Event
Node IP address changed
Event Type
nodeIPChanged
Event Code
823
Severity
Informational
Attribute
“nodeName”=”xxx”, “nodeMac”=” xx:xx:xx:xx:xx:xx”, “ifName”=”xxxx”,
“ip”=”xxx.xxx.xxx.xxx”
Displayed on the web
interface
IP address of network interface [{networkInterface||ifName}] on node
[{nodeName}] changed to [{ip}].
Description
This event occurs when the node’s network interface IP address
changes.
Node physical interface down
Table 251. Node physical interface down event
Event
Node physical interface down
Event Type
nodePhyInterfaceDown
Event Code
824
Severity
Critical
Attribute
“nodeName”=”xxx”, “nodeMac”=” xx:xx:xx:xx:xx:xx”, “ifName”=”xxxx”
Displayed on the web
interface
Physical network interface [{networkInterface||ifName}] on node
[{nodeName}] is down.
Description
This event occurs when the node’s physical interface is down.
Auto Clearance
This event triggers the alarm 810, which is auto cleared by the event
code 825.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
202
Events Types
Cluster Events
Node physical interface up
Table 252. Node physical interface up event
Event
Node physical interface up
Event Type
nodePhyInterfaceUp
Event Code
825
Severity
Informational
Attribute
“nodeName”=”xxx”, “nodeMac”=” xx:xx:xx:xx:xx:xx”, “ifName”=”xxxx”
Displayed on the web
interface
Physical network interface [{networkInterface||ifName}] on node
[{nodeName}] is up.
Description
This event occurs when the node’s physical interface is up.
Cluster node rebooted
Table 253. Cluster node rebooted event
Event
Cluster node rebooted
Event Type
nodeRebooted
Event Code
826
Severity
Major
Attribute
“nodeName”=”xxx”, “nodeMac”=” xx:xx:xx:xx:xx:xx”,
“clusterName”=”xxx”,
Displayed on the web
interface
Node [{nodeName}] in cluster [{clusterName}] rebooted
Description
This event occurs when the node, belonging to a cluster reboots.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
203
Events Types
Cluster Events
NTP time synchronized
Table 254. NTP time synchronized event
Event
NTP time synchronized
Event Type
ntpTimeSynched
Event Code
827
Severity
Informational
Attribute
“nodeName”=”xxx”, “nodeMac”=” xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Date and time settings on node [{nodeName}] synchronized with NTP
server
Description
This event occurs when the date and time settings of a node
synchronizes with the NTP server.
Cluster node shutdown
Table 255. Cluster node shutdown event
Event
Cluster node shutdown
Event Type
nodeShutdown
Event Code
828
Severity
Major
Attribute
“nodeName"="xxx", "nodeMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
Node [{nodeName}] has been shut down
Description
This event occurs when the node is shut down.
Auto Clearance
This event triggers the alarm 813, which is auto cleared by the event
code 826.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
204
Events Types
Cluster Events
Cluster upload started
Table 256. Cluster upload started event
Event
Cluster upload started
Event Type
clusterUploadStart
Event Code
830
Severity
Informational
Attribute
"clusterName"=”xxx”
Displayed on the web
interface
Starting upload in cluster [{clusterName}].
Description
This event occurs when the cluster upload process starts.
Cluster upload completed
Table 257. Cluster upload completed event
Event
Cluster upload completed
Event Type
uploadClusterSuccess
Event Code
831
Severity
Informational
Attribute
"clusterName"=”xxx”
Displayed on the web
interface
Cluster [{clusterName}] upload completed
Description
This event occurs when the cluster upload process is successful.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
205
Events Types
Cluster Events
Cluster upload failed
Table 258. Cluster upload failed event
Event
Cluster upload failed
Event Type
uploadClusterFailed
Event Code
832
Severity
Major
Attribute
"clusterName"=”xxx”, "reason"=”xxx”
Displayed on the web
interface
Cluster [{clusterName}] upload failed. Reason [{reason}]
Description
This event occurs when the cluster upload process fails.
SSH tunnel switched
Table 259. SSH tunnel switched event
Event
SSH tunnel switched
Event Type
sshTunnelSwitched
Event Code
833
Severity
Major
Attribute
"clusterName"="xx", "nodeName"="xx",
"nodeMac"="xx.xx.xx.xx.xx.xx", "wsgMgmtIp"="xx.xx.xx.xx",
"status"="ON->OFF", "sourceBladeUUID"="054ee469"
Displayed on the web
interface
Node [{nodeName}] SSH tunnel switched [{status}]
Description
This event occurs when the SSH tunnel is switched.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
206
Events Types
Cluster Events
Cluster remove node started
Table 260. Cluster remove node started event
Event
Cluster remove node started
Event Type
removeNodeStarted
Event Code
834
Severity
Informational
Attribute
"clusterName"=”xxx”, "nodeName" =”xxx”,
“nodeMac"=”xx:xx:xx:xx:xx”
Displayed on the web
interface
Start to remove node [{nodeName}] from cluster [{clusterName}]
Description
This event occurs when the node start is removed.
Node back in service
Table 261. Node back in service event
Event
Node back in service
Event Type
nodeBackToInService
Event Code
835
Severity
Informational
Attribute
"clusterName"="xx", "nodeName" =”xxx”, "nodeMac"=”xx:xx:xx:xx:xx”
Displayed on the web
interface
Node [{nodeName}] in cluster [{clusterName}] is in service
Description
This event occurs when a node status changes to 'in service'.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
207
Events Types
Cluster Events
Resync NTP time
Table 262. Resync NTP time event
Event
Resync NTP time
Event Type
resyncNTPTime
Event Code
837
Severity
Major
Attribute
"nodeName"="xx", "status"="xx"
Displayed on the web
interface
Node [{nodeName}] resyncs time from [{reason}]. The time difference is
[{status}] seconds.
Description
This event occurs when cluster time is not synchronized.
Disk usage exceed threshold
Table 263. Disk usage exceed threshold event
Event
Disk usage exceed threshold
Event Type
diskUsageExceed
Event Code
838
Severity
Critical
Attribute
"nodeName"="xx", "status"="xx"
Displayed on the web
interface
The disk usage of node [{nodeName}] is over {status}%.
Description
This event occurs when the disk usage exceeds the threshold limit of
96%. For event 838, the threshold is 95%.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
208
Events Types
Cluster Events
Cluster out of service
Table 264. Cluster out of service event
Event
Cluster out of service
Event Type
clusterOutOfService
Event Code
843
Severity
Critical
Attribute
"clusterName"="xx"
Displayed on the web
interface
Cluster [{clusterName}] is out of service.
Description
This event occurs when the cluster is out of service.
Auto Clearance
This event triggers the alarm 843, which is auto cleared by the event
code 808.
Initiated moving APs in node to a new cluster
Table 265. Initiated moving APs in node to a new cluster event
Event
Initiated moving APs in node to a new cluster
Event Type
clusterInitiatedMovingAp
Event Code
844
Severity
Informational
Attribute
"nodeName"="xxx”, "clusterName"="xxx"
Displayed on the web
interface
Initiated moving APs in node [{nodeName}] of cluster [{clusterName}] to
a new cluster.
Description
This event occurs when the command to move the APs in the node to
another cluster is received.
NOTE: Events 845, 846 and 847 are not applicable for SZ.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
209
Events Types
Cluster Events
Cluster upload vSZ-D firmware started
Table 266. Cluster upload vSZ-D firmware started event
Event
Cluster upload vSZ-D firmware started
Event Type
clusterUploadVDPFirmwareStart
Event Code
845
Severity
Informational
Attribute
"clusterName"="xx"
Displayed on the web
interface
Starting upload vSZ-D firmware in cluster [{clusterName}]
Description
This event occurs when the cluster starts and uploads vSZ-data plane
firmware.
Cluster upload vSZ-D firmware completed
Table 267. Cluster upload vSZ-D firmware completed event
Event
Cluster upload vSZ-D firmware completed
Event Type
uploadClusterVDPFirmwareSuccess
Event Code
846
Severity
Informational
Attribute
"clusterName"="xxx" "status"="StartTime:yyyy-MM-dd hh:mm:ss,
EndTime:yyyy-MM-dd hh:mm:ss, Duration:hh:mm:ss"
Displayed on the web
interface
Cluster [{clusterName}] upload vSZ-D firmware completed. [{status}]
Description
This event occurs when the cluster upload process of vSZ-data plane
firmware is successful.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
210
Events Types
Cluster Events
Cluster upload vSZ-D firmware failed
Table 268. Cluster upload vSZ-D firmware failed event
Event
Cluster upload vSZ-D firmware failed
Event Type
uploadClusterVDPFirmwareFailed
Event Code
847
Severity
Informational
Attribute
"reason"="xxx", "clusterName"="xxx"
Displayed on the web
interface
Cluster [{clusterName}] upload vSZ-D firmware failed.
Reason:[{reason}].
Description
This event occurs when the cluster upload process of vSZ-data plane
firmware fails.
Cluster upload AP firmware started
Table 269. Cluster upload AP firmware started event
Event
Cluster upload AP firmware started
Event Type
clusterUploadAPFirmwareStart
Event Code
848
Severity
Informational
Attribute
"clusterName"="xxx"
Displayed on the web
interface
Starting upload AP firmware in cluster [{clusterName}]
Description
This event occurs when the cluster upload process to the AP firmware
starts.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
211
Events Types
Cluster Events
Cluster upload AP firmware completed
Table 270. Cluster upload AP firmware completed event
Event
Cluster upload AP firmware completed
Event Type
clusterUploadAPFirmwareSuccess
Event Code
849
Severity
Informational
Attribute
"clusterName"="xxx"
Displayed on the web
interface
Cluster [{clusterName}] upload AP firmware completed.
Description
This event occurs when the cluster upload process to the AP firmware
is successful.
Cluster upload AP firmware failed
Table 271. Cluster upload AP firmware failed event
Event
Cluster upload AP firmware failed
Event Type
clusterUploadAPFirmwareFailed
Event Code
850
Severity
Major
Attribute
"reason"="xxx", "clusterName"="xxx"
Displayed on the web
interface
Cluster [{clusterName}] upload AP firmware failed. Reason:[{reason}].
Description
This event occurs when the cluster upload process to the AP firmware
fails.
Cluster add AP firmware started
Table 272. Cluster add AP firmware started event
Event
Cluster add AP firmware started
Event Type
clusterAddAPFirmwareStart
Event Code
851
Severity
Informational
Attribute
"clusterName"="xxx"
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
212
Events Types
Cluster Events
Table 272. Cluster add AP firmware started event
Displayed on the web
interface
Starting add AP firmware in cluster [{clusterName}]
Description
This event occurs when the cluster add process to the AP firmware
process starts.
Cluster add AP firmware completed
Table 273. Cluster add AP firmware completed event
Event
Cluster add AP firmware completed
Event Type
clusterAddAPFirmwareSuccess
Event Code
852
Severity
Informational
Attribute
"clusterName"="xxx"
Displayed on the web
interface
Cluster [{clusterName}] add AP firmware completed.
Description
This event occurs when the cluster add process to the AP firmware is
successful.
Cluster add AP firmware failed
Table 274. Cluster add AP firmware failed event
Event
Cluster add AP firmware failed
Event Type
clusterAddAPFirmwareFailed
Event Code
853
Severity
Major
Attribute
"reason"="xxx”, "clusterName"="xxx"
Displayed on the web
interface
Cluster [{clusterName}] add AP firmware failed. Reason:[{reason}].
Description
This event occurs when the cluster add process to the AP firmware fails.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
213
Events Types
Cluster Events
Cluster name is changed
Table 275. Cluster name is changed event
Event
Cluster name is changed
Event Type
clusterNameChanged
Event Code
854
Severity
Major
Attribute
"clusterName"="xxx"
Displayed on the web
interface
Cluster name is changed to [{clusterName}]
Description
This event occurs when the cluster node name is modified. By enabling
email and SNMP notification in the controller user interface
(Configuration > System > Event Management) of the event, SNMP
trap and email will be generated on successful cluster-name
modification.
Cluster name change will fail if any node in either a two, three or four
node cluster is out of service. For example, if in a three node cluster, any
one node is powered off or the Ethernet cable is unplugged, cluster
name change will fail.
Configuration backup started
Table 276. Configuration backup started event
Event
Configuration backup started
Event Type
clusterCfgBackupStart
Event Code
860
Severity
Informational
Attribute
"clusterName"="xxx"
Displayed on the web
interface
Cluster [{clusterName}] configuration backup is started.
Description
This event occurs when cluster configuration backup starts.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
214
Events Types
Cluster Events
Configuration backup succeeded
Table 277. Configuration backup succeeded
Event
Configuration backup succeeded
Event Type
clusterCfgBackupSuccess
Event Code
861
Severity
Informational
Attribute
"clusterName"="xxx"
Displayed on the web
interface
Cluster [{clusterName}] configuration backup succeeded.
Description
This event occurs when cluster backup configuration is successful.
Configuration backup failed
Table 278. Configuration backup failed event
Event
Configuration backup failed
Event Type
clusterCfgBackupFailed
Event Code
862
Severity
Major
Attribute
"clusterName"="xxx"
Displayed on the web
interface
Cluster [{clusterName}] configuration backup failed.
Description
This event occurs when backup configuration fails.
Auto Clearance
This event triggers the alarm 862, which is auto cleared by the event
code 861.
Configuration restore succeeded
Table 279. Configuration restore succeeded event
Event
Configuration restore succeeded
Event Type
clusterCfgRestoreSuccess
Event Code
863
Severity
Informational
Attribute
"clusterName"="xxx"
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
215
Events Types
Cluster Events
Table 279. Configuration restore succeeded event
Displayed on the web
interface
Cluster [{clusterName}] configuration restore succeeded.
Description
This event occurs when the cluster restore configuration is successful.
Configuration restore failed
Table 280. Configuration restore failed event
Event
Configuration restore failed
Event Type
clusterCfgRestoreFailed
Event Code
864
Severity
Major
Attribute
"clusterName"="xxx"
Displayed on the web
interface
Cluster [{clusterName}] configuration restore failed.
Description
This event occurs when the restore configuration fails.
Auto Clearance
This event triggers the alarm 864, which is auto cleared by the event
code 863.
AP Certificate Expired
Table 281. AP Certificate Expired event
Event
AP Certificate Expired
Event Type
apCertificateExpire
Event Code
865
Severity
Critical
Attribute
"count"="XXX"
Displayed on the web
interface
[{count}] APs need to update their certificates.
Description
This event occurs when the AP certificate expires.
Auto Clearance
This event triggers the alarm 865, which is auto cleared by the event
code 866.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
216
Events Types
Cluster Events
AP Certificate Updated
Table 282. AP Certificate Updated event
Event
AP Certificate Updated
Event Type
apCertificateExpireClear
Event Code
866
Severity
Informational
Attribute
"clusterName"="xxx"
Displayed on the web
interface
Clear AP certificate expiration alarm.
Description
This event occurs when the AP certificates are updated.
Node IPv6 address added
Table 283. Node IPv6 address added event
Event
Node IPv6 address added
Event Type
nodeIPv6Added
Event Code
2501
Severity
Informational
Attribute
“nodeMac”=“xxx”, “ifName”=“ xx:xx:xx:xx:xx:xx”,
“ip”=“xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Network interface [{networkInterface||ifName}] on node [{nodeName}]
added IPv6 address [{ip}].
Description
This event occurs when the node adds the IPv6 address.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
217
Events Types
Cluster Events
Node IPv6 address deleted
Table 284. Node IPv6 address deleted event
Event
Node IPv6 address deleted
Event Type
nodeIPv6Deleted
Event Code
2502
Severity
Informational
Attribute
“nodeMac”=“xxx”, “ifName”=“ xx:xx:xx:xx:xx:xx”,
“ip”=“xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Network interface [{networkInterface||ifName}] on node [{nodeName}]
deleted IPv6 address [{ip}].
Description
This event occurs when the node deletes the IPv6 address.
NOTE: Refer to Cluster Alarms.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
218
Events Types
Configuration Events
Configuration Events
Following are events related to configuration.
• Configuration updated
• Configuration update failed
• Configuration receive failed
• Incorrect flat file configuration
• Zone configuration preparation failed
• AP configuration generation failed
• End-of-life AP model detected
Configuration updated
Table 285. Configuration updated event
Event
Configuration updated
Event Type
cfgUpdSuccess
Event Code
1007
Severity
Informational
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess”=”cnr” “realm”=”NA”
“processName”=”aut” "SZMgmtIp"="2.2.2.2" “cause”=”detail of the
configuration applied”
Displayed on the web
interface
Configuration [{cause}] applied successfully in [{processName}] process
at {produce.short.name} [{SZMgmtIp}]
Description
This event occurs when the configuration notification receiver (CNR)
process successfully applies the configuration to the modules.
Configuration update failed
Table 286. Configuration update failed event
Event
Configuration update failed
Event Type
cfgUpdFailed
Event Code
1008
Severity
Debug
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
219
Events Types
Configuration Events
Table 286. Configuration update failed event
Attribute
“ctrlBladeMac"="aa:bb:cc:dd:ee:ff" , "srcProcess"="cnr" "realm"="NA"
"processName"="aut" "SZMgmtIp"="x.x.x.x" "cause"="xx"
Displayed on the web
interface
Failed to apply configuration [{cause}] in [{processName}] process at
{produce.short.name} [{SZMgmtIp}].
Description
This event occurs when the CNR receives a negative acknowledgment
when applying the configuration settings to the module. Possible cause
is that a particular process/module is down.
Configuration receive failed
Table 287. Configuration receive failed event
Event
Configuration receive failed
Event Type
cfgRcvFailed
Event Code
1009
Severity
Debug
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess”=”cnr” “realm”=”NA”
"SZMgmtIp"="2.2.2.2" “cause”= ”mention the configuration that is not
received properly”
Displayed on the web
interface
Failed to fetch configuration [{cause}] by CNR in {produce.short.name}
[{SZMgmtIp}].
Description
This event occurs when the CNR receives an error or negative
acknowledgment/improper/incomplete information from the
configuration change notifier (CCN).
Incorrect flat file configuration
Table 288. Incorrect flat file configuration event
Event
Incorrect flat file configuration
Event Type
incorrectFlatFileCfg
Event Code
1012
Severity
Major
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess”=”aut” “realm”=”NA”
"SZMgmtIp"="2.2.2.2" “cause”=”mention the configuration that is not
received properly” “file”=”mention the config file name”
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
220
Events Types
Configuration Events
Table 288. Incorrect flat file configuration event
Displayed on the web
interface
[{srcProcess}] detected an configuration parameter is incorrectly
configured in file [{file}] at {produce.short.name} [{SZMgmtIp}].
Description
This event occurs when any flat file configuration parameter is not
semantically or syntactically correct.
Zone configuration preparation failed
Table 289. Zone configuration preparation failed event
Event
Zone configuration preparation failed
Event Type
zoneCfgPrepareFailed
Event Code
1021
Severity
Major
Attribute
"nodeMac"="50:A7:33:24:E7:90","zoneName"="openZone"
Displayed on the web
interface
Failed to prepare zone [{zoneName}] configuration required by ap
configuration generation
Description
This event occurs when the controller is unable to prepare a zone
configuration required by the AP.
AP configuration generation failed
Table 290. AP configuration generation failed event
Event
AP configuration generation failed
Event Type
apCfgGenFailed
Event Code
1022
Severity
Major
Attribute
"nodeMac"="50:A7:33:24:E7:90","zoneName"="openZone",
"apCfgGenFailedCount"="25"
Displayed on the web
interface
Failed to generate configuration for [{apCfgGenFailedCount}] AP(s)
under zone[{zoneName}].
Description
This event occurs when the controller fails to generate the AP
configuration under a particular zone.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
221
Events Types
Configuration Events
End-of-life AP model detected
Table 291. End-of-life AP model detected event
Event
End-of-life AP model detected
Event Type
cfgGenSkippedDueToEolAp
Event Code
1023
Severity
Major
Attribute
“nodeMac”="50:A7:33:24:E7:90","zoneName"="openZone","model"=
"R300,T300"
Displayed on the web
interface
Detected usage of end-of-life ap model(s)[{model}] while generating
configuration for AP(s) under zone[{zoneName}].
Description
This event occurs when the controller detects the AP model’s end-oflife under a certain zone.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
222
Events Types
Data Plane Events
Data Plane Events
Following are the events related to data plane.
Data plane discovered
Data plane discovery failed
Data plane configuration
updated
Data plane configuration
update failed
Data plane heartbeat lost
Data plane IP address
updated
Data plane updated to a new Data plane status update failed
control plane
Data plane statistics update
failed
Data plane connected
Data plane physical interface
down
Data plane disconnected
Data plane physical interface Data plane packet pool is under low Data plane packet pool is
up
water mark
under critical low water mark
Data plane packet pool is
above high water mark
Data plane core dead
Data plane process restarted
Data plane discovery
succeeded
Data plane managed
Data plane deleted
Data plane license is not
enough
Data plane upgrade started
Data plane upgrading
Data plane upgrade
succeeded
Data plane upgrade failed
Data plane discovered
Table 292. Data plane discovered event
Event
Data plane discovered
Event Type
dpDiscoverySuccess (server side detect)
Event Code
501
Severity
Informational
Attribute
“dpKey”=”xx:xx:xx:xx:xx:xx”, “wsgIP"=”xxx.xxx.xxx.xxx”
Displayed on the web
interface
Data plane [{dpName&&dpKey}] sent a connection request to
{produce.short.name} [{cpName||wsgIP}].
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
223
Events Types
Data Plane Events
Table 292. Data plane discovered event
Description
This event occurs when the data plane successfully connects to the
controller.
Data plane discovery failed
Table 293. Data plane discovery failed event
Event
Data plane discovery failed
Event Type
dpDiscoveryFail (detected on the server side)
Event Code
502
Severity
Informational
Attribute
“dpKey”=”xx:xx:xx:xx:xx:xx”, “wsgIP"=”xxx.xxx.xxx.xxx”
Displayed on the web
interface
Data plane [{dpName&&dpKey}] failed to send a discovery request to
{produce.short.name} [{cpName||wsgIP}].
Description
This event occurs when the data plane fails to connect to the controller.
Data plane configuration updated
Table 294. Data plane configuration updated event
Event
Data plane configuration updated
Event Type
dpConfUpdated
Event Code
504
Severity
Informational
Attribute
"dpKey"="xx:xx:xx:xx:xx:xx", "configID"= "123456781234567"
Displayed on the web
interface
Data plane [{dpName&&dpKey}] updated to configuration [{configID}].
Description
This event occurs when the data plane configuration is updated.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
224
Events Types
Data Plane Events
Data plane configuration update failed
Table 295. Data plane configuration update failed event
Event
Data plane configuration update failed
Event Type
dpConfUpdateFailed
Event Code
505
Severity
Major
Attribute
“dpKey”=”xx:xx:xx:xx:xx:xx”, “configID”=” 123456781234567”
Displayed on the web
interface
Data plane [{dpName&&dpKey}] failed to update to configuration
[{configID}]
Description
This event occurs when the data plane configuration update fails.
Auto Clearance
This event triggers the alarm 501, which is auto cleared by the event
code 504.
Data plane rebooted
NOTE: This event is not applicable for SZ.
Table 296. Data plane rebooted event
Event
Data plane rebooted
Event Type
dpReboot (server side detect)
Event Code
506
Severity
Minor
Attribute
“dpKey”=”xx:xx:xx:xx:xx:xx”,
Displayed on the web
interface
Data plane [{dpName||dpKey}] rebooted
Description
This event occurs when the data plane is rebooted.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
225
Events Types
Data Plane Events
Data plane heartbeat lost
Table 297. Data plane heartbeat lost event
Event
Data plane heartbeat lost
Event Type
dpLostConnection (detected on the server side)
Event Code
507
Severity
Informational
Attribute
“dpKey”=”xx:xx:xx:xx:xx:xx”,
Displayed on the web
interface
Data plane [{dpName&&dpKey}] heartbeat lost.
Description
This event occurs when the data plane heartbeat lost.
Data plane IP address updated
Table 298. Data plane IP address updated event
Event
Data plane IP address updated
Event Type
dpIPChanged
Event Code
508
Severity
Informational
Attribute
“dpKey”=”xx:xx:xx:xx:xx:xx”,
Displayed on the web
interface
Data plane [{dpName&&dpKey}] IP address changed
Description
This event occurs when the IP address of the data plane is modified.
Data plane updated to a new control plane
Table 299. Data plane updated to a new control plane event
Event
Data plane updated to a new control plane
Event Type
dpChangeControlBlade
Event Code
509
Severity
Informational
Attribute
“dpKey”=”xx:xx:xx:xx:xx:xx”, “oldwsgIP”=”xxx.xxx.xxx.xxx”,
“newwsgIP”=”xxx.xxx.xxx.xxx”
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
226
Events Types
Data Plane Events
Table 299. Data plane updated to a new control plane event
Displayed on the web
interface
Data plane [{dpName&&dpKey}] switched from {produce.short.name}
[{oldCpName||oldwsgIP}] to [{cpName||newwsgIP}].
Description
This event occurs when the data plane connects to a new controller
instance.
Data plane status update failed
Table 300. Data plane status update failed event
Event
Data plane status update failed
Event Type
dpUpdateStatusFailed
Event Code
510
Severity
Minor
Attribute
“dpKey”=”xx:xx:xx:xx:xx:xx”, “wsgIP"=”xxx.xxx.xxx.xxx”
Displayed on the web
interface
Data plane [{dpName&&dpKey}] failed to update its status to
{produce.short.name} [{cpName||wsgIP}].
Description
This event occurs when the data plane fails to update its status on the
controller.
Data plane statistics update failed
Table 301. Data plane statistics update failed event
Event
Data plane statistics update failed
Event Type
dpUpdateStatisticFailed
Event Code
511
Severity
Minor
Attribute
“dpKey”=”xx:xx:xx:xx:xx:xx”, “wsgIP"=”xxx.xxx.xxx.xxx”
Displayed on the web
interface
Data plane [{dpName&&dpKey}] failed to update its statistics to
{produce.short.name} [{cpName||wsgIP}].
Description
This event occurs when the data plane fails to update statistics to the
controller.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
227
Events Types
Data Plane Events
Data plane connected
Table 302. Data plane connected event
Event
Data plane connected
Event Type
dpConnected
Event Code
512
Severity
Informational
Attribute
“dpKey”=”xx:xx:xx:xx:xx:xx”, “wsgIP"=”xxx.xxx.xxx.xxx”
Displayed on the web
interface
Data plane [{dpName&&dpKey}] connected to {produce.short.name}
[{cpName||wsgIP}].
Description
This event occurs when the data plane connects to the controller.
Data plane disconnected
Table 303. Data plane disconnected event
Event
Data plane disconnected
Event Type
dpDisconnected
Event Code
513
Severity
Critical
Attribute
“dpKey”=”xx:xx:xx:xx:xx:xx”, “wsgIP"=”xxx.xxx.xxx.xxx”
Displayed on the web
interface
Data plane [{dpName&&dpKey}] disconnected from
{produce.short.name} [{cpName||wsgIP}], Reason: [{reason}].
Description
This event occurs when the data plane disconnects from the controller.
Auto Clearance
This event triggers the alarm 503, which is auto cleared by the event
code 512.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
228
Events Types
Data Plane Events
Data plane physical interface down
Table 304. Data plane physical interface down event
Event
Data plane physical interface down
Event Type
dpPhyInterfaceDown
Event Code
514
Severity
Critical
Attribute
“portID”=”xx”, “dpKey”=”xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Network link of port [{portID}] on data plane [{dpName&&dpKey}] is
down.
Description
This event occurs when the network link of the data plane is down.
Auto Clearance
This event triggers the alarm 504, which is auto cleared by the event
code 515.
Data plane physical interface up
Table 305. Data plane physical interface up event
Event
Data plane physical interface up
Event Type
dpPhyInterfaceUp
Event Code
515
Severity
Informational
Attribute
“portID”=”xx”, “dpKey”=”xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Network link of port [{portID}] on data plane [{dpName&&dpKey}] is up.
Description
This event occurs when the network link of the data plane is UP.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
229
Events Types
Data Plane Events
Data plane packet pool is under low water mark
Table 306. Data plane packet pool is under low water mark event
Event
Data plane packet pool is under low water mark
Event Type
dpPktPoolLow
Event Code
516
Severity
Informational
Attribute
"dpKey"="xx:xx:xx:xx:xx:xx", "id"="x"
Displayed on the web
interface
Pool [{id}] on data plane [{dpName&&dpKey}] is under low-water mark.
Description
This event occurs when the data core packet pool is below the water
mark level.
Auto Clearance
This event triggers the alarm 516, which is auto cleared by the event
code 518.
Data plane packet pool is under critical low water mark
Table 307. Data plane's packet pool is under critical low water mark event
Event
Data plane packet pool is under critical low water mark
Event Type
dpPktPoolCriticalLow
Event Code
517
Severity
Major
Attribute
dpKey="xx:xx:xx:xx:xx:xx", "id"="x"
Displayed on the web
interface
Pool [{id}] on data plane [{dpName&&dpKey}] is under critical low-water
mark.
Description
This event occurs when the data core packet pool reaches the critical
water mark level.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
230
Events Types
Data Plane Events
Data plane packet pool is above high water mark
Table 308. Data plane packet pool is above high water mark event
Event
Data plane packet pool is above high water mark
Event Type
dpPktPoolRecover
Event Code
518
Severity
Informational
Attribute
dpKey="xx:xx:xx:xx:xx:xx", "id"="x"
Displayed on the web
interface
Pool [{id}] on data plane [{dpName&&dpKey}] is above high-water mark
Description
This event occurs when the data plane's packet pool is recovered when
it is above the high-water mark.
Data plane core dead
Table 309. Data plane core dead event
Event
Data plane core dead
Event Type
dpCoreDead
Event Code
519
Severity
Major
Attribute
dpKey="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
Data plane [{dpName&&dpKey}] has dead data core.
Description
This event occurs when one or multiple data core packet pool is lost /
dead.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
231
Events Types
Data Plane Events
Data plane process restarted
Table 310. Data plane process restarted event
Event
Data plane process restarted
Event Type
dpProcessRestart
Event Code
520
Severity
Major
Attribute
dpKey="xx:xx:xx:xx:xx:xx", processName="xxxx"
Displayed on the web
interface
[{processName}] process got re-started on data plane
[{dpName&&dpKey}].
Description
This event occurs when a process in the data plane restarts since it fails
to pass the health check.
NOTE: Event 530 is not applicable for SZ.
Data plane discovery succeeded
Table 311. Data plane discovery succeeded event
Event
Data plane discovery succeeded
Event Type
dpDiscoverySuccess
Event Code
530
Severity
Informational
Attribute
“dpKey”=“xx:xx:xx:xx:xx:xx”, “wsgIP”=“xxx.xxx.xxx.xxx”
Displayed on the web
interface
Data plane [{dpName&&dpKey}] sent a discovery request to
{produce.short.name} [{wsgIP}]
Description
This event occurs when data plane sends a discovery request to the
{produce.short.name} successfully.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
232
Events Types
Data Plane Events
NOTE: Event 532 is not applicable for SZ.
Data plane managed
Table 312. Data plane managed event
Event
Data plane managed
Event Type
dpStatusManaged
Event Code
532
Severity
Informational
Attribute
“dpKey”=“xx:xx:xx:xx:xx:xx”, “wsgIP”=“xxx.xxx.xxx.xxx”
Displayed on the web
interface
Data plane [{dpName&&dpKey}] approved by {produce.short.name}
[{wsgIP}].
Description
This event occurs when data plane is approved by the
{produce.short.name}.
NOTE: Events 537 to 553 are not applicable for SZ.
Data plane deleted
Table 313. Data plane deleted event
Event
Data plane deleted
Event Type
dpDeleted
Event Code
537
Severity
Informational
Attribute
“dpKey”=“xxx.xxx.xxx.xxx”
Displayed on the web
interface
Data plane [{dpName&&dpKey}] deleted.
Description
This event occurs when data plane is deleted.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
233
Events Types
Data Plane Events
Data plane license is not enough
Table 314. Data plane license is not enough event
Event
Data plane license is not enough
Event Type
dpLicenseInsufficient
Event Code
538
Severity
Major
Attribute
"count"=
Displayed on the web
interface
Data plane license is not enough, [{count}] instance of data plane will
be deleted.
Description
This event occurs when data plane licenses are insufficient.
Data plane upgrade started
Table 315. Data plane upgrade started event
Event
Data plane upgrade started
Event Type
dpUpgradeStart
Event Code
550
Severity
Informational
Attribute
“dpKey”=“xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Data plane [{dpName&&dpKey}]started the upgrade process.
Description
This event occurs when data plane starts the upgrade process.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
234
Events Types
Data Plane Events
Data plane upgrading
Table 316. Data plane upgrading event
Event
Data plane upgrading
Event Type
dpUpgrading
Event Code
551
Severity
Informational
Attribute
“dpKey”=“xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Data plane [{dpName&&dpKey}] is upgrading.
Description
This event occurs when data plane starts to upgrade programs and
configuration.
Data plane upgrade succeeded
Table 317. Data plane upgrade succeeded event
Event
Data plane upgrade succeeded
Event Type
dpUpgradeSuccess
Event Code
552
Severity
Informational
Attribute
“dpKey”=“xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Data plane [{dpName&&dpKey}] has been upgraded successfully..
Description
This event occurs when data plane upgrade is successful.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
235
Events Types
Data Plane Events
Data plane upgrade failed
Table 318. Data plane upgrade failed event
Event
Data plane upgrade failed
Event Type
dpUpgradeFailed
Event Code
553
Severity
Major
Attribute
“dpKey”=“xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Data plane [{dpName&&dpKey}] failed to upgrade.
Description
This event occurs when data plane upgrade fails.
Auto Clearance
This event triggers the alarm 553, which is auto cleared by the event
code 552.
•
NOTE: Refer to Data Plane Alarms.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
236
Events Types
IPMI Events
IPMI Events
NOTE: This section is not applicable for vSZ-E.
Following are the events related to IPMIs.
• ipmiThempBB
• ipmiThempP
• ipmiFan
• ipmiFanStatus
• ipmiREThempBB
• ipmiREThempP
• ipmiREFan
• ipmiREFanStatus
ipmiThempBB
Table 319. ipmiThempBB event
Event
ipmiThempBB
Event Type
ipmiThempBB
Event Code
902
Severity
Major
Attribute
"id"="x", "status"="xxxxx", "nodeMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
Baseboard temperature [{status}] on controlplane [{nodeMac}]
Description
This event occurs when the baseboard temperature status is sent.
Baseboard threshold temperatures are in the range of 100 Celsius to
610 Celsius. The default threshold is 610C.
Auto Clearance
This event triggers the alarm 902, which is auto cleared by the event
code 927.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
237
Events Types
IPMI Events
ipmiThempP
Table 320. ipmiThempP event
Event
ipmiThempP
Event Type
ipmiThempP
Event Code
907
Severity
Major
Attribute
"id"="x", "status"="xxxxx", "nodeMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
Processor [{id}] temperature [{status}] on control plane [{nodeMac}]
Description
This event is triggered when the threshold value in the range of 10 to
110 Celsius. The default threshold is 110C.
Auto Clearance
This event triggers the alarm 907, which is auto cleared by the event
code 932.
ipmiFan
Table 321. ipmiFan event
Event
ipmiFan
Event Type
ipmiFan
Event Code
909
Severity
Major
Attribute
"id"="x", "status"="xxxxx", "nodeMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
System fan [{id}] module [{status}] on control plane [{nodeMac}]
Description
This event occurs when the system fan module status is sent.
Auto Clearance
This event triggers the alarm 909, which is auto cleared by the event
code 934.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
238
Events Types
IPMI Events
ipmiFanStatus
Table 322. ipmiFanStatus event
Event
ipmiFanStatus
Event Type
ipmiFanStatus
Event Code
912
Severity
Major
Attribute
"id"="x", "status"="xxxxx", "nodeMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
Fan module [{id}] [{status}] on control plane [{nodeMac}]
Description
This event occurs when the fan module status is sent.
Auto Clearance
This event triggers the alarm 912, which is auto cleared by the event
code 937.
ipmiREThempBB
Table 323. ipmiREThempBB event
Event
ipmiREThempBB
Event Type
ipmiREThempBB
Event Code
927
Severity
Informational
Attribute
"id"="x", "status"="xxxxx", "nodeMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
Baseboard temperature [{status}] on control plane [{nodeMac}].
Description
This event occurs when the baseboard temperature comes back to the
normal status.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
239
Events Types
IPMI Events
ipmiREThempP
Table 324. ipmiREThempP event
Event
ipmiREThempP
Event Type
ipmiREThempP
Event Code
932
Severity
Informational
Attribute
"id"="x", "status"="xxxxx", "nodeMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
Processor [{id}] temperature [{status}] on control plane [{nodeMac}].
Description
This event occurs when the processor temperature comes back to the
normal status.
ipmiREFan
Table 325. ipmiREFan event
Event
ipmiREFan
Event Type
ipmiREFan
Event Code
934
Severity
Informational
Attribute
"id"="x", "status"="xxxxx", "nodeMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
System fan [{id}] module [{status}] on control plane [{nodeMac}].
Description
This event occurs when the system fan module comes back to the
normal status.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
240
Events Types
IPMI Events
ipmiREFanStatus
Table 326. ipmiREFanStatus event
Event
ipmiREFanStatus
Event Type
ipmiREFanStatus
Event Code
937
Severity
Informational
Attribute
"id"="x", "status"="xxxxx", "nodeMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
Fan module [{id}] [{status}] on control plane [{nodeMac}].
Description
This event occurs when the fan module comes back to the normal
status.
NOTE: Refer to IPMI Alarms.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
241
Events Types
Licensing Interface Events
Licensing Interface Events
Following are the events related to licensing.
• License sync succeeded
• License sync failed
• License import succeeded
• License import failed
• License data changed
• License going to expire
• Insufficient license capacity
License sync succeeded
Table 327. License sync succeeded event
Event
License sync succeeded
Event Type
licenseSyncSuccess
Event Code
1250
Severity
Informational
Attribute
"nodeName"="xxxxxxxx",
"licenseServerName"="ruckuswireless.flexeraoperation.com"
Displayed on the web
interface
Node [{nodeName}] sync-up license with license server
[{licenseServerName}] succeeded.
Description
This event occurs when the controller successfully synchronizes the
license data with the license server.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
242
Events Types
Licensing Interface Events
License sync failed
Table 328. License sync failed event
Event
License sync failed
Event Type
licenseSyncFail
Event Code
1251
Severity
Warning
Attribute
"nodeName"="xxxxxxxx",
"licenseServerName"="ruckuswireless.flexeraoperation.com"
Displayed on the web
interface
Node [{nodeName}] sync-up license with license server
[{licenseServerName}] failed.
Description
This event occurs when the controller fails to synchronize the license
data with the license server.
License import succeeded
Table 329. License import succeeded event
Event
License import succeeded
Event Type
licenseImportSuccess
Event Code
1252
Severity
Informational
Attribute
"nodeName"="xxxxxxxx",
Displayed on the web
interface
Node [{nodeName}] import license data succeeded.
Description
This event occurs when the controller successfully imports the license
data
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
243
Events Types
Licensing Interface Events
License import failed
Table 330. License import failed event
Event
License import failed
Event Type
licenseImportFail
Event Code
1253
Severity
Warning
Attribute
"nodeName"="xxxxxxxx",
Displayed on the web
interface
Node [{nodeName}] import license data failed.
Description
This event occurs when the controller fails to imports the license data
License data changed
Table 331. License data changed event
Event
License data changed
Event Type
licenseChanged
Event Code
1254
Severity
Informational
Attribute
"nodeName"="xxxxxxxx"
Displayed on the web
interface
Node [{nodeName}] license data has been changed.
Description
This event occurs when the controller license data is modified.
License going to expire
Table 332. License going to expire event
Event
License going to expire
Event Type
licenseGoingToExpire
Event Code
1255
Severity
Major
Attribute
“nodeName”=“xxx”, “licenseType”=“ xxx”
Displayed on the web
interface
The [{licenseType}] on node [{nodeName}] will expire on
[{associationTime}].
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
244
Events Types
Licensing Interface Events
Table 332. License going to expire event
Description
This event occurs when the validity of the license is going to expire.
Insufficient license capacity
Table 333. Insufficient license capacity event
Event
Insufficient license capacity
Event Type
apConnectionTerminatedDueToInsufficientLicense
Event Code
1256
Severity
Major
Attribute
"licenseType”=“ xxx”
Displayed on the web
interface
Insufficient [{licenseType}] license is detected and it will cause existing
AP connections to terminate.
Description
This event occurs when connected APs are rejected due to insufficient
licenses.
NOTE: Refer to Licensing Interface Alarms.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
245
Events Types
Session Events
Session Events
Following event is related to user equipment TTG session.
• Delete all sessions
Delete all sessions
Table 334. Delete all sessions event
Event
Delete all sessions
Event Type
delAllSess
Event Code
1237
Severity
Minor
Attribute
“mvnoId”=”NA” “ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”
“srcProcess”=”aut” “realm”=”NA" "cause"="Admin Delete"
"SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
All sessions got terminated on {produce.short.name} [{SZMgmtIp}] due
to [{cause}]
Description
This event occurs when all sessions are deleted based on the indicators
received from the controller web Interface or CLI.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
246
Events Types
System Events
System Events
Following are the events related to system log severity.
NOTE: {produce.short.name} refers to SZ or vSZ-E
No LS responses
LS authentication failure
{produce.short.name}
connected to LS
{produce.short.name} failed
to connect to LS
{produce.short.name} received {produce.short.name} sent
passive request
controller information report
{produce.short.name}
received management
request
{produce.short.name} sent AP
info by venue report
{produce.short.name} sent
associated client report
{produce.short.name}
{produce.short.name} forwarded
forwarded calibration request to footfall request to AP
AP
{produce.short.name}
received unrecognized
request
Syslog server reachable
Syslog server unreachable
Syslog server switched
Generate AP config for plane
load rebalance succeeded
Generate AP config for plane load
rebalance failed
FTP transfer
FTP transfer error
File upload
Email sent successfully
Email sent failed
SMS sent successfully
SMS sent failed
Process restart
Service unavailable
Keepalive failure
Resource unavailable
ZD AP migrating
ZD AP migrated
ZD AP rejected
ZD AP migration failed
Database error
Database error
{produce.short.name} sent query
venues report
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
247
Events Types
System Events
No LS responses
Table 335. No LS responses event
Event
No LS responses
Event Type
scgLBSNoResponse
Event Code
721
Severity
Major
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”, “url”=““, “port”=““, “SZMgmtIp”=““
Displayed on the web
interface
Smart Zone [{SZMgmtIp}] no response from LS: url=[{url}], port=[{port}]
Description
This event occurs when the controller does not get a response while
connecting to the location based service.
LS authentication failure
Table 336. LS authentication failure event
Event
LS authentication failure
Event Type
scgLBSAuthFailed
Event Code
722
Severity
Major
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”, “url”=““, “port”=““, “SZMgmtIp”=““
Displayed on the web
interface
{produce.short.name} [{SZMgmtIp}] authentication failed: url=[{url}],
port=[{port}]
Description
This event occurs due to the authentication failure on connecting to the
location based service.
{produce.short.name} connected to LS
Table 337. {produce.short.name} connected to LS event
Event
{produce.short.name} connected to LS
Event Type
scgLBSConnectSuccess
Event Code
723
Severity
Informational
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”, “url”=““, “port”=““, “SZMgmtIp”=““
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
248
Events Types
System Events
Table 337. {produce.short.name} connected to LS event
Displayed on the web
interface
{produce.short.name}[{SZMgmtIp}] connected to LS: url=[{url}],
port=[{port}]
Description
This event occurs when the controller successfully connects to the
location based service.
{produce.short.name} failed to connect to LS
Table 338. {produce.short.name} failed to connect to LS event
Event
{produce.short.name} failed to connect to LS
Event Type
scgLBSConnectFailed
Event Code
724
Severity
Major
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”, “url”=““, “port”=““, “SZMgmtIp”=““
Displayed on the web
interface
{produce.short.name} [{SZMgmtIp}] connection failed to LS: url=[{url}],
port=[{port}]
Description
This event occurs when the controller failed to connect to the location
based service.
Auto Clearance
This event triggers the alarm 724, which is auto cleared by the event
code 723.
{produce.short.name} received passive request
Table 339. {produce.short.name} received passive request event
Event
{produce.short.name} received passive request
Event Type
scgLBSStartLocationService
Event Code
725
Severity
Informational
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx:”, “type”=““, “venue”=““,
“SZMgmtIp”=““, "band"=""
Displayed on the web
interface
{produce.short.name} [{SZMgmtIp}] received Passive Request,
band=[{band}], type=[{type}]
Description
This event occurs when the controller receives a passive request.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
249
Events Types
System Events
{produce.short.name} sent controller information report
Table 340. {produce.short.name} sent controller information report event
Event
{produce.short.name} sent controller information report
Event Type
scgLBSSentControllerInfo
Event Code
727
Severity
Informational
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”, “api”=““, “sw”=““,
“clusterName”=““,”SZMgmtIp”=““
Displayed on the web
interface
{produce.short.name} [{SZMgmtIp}] sent Controller Info Report: mac
=[{mac}], api=[{api}], sw=[{sw}], clusterName =[{clusterName}]
Description
This event occurs when the controller sends the controller information
report.
{produce.short.name} received management request
Table 341. {produce.short.name} received management request event
Event
{produce.short.name} received management request
Event Type
scgLBSRcvdMgmtRequest
Event Code
728
Severity
Informational
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”, “venue”=““,”type”=““, “SZMgmtIp”=““
Displayed on the web
interface
Smart Zone [{SZMgmtIp}] received Management Request:
venue=[{venue}], type=[{type}]
Description
This event occurs when the controller receives the management
request.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
250
Events Types
System Events
{produce.short.name} sent AP info by venue report
Table 342. {produce.short.name} sent AP info by venue report event
Event
{produce.short.name} sent AP info by venue report
Event Type
scgLBSSendAPInfobyVenueReport
Event Code
729
Severity
Informational
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”, “venue”=““,”count”=““,
“SZMgmtIp”=““
Displayed on the web
interface
{produce.short.name}[{SZMgmtIp}] sent AP Info by Venue Report:
venue=[{venue}], count =[{count}]
Description
This event occurs when the controller sends the venue report regarding
AP information.
{produce.short.name} sent query venues report
Table 343. {produce.short.name} sent query venues report event
Event
{produce.short.name} sent query venues report
Event Type
scgLBSSendVenuesReport
Event Code
730
Severity
Informational
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”, “count”=““, “SZMgmtIp”=““
Displayed on the web
interface
Smart Zone [{SZMgmtIp}] sent Query Venues Report: count=[{count}]
Description
This event occurs when the controller sends the query venue report.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
251
Events Types
System Events
{produce.short.name} sent associated client report
Table 344. {produce.short.name} sent associated client report event
Event
{produce.short.name} sent associated client report
Event Type
scgLBSSendClientInfo
Event Code
731
Severity
Informational
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”, “count”=““, “SZMgmtIp”=““, “type”=““
Displayed on the web
interface
{produce.short.name} [{SZMgmtIp}] sent Associated Client Report:
count=[{count}], type=[{type}]
Description
This event occurs when the controller sends the associated client report.
{produce.short.name} forwarded calibration request to
AP
Table 345. {produce.short.name} forwarded calibration request to AP event
Event
{produce.short.name} forwarded calibration request to AP
Event Type
scgLBSFwdPassiveCalReq
Event Code
732
Severity
Informational
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”, “SZMgmtIp”=““,
”apMac”=“xx:xx:xx:xx:xx:xx”, “venue “=““, “interval”=““, “duration “=““,
“band”=““, “count”=““
Displayed on the web
interface
{produce.short.name} [{SZMgmtIp}] forwarded Passive Calibration
Request to [{apName&&apMac}]: venue=[{venue}], interval=[{interval}s],
duration=[{duration}m], band=[{band}], count=[{count}]
Description
This event occurs when the controller sends a forward calibration
request to the AP on its reconnection to the controller.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
252
Events Types
System Events
{produce.short.name} forwarded footfall request to AP
Table 346. {produce.short.name} forwarded footfall request to AP event
Event
{produce.short.name} forwarded footfall request to AP
Event Type
scgLBSFwdPassiveFFReq
Event Code
733
Severity
Informational
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”, “SZMgmtIp”=““,
“apMac”=“xx:xx:xx:xx:xx:xx”, “venue “=““, “interval”=““, “duration “=““,
“band”=“
Displayed on the web
interface
{produce.short.name} [{SZMgmtIp}] forwarded Passive Footfall
Request to [{apName&&apMac}]: venue=[{venue}], interval=[{interval}s]
duration=[{duration}m], band=[{band}]
Description
This event occurs when the controller sends a forward footfall request
to the AP on its reconnection to the controller.
{produce.short.name} received unrecognized request
Table 347. {produce.short.name} received unrecognized request event
Event
{produce.short.name} received unrecognized request
Event Type
scgLBSRcvdUnrecognizedRequest
Event Code
734
Severity
Warning
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”, “type”=““, “length”=““, “SZMgmtIp”=““
Displayed on the web
interface
{produce.short.name} [{SZMgmtIp}] received Unrecognized: length
=[{length}]
Description
This event occurs when the controller receives an unrecognized request.
Syslog server reachable
Table 348. Syslog server reachable event
Event
Syslog server reachable
Event Type
syslogServerReachable
Event Code
750
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
253
Events Types
System Events
Table 348. Syslog server reachable event
Severity
Informational
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”,
“ syslogServerAddress"="xxx.xxx.xxxx.xxx"
Displayed on the web
interface
Syslog server [{syslogServerAddress}] is reachable on
{produce.short.name}.
Description
This event occurs when the syslog server can be reached.
Syslog server unreachable
Table 349. Syslog server unreachable event
Event
Syslog server unreachable
Event Type
syslogServerUnreachable
Event Code
751
Severity
Major
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”,
"syslogServerAddress"="xxx.xxx.xxxx.xxx"
Displayed on the web
interface
Syslog server [{syslogServerAddress}] is unreachable on
{produce.short.name}.
Description
This event occurs when the syslog server is unreachable.
Auto Clearance
This event triggers the alarm 751, which is auto cleared by the event
code 750.
Syslog server switched
Table 350. Syslog server switched event
Event
Syslog server switched
Event Type
syslogServerSwitched
Event Code
752
Severity
Informational
Attribute
“nodeMac”=“xx:xx:xx:xx:xx:xx”, "srcAddress"="xxx.xxx.xxx.xxx”,
"destAddress"="xxx.xxx.xxx.xxx”
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
254
Events Types
System Events
Table 350. Syslog server switched event
Displayed on the web
interface
Syslog server is switched from [{srcAddress}] to [{destAddress}] on
{produce.short.name}.
Description
This event occurs when the syslog server is switched.
Generate AP config for plane load rebalance succeeded
Table 351. Generate AP config for plane load rebalance succeeded event
Event
Generate AP config for plane load rebalance succeeded
Event Type
planeLoadingRebalancingSucceeded
Event Code
770
Severity
Informational
Attribute
Displayed on the web
interface
Generate new AP configs for plane's loading re-balancing succeeded.
Description
This event occurs when the user executes the load of data plane for rebalancing and generates a new AP configuration successfully.
Generate AP config for plane load rebalance failed
Table 352. Generate AP config for plane load rebalance failed event
Event
Generate AP config for plane load rebalance failed
Event Type
planeLoadingRebalancingFailed
Event Code
771
Severity
Informational
Attribute
Displayed on the web
interface
Generate new AP configs for plane's loading re-balancing failed.
Description
This event occurs when the user executes the load of data plane for rebalancing and generation of a new AP configuration fails.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
255
Events Types
System Events
FTP transfer
Table 353. FTP transfer event
Event
FTP transfer
Event Type
ftpTransfer
Event Code
970
Severity
Informational
Attribute
“ip”=”xxx.xxx.xxx.xxx”, “portID”=”xxxx”, “reason”=”xxxxx”
Displayed on the web
interface
File [{reason}] transferred to FTP server [{ip}:{portID}] successfully
Description
This event occurs when a file transfer to the FTP server is successful.
FTP transfer error
Table 354. FTP transfer error event
Event
FTP transfer error
Event Type
ftpTransferError
Event Code
971
Severity
Warning
Attribute
“ip”=”xxx.xxx.xxx.xxx”, “portID”=”xxxx”, “reason”=”xxxxx”
Displayed on the web
interface
File [{reason}] transferred to FTP server [{ip}:{portID}] unsuccessfully
Description
This event occurs when the file transfer to the FTP server fails.
File upload
Table 355. File upload event
Event
File upload
Event Type
fileUpload
Event Code
980
Severity
Informational
Attribute
“ip”=”xxx.xxx.xxx.xxx”,“cause”=”xxxxx”
Displayed on the web
interface
Backup file [{cause}] uploading from [{ip}] failed
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
256
Events Types
System Events
Table 355. File upload event
Description
This event occurs when the backup file upload fails.
Email sent successfully
Table 356. Email sent successfully event
Event
Email sent successfully
Event Type
mailSendSuccess
Event Code
981
Severity
Informational
Attribute
"srcProcess"="xxxxx", "receiver"= "xxxxx",
"nodeMac"="xxxxx","nodeName"="xxxxx","tenantUUID"="xxxxx"
Displayed on the web
interface
[{srcProcess}] sent email to [{receiver}] successfully.
Description
This event occurs when system sends mail successfully.
Email sent failed
Table 357. Email sent failed event
Event
Email sent failed
Event Type
mailSendFailed
Event Code
982
Severity
Warning
Attribute
"srcProcess"="xxxxx","receiver"= "xxxxx", "nodeMac"="xxxxx",
"nodeName"="xxxxx","tenantUUID"="xxxxx"
Displayed on the web
interface
[{srcProcess}] sent email to [{receiver}] failed.
Description
This event occurs when the system fails to send the mail.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
257
Events Types
System Events
SMS sent successfully
Table 358. SMS sent successfully event
Event
SMS sent successfully
Event Type
smsSendSuccess
Event Code
983
Severity
Informational
Attribute
"srcProcess"="xxxxx","receiver"= "xxxxx",
"nodeMac"="xxxxx","nodeName"="xxxxx","tenantUUID"="xxxxx"
Displayed on the web
interface
[{srcProcess}] sent short message to [{receiver}] successfully.
Description
This event occurs when system sends the short message successfully.
SMS sent failed
Table 359. SMS sent failed event
Event
SMS sent failed
Event Type
smsSendFailed
Event Code
984
Severity
Warning
Attribute
"srcProcess"="xxxxx","receiver"= "xxxxx",
"reason"="xxxxx","nodeMac"="xxxxx","nodeName"="xxxxx","tenantU
UID"="xxxxx"
Displayed on the web
interface
[{srcProcess}] sent short message to [{receiver}] failed, reason:
[{reason}].
Description
This event occurs when system fails to send the short message
successfully.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
258
Events Types
System Events
Process restart
Table 360. Process restart event
Event
Process restart
Event Type
processRestart
Event Code
1001
Severity
Major
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess”=”nc” “realm”=”NA”
“processName”=”aut” "SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
[{processName}] process got re-started on {produce.short.name}
[{SZMgmtIp}]
Description
This event occurs when any process crashes and restarts.
Service unavailable
Table 361. Service unavailable event
Event
Service unavailable
Event Type
serviceUnavailable
Event Code
1002
Severity
Critical
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess”=”nc” “realm”=”NA”
“processName”=”aut” "SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
[{processName}] process is not stable on {produce.short.name}
[{SZMgmtIp}]
Description
This event occurs when the process repeatedly restarts and is unstable.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
259
Events Types
System Events
Keepalive failure
Table 362. Keepalive failure event
Event
Keepalive failure
Event Type
keepAliveFailure
Event Code
1003
Severity
Major
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess”=”nc” “realm”=”NA”
“processName”=”aut” "SZMgmtIp"="2.2.2.2"
Displayed on the web
interface
[{srcProcess}] on {produce.short.name} [{SZMgmtIp}] restarted
[{processName}] process
Description
This event occurs when the mon/nc restarts the process due to a keep
alive failure.
Resource unavailable
Table 363. Resource unavailable event
Event
Resource unavailable
Event Type
resourceUnavailable
Event Code
1006
Severity
Critical
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess” = “radiusd”
“realm”=”NA” ”SZMgmtIp” = “3.3.3.3’ “cause” = “resource that is not
available”
Displayed on the web
interface
System resource [{cause}] not available in [{srcProcess}] process at
{produce.short.name} [{SZMgmtIp}]
Description
This event is generated due to unavailability of any other system
resource, such as memcached.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
260
Events Types
System Events
ZD AP migrating
Table 364. ZD AP migrating event
Event
ZD AP migrating
Event Type
zdAPMigrating
Event Code
2001
Severity
Informational
Attribute
"apMac"=" C0:C5:20:12:2B:2C ",
"serialNumber"="501003003033","model"="R700",
“firmware”=“3.2.0.0.x”
Displayed on the web
interface
ZD-AP [{apMac}] / [{serialNumber}] model [{model}] is upgrading with
{produce.short.name} AP firmware version - [{firmware}]
Description
This event occurs when a ZoneDirector AP is upgrading with
{produce.short.name} AP firmware image.
ZD AP migrated
Table 365. ZD AP migrated event
Event
ZD AP migrated
Event Type
zdAPMigrated
Event Code
2002
Severity
Informational
Attribute
"apMac"=" C0:C5:20:12:2B:2C ", "serialNumber"="501003003033",
"model"="R700", “firmware”=“3.2.0.0.x”,
Displayed on the web
interface
ZD-AP [{apMac}] / [{serialNumber}] model [{model}] has been upgraded
with {produce.short.name} AP firmware version - [{firmware}]
Description
This event occurs when a ZoneDirector AP has upgraded its firmware
with the {produce.short.name} AP firmware image.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
261
Events Types
System Events
ZD AP rejected
Table 366. ZD AP rejected event
Event
ZD AP rejected
Event Type
zdAPRejected
Event Code
2003
Severity
Warning
Attribute
"apMac"=" C0:C5:20:12:2B:2C ", "serialNumber"="501003003033",
"model"="R700"
Displayed on the web
interface
ZD-AP [{apMac}] / [{serialNumber}] model [{model}] is not being
upgraded with {produce.short.name} AP firmware because of ACL
setting.
Description
This event occurs when the ZoneDirector AP is not upgraded with
{produce.short.name} AP firmware because of the ACL setting.
ZD AP migration failed
Table 367. ZD AP migration failed event
Event
ZD AP migration failed
Event Type
zdAPMigrationFailed
Event Code
2004
Severity
Major
Attribute
"apMac"=" C0:C5:20:12:2B:2C ",
"serialNumber"="501003003033","model"="R700",
“firmware”=“3.2.0.0.x”
Displayed on the web
interface
ZD-AP [{apMac}] / [{serialNumber}] model [{model}] is failed to upgrade
with {produce.short.name} AP firmware version - [{firmware}]
Description
This event occurs when a ZoneDirector AP fails to upgrade with
[produce.short.name} AP firmware image.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
262
Events Types
System Events
Database error
Table 368. Database error event
Event
Database error
Event Type
cassandraError
Event Code
3001
Severity
Major
Attribute
“ctrlBladeMac”=“aa:bb:cc:dd:ee:ff”,”SZMgmtIp”=“2.2.2.2”
reason=“reason”
Displayed on the web
interface
Database internal error on node [{nodeName}], reason: [{reason}].
Description
This event occurs when internal errors occurs on the database.
Database error
Table 369. Database error event
Event
Database error
Event Type
recoverCassandraError
Event Code
3011
Severity
Informational
Attribute
“nodeName”=“xxx”,”reason”=“recovery reason”
Displayed on the web
interface
Recover database error on node [{nodeName}], reason : [].
Description
This event occurs when the internal errors on the database are fixed.
NOTE: Refer to System Alarms.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
263
Events Types
Threshold Events
Threshold Events
Following are the events related to threshold limits.
• CPU threshold exceeded
• Memory threshold exceeded
• Disk usage threshold exceeded
• CPU threshold back to normal
• Memory threshold back to normal
• Disk threshold back to normal
• License threshold exceeded
• Rate limit threshold surpassed
• Rate limit threshold restored
• Rate limit for TOR surpassed
• The number of users exceed its limit
• The number of devices exceeded its limit
CPU threshold exceeded
Table 370. CPU threshold exceeded event
Event
CPU threshold exceeded
Event Type
cpuThresholdExceeded
Event Code
950
Severity
Critical
Attribute
“nodeName”=”xxx”, “nodeMac”=”xx:xx:xx:xx:xx:xx”, “perc”=”XX”
Displayed on the web
interface
CPU threshold [{perc}%] exceeded on control plane [{nodeName}-C]
Description
This event occurs when the CPU usage exceeds the threshold limit of
80%.
Auto Clearance
This event triggers the alarm 950, which is auto cleared by the event
code 953.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
264
Events Types
Threshold Events
Memory threshold exceeded
Table 371. Memory threshold exceeded event
Event
Memory threshold exceeded
Event Type
memoryThresholdExceeded
Event Code
951
Severity
Critical
Attribute
“nodeName”=”xxx”,“nodeMac”=”xx:xx:xx:xx:xx:xx”, “perc”=”XX”
Displayed on the web
interface
Memory threshold [{perc}%] exceeded on control plane [{nodeName}C].
Description
This event occurs when the memory usage exceeds the threshold limit
of 85%.
Auto Clearance
This event triggers the alarm 951, which is auto cleared by the event
code 954.
Disk usage threshold exceeded
Table 372. Disk usage threshold exceeded event
Event
Disk usage threshold exceeded
Event Type
diskUsageThresholdExceeded
Event Code
952
Severity
Critical
Attribute
“nodeName”=”xxx”,“nodeMac”=”xx:xx:xx:xx:xx:xx”, “perc”=”XX”
Displayed on the web
interface
Disk usage threshold [{perc}%] exceeded on control plane
[{nodeName}-C].
Description
This event occurs when the disk usage exceeds the threshold limit of
80%.
Auto Clearance
This event triggers the alarm 952, which is auto cleared by the event
code 955.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
265
Events Types
Threshold Events
CPU threshold back to normal
Table 373. CPU threshold back to normal event
Event
CPU threshold back to normal
Event Type
cpuThresholdBackToNormal
Event Code
953
Severity
Informational
Attribute
“nodeName”=”xxx”,“nodeMac”=”xx:xx:xx:xx:xx:xx”, “perc”=”XX”
Displayed on the web
interface
CPU threshold [{perc}%] got back to normal on control plane
[{nodeName}-C].
Description
This event occurs when the CPU usage comes back to normal.
Memory threshold back to normal
Table 374. Memory threshold back to normal event
Event
Memory threshold back to normal
Event Type
memoryThresholdBackToNormal
Event Code
954
Severity
Informational
Attribute
“nodeName”=”xxx”,“nodeMac”=”xx:xx:xx:xx:xx:xx”, “perc”=”XX”
Displayed on the web
interface
Memory threshold [{perc}%] got back to normal on control plane
[{nodeName}-C].
Description
This event occurs when the memory usage comes back to normal.
Disk threshold back to normal
Table 375. Disk threshold back to normal event
Event
Disk threshold back to normal
Event Type
diskUsageThresholdBackToNormal
Event Code
955
Severity
Informational
Attribute
“nodeName”=”xxx”,“nodeMac”=”xx:xx:xx:xx:xx:xx”, “perc”=”XX”
Displayed on the web
interface
Disk threshold [{perc}%] got back to normal on control plane
[{nodeName}-C].
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
266
Events Types
Threshold Events
Table 375. Disk threshold back to normal event
Description
This event occurs when the disk usage comes back to normal.
License threshold exceeded
Table 376. License threshold exceeded event
Event
License threshold exceeded
Event Type
licenseThresholdExceeded
Event Code
960
Severity
Critical 90%; Major 80%; Informational 70%;
Attribute
"perc"="xxx", "nodeName"="", "nodeMac"="xx:xx:xx:xx:xx:xx",
licenseType="SG00"
Displayed on the web
interface
[{licenseType}] limit reached at [{perc}%]
Description
This event occurs when the number of user equipment attached to the
system have exceeded the license limit.
Rate limit threshold surpassed
Table 377. Rate limit threshold surpassed event
Event
Rate limit threshold surpassed
Event Type
rateLimitThresholdSurpassed
Event Code
1300
Severity
Major
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess”=”radiusd”
"SZMgmtIp"="2.2.2.2" “aaaSrvIp”=”1.1.1.1” “AAAServerType”=”Auth/
Acct” “MOR”=1000 “THRESHOLD”=”500” “TOR”=”501”
Displayed on the web
interface
Threshold surpassed for AAA Server [{aaaSrvrIp}] and ServerType
[{AAAServerType}]
Description
This event occurs when the rate limit threshold is surpassed. The
threshold limit for this event is dependent of the maximum outstanding
request (MOR) value as configured in the web interface of Authentication
or Accounting Service. For example, if the MOR value is 1000, and
threshold limit is set to 70%, then this event will be raised when total
outstanding requests for this server exceeds the limit of 701.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
267
Events Types
Threshold Events
Rate limit threshold restored
Table 378. Rate limit threshold restored event
Event
Rate limit threshold restored
Event Type
rateLimitThresholdRestored
Event Code
1301
Severity
Informational
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess”=”radiusd”
"SZMgmtIp"="2.2.2.2" “aaaSrvrIp”=”1.1.1.1” “AAAServerType”=”Auth/
Acct” “MOR”=1000 “THRESHOLD”=”500” “TOR”=”501”
Displayed on the web
interface
Threshold restored for AAA Server [{aaaSrvrIp}] and ServerType
[{AAAServerType}]
Description
This event occurs when the rate limit threshold is restored. The threshold
limit for this event is dependent of the maximum outstanding request
(MOR) value as configured in the web interface of Authentication or
Accounting Service. For example, if the MOR value is 1000, and
threshold limit is set to 70%, then this event will be raised when total
outstanding requests for this server is lesser or equal to 700.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
268
Events Types
Threshold Events
Rate limit for TOR surpassed
Table 379. Rate limit for TOR surpassed event
Event
Rate limit for TOR surpassed
Event Type
rateLimitTORSurpassed
Event Code
1302
Severity
Critical
Attribute
“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff” “srcProcess”=”radiusd”
"SZMgmtIp"="2.2.2.2" “aaaSrvrIp”=”1.1.1.1” “AAAServerType”=”Auth/
Acct” “MOR”=1000 “THRESHOLD”=”500” “TOR”=”501”
Displayed on the web
interface
Maximum Outstanding Requests (MOR) surpassed for AAA Server
[{aaaSrvrIp}] and ServerType [{AAAServerType}]. Dropping requests to
be proxied to AAA.
Description
This event occurs when the rate limit for total outstanding requests (TOR)
is surpassed. Threshold limits for this event is dependent of the
maximum outstanding request (MOR) value as configured in the web
interface of Authentication or Accounting Service. For example, if the
MOR value is 1000, and threshold limit is set to 70%, then this event
will be raised when total outstanding requests for this server exceeds
1000.
Auto Clearance
This event triggers the alarm1302, which is auto cleared by the event
code 1301.
The number of users exceed its limit
Table 380. The number of users exceed its limit
Event
The number of users exceed its limit
Event Type
tooManyUsers
Event Code
7001
Severity
Major
Attribute
This event has no attributes.
Displayed on the web
interface
The number of users exceed its limits. The threshold limit for SZ-100 is
114000 and 38000 for vSZ-E.
Description
This event occurs when the number of users exceeds the specified limit.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
269
Events Types
Threshold Events
The number of devices exceeded its limit
Table 381. The number of devices exceeded its limit event
Event
The number of devices exceeded its limit
Event Type
tooManyDevices
Event Code
7002
Severity
Major
Attribute
This event has not attributes.
Displayed on the web
interface
The number of devices exceeded its limit
Description
This event occurs when the number of devices exceeds the specified
limit. The threshold limit for SZ-100 is 342000 and 152000 for vSZ-E.
NOTE: Refer to Threshold Alarms.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
270
Events Types
Tunnel Events - Access Point (AP)
Tunnel Events - Access Point (AP)
Following are the events related to tunnel events on access point.
• Data plane accepted a tunnel request
• Data plane rejected a tunnel request
• Data plane terminated a tunnel
• AP created a tunnel
• AP tunnel disconnected
• AP SoftGRE tunnel fails over primary to secondary
• AP SoftGRE tunnel fails over secondary to primary
• AP SoftGRE gateway reachable
• AP SoftGRE gateway not reachable
• Data plane set up a tunnel
• AP secure gateway association success
• AP is disconnected from secure gateway
• AP secure gateway association failure
Data plane accepted a tunnel request
NOTE: This event is not applicable for vSZ-E.
Table 382. Data plane accepted a tunnel request event
Event
Data plane accepted a tunnel request
Event Type
dpAcceptTunnelRequest
Event Code
601
Severity
Informational
Attribute
“dpKey”=”xx:xx:xx:xx:xx:xx”, “apMac”=”xx:xx:xx:xx:xx:xx”
Displayed on the web
interface
Data plane [{dpName&&dpKey}] accepted a tunnel request from AP
[{apName&&apMac}].
Description
This event occurs when the data plane accepts a tunnel request from
the AP.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
271
Events Types
Tunnel Events - Access Point (AP)
Data plane rejected a tunnel request
NOTE: This event is not applicable for vSZ-E.
Table 383. Data plane rejected a tunnel request event
Event
Data plane rejected a tunnel request
Event Type
dpRejectTunnelRequest
Event Code
602
Severity
Informational
Attribute
“dpKey”=”xx:xx:xx:xx:xx:xx”, “apMac”=”xx:xx:xx:xx:xx:xx”,
“reason”=”xxxxxxxxxxxxx”
Displayed on the web
interface
Data plane [{dpName&&dpKey}] rejected a tunnel request from AP
[{apName&&apMac}] because of reason [{reason}].
Description
This event occurs when the data plane rejects a tunnel request from the
AP.
Data plane terminated a tunnel
NOTE: This event is not applicable for vSZ-E.
Table 384. Data plane terminated a tunnel event
Event
Data plane terminated a tunnel
Event Type
dpTearDownTunnel
Event Code
603
Severity
Informational
Attribute
“dpKey”=”xx:xx:xx:xx:xx:xx”, “apMac”=”xx:xx:xx:xx:xx:xx”,
“reason”=”xx”
Displayed on the web
interface
Data plane [{dpName&&dpKey}] terminated a tunnel from AP
[{apName&&apMac}]. Reason: [{reason}]
Description
This event occurs when the data plane terminates a tunnel from the AP.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
272
Events Types
Tunnel Events - Access Point (AP)
AP created a tunnel
NOTE: This event is not applicable for vSZ-E.
Table 385. AP created a tunnel event
Event
AP created a tunnel
Event Type
apBuildTunnelSuccess
Event Code
608
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "dpIP"="xxx.xxx.xxx.xxx",
Displayed on the web
interface
AP [{apName&&apMac}] created a tunnel to data plane [{dpIP}].
Description
This event occurs when AP creates a tunnel to the data plane.
AP tunnel disconnected
NOTE: This event is not applicable for vSZ-E.
Table 386. AP tunnel disconnected event
Event
AP tunnel disconnected
Event Type
apTunnelDisconnected
Event Code
610
Severity
Informational
Attribute
“apMac”=”xx:xx:xx:xx:xx:xx”, “dpIP”=”xxx.xxx.xxx.xxx”,
“reason”=”xxxxx”
Displayed on the web
interface
AP [{apName&&apMac}] disconnected from data plane [{dpIP}].
Reason: [{reason}]
Description
This event occurs when AP disconnects from the data plane.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
273
Events Types
Tunnel Events - Access Point (AP)
AP SoftGRE tunnel fails over primary to secondary
Table 387. AP SoftGRE tunnel fails over primary to secondary event
Event
AP SoftGRE tunnel fails over primary to secondary
Event Type
apSoftGRETunnelFailoverPtoS
Event Code
611
Severity
Warning
Attribute
“apMac"="xx:xx:xx:xx:xx:xx", "primaryGRE"="xxx.xxx.xxx.xxx",
"secondaryGRE"="xxx.xxx.xxx.xxx"
Displayed on the web
interface
AP [{apName&&apMac}] fails over from primaryGRE [{primaryGRE}] to
secondaryGRE[{secondaryGRE}].
Description
This event occurs when AP moves from a primary to a secondary GRE.
AP SoftGRE tunnel fails over secondary to primary
Table 388. AP SoftGRE tunnel fails over secondary to primary event
Event
AP SoftGRE tunnel fails over secondary to primary
Event Type
apSoftGRETunnelFailoverStoP
Event Code
612
Severity
Warning
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "primaryGRE"="xxx.xxx.xxx.xxx",
"secondaryGRE"="xxxx"
Displayed on the web
interface
AP [{apName&&apMac}] fails over from
secondaryGRE[{secondaryGRE}] to primaryGRE[{primaryGRE}].
Description
This event occurs when AP moves from a secondary to a primary GRE.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
274
Events Types
Tunnel Events - Access Point (AP)
AP SoftGRE gateway reachable
Table 389. AP SoftGRE gateway reachable event
Event
AP SoftGRE gateway reachable
Event Type
apSoftGREGatewayReachable
Event Code
613
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx", "softgreGW"="xxx.xxx.xxx.xxx",
"softgreGWAddress"="xxxx"
Displayed on the web
interface
AP [{apname&&apMac}] is able to reach [{softgreGW}]
[{softgreGWAddress}] successfully
Description
This event occurs when AP builds a soft GRE tunnel successfully.
AP SoftGRE gateway not reachable
Table 390. AP SoftGRE gateway not reachable event
Event
AP SoftGRE gateway not reachable
Event Type
apSoftGREGatewayNotReachable
Event Code
614
Severity
Critical
Attribute
"apMac"="xx:xx:xx:xx:xx:xx",
"softGREGatewayList"="xxx.xxx.xxx.xxx"
Displayed on the web
interface
AP [{apName&&apMac}] is unable to reach the following gateways:
[{softGREGatewayList}].
Description
This event occurs when AP fails to build a soft GRE tunnel either on the
primary or the secondary GRE.
Auto Clearance
This event triggers the alarm 614, which is auto cleared by the event
code 613.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
275
Events Types
Tunnel Events - Access Point (AP)
Data plane set up a tunnel
NOTE: This event is not applicable for vSZ-E.
Table 391. Data plane set up a tunnel event
Event
Data plane set up a tunnel
Event Type
dpSetUpTunnel
Event Code
627
Severity
Informational
Attribute
"dpKey"="xx:xx:xx:xx:xx:xx", "apMac"="xx:xx:xx:xx:xx:xx"
Displayed on the web
interface
Data plane [{dpName&&dpKey}] set up a tunnel from AP
[{apName&&apMac}].
Description
This event occurs when the data plane sets up a tunnel from the AP.
AP secure gateway association success
Table 392. AP secure gateway association success event
Event
AP secure gateway association success
Event Type
ipsecTunnelAssociated
Event Code
660
Severity
Informational
Attribute
"apMac"="xx:xx:xx:xx:xx:xx","ipsecGWAddress"="x.x.x.x"
Displayed on the web
interface
AP [{apName&&apMac}] is able to reach secure gateway
[{ipsecGWAddress}] successfully.
Description
This event occurs when the AP is able to reach the secure gateway
successfully.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
276
Events Types
Tunnel Events - Access Point (AP)
AP is disconnected from secure gateway
Table 393. AP is disconnected from secure gateway event
Event
AP is disconnected from secure gateway
Event Type
ipsecTunnelDisassociated
Event Code
661
Severity
Major
Attribute
"apMac"="xx:xx:xx:xx:xx:xx","ipsecGWAddress"="x.x.x.x"
Displayed on the web
interface
AP [{apName&&apMac}] is disconnected from secure gateway
[{ipsecGWAddress}].
Description
This event occurs when the AP is disconnected from secure gateway.
AP secure gateway association failure
Table 394. AP secure gateway association failure event
Event
AP secure gateway association failure
Event Type
ipsecTunnelAssociateFailed
Event Code
662
Severity
Major
Attribute
"apMac"="xx:xx:xx:xx:xx:xx","ipsecGWAddress"="x.x.x.x"
Displayed on the web
interface
AP [{apName&&apMac}] is unable to establish secure gateway with
[{ipsecGWAddress}].
Description
This event occurs when the AP is unable to reach the secure gateway.
Auto Clearance
This event triggers the alarm 662, which is auto cleared by the event
code 660.
•
NOTE: Refer to Tunnel Alarms - Access Point.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
277
Events Types
Tunnel Events - Data Plane
Tunnel Events - Data Plane
NOTE: Events 615, 616, 617, 620, 622, 624 and 625 are not applicable for SZ.
Following are the events related to tunnel events on the data plane.
• DP sGRE GW unreachable
• DP sGRE keep alive timeout
• DP sGRE GW inactive
• DP DHCPRelay no response
• DP DHCPRelay failover
• DP sGRE new tunnel
• DP sGRE keepalive recovery
• DP DHCPRelay response recovery
• DP sGRE GW reachable
• DP sGRE GW active
DP sGRE GW unreachable
Table 395. DP sGRE GW unreachable event
Event
DP sGRE GW unreachable
Event Type
dpSgreGWUnreachable
Event Code
615
Severity
Informational
Attribute
"dpKey"="xx:xx:xx:xx:xx:xx", "gatewayIP"="x.x.x.x"
Displayed on the web
interface
Data plane [{dpName&&dpKey}] detected Core Gateway [{GatewayIP}]
is unreachable.
Description
This event occurs when the dataplane detects that a core network
gateway is unreachable.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
278
Events Types
Tunnel Events - Data Plane
DP sGRE keep alive timeout
Table 396. DP sGRE keep alive timeout event
Event
DP sGRE keep alive timeout
Event Type
dpSgreKeepAliveTimeout
Event Code
616
Severity
Informational
Attribute
"dpKey"="xx:xx:xx:xx:xx:xx", "gatewayIP"="x.x.x.x
Displayed on the web
interface
Data plane [{dpName&&dpKey}] detected KeepAlive packet to Core
Gateway [{GatewayIP}] is lost due to timeout
Description
This event occurs when the data plane detects that a keep alive packet
to the core network gateway is lost due to a timeout.
DP sGRE GW inactive
Table 397. DP sGRE GW inactive event
Event
DP softGRE GW inactive
Event Type
dpSgreGWInact
Event Code
617
Severity
Informational
Attribute
"dpKey"="xx:xx:xx:xx:xx:xx", "gatewayIP"="x.x.x.x
Displayed on the web
interface
Data plane [{dpName&&dpKey}] detected [{GatewayIP}] is inactive
because there is no RX traffic
Description
This event occurs when the data plane detects that a core network
gateway is inactive.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
279
Events Types
Tunnel Events - Data Plane
DP DHCPRelay no response
Table 398. DP DHCPRelay no response event
Event
DP DHCPRelay no response
Event Type
dpDhcpRelayNoResp
Event Code
618
Severity
Informational
Attribute
"dpKey"="xx:xx:xx:xx:xx:xx", "dhcpIP"="x.x.x.x"
Displayed on the web
interface
Data plane [{dpName&&dpKey}] detected no response from DHCP
server [{dhcpIP}] for a while
Description
This event occurs when the data plane does not get a a response from
the DHCP server.
DP DHCPRelay failover
Table 399. DP DHCPRelay failover event
Event
DP DHCPRelay failover
Event Type
dpDhcpRelayFailOver
Event Code
619
Severity
Informational
Attribute
"dpKey"="xx:xx:xx:xx:xx:xx", "preDhcpIP"="x.x.x.x",
"curDhcpIP"="x.x.x.x"
Displayed on the web
interface
Data plane [{dpName&&dpKey}] detected DHCP server fail-over from
[preDhcpIP}] to [{curDhcpIP}]
Description
This event occurs when the data plane detects a DHCP server relay fall
over.
DP sGRE new tunnel
Table 400. DP sGRE new tunnel event
Event
DP sGRE new tunnel
Event Type
dpSgreNewTunnel
Event Code
620
Severity
Informational
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
280
Events Types
Tunnel Events - Data Plane
Table 400. DP sGRE new tunnel event
Attribute
"dpKey"="xx:xx:xx:xx:xx:xx", "greType"="L2oGRE, L3oGRE",
"apIpAddress"="x.x.x.x"
Displayed on the web
interface
Data plane [{dpName&&dpKey}] established a [{greType}] tunnel with
AP[{apIP}].
Description
This event occurs when the data plane establishes a tunnel with AP.
DP sGRE keepalive recovery
Table 401. DP sGRE keepalive recovery event
Event
DP sGRE keepalive recovery
Event Type
dpSgreKeepAliveRecovery
Event Code
622
Severity
Informational
Attribute
"dpKey"="xx:xx:xx:xx:xx:xx", "gatewayIP"="x.x.x.x"
Displayed on the web
interface
Data plane [{dpName&&dpKey}] detected KeepAlive packet to Core
Gateway [{gatewayIP}] is now responsive.
Description
The event occurs when the core gateway resumes answering to
keepalive.
DP DHCPRelay response recovery
Table 402. DP DHCPRelay response recovery event
Event
DP DHCPRelay response recovery
Event Type
dpDhcpRelayRespRecovery
Event Code
623
Severity
Informational
Attribute
"dpKey"="xx:xx:xx:xx:xx:xx", "dhcpIP"="x.x.x.x"
Displayed on the web
interface
Data plane [{dpName&&dpKey}] detected DHCP server [{dhcpIP}] is
now responsive.
Description
This event occurs when the DHCP server resumes to answer the relay
request from data plane.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
281
Events Types
Tunnel Events - Data Plane
DP sGRE GW reachable
Table 403. DP sGRE GW reachable event
Event
DP sGRE GW reachable
Event Type
dpSgreGWReachable
Event Code
624
Severity
Informational
Attribute
"dpKey"="xx:xx:xx:xx:xx:xx", "gatewayIP"="x.x.x.x"
Displayed on the web
interface
Data plane [{dpName&&dpKey}] detected Core Gateway [{gatewayIP}]
is now reachable
Description
This event occurs when the core gateway is reachable.
DP sGRE GW active
Table 404. DP sGRE GW active event
Event
DP sGRE GW active
Event Type
dpSgreGWAct
Event Code
625
Severity
Informational
Attribute
"dpKey"="xx:xx:xx:xx:xx:xx", "gatewayIP"="x.x.x.x"
Displayed on the web
interface
Data plane [{dpName&&dpKey}] detected [{gatewayIP}] is now active
Description
This event occurs when core gateway changes to an active mode.
NOTE: Refer to Tunnel Alarms - Access Point.
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
282
Index
A
accounting alarms 43
accounting server not reachable 43, 111
accSrvrNotReachable 43, 111
ad server unreachable 45
ad/LDAP connected successfully 164
ad/ldap connectivity failure 62
ad-hoc network device 124
ad-hoc-networkRogueAPDetecte 124
adServerUnreachable 45
alarm 37, 38
alarm and event management 37
ap account message drop while no accounting start message 113
ap accounting response while invalid config 112
AP Brownout 147
ap cable modem interface down 59, 147
ap cable modem power-cycled by user
148
ap cable modem set to factory default by
user 152
ap cable modem soft-rebooted by user
152
ap capacity reached 150
ap capacity recovered 151
ap certificate expired 83, 216
ap certificate updated 217
ap change control plane 144
ap channel updated 143
ap channel updated dfs detected a radar
144
ap client load balancing limit reached 149
ap client load balancing limit recovered
149
ap communication alarms 49
ap communication events 115, 161
ap configuration generation failed 85, 221
ap configuration update failed 50, 119
ap configuration updated 119
ap connected 145
ap connected to ls 126
ap country code updated 143
ap created a tunnel 273
ap deleted 58, 145
AP disconnected 141
ap disconnected 58
ap discovery succeeded 115
aP failed to connect to LS 56
ap failed to connect to ls 127
ap firmware update failed 52, 117
ap firmware updated 117
ap heartbeat lost 146
ap illegal to change country code 121
ap ip address updated 142
ap is disconnected from secure gateway
108, 277
ap managed 116
ap mesh events 130
ap pre-provision model mismatched 51,
120
ap rebooted by system 57, 141
ap rebooted by user 140
ap received passive calibration request
128
ap received passive footfall request 129
AP received unrecognized request 129
ap rejected 49, 116
ap reset to factory default settings 142
ap secure gateway association failure 277
ap secure gateway association success
276
ap smart monitor turn off wlan 148
ap softgre gateway not reachable 108,
275
ap softgre gateway reachable 275
ap softgre tunnel fails over primary to secondary 274
ap softgre tunnel fails over secondary to
primary 274
ap started location service 127
ap state change alarms 57
ap state change events 140
ap stopped location service 128
ap swap model mismatched 50, 120
ap tagged as critical 146
ap tunnel disconnected 273
ap USB software package download failed
161
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
283
Index
ap USB software package downloaded
161
ap WLAN oversubscribed 53
ap wlan oversubscribed 121
ap wlan state changed 150
apAcctMsgDropNoAcctStartMsg 113
apAcctRespWhileInvalidConfig 112
apBrownout 147
apBuildTunnelSuccess 273
apCapacityReached 150
apCapacityRecovered 151
apCertificateExpire 83, 216
apCertificateExpireClear 217
apCfgGenFailed 85, 221
apChangeControlBlade 144
apChannelChanged 143
apCLBlimitReached 149
apCLBlimitRecovered 149
apConfApplying 118
apConfUpdated 119
apConfUpdateFailed 50, 119
apConnected 145
apConnectionTerminatedDueToInsufficientLicense 245
apCountryCodeChanged 143
apDeleted 145
apDfsRadarEvent 144
apDiscoverySuccess 115
apFirmwareApplying 118
apFirmwareUpdated 117
apFirmwareUpdateFailed 52, 117
apHeartbeatLost 146
apIPChanged 142
apLBSAuthFailed 55, 126
apLBSConnectFailed 56, 127
apLBSConnectSuccess 126
apLBSNoResponses 54, 125
apLBSRcvdPassiveCalReq 128
apLBSRcvdPassiveFFReq 129
apLBSRcvdUnrecognizedRequest 129
apLBSStartLocationService 127
apLBSStopLocationService 128
apModelDiffWithPreProvConfig 51, 71,
120, 194
apModelDiffWithSwapOutAP 50, 120
apP cable modem interface up 151
apRebootBySystem 57, 141
apSoftGREGatewayNotReachable 108,
275
apSoftGREGatewayReachable 275
apSoftGRETunnelFailoverPtoS 274
apSoftGRETunnelFailoverStoP 274
apStatusManaged 116
apStatusRejected 49, 116
apTaggedAsCritical 146
apTunnelDisconnected 273
apUsbSoftwarePackageDownloaded 161
apUsbSoftwarePackageDownloadFailed
161
apWlanOversubscribed 53, 121
apWLANStateChanged 150
authentication alarms 60
authentication events 162
authentication failed over to secondary
61, 162
authentication fallback to primary 61, 163
authentication server not reachable 60,
162
authFailedOverToSecondary 61, 162
authFallbackToPrimary 61, 163
authorization events 168
authSrvrNotReachable 60, 162
auto cleared 44, 45, 46, 47, 48, 49, 50,
52, 56, 58, 59, 67, 69, 70, 71, 72, 73,
74, 75, 76, 77, 80, 81, 82, 83, 87, 88,
92, 93, 94, 98, 99, 103, 104, 106,
108, 109, 116, 117, 119, 127, 141,
147, 154, 155, 156, 157, 158, 159,
160, 175, 192, 193, 194, 196, 198,
201, 202, 204, 209, 215, 216, 225,
228, 229, 230, 236, 237, 238, 239,
249, 254, 264, 265, 269, 275, 277
aystem alarms 97
B
backupClusterFailed 72, 195
backupClusterSuccess 195
bind fails with AD/LDAP 63
bind success with LDAP 63, 165
C
c2d configuration failed 178
c2dCfgFailed 178
cableModemDown 147
cableModemUp 151
cassandraError 263
cfgGenSkippedDueToEolAp 222
cfgRcvFailed 220
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
284
Index
cfgUpdFailed 219
cfgUpdSuccess 219
client authentication failed 180
client authorization failed 183
client authorization successfully 182
client blocked 185
client connection timed out 181
client disconnected 181
client events 179
client failed to join 180
client grace period 186
client joined 180
client logged out 184
client roaming 184
client roaming disconnected 185
client session expired 183
clientAuthFailure 180
clientAuthorization 182
clientAuthorizationFailure 183
clientBlockByDeviceType 185
clientDisconnect 181
clientGracePeriod 186
clientInactivityTimeout 181
clientJoin 180
clientJoinFailure 180
clientRoaming 184
clientSessionExpiration 183
clientSessionLogout 184
cluster add AP firmware completed 213
Cluster add AP firmware failed 81
cluster add AP firmware failed 213
cluster add AP firmware started 212
cluster application started 199
cluster application stopped 75, 198
cluster back in service 195
cluster backup completed 195
cluster backup failed 72, 195
cluster backup started 199
cluster created successfully 191
cluster events 190
cluster in maintenance state 71, 194
cluster leader changed 200
cluster name is changed 214
cluster node rebooted 77, 203
cluster node shut down 77
cluster node shutdown 204
cluster node upgrade completed 197
cluster out of service 80, 209
cluster remove node started 207
cluster restore completed 196
cluster restore failed 73, 196
Cluster upgrade failed 74
cluster upgrade failed 198
cluster upgrade started 200
cluster upload AP firmware completed
212
cluster upload AP firmware failed 80, 212
cluster upload AP firmware started 211
cluster upload completed 205
cluster upload failed 206
cluster upload started 205
cluster upload vSZ-D firmware failed 211
clusterAddAPFirmwareFailed 81, 213
clusterAddAPFirmwareStart 212
clusterAddAPFirmwareSuccess 213
clusterAppStart 199
clusterAppStop 75, 198
clusterBackToInService 195
clusterBackupStart 199
clusterCfgBackupFailed 81, 215
clusterCfgBackupStart 214
clusterCfgBackupSuccess 215
clusterCfgRestoreFailed 82, 216
clusterCfgRestoreSuccess 215
clusterCreatedSuccess 191
clusterLeaderChanged 200
clusterNameChanged 214
clusterOutOfService 80, 209
clusterUpgradeStart 200
clusterUploadAPFirmwareFailed 80, 212
clusterUploadAPFirmwareStart 211
clusterUploadAPFirmwareSuccess 212
cmRebootByUser 148
cmResetByUser 152
cmResetFactoryByUser 152
coA authorize only access reject 172
coA nack sent to AAA 171
coA NAK received NAS 172
coA received from AAA 170
coA RWSG MWSG notification failure 173
coA sent NAS 171
coaAuthorizeOnlyAccessReject 172
coaNackSntAAA 171
coaNakRcvdNas 172
coaRcvdAAA 170
coaRWSGMWSGNotifFailure 173
coaSentNas 171
configuration 84
Configuration backup failed 81
configuration backup failed 215
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
285
Index
configuration backup started 214
configuration backup succeeded 215
configuration events 219
configuration receive failed 220
configuration restore failed 82, 216
configuration restore succeeded 215
configuration update failed 219
configuration update success 219
configuration-change events 37
connectedToDblade 174
control and data plane 67, 174
cpu threshold back to normal 266
cpu threshold exceeded 103, 264
cpuThresholdBackToNormal 266
cpuThresholdExceeded 103, 264
D
data plane 87, 223
data plane accepted a tunnel request 271
data plane configuration update failed 87,
225
data plane configuration updated 224
data plane connected 228
data plane core dead 231
data plane deleted 233
data plane disconnected 88, 228
data plane discovered 223
data plane discovery failed 224
data plane discovery succeeded 232
data plane heartbeat lost 226
data plane ip address updated 226
data plane license is not enough 89, 234
data plane managed 233
data plane packet pool is above high water
mark 231
data plane packet pool is under critical low
water mark 230
data plane packet pool is under low water
mark 230
data plane physical interface down 88,
229
data plane physical interface up 229
data plane process restarted 89, 232
data plane rebooted 225
data plane rejected a tunnel request 272
data plane set up a tunnel 276
data plane statistics update failed 227
data plane status update failed 227
data plane terminated a tunnel 272
data plane updated to a new control plane
226
data plane upgrade failed 90, 236
data plane upgrade started 234
data plane upgrade succeeded 235
data plane upgrading 235
database error 263
datablade alarms 87
debug 38
delAllSess 246
delete all sessions 246
disk threshold back to normal 266
disk usage exceed threshold 78, 208
disk usage threshold exceeded 104, 265
diskUsageExceed 78, 208
diskUsageThresholdExceeded 104, 265
dm nack received from NAS 170
dm nack sent to AAA 169
dm received from AAA 168
dm sent to NAS 169
dmNackRcvdNAS 170
dmNackSntAAA 169
dmRcvdAAA 168
dmSntNAS 169
dp connected 174
dp DHCPRelay failover 280
dp DHCPRelay no response 280
dp dhcprelay response recovery 281
dp sGRE GW active 282
dp sGRE GW reachable 282
dp sGRE GW unreachable 278
dp sGRE keep alive timeout 279
dp sGRE new tunnel 280
dp SoftGRE GW inactive 279
dpAcceptTunnelRequest 271
dpCoreDead 231
dpDeleted 233
dpDhcpRelayFailOver 280
dpDhcpRelayNoResp 280
dpDhcpRelayRespRecovery 281
dpDisconnected 88
dpDiscoverySuccess 232
dpLicenseInsufficient 89, 90, 234
dpP sGRE keepalive recovery 281
dpPhyInterfaceDown 88
dpPktPoolCriticalLow 230
dpPktPoolLow 230
dpPktPoolRecover 231
dpProcessRestart 89, 232
dpRejectTunnelRequest 272
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
286
Index
dpSetUpTunnel 276
dpSgreGWAct 282
dpSgreGWInact 279
dpSgreGWReachable 282
dpSgreGWUnreachable 278
dpSgreKeepAliveRecovery 281
dpSgreKeepAliveTimeout 279
dpSgreNewTunnel 280
dpStatusManaged 233
dpTearDownTunnel 272
dpUpdateStatisticFailed 227
dpUpgradeFailed 236
dpUpgradeStart 234
dpUpgradeSuccess 235
dpUpgrading 235
E
ftp transfer error 256
ftpTransfer 256
ftpTransferError 256
G
generate AP config for plane load rebalance failed 255
generate AP config for plane load rebalance succeeded 255
generation of event and alarm 38
gtpManager (DP) disconnected 67, 175
H
hIP failed over 102
hipFailover 102
email sent failed 257
email sent successfully 257
emapDlinkConnectWithMap 130
emapDlinkDisconnectWithMap 131
emapUlinkConnectWithMap 131
emapUlinkDisconnectWithMap 132
end -of-life AP model detected 86, 222
entire cluster upgraded successfully 197
espAuthServerReachable 156
espAuthServerResolvable 157
espAuthServerUnreachable 46, 157
espAuthServerUnResolvable 47, 158
espDNATServerReachable 158
espDNATServerResolvable 159
espDNATServerUnreachable 47, 159
espDNATServerUnresolvable 160
event 38
event attributes 38
event categories 37
event detail information 38
event severity 38
event source 38
event type 38
I
F
L
failed to connect to LS 98
file upload 256
fileUpload 256
force DHCP disconnected 188
forceDHCPDisconnect 188
ftp transfer 256
ldap server unreachable 45
ldapServerUnreachable 45
license data changed 244
license going to expire 95, 244
license import failed 244
license import succeeded 243
license sync failed 243
incorrect flat file configuration 220
informational 38
insufficient license capacity 245
ipmi alarms 92
ipmi events 237
ipmiFan 93, 238
ipmiFanStatus 94, 239
ipmiREFan 240
ipmiREFanStatus 241
ipmiREThempBB 239
ipmiREThempP 240
ipmiThempBB 92, 237
ipmiThempP 93, 238
ipsecTunnelAssociated 276
ipsecTunnelAssociateFailed 277
ipsecTunnelDisassociated 108, 277
K
keepalive failure 100, 260
keepAliveFailure 100, 260
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
287
Index
license sync succeeded 242
license threshold exceeded 105, 267
licenseChanged 244
licenseGoingToExpire 95, 244
licenseImportFail 244
licenseImportSuccess 243
licenseSyncFail 243
licenseSyncSuccess 242
licenseThresholdExceeded 105, 267
licensing alarms 95
licensing interface events 242
logging events 37
lostCnxnToDblade 67, 175
LS authentication failure 98
lS authentication failure 55
ls authentication failure 126, 248
M
mac-spoofing rogue ap 123
mac-spoofingRogueAPDetected 123
mailSendFailed 257
mailSendSuccess 257
map disconnected 132
map downlink connected 132
map downlink connected to emap 133
map downlink connected to map 138
map downlink disconnected from emap
133
map downlink disconnected from map
139
map uplink connected to emap 134
map uplink connected to map 136
map uplink connected to rap 135
map uplink disconnected from emap 135
mapDisconnected 132
mapDlinkConnected 132
mapDlinkConnectWitheMap 133
mapDlinkConnectWithMap 138
mapDlinkDisconnectWitheMap 133
mapDlinkDisconnectWithMap 139
mapUlinkConnectToeMap 134
mapUlinkConnectToMap 136
mapUlinkConnectToRap 135
mapUlinkDisconnectToeMap 135
memory threshold back to normal 266
memory threshold exceeded 104, 265
memoryThresholdBackToNormal 266
memoryThresholdExceeded 104, 265
Mesh state update to rap no channel 138
mesh state updated to map 136
mesh state updated to map no channel
137
mesh state updated to rap 137
meshStateUpdateToMap 136
meshStateUpdateToMapNoChannel 137
meshStateUpdateToRap 137
meshStateUpdateToRapNoChannel 138
N
new node failed to join 69, 191
new node joined successfully 191
newNodeJoinFailed 69, 191
newNodeJoinSuccess 191
No LS responses 125
no LS responses 54, 97
no ls responses 248
node back in service 207
node bond interface down 75, 201
node bond interface up 201
Node ip address changed 202
node out of service 70, 194
node physical interface down 76, 202
node physical interface up 203
node removal completed 192
node removal failed 70, 192
nodeBondInterfaceDown 75, 201
nodeBondInterfaceUp 201
nodeIPChanged 202
nodeOutOfService 70, 194
nodePhyInterfaceUp 203
nodeShutdown 77, 204
ntp time synchronized 204
ntpTimeSynched 204
number of devices exceeded it’s limit 107
number of users exceeded it’s limit 106
O
onboarding registration failed 187
onboarding registration succeeded 186
onboardingRegistrationFailure 187
onboardingRegistrationSuccess 186
overview 37
P
planeLoadingRebalancingFailed 255
planeLoadingRebalancingSucceeded
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
288
Index
255
process restart 99, 259
processRestart 99, 259
R
racADLDAPBindFail 63
racADLDAPFail 62
racADLDAPSuccess 164
racADNPSFail 64, 165
racADNPSFailToAuthenticate 65, 167
racLDAPFailToFindPassword 63, 165
radius fails to authenticate with AD NPS
server 65, 167
radius fails to connect to AD NPS server
64, 165
radius server reachable 153
radius server unreachable 44, 154
radiusServerUnreachable 44
rap downlink connected to map 134
rap downlink disconnected from map 139
rapDlinkDisconnectWithMap 139
rate limit for MOR surpassed 269
rate limit for TOR surpassed 106
rate limit threshold restored 268
rate limit threshold surpassed 267
rateLimitMORSurpassed 106
rateLimitThresholdRestored 268
rateLimitThresholdSurpassed 267
rateLimitTORSurpassed 269
recoverCassandraError 263
remediation failed 188
remediation succeeded 187
remediationFailure 188
remediationSuccess 187
removeNodeFailed 70, 192
removeNodeSuccess 192
resource unavailable 101, 260
resourceUnavailable 101, 260
restoreClusterFailed 73, 196
restoreClusterSuccess 196
resync NTP time 79, 208
resyncNTPTime 28, 79, 208
rmapDlinkConnectWithMap 134
Rogue AP 122
rogue AP disappeared 124
S
same network rogue ap 123
same-networkRogueAPDetected 123
scgLBSAuthFailed 98, 248
scgLBSConnectFailed 98, 249
scgLBSConnectSuccess 248
scgLBSFwdPassiveCalReq 252
scgLBSFwdPassiveFFReq 253
scgLBSNoResponse 97, 248
scgLBSRcvdMgmtRequest 250
scgLBSRcvdUnrecognizedRequest 253
scgLBSSendAPInfobyVenueReport 251
scgLBSSendClientInfo 252
scgLBSSendVenuesReport 251
scgLBSStartLocationService 249
service unavailable 100, 259
serviceUnavailable 100, 259
sessDeletedAtDblade 176
sessDeleteErrAtDblade 177
session delete at DP failed 177
session deleted at DP 176
session interface events 246
session update at DP failed 176
session updated at DP 175
sessUpdatedAtDblade 175
sessUpdateErrAtDblade 176
smartMonitorTurnOffWLAN 148
smartRoamDisconnect 185
SmartZone 251
SmartZone connected to LS 248
SmartZone failed to connect to LS 249
SmartZone forwarded calibration request
to AP 252
SmartZone forwarded footfall request to
AP 253
SmartZone received management request
250
SmartZone received passive request 249
SmartZone received unrecognized request 253
SmartZone sent AP info by venue report
251
SmartZone sent associated client report
252
SmartZone sent controller information report 250
sms sent failed 258
sms sent successfully 258
smsSendFailed 258
smsSendSuccess 258
ssid-spoofing rogue AP 122
ssid-spoofingRogueAPDetected 122
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
289
Index
syslog server reachable 253
syslog server switched 254
syslog server unreachable 99, 254
syslogServerReachable 253
syslogServerSwitched 254
syslogServerUnreachable 99, 254
system interface events 247
T
threshold alarms 103
threshold events 264
threshold-crossing alerts 37
timestamp 38
tooManyUsers 106
tunnel alarms 108
tunnel events - datablade 278
47, 159
weChat ESP DNAT server unresolvable
160
Z
zD AP Migrated 261
ZD AP Migrating 261
ZD AP Migration Failed 262
zD AP Rejected 262
zdAPMigrated 261
zdAPMigrating 261
zdAPMigrationFailed 262
zdAPRejected 262
zone configuration preparation failed 84,
221
zoneCfgPrepareFailed 84, 85, 221
U
unauthorized COA/DM message dropped
114
unauthorizedCoaDmMessageDropped
114
updating ap configuration 118
updating ap firmware 118
upgradeClusterFailed 74, 198
upgradeClusterNodeSuccess 197
upgradeEntireClusterSuccess 197
uploadClusterVDPFirmwareFailed 211
W
wds device joined 189
wds device left 189
wdsDeviceJoin 189
wdsDeviceLeave 189
wechat ESP authentication server reachable 156
weChat ESP authentication server resolvable 157
WeChat ESP authentication server unreachable 157
weChat ESP authentication server unreachable 46
weChat ESP authentication server unresolvable 47, 158
weChat ESP DNAT server reachable 158
weChat ESP DNAT server resolvable 159
weChat ESP DNAT server unreachable
SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.4.1, 800-71374-001 Rev B
290
Copyright © 2006-2017. Ruckus Wireless, Inc.
350 West Java Dr. Sunnyvale, CA 94089. USA
www.ruckuswireless.com
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.6 Linearized : No Has XFA : No Language : en XMP Toolkit : Adobe XMP Core 5.4-c006 80.159825, 2016/09/16-03:31:08 Creator Tool : FrameMaker 11.0.2 Modify Date : 2017:04:27 14:58:06+05:30 Create Date : 2017:04:27 14:49:59Z Metadata Date : 2017:04:27 14:58:06+05:30 Format : application/pdf Title : SZ™ 100 and vSZ-E™ Alarm and Event Reference Guide for SmartZone 3.4.1 Creator : Ruckus Wireless™, Inc. Description : SZ™ 100 and vSZ-E™ Alarm and Event Reference Guide for SmartZone 3.4.1 Producer : Acrobat Distiller 11.0 (Windows) Document ID : uuid:e16231a3-fdde-4fe8-bf6f-699664ec19a6 Instance ID : uuid:1363d3bd-64d5-4425-9b25-2b45d547fee7 Page Mode : UseOutlines Page Count : 291 Author : Ruckus Wireless™, Inc. Subject : SZ™ 100 and vSZ-E™ Alarm and Event Reference Guide for SmartZone 3.4.1 Warning : [Minor] Ignored duplicate Info dictionaryEXIF Metadata provided by EXIF.tools