Ruckus SZ™ 100 And VSZ E™ Alarm Event Reference Guide For SmartZone 3.5 Smart Zone (GA) (SZ100/v SZ E) Sz100Vsze Guide20170407

User Manual: Ruckus SmartZone 3.5 (GA) Alarm and Event Reference Guide (SZ100/vSZ-E)

Open the PDF directly: View PDF .
Page Count: 346

Download
Open PDF In Browser	View PDF

Ruckus Wireless
SmartZone 100 and
Virtual SmartZone Essentials
™

™

™

Alarm and Event Reference Guide for
SmartZone 3.5

Part Number 800-71290-001 Rev A
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.5, 800-71290-001 Rev A

2

Contents

About This Guide
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Online Training Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

1

Revision History
SmartZone Version 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Deprecated Alarm and Event. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
New Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
New Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
SmartZone Version 3.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
SmartZone Version 3.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
New Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Displayed on the Web Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
New Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
SmartZone Version 3.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
New Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
New Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Event on Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
SmartZone Version 3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
New Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Attribute Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Renamed Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
New Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Severity Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Attribute Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Renamed Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Auto Clearance of Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
SmartZone Version 3.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
New Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
New Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

3

Contents

Re-added Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Renamed Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Deprecated Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
RuckOS Version 3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
New Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Deprecated Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Renamed Alarm Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Renamed Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
New Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Renamed Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

2

Alarm and Event Management
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Alarm and Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Event Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Event Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Generation of Alarm and Event. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3

Alarm Types
Accounting Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Accounting server not reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
AP Authentication Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
RADIUS server unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
LDAP server unreachable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
AD server unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
WeChat ESP authentication server unreachable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
WeChat ESP authentication server unresolvable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
WeChat ESP DNAT server unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
WeChat ESP DNAT server unresolvable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
AP Communication Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
AP rejected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
AP configuration update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
AP swap model mismatched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
AP pre-provision model mismatched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
AP firmware update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
AP WLAN oversubscribed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
AP LBS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
No LS responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
LS authentication failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

4

Contents

AP failed to connect to LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
AP State Change Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
AP rebooted by system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
AP disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
AP deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
AP cable modem interface down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
AP DHCP service failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
AP NAT failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Authentication Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Authentication server not reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Authentication failed over to secondary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Authentication fallback to primary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
AD/LDAP connectivity failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Bind fails with AD/LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Bind success with LDAP, but unable to find clear text password for the user . . . . . . . . 70
RADIUS fails to connect to AD NPS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
RADIUS fails to authenticate with AD NPS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Fails to establish TLS tunnel with AD/LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Control and Data Plane Interface Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
GtpManager (DP) disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Cluster Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
New node failed to join. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Node removal failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Node out of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Cluster in maintenance state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Cluster backup failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Cluster restore failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Cluster upgrade failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Cluster application stopped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Node bond interface down. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Node physical interface down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Cluster node rebooted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Cluster node shut down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Disk usage exceed threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Cluster out of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Cluster upload AP firmware failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Cluster add AP firmware failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Unsync NTP time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Cluster upload KSP file failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

5

Contents

Configuration backup failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Configuration restore failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
AP Certificate Expired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Configuration Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Zone configuration preparation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
AP configuration generation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
End-of-life AP model detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
VLAN configuration mismatch on non DHCP/NAT WLAN . . . . . . . . . . . . . . . . . . . . . . 94
VLAN configuration mismatch on DHCP/NAT WLAN . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Data Plane Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Data plane configuration update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Data plane disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Data plane physical interface down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Data plane process restarted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Data plane license is not enough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Data plane upgrade failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Data plane of data center side fails to connect to the CALEA server. . . . . . . . . . . . . . 100
Data Plane fails to connects to the other data plane. . . . . . . . . . . . . . . . . . . . . . . . . . 101
Data Plane DHCP IP Pool usage rate is 100 percent . . . . . . . . . . . . . . . . . . . . . . . . . 102
IPMI Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
ipmiThempBB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
ipmiThempP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
ipmiFan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
ipmiFanStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Licensing Interface Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
License going to expire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Insufficient license capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
SCI Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Connect to SCI failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
SCI has been disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
SCI and FTP have been disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
System Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
No LS responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
LS authentication failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
{produce.short.name} failed to connect to LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Syslog server unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Process restart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Service unavailable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Keepalive failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

6

Contents

Resource unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
HIP failed over . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
The last one data plane is disconnected zone affinity profile . . . . . . . . . . . . . . . . . . . . 116
Threshold Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
CPU threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Memory threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Disk usage threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
License threshold exceeded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Rate limit for TOR surpassed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
The number of users exceeded its limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
The number of devices exceeded its limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Tunnel Alarms - Access Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
AP softGRE gateway not reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
AP is disconnected from secure gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
AP secure gateway association failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

4

Events Types
Accounting Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Accounting server not reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
AP accounting response while invalid config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
AP account message drop while no accounting start message . . . . . . . . . . . . . . . . . 128
Unauthorized COA/DM message dropped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
AP Communication Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
AP discovery succeeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
AP managed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
AP rejected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
AP firmware updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
AP firmware update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Updating AP firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Updating AP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
AP configuration updated. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
AP configuration update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
AP pre-provision model mismatched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
AP swap model mismatched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
AP WLAN oversubscribed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
AP illegal to change country code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
AP configuration get failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Rogue AP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
SSID-spoofing rogue AP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

7

Contents

Mac-spoofing rogue AP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Same-network rogue AP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Ad-hoc network device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Rogue AP disappeared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
AP LBS Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
No LS responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
LS authentication failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
AP connected to LS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
AP failed to connect to LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
AP started location service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
AP stopped location service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
AP received passive calibration request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
AP received passive footfall request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
AP received unrecognized request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
AP Mesh Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
EMAP downlink connected to MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
EMAP downlink disconnected from MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
EMAP uplink connected to MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
EMAP uplink disconnected from MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
MAP disconnected. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
MAP downlink connected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
MAP downlink connected to EMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
MAP downlink disconnected from EMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
RAP downlink connected to MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
MAP uplink connected to EMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
MAP uplink disconnected from EMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
MAP uplink connected to RAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
MAP uplink connected to MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Mesh state updated to MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Mesh state updated to MAP no channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Mesh state updated to RAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Mesh state update to RAP no channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
MAP downlink connected to MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
MAP downlink disconnected from MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
RAP downlink disconnected from MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
AP State Change Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
AP rebooted by user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
AP rebooted by system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
AP disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

8

Contents

AP IP address updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
AP reset to factory default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
AP channel updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
AP country code updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
AP channel updated because dynamic frequency selection (DFS) detected a radar . . 160
AP change control plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
AP connected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
AP deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
AP heartbeat lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
AP tagged as critical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
AP cable modem interface down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
AP brownout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
AP cable modem power-cycled by user. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
AP smart monitor turn off WLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
AP client load balancing limit reached . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
AP client load balancing limit recovered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
AP WLAN state changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
AP capacity reached . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
AP capacity recovered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
AP cable modem interface up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
AP cable modem soft-rebooted by user. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
AP cable modem set to factory default by user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
AP health high latency flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
AP health low capacity flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
AP health high connection failure flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
AP health high client count flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
AP health high latency clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
AP health low capacity clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
AP health high connection failure clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
AP health high client count clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Primary DHCP AP is down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Primary DHCP AP is up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Secondary DHCP AP is down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Secondary DHCP AP is up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Primary or secondary DHCP AP detects 90% of the configured total IPs . . . . . . . . . . 175
Both primary and secondary DHCP server APs are down . . . . . . . . . . . . . . . . . . . . . 175
AP NAT gateway IP failover detected for particular VLAN pool . . . . . . . . . . . . . . . . . . 176
AP NAT gateway IP fall back detected for particular VLAN pool . . . . . . . . . . . . . . . . . 176
NAT VLAN capacity affected detected by NAT gateway AP at zone due to three (3)

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

9

Contents

consecutive NAT gateway AP IPs are down for particular VLAN pool . . . . . . . . . . . . 177
NAT VLAN capacity restored detected by NAT gateway AP due to (at least) one out of the
three (3) consecutive NAT gateway AP IP were down is now up . . . . . . . . . . . . . . . . 178
AP NAT failure detected by SZ due to three (3) consecutive NAT gateway APs are down
179
AP health high airtime utilization flag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
AP health high airtime utilization clear. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
AP Authentication Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Radius server reachable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Radius server unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
LDAP server reachable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
LDAP server unreachable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
AD server reachable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
AD server unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Wechat ESP authentication server reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
WeChat ESP authentication server unreachable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
WeChat ESP authentication server resolvable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
WeChat ESP authentication server unresolvable . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
WeChat ESP DNAT server reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
WeChat ESP DNAT server unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
WeChat ESP DNAT server resolvable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
WeChat ESP DNAT server unresolvable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
AP USB Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
AP USB software package downloaded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
AP USB software package download failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Authentication Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Authentication server not reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Authentication failed over to secondary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Authentication fallback to primary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
AD/LDAP connected successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
AD/LDAP connectivity failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Bind fails with AD/LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Bind success with LDAP, but unable to find clear text password for the user . . . . . . . 193
RADIUS fails to connect to AD NPS server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
RADIUS fails to authenticate with AD NPS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Successfully established the TLS tunnel with AD/LDAP . . . . . . . . . . . . . . . . . . . . . . . 195
Fails to establish TLS tunnel with AD/LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Authorization Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
DM received from AAA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

10

Contents

DM NACK sent to AAA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
DM sent to NAS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
DM NACK received from NAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
CoA received from AAA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
CoA NACK sent to AAA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
CoA sent NAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
CoA NAK received NAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
CoA authorize only access reject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
CoA RWSG MWSG notification failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Control and Data Plane Interface Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
DP connected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
GtpManager (DP) disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Session updated at DP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Session update at DP failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Session deleted at DP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Session delete at DP failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
C2d configuration failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Client Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Client authentication failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Client joined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Client failed to join . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Client disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Client connection timed out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Client authorization successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Client authorization failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Client session expired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Client roaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Client logged out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Client roaming disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Client blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Client grace period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Onboarding registration succeeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Onboarding registration failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Remediation succeeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Remediation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Force DHCP disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
WDS device joined. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
WDS device left . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Client is blocked because of barring UE rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

11

Contents

Client is unblocked because of barring UE rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Start CALEA mirroring client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Stop CALEA mirroring client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Cluster Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Cluster created successfully. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
New node joined successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
New node failed to join. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Node removal completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Node removal failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Node out of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Cluster in maintenance state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Cluster back in service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Cluster backup completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Cluster backup failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Cluster restore completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Cluster restore failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Cluster node upgrade completed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Entire cluster upgraded successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Cluster upgrade failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Cluster application stopped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Cluster application started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Cluster backup started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Cluster upgrade started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Cluster leader changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Node bond interface down. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Node bond interface up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Node IP address changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Node physical interface down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Node physical interface up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Cluster node rebooted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
NTP time synchronized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Cluster node shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Cluster upload started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Cluster upload completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Cluster upload failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
SSH tunnel switched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Cluster remove node started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Node back in service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Disk usage exceed threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

12

Contents

Cluster out of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Initiated moving APs in node to a new cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Cluster upload vSZ-D firmware started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Cluster upload vSZ-D firmware completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Cluster upload vSZ-D firmware failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Cluster upload AP firmware started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Cluster upload AP firmware completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Cluster upload AP firmware failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Cluster add AP firmware started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Cluster add AP firmware completed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Cluster add AP firmware failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Cluster name is changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Unsync NTP time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Cluster upload KSP file started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Cluster upload KSP file completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Cluster upload KSP file failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Configuration backup started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Configuration backup succeeded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Configuration backup failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Configuration restore succeeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Configuration restore failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
AP Certificate Expired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
AP Certificate Updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Configuration restore started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Upgrade SSTable failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Reindex Elastic Search finished . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Initiated APs contact APR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Node IPv6 address added . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Node IPv6 address deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Configuration Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Configuration updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Configuration update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Configuration receive failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Incorrect flat file configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Zone configuration preparation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
AP configuration generation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
End-of-life AP model detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
VLAN configuration mismatch on non-DHCP/NAT WLAN . . . . . . . . . . . . . . . . . . . . . 257
VLAN configuration mismatch on a DHCP/NAT WLAN . . . . . . . . . . . . . . . . . . . . . . . 258

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

13

Contents

Data Plane Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Data plane discovered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Data plane discovery failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Data plane configuration updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Data plane configuration update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Data plane rebooted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Data plane heartbeat lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Data plane IP address updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Data plane updated to a new control plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Data plane status update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Data plane statistics update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Data plane connected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Data plane disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Data plane physical interface down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Data plane physical interface up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Data plane packet pool is under low water mark . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Data plane packet pool is under critical low water mark . . . . . . . . . . . . . . . . . . . . . . . 267
Data plane packet pool is above high water mark . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Data plane core dead. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Data plane process restarted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Data plane discovery succeeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Data plane managed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Data plane deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Data plane license is not enough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Data plane upgrade started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Data plane upgrading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Data plane upgrade succeeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Data plane upgrade failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Data plane of data center side successfully connects to the CALEA server . . . . . . . . 273
Data plane of data center side fails to connect to the CALEA server. . . . . . . . . . . . . . 274
Data plane successfully connects to the other data plane . . . . . . . . . . . . . . . . . . . . . 274
Data plane fails to connects to the other data plane . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Data plane disconnects to the other data plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Start CALEA mirroring client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Stop CALEA mirroring client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Data plane DHCP IP pool usage rate is 100 percent . . . . . . . . . . . . . . . . . . . . . . . . . 277
Data plane DHCP IP pool usage rate is 80 percent . . . . . . . . . . . . . . . . . . . . . . . . . . 277
IPMI Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
ipmiThempBB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

14

Contents

ipmiThempP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
ipmiFan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
ipmiFanStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
ipmiREThempBB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
ipmiREThempP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
ipmiREFan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
ipmiREFanStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Licensing Interface Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
License sync succeeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
License sync failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
License import succeeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
License import failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
License data changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
License going to expire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Insufficient license capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
SCI Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Connect to SCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Disconnect to SCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Connect to SCI failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
SCI has been disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
SCI and FTP have been disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Session Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Delete all sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
System Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
No LS responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
LS authentication failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
{produce.short.name} connected to LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
{produce.short.name} failed to connect to LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
{produce.short.name} received passive request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
{produce.short.name} sent controller information report. . . . . . . . . . . . . . . . . . . . . . . 294
{produce.short.name} received management request . . . . . . . . . . . . . . . . . . . . . . . . 295
{produce.short.name} sent AP info by venue report . . . . . . . . . . . . . . . . . . . . . . . . . . 295
{produce.short.name} sent query venues report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
{produce.short.name} sent associated client report . . . . . . . . . . . . . . . . . . . . . . . . . . 296
{produce.short.name} forwarded calibration request to AP . . . . . . . . . . . . . . . . . . . . 297
{produce.short.name} forwarded footfall request to AP . . . . . . . . . . . . . . . . . . . . . . . 297
{produce.short.name} received unrecognized request . . . . . . . . . . . . . . . . . . . . . . . . 298
Syslog server reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Syslog server unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

15

Contents

Syslog server switched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Generate AP config for plane load rebalance succeeded . . . . . . . . . . . . . . . . . . . . . . 300
Generate AP config for plane load rebalance failed. . . . . . . . . . . . . . . . . . . . . . . . . . . 300
FTP transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
FTP transfer error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
File upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Email sent successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Email sent failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
SMS sent successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
SMS sent failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Process restart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Service unavailable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Keepalive failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Resource unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Data plane of data center side successfully connects to the CALEA server . . . . . . . . 306
Data plane of data center side fails to connect to the CALEA server. . . . . . . . . . . . . . 306
Data Plane of data center side disconnects to CALEA server . . . . . . . . . . . . . . . . . . . 307
Data plane successfully connects to the other data plane . . . . . . . . . . . . . . . . . . . . . 307
Data plane fails to connects to the other data plane . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Data plane disconnects to the other data plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Start CALEA mirroring client in data plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Stop CALEA mirroring client in data plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Data plane DHCP IP pool usage rate is 100 percent . . . . . . . . . . . . . . . . . . . . . . . . . 310
Data plane DHCP IP pool usage rate is 80 percent . . . . . . . . . . . . . . . . . . . . . . . . . . 310
All data planes in the zone affinity profile are disconnected. . . . . . . . . . . . . . . . . . . . . 311
CALEA UE Matched. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
ZD AP migrating. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
ZD AP migrated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
ZD AP rejected. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
ZD AP migration failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Database error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Database error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Threshold Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
CPU threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Memory threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Disk usage threshold exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
CPU threshold back to normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Memory threshold back to normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Disk threshold back to normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

16

Contents

License threshold exceeded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Rate limit threshold surpassed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Rate limit threshold restored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Rate limit for TOR surpassed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
The number of users exceed its limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
The number of devices exceeded its limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Tunnel Events - Access Point (AP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Data plane accepted a tunnel request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Data plane rejected a tunnel request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Data plane terminated a tunnel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
AP created a tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
AP tunnel disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
AP SoftGRE tunnel fails over primary to secondary . . . . . . . . . . . . . . . . . . . . . . . . . . 326
AP SoftGRE tunnel fails over secondary to primary . . . . . . . . . . . . . . . . . . . . . . . . . . 326
AP SoftGRE gateway reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
AP SoftGRE gateway not reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Data plane set up a tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
AP secure gateway association success . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
AP is disconnected from secure gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
AP secure gateway association failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Tunnel Events - Data Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
DP Core GW unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
DPs GRE keep alive timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
DP Core GW inactive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
DP DHCPRelay no response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
DP DHCPRelay failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
DP sGRE new tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
DP sGRE keepalive recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
DP DHCPRelay response recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
DP Core GW reachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
DP Core GW active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Index

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

17

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.5, 800-71290-001 Rev A

18

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.5, 800-71290-001 Rev A

19

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.5, 800-71290-001 Rev A

20

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.5, 800-71290-001 Rev A

21

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.5
• Part number: 800-71290-001
• Page 60

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

22

Revision History

1

This chapter contains revision history for:
• SmartZone Version 3.5
• 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.5, 800-71290-001 Rev A

23

Revision History
SmartZone Version 3.5

SmartZone Version 3.5
The following are the changes for version 3.5.

Deprecated Alarm and Event
Code

Type

Replaced With

Alarm 835 and Event 837

resyncNTPTime

Alarm and Event 855 unsyncNTPTime

New Alarm
• Description for Alarm 346 is changed.

Alarm Code

Alarm

341

apDHCPServiceFailure

346

apNATFailureDetectedbySZ

855

unsyncNTPTime

858

clusterUploadKspFileFailed

974

csvFtpTransferMaxRetryReached

975

csvDiskThreshholdExceeded

976

csvDiskMaxCapacityReached

1024

apCfgNonDhcpNatWlanVlanConfigMismatch

1025

apCfgDhcpNatWlanVlanConfigMismatch

1258

dpDcToCaleaConnectFail

1261

dpP2PTunnelConnectFail

1265

dpDhcpIpPoolUsageRate100

1267

zoneAffinityLastDpDisconnected

1762

racADLDAPTLSFailed

4003

disabledSciDueToUpgrade

4004

disabledSciDueToUpgrade

4005

disabledSciAndFtpDueToMutuallyExclusive

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

24

Revision History
SmartZone Version 3.5

New Event
Event Code

Event

117

apGetConfigFailed

228

clientBlockByBarringUERule

229

clientUnblockByBarringUERule

328

apHealthLatencyFlag

329

apHealthCapacityFlag

330

apHealthConnectionFailureFlag

331

apHealthClientCountFlag

332

apHealthLatencyClear

333

apHealthCapacityClear

334

apHealthConnectionFailureClear

335

apHealthClientCountClear

336

apDHCPFailoverDetected

337

apDHCPFallbackDetected

338

apSecondaryDHCPAPDown

339

apSecondaryDHCPAPUp

340

apDHCPIPPoolMaxThresholdReached

341

apDHCPServiceFailure

342

apNATFailoverDetected

343

apNATFallbackDetected

344

apNATVlanCapacityAffected

345

apNATVlanCapacityRestored

346

apNATFailureDetectedbySZ

347

apHealthAirUtilizationFlag

348

apHealthAirUtilizationClear

855

unsyncNTPTime

869

Reindex ElasticSearch finished

870

clusterInitContactApr

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

25

Revision History
SmartZone Version 3.5

Event Code

Event

972

csvFtpTransfer

973

csvFtpTransferError

974

csvFtpTransferMaxRetryReached

975

csvDiskThreshholdExceeded

976

csvDiskMaxCapacityReached

977

csvDiskThreshholdBackToNormal

1024

apCfgNonDhcpNatWlanVlanConfigMismatch

1025

apCfgDhcpNatWlanVlanConfigMismatch

1257

dpDcToCaleaConnected

1258

dpDcToCaleaConnectFail

1259

dpDcToCaleaDisconnected

1268

dpCaleaUeInterimMatched’

1260

dpP2PTunnelConnected

1261

dpP2PTunnelConnectFail

1262

dpP2PTunnelDisconnected

1263

dpStartMirroringClient

1264

dpStopMirroringClient

1265

dpDhcpIpPoolUsageRate100

1266

dpDhcpIpPoolUsageRate80

1267

zoneAffinityLastDpDisconnected

1761

racADLDAPTLSSuccess

1762

racADLDAPTLSFailed

4001

connectedToSci

4002

disconnectedFromSci

4003

disabledSciDueToUpgrade

4004

disabledSciDueToUpgrade

4005

disabledSciAndFtpDueToMutuallyExclusive

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

26

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}]

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

27

Revision History
SmartZone Version 3.4

New Event
2

Event Code

Event

848

clusterUploadAPFirmwareStart

849

clusterUploadAPFirmwareSuccess

850

clusterUploadAPFirmwareFailed

851

clusterAddAPFirmwareStart

852

clusterAddAPFirmwareSuccess

853

clusterAddAPFirmwareFailed

854

clusterNameChanged

1021

zoneCfgPrepareFailed

1022

apCfgGenFailed

1023

cfgGenSkippedDueToEolAp

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

28

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.5, 800-71290-001 Rev A

29

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.5, 800-71290-001 Rev A

30

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.5, 800-71290-001 Rev A

31

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.5, 800-71290-001 Rev A

32

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.5, 800-71290-001 Rev A

33

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.5, 800-71290-001 Rev A

34

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.5, 800-71290-001 Rev A

35

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.5, 800-71290-001 Rev A

36

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.5, 800-71290-001 Rev A

37

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.5, 800-71290-001 Rev A

38

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.5, 800-71290-001 Rev A

39

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.5, 800-71290-001 Rev A

40

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.5, 800-71290-001 Rev A

41

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 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.5, 800-71290-001 Rev A

42

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 due to the volume. 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 involved in generating an alarm or event.
1 Alarm
a An alarm is a persistent indication of a fault that clears only when the triggering
condition has 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 Events & Alarms > Alarms
-

Date and Time

-

Code

-

Alarm Type

-

Severity

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

43

Alarm and Event Management
Alarm and Event Management

-

Status

-

Activity

-

Acknowledged on

-

Cleared By

-

Cleared On

-

Comments

d On an alarm generation, the controller web interface 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, unacknowledged alarm counts, etc.

-

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 Alarm 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.

-

You may acknowledge an alarm or a set of alarms to let other administrators know that you have acknowledged it. When you select an alarm
or group of alarms, the Acknowledge Alarm button is activated. Click
this button. A text box appears where you need to confirm the acknowledgment. Click Yes when done. The Acknowledged on column in the
Alarms table gets updated.

-

Filtering features based on the alarm attributes. The Filter button is
deactivated by default. Click this button if you want to turn on the filter.
Click the gear icon to set the filters. A text box appears where you can
enter the severity, status and start and end date and time. Click OK when
done.

-

You may also export the data as a CSV file.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

44

Alarm and Event Management
Alarm and Event Management

Figure 1. Alarms

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.
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 an Events log window as seen in Figure 2 for users
to visualize and analyze the events. To view the below event information in
the controller web interface navigate to Events & Alarms > Events.
-

Date and Time

-

Code

-

Type

-

Severity

-

Activity

Event Management lists the disabled events that are filtered at the source
whenever possible to minimize resources for processing events. The SMTP
server is disabled by default. You must enable and configure the SMTP server
so notification emails can be delivered successfully.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

45

Alarm and Event Management
Alarm and Event Management

Threshold Events are triggered at the source whenever possible.
Users are able to perform various operations on the events, such as filtration,
aggregation and counting. The Filter button is deactivated by default. Click
this button if you want to turn off the filter. Click on the gear icon to set the
filters. A text box appears where you can enter the severity, status and start
and end date and time. Click OK when done.
The controller gives you the option of exporting the data as a CSV file.

Figure 2. Events

NOTE: Refer to Alarm Types and Events Types for the list of alarm and event that
the controller generates.

NOTE: Refer to the SNMP MIB Reference Guide for the list of SNMP alarm traps
that the controller generates.

NOTE: Refer to the Administrator Guide for viewing Alarms and Events.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

46

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
• SCI Alarms
• System Alarms
• Threshold Alarms
• Tunnel Alarms - Access Point

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

47

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.5, 800-71290-001 Rev A

48

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 an AP is unable to reach the 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.5, 800-71290-001 Rev A

49

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 the 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.5, 800-71290-001 Rev A

50

Alarm Types
AP Authentication Alarms

Table 8.

AD server unreachable alarm

Description

This alarm is triggered when the 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 the 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.5, 800-71290-001 Rev A

51

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 the AP is unable to resolve the 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.5, 800-71290-001 Rev A

52

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 the 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 the 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.5, 800-71290-001 Rev A

53

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 been exceeded the limit. Purchase
additional licenses.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

54

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 to trigger another
configuration change. 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.

Recommended Actions If the model is incorrect delete and rejoin the AP.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

55

Alarm Types
AP Communication Alarms

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 preprovisioned configuration model.

Recommended Actions If the model is incorrect, delete the AP to rejoin and receive the proper
AP configuration.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

56

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 firmware update fails.

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.5, 800-71290-001 Rev A

57

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.5, 800-71290-001 Rev A

58

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 when the server is in maintenance mode.
Report this to the location server owner.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

59

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 when the AP fails to connect to the location
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.5, 800-71290-001 Rev A

60

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.5, 800-71290-001 Rev A

61

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 DHCP service failure
• AP NAT failure

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.5, 800-71290-001 Rev A

62

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 connectivity between the AP and 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 No action required.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

63

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.

AP DHCP service failure
Table 26. AP DHCP service failure alarm
Alarm

Both primary and secondary DHCP server APs are down

Alarm Type

apDHCPServiceFailure

Alarm Code

341

Severity

Major

Aggregation Policy

From the event code xxx an alarm is raised for every event. A single
event triggers a single alarm.

Attribute

”primaryServerMac”=“xx:xx:xx:xx:xx:xx”,
“secondaryServerMac”=“xx:xx:xx:xx:xx:xx”

Displayed on the web
interface

AP DHCP service failure. Both primary DHCP AP [{primaryServerMac}]
and secondary DHCP server AP [{secondaryServerMac}] are down.

Description

This alarm is triggered when the primary and secondary DHCP server
APs fail.

Recommended Actions Deploy DHCP service on another AP.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

64

Alarm Types
AP State Change Alarms

AP NAT failure
Table 27. AP NAT failure alarm
Alarm

AP NAT failure detected by controller due to three (3) consecutive NAT
gateway APs are down

Alarm Type

apNATFailureDetectedbySZ

Alarm Code

346

Severity

Critical

Aggregation Policy

From the event code 346 an alarm is raised for every event. A single
event triggers a single alarm.

Attribute

”apMac1”=“xx:xx:xx:xx:xx:xx”, ”apMac2”=“xx:xx:xx:xx:xx:xx”,
”apMac3”=“xx:xx:xx:xx:xx:xx”

Displayed on the web
interface

NAT failure detected by SZ since three (3) consecutive NAT gateway IPs
are down AP1=[{apMac1}] AP2=[{apMac2}] AP3=[{apMac3}] (All
consecutive NAT APs are down in case of less than 3 NAT Gateway APs
configured). The NAT traffic for some of the clients may get affected for
the respective VLANs.

Description

This alarm is triggered when the controller detects three (3) consecutive
failures of NAT server APs.

NOTE: Refer to AP State Change Events.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

65

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
• Fails to establish TLS tunnel with AD/LDAP

Authentication server not reachable
Table 28. 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 primary or secondary authentication 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 controller. Ensure that the AAA server is UP.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

66

Alarm Types
Authentication Alarms

Authentication failed over to secondary
Table 29. 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 becomes
available after the primary server becomes unreachable.

Recommended Actions No operator action is required.

Authentication fallback to primary
Table 30. 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.5, 800-71290-001 Rev A

67

Alarm Types
Authentication Alarms

Table 30. 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 authentication server failover recovery has
occurred.

Recommended Actions No action is required.

AD/LDAP connectivity failure
Table 31. 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 the RADIUS server fails to connect with an
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.5, 800-71290-001 Rev A

68

Alarm Types
Authentication Alarms

Bind fails with AD/LDAP
Table 32. 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 the RADIUS server binding to the AD/LDAP
server fails.

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

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

69

Alarm Types
Authentication Alarms

Bind success with LDAP, but unable to find clear text
password for the user
Table 33. 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

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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

70

Alarm Types
Authentication Alarms

RADIUS fails to connect to AD NPS server
Table 34. 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.

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

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

71

Alarm Types
Authentication Alarms

RADIUS fails to authenticate with AD NPS server
Table 35. 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.5, 800-71290-001 Rev A

72

Alarm Types
Authentication Alarms

Fails to establish TLS tunnel with AD/LDAP
Table 36. Fails to establish TLS tunnel with AD/LDAP alarm
Alarm

Fails to establish TLS tunnel with AD/LDAP

Alarm Type

racADLDAPTLSFailed

Alarm Code

1762

Severity

Major

Aggregation Policy

From the event code 1762 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”
“authSrvrPort”=“636”, "SCGMgmtIp"="2.2.2.2"
“desc”=” Fail to establish TLS Tunnel with LDAP/AD”

Displayed on the web
interface

[{srcProcess}] Fails to authenticate AD NPS[{authSrvrIp}] on
SCG[{SCGMgmtIp}] for User[{userName}

Description

This alarm is triggered when TLS connection between the controller and
AD/LDAP fails.

NOTE: Refer to Authentication Events.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

73

Alarm Types
Control and Data Plane Interface Alarms

Control and Data Plane Interface Alarms
NOTE: This section is not applicable to vSZ-E.
Following alarm relates to control and data plane.
• GtpManager (DP) disconnected

GtpManager (DP) disconnected
v

Table 37. 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.5, 800-71290-001 Rev A

74

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
• Cluster out of service
• Cluster upload AP firmware failed
• Cluster add AP firmware failed
• Unsync NTP time
• Cluster upload KSP file failed
• Configuration backup failed
• Configuration restore failed
• AP Certificate Expired

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

75

Alarm Types
Cluster Alarms

New node failed to join
Table 38. 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.

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
Diagnostics > Application Logs. 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.5, 800-71290-001 Rev A

76

Alarm Types
Cluster Alarms

Node removal failed
Table 39. 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 40. 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.5, 800-71290-001 Rev A

77

Alarm Types
Cluster Alarms

Table 40. 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 41. 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.5, 800-71290-001 Rev A

78

Alarm Types
Cluster Alarms

Cluster backup failed
Table 42. 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.5, 800-71290-001 Rev A

79

Alarm Types
Cluster Alarms

Cluster restore failed
Table 43. 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.5, 800-71290-001 Rev A

80

Alarm Types
Cluster Alarms

Cluster upgrade failed
Table 44. 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.5, 800-71290-001 Rev A

81

Alarm Types
Cluster Alarms

Cluster application stopped
Table 45. 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 46. 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.5, 800-71290-001 Rev A

82

Alarm Types
Cluster Alarms

Table 46. 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 47. 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.5, 800-71290-001 Rev A

83

Alarm Types
Cluster Alarms

Cluster node rebooted
Table 48. 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 49. 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.5, 800-71290-001 Rev A

84

Alarm Types
Cluster Alarms

Table 49. 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 50. 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.5, 800-71290-001 Rev A

85

Alarm Types
Cluster Alarms

Cluster out of service
Table 51. 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 52. 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.5, 800-71290-001 Rev A

86

Alarm Types
Cluster Alarms

Cluster add AP firmware failed
Table 53. 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.

Unsync NTP time
Table 54. Unsync NTP time alarm
Alarm

Unsync NTP time

Alarm Type

unsyncNTPTime

Alarm Code

855

Severity

Major

Aggregation Policy

From the event code 855 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}] time is not synchronized because of [{reason}]. The
time difference is [{status}] seconds.

Description

This alarm is triggered when the cluster time is not synchronized.

Cluster upload KSP file failed
Table 55. Cluster upload KSP file failed alarm
Alarm

Cluster upload KSP file failed

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

87

Alarm Types
Cluster Alarms

Table 55. Cluster upload KSP file failed alarm
Alarm Type

clusterUploadKspFileFailed

Alarm Code

858

Severity

Major

Aggregation Policy

From the event code 858 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 857

Attribute

"clusterName"="xxx"

Displayed on the web
interface

Cluster [{clusterName}] upload KSP file failed.

Description

This alarm is triggered when the cluster time is not synchronized.

Configuration backup failed
Table 56. 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.

Configuration restore failed
Table 57. Configuration restore failed alarm
Alarm

Configuration restore failed

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

88

Alarm Types
Cluster Alarms

Table 57. Configuration restore failed alarm
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.5, 800-71290-001 Rev A

89

Alarm Types
Cluster Alarms

AP Certificate Expired
Table 58. 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.5, 800-71290-001 Rev A

90

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
• VLAN configuration mismatch on non DHCP/NAT WLAN
• VLAN configuration mismatch on DHCP/NAT WLAN

Zone configuration preparation failed
Table 59. 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.5, 800-71290-001 Rev A

91

Alarm Types
Configuration Alarms

AP configuration generation failed
Table 60. 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.5, 800-71290-001 Rev A

92

Alarm Types
Configuration Alarms

End-of-life AP model detected
Table 61. 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 occupy licensed AP space. Disconnect these
unsupported AP models from the given zone.
• Reset the APs to a factory setting using the AP command line
Delete these APs through the controller user interface > AP List

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

93

Alarm Types
Configuration Alarms

VLAN configuration mismatch on non DHCP/NAT WLAN
Table 62. VLAN configuration mismatch on non DHCP/NAT WLAN alarm
Alarm

VLAN configuration mismatch detected between configured and
resolved VLAN with DVLAN/VLAN pooling configuration on non-DHCP/
NAT WLAN

Alarm Type

apCfgNonDhcpNatWlanVlanConfigMismatch

Alarm Code

1024

Severity

Critical

Aggregation Policy

From the event code 1023 an alarm is raised for every event. A single
event triggers a single alarm.

Attribute

“ssid”=”xxxx”, “wlanID”=”xxxx”, “configuredVlan”=”5”,

Displayed on the web
interface

DHCP/NAT gateway AP [{apMac}] detected VLAN configuration
mismatch on non-DHCP/NAT WLAN [{ssid}]. Configured VLAN is
[{configuredVlan}] and resolved VLAN is [{vlanId}]. Clients may not be
able to get IP or access Internet.

Description

This alarm is triggered when the AP detects a non DHCP/NAT WLAN.
VLAN configuration mismatches with DVLAN/VLAN pooling
configuration on gateway AP.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

94

Alarm Types
Configuration Alarms

VLAN configuration mismatch on DHCP/NAT WLAN
Table 63. VLAN configuration mismatch on DHCP/NAT WLAN alarm
Alarm

VLAN configuration mismatch detected between configured and
resolved VLAN with DVLAN/VLAN pooling configuration on a DHCP/
NAT WLAN

Alarm Type

apCfgDhcpNatWlanVlanConfigMismatch

Alarm Code

1025

Severity

Critical

Aggregation Policy

From the event code 1023 an alarm is raised for every event. A single
event triggers a single alarm.

Attribute

“ssid”=”xxxx”, “vlanID”=”xxxx”, “configuredVlan”=”5”, “vlanId”=”11”,
"apMac"=""xx:xx:xx:xx:xx:xx"

Displayed on the web
interface

DHCP/NAT gateway AP [{apMac}] detected VLAN configuration
mismatch on DHCP/NAT WLAN [{ssid}]. Configured VLAN is
[{configuredVlan}] and resolved VLAN is [{vlanId}]. Clients may not be
able to get IP or access Internet

Description

This alarm is triggered when VLAN configuration mismatch is detected
between configured and resolved VLAN with DVLAN/VLAN pooling
configuration on a DHCP/NAT WLAN.

NOTE: Refer to Configuration Events.
show upgrade-state

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

95

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 of data center side fails to connect to the CALEA server
• Data Plane fails to connects to the other data plane
• Data Plane DHCP IP Pool usage rate is 100 percent

Data plane configuration update failed
Table 64. 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 due to 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.5, 800-71290-001 Rev A

96

Alarm Types
Data Plane Alarms

Data plane disconnected
Table 65. 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 66. 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.5, 800-71290-001 Rev A

97

Alarm Types
Data Plane Alarms

Table 66. 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 67. 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 to vSZ-E.
Table 68. 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.5, 800-71290-001 Rev A

98

Alarm Types
Data Plane Alarms

Table 68. 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.
Purchase additional licenses.

Data plane upgrade failed
NOTE: Alarm 553 is applicable only to vSZ-E.
Table 69. 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.5, 800-71290-001 Rev A

99

Alarm Types
Data Plane Alarms

Table 69. 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.

Data plane of data center side fails to connect to the
CALEA server
Table 70. Data plane of data center side fails to connect to the CALEA server alarm
Alarm

Data plane of data center side fails to connect to the CALEA server

Alarm Type

dpDcToCaleaConnectFail

Alarm Code

1258

Severity

Major

Aggregation Policy

From the event code 1258 an alarm is raised for every event. A single
event triggers a single alarm.

Attribute

“dpKey”=“xx:xx:xx:xx:xx:xx”, “caleaServerIP”=“xxx.xxx.xxx.xxx”,
"dpIP"="xx.xx.xx.xx", "reason"="xxxxxx"

Displayed on the web
interface

Data Plane of Data Center side[{dpName&&dpKey}] fails to connects to
the CALEA server[{caleaServerIP}]

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

100

Alarm Types
Data Plane Alarms

Table 70. Data plane of data center side fails to connect to the CALEA server alarm
Description

This alarm is triggered when the data plane fails to connect to the CALEA
server.

Recommended Actions Check the connectivity between data plane and CALEA server.

Data Plane fails to connects to the other data plane
Table 71. Data Plane fails to connects to the other data plane alarm
Alarm

Data Plane fails to connects to the other data plane

Alarm Type

dpP2PTunnelConnectFail

Alarm Code

1261

Severity

Warning

Aggregation Policy

From the event code 1261 an alarm is raised for every event. A single
event triggers a single alarm.

Attribute

“dpKey”=“xx:xx:xx:xx:xx:xx”, "dpIP"="xx.xx.xx.xx",
“targetDpKey”=“xx:xx:xx:xx:xx:xx”, “targetDpIp”=“xxx.xxx.xxx.xxx”

Displayed on the web
interface

Data Plane[{dpName&&dpKey}] fails connects to the other Data
Plane[{targetDpKey&&targetDpIp}]

Description

This alarm is triggered when the data plane fails to connect to another
data plane.

Recommended Actions Increase the size of the DHCP IP address pool, or reduce the number
of stations requiring addresses.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

101

Alarm Types
Data Plane Alarms

Data Plane DHCP IP Pool usage rate is 100 percent
Table 72. Data Plane DHCP IP Pool usage rate is 100 percent alarm
Alarm

Data Plane DHCP IP Pool usage rate is 100 percent

Alarm Type

dpDhcpIpPoolUsageRate100

Alarm Code

1265

Severity

Critical

Aggregation Policy

From the event code 1265 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}] DHCP IP Pool usage rate is 100
percent

Description

This alarm is triggered when data plane DHCP pool usage rate reaches
100%

Recommended Actions

NOTE: Refer to Data Plane Events.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

102

Alarm Types
IPMI Alarms

IPMI Alarms
NOTE: This section is not applicable to vSZ-E.
Following are the alarms related to IPMIs.
• ipmiThempBB
• ipmiThempP
• ipmiFan
• ipmiFanStatus

ipmiThempBB
Table 73. 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.5, 800-71290-001 Rev A

103

Alarm Types
IPMI Alarms

ipmiThempP
Table 74. 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 processor temperature on the control plane
reaches the threshold value. The default threshold is 110C.

Recommended Actions Check and replace the CPU fan module if required. Decrease the
ambient temperature if the fan module is working.

ipmiFan
Table 75. 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.5, 800-71290-001 Rev A

104

Alarm Types
IPMI Alarms

ipmiFanStatus
Table 76. 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.5, 800-71290-001 Rev A

105

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 77. 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. Purchase additional licenses.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

106

Alarm Types
Licensing Interface Alarms

Insufficient license capacity
Table 78. 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. Purchase additional licenses.

NOTE: Refer to Licensing Interface Events.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

107

Alarm Types
SCI Alarms

SCI Alarms
Following are the events related to SCI (Small Cell Insight).
• Connect to SCI failure
• SCI has been disabled
• SCI and FTP have been disabled

Connect to SCI failure
Table 79. Connect to SCI failure alarm
Alarm

Connect to SCI failure

Alarm Type

connectToSciFailure

Alarm Code

4003

Severity

Major

Aggregation Policy

From the event code 4003 an alarm is raised for every event. A single
event triggers a single alarm.

Displayed on the web
interface

Try to connect to SCI with all SCI profiles but failure.

Description

This alarm occurs when the controller tries connecting to SCI with its
profiles but fails.

Recommended Actions Check the connectivity between SCI and the controller server. Ensure
that SCI MQTT server's IP address, port number, username and
password are correct.

SCI has been disabled
Table 80. SCI has been disabled alarm
Alarm

SCI has been disabled

Alarm Type

disabledSciDueToUpgrade

Alarm Code

4004

Severity

Warning

Aggregation Policy

From the event code 4004 an alarm is raised for every event. A single
event triggers a single alarm.

Displayed on the web
interface

SCI has been disabled due to SZ upgrade, please reconfigure SCI if
need

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

108

Alarm Types
SCI Alarms

Table 80. SCI has been disabled alarm
Description

This alarm occurs when SCI is disabled due to the controller upgrade.

Recommended Actions The controller does not support SCI prior to version 2.3. You would need
to upgrade SCI to 2.3 or above and reconfigure the required information
of SCI on the controller dashboard.

SCI and FTP have been disabled
Table 81. SCI and FTP have been disabled alarm
Alarm

SCI and FTP have been disabled

Alarm Type

disabledSciAndFtpDueToMutuallyExclusive

Alarm Code

4005

Severity

Warning

Aggregation Policy

From the event code 4005 an alarm is raised for every event. A single
event triggers a single alarm.

Displayed on the web
interface

SCI and FTP have been disabled. It is recommended to enable SCI
instead of FTP

Description

This event occurs when the SCI and FTP are disabled.

Recommended Actions SCI and FTP cannot be enabled simultaneously. Both features have
disabled during an upgrade of the controller. Enable either SCI or FTP
feature on the controller dashboard.

NOTE: Refer to SCI Events.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

109

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
• The last one data plane is disconnected zone affinity profile

No LS responses
Table 82. 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.5, 800-71290-001 Rev A

110

Alarm Types
System Alarms

LS authentication failure
Table 83. 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 authentication failure when SmartZone
tries connecting to the location based service.

Recommended Actions Check the location server password.

{produce.short.name} failed to connect to LS
Table 84. {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.5, 800-71290-001 Rev A

111

Alarm Types
System Alarms

Syslog server unreachable
Table 85.

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 86. 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.5, 800-71290-001 Rev A

112

Alarm Types
System Alarms

Service unavailable
Table 87. 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 88. 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.5, 800-71290-001 Rev A

113

Alarm Types
System Alarms

Table 88. 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 89. 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.5, 800-71290-001 Rev A

114

Alarm Types
System Alarms

HIP failed over
NOTE: This alarm is not applicable to vSZ-E.
Table 90. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

115

Alarm Types
System Alarms

The last one data plane is disconnected zone affinity
profile
Table 91. The last one data plane is disconnected zone affinity profile alarm
Alarm

The last one data plane is disconnected zone affinity profile

Alarm Type

zoneAffinityLastDpDisconnected

Alarm Code

1267

Severity

Informational

Aggregation Policy

Alarm is raised for every event from event code 1267. A single event
triggers a single alarm.

Attribute

“dpName="xxxxxxxx",“dpKey”=“xx:xx:xx:xx:xx:xx”,
"zoneAffinityProfileId"="xxxxxxxx"

Displayed on the web
interface

The Last one Data Plane[{dpName&&dpKey}] is disconnected Zone
Affinity profile[{zoneAffinityProfileId}] .

Description

This alarm is logged when the last data plane is disconnected from the
zone affinity.

Recommended Actions

NOTE: Refer to System Events.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

116

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 92. 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
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.5, 800-71290-001 Rev A

117

Alarm Types
Threshold Alarms

Memory threshold exceeded
Table 93. 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 94. 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.5, 800-71290-001 Rev A

118

Alarm Types
Threshold Alarms

Table 94. 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 95. 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, buy new
licenses.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

119

Alarm Types
Threshold Alarms

Rate limit for TOR surpassed
Table 96. 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 97. 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.5, 800-71290-001 Rev A

120

Alarm Types
Threshold Alarms

Table 97. 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 98. 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.5, 800-71290-001 Rev A

121

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 99. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

122

Alarm Types
Tunnel Alarms - Access Point

AP is disconnected from secure gateway
Table 100. 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.

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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

123

Alarm Types
Tunnel Alarms - Access Point

AP secure gateway association failure
Table 101. 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.5, 800-71290-001 Rev A

124

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
• SCI 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.5, 800-71290-001 Rev A

125

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 102. 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.5, 800-71290-001 Rev A

126

Events Types
Accounting Events

AP accounting response while invalid config
Table 103. 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 due to incorrect controller configuration.. 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.5, 800-71290-001 Rev A

127

Events Types
Accounting Events

AP account message drop while no accounting start
message
Table 104. 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.5, 800-71290-001 Rev A

128

Events Types
Accounting Events

Unauthorized COA/DM message dropped
Table 105. 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.5, 800-71290-001 Rev A

129

Events Types
AP Communication Events

AP Communication Events
All events from APs 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

AP configuration get failed

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 106. 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
controller successfully.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

130

Events Types
AP Communication Events

AP managed
Table 107. 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 108. 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.5, 800-71290-001 Rev A

131

Events Types
AP Communication Events

AP firmware updated
Table 109. 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 its firmware.

AP firmware update failed
Table 110. 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 firmware update fails

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.5, 800-71290-001 Rev A

132

Events Types
AP Communication Events

Updating AP firmware
Table 111. 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 the AP update is in progress.

Updating AP configuration
Table 112. 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 an AP configuration update is in progress.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

133

Events Types
AP Communication Events

AP configuration updated
Table 113. 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 an AP configuration update is complete.

AP configuration update failed
Table 114. 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 configuration update fails.

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.5, 800-71290-001 Rev A

134

Events Types
AP Communication Events

AP pre-provision model mismatched
Table 115. 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 116. 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.5, 800-71290-001 Rev A

135

Events Types
AP Communication Events

AP WLAN oversubscribed
Table 117. 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 maximum WLAN capacity has been
exceeded.

AP illegal to change country code
Table 118. 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.5, 800-71290-001 Rev A

136

Events Types
AP Communication Events

AP configuration get failed
Table 119. AP configuration get failed event
Event

AP configuration get failed

Event Type

apGetConfigFailed

Event Code

117

Severity

Informational

Attribute

“apMac”=“xxx.xxx.xxx.xxx” , “configID”=“23456781234”

Displayed on the web
interface

AP [{apName&&apMac}] failed to get the configuration [{configID}].

Description

This event occurs when the AP fails to get the configuration.

Rogue AP
Table 120. 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 121. 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"

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

137

Events Types
AP Communication Events

Table 121. SSID-spoofing rogue AP event
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.5, 800-71290-001 Rev A

138

Events Types
AP Communication Events

Mac-spoofing rogue AP
Table 122. 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 123. 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 on the same
network.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

139

Events Types
AP Communication Events

Ad-hoc network device
Table 124. 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 125. 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.5, 800-71290-001 Rev A

140

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 126. 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.

Auto Clearance

This event triggers the alarm 701, which is auto cleared by the event
code 703.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

141

Events Types
AP LBS Events

LS authentication failure
Table 127. 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 when the AP fails to connect to the location service.

Auto Clearance

This event triggers the alarm 702, which is auto cleared by the event
code 703.

AP connected to LS
Table 128. 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.5, 800-71290-001 Rev A

142

Events Types
AP LBS Events

AP failed to connect to LS
Table 129. 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 130. 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 location service is started on an AP.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

143

Events Types
AP LBS Events

AP stopped location service
Table 131. 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 location service on an AP is stopped.

AP received passive calibration request
Table 132. 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.5, 800-71290-001 Rev A

144

Events Types
AP LBS Events

AP received passive footfall request
Table 133. 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 134. 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.5, 800-71290-001 Rev A

145

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 135. 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.5, 800-71290-001 Rev A

146

Events Types
AP Mesh Events

EMAP downlink disconnected from MAP
Table 136. 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 137. 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.5, 800-71290-001 Rev A

147

Events Types
AP Mesh Events

EMAP uplink disconnected from MAP
Table 138. 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 139. 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 140. 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.5, 800-71290-001 Rev A

148

Events Types
AP Mesh Events

Table 140. MAP downlink connected event
Description

This event occurs when the MAP downlink connects to the AP.

MAP downlink connected to EMAP
Table 141. 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 142. 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.5, 800-71290-001 Rev A

149

Events Types
AP Mesh Events

RAP downlink connected to MAP
Table 143. 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 144. 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.5, 800-71290-001 Rev A

150

Events Types
AP Mesh Events

MAP uplink disconnected from EMAP
Table 145. 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 146. 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.5, 800-71290-001 Rev A

151

Events Types
AP Mesh Events

MAP uplink connected to MAP
Table 147. 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 148. 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.5, 800-71290-001 Rev A

152

Events Types
AP Mesh Events

Mesh state updated to MAP no channel
Table 149. 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's mesh state is changed to Mesh AP
(MAP). The message also indicates the MAP's uplink AP, number of
hops, and downlink state.

Mesh state updated to RAP
Table 150. 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 's mesh state changes to Root AP (RAP).
The message also indicates the radio channel and downlink state.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

153

Events Types
AP Mesh Events

Mesh state update to RAP no channel
Table 151. 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's state changes to Root AP. The
message also indicates the downlink state.

MAP downlink connected to MAP
Table 152. 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.5, 800-71290-001 Rev A

154

Events Types
AP Mesh Events

MAP downlink disconnected from MAP
Table 153. 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 154. 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.5, 800-71290-001 Rev A

155

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 interface up

AP cable modem softrebooted by user

AP cable modem set to
factory default by user

AP health high latency flag

AP health low capacity flag

AP health high connection
failure flag

AP health high client count flag

AP health high latency clear

AP health low capacity clear AP health high connection failure
clear

AP health high client count
clear

Primary DHCP AP is down

Primary or secondary DHCP
AP detects 90% of the
configured total IPs

Primary DHCP AP is up

Both primary and secondary AP NAT gateway IP failover
AP NAT gateway IP fall back
DHCP server APs are down detected for particular VLAN pool detected for particular VLAN
pool
NAT VLAN capacity affected AP NAT failure detected by SZ due AP health high airtime utilization
detected by NAT gateway to three (3) consecutive NAT
flag
AP at zone due to three (3) gateway APs are down
consecutive NAT gateway
AP IPs are down for
particular VLAN pool

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

156

Events Types
AP State Change Events

AP health high airtime
utilization clear

AP rebooted by user
Table 155. 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 been power-cycled by the user.

AP rebooted by system
Table 156. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

157

Events Types
AP State Change Events

AP disconnected
Table 157. 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.

AP IP address updated
Table 158. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

158

Events Types
AP State Change Events

AP reset to factory default
Table 159. 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.

AP channel updated
Table 160. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

159

Events Types
AP State Change Events

AP country code updated
Table 161. 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.

AP channel updated because dynamic frequency
selection (DFS) detected a radar
Table 162. 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 channel
and the channel moves to a non-occupancy mode.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

160

Events Types
AP State Change Events

AP change control plane
Table 163. 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.

AP connected
Table 164. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

161

Events Types
AP State Change Events

AP deleted
Table 165. 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.

AP heartbeat lost
Table 166. 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 loss is detected.

AP tagged as critical
Table 167. 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

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

162

Events Types
AP State Change Events

Table 167. AP tagged as critical event
Description

This event occurs when the AP is tagged critical.

AP cable modem interface down
Table 168. 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 169. 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.5, 800-71290-001 Rev A

163

Events Types
AP State Change Events

AP cable modem power-cycled by user
Table 170. 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 171. 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.5, 800-71290-001 Rev A

164

Events Types
AP State Change Events

AP client load balancing limit reached
Table 172. 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 173. 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.5, 800-71290-001 Rev A

165

Events Types
AP State Change Events

AP WLAN state changed
Table 174. 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 175. 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 because the client
association threshold has been reached.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

166

Events Types
AP State Change Events

AP capacity recovered
Table 176. 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 177. 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.5, 800-71290-001 Rev A

167

Events Types
AP State Change Events

AP cable modem soft-rebooted by user
Table 178. 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 rebooted because the
user executes the soft-reboot CLI command.

AP cable modem set to factory default by user
Table 179. 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 defaults
because the user executes the set factory CLI command.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

168

Events Types
AP State Change Events

AP health high latency flag
Table 180. AP health high latency flag event
Event

AP health high latency flag

Event Type

apHealthLatencyFlag

Event Code

328

Severity

Warning

Attribute

”apName”=“xxxxx”, ”apMac”=“xx:xx:xx:xx:xx:xx”,
”currentValue”=“xxxxx”,”configuredThreshold”=“xxxxx”,
"radio" = "X.XG"

Displayed on the web
interface

AP [{apName&&apMac}] flagged {{radio}} latency health [{currentValue}]
because it crossed the threshold [{configuredThreshold}].

Description

This event occurs when the AP is flagged because the radio has crossed
the latency health threshold configured by the administrator.

AP health low capacity flag
Table 181. AP health low capacity flag event
Event

AP health low capacity flag

Event Type

apHealthCapacityFlag

Event Code

329

Severity

Warning

Attribute

”apName”=“xxxxx”, ”apMac”=“xx:xx:xx:xx:xx:xx”,
”currentValue”=“xxxxx”,”configuredThreshold”=“xxxxx”,
"radio" = "X.XG"

Displayed on the web
interface

AP [{apName&&apMac}] flagged {{radio}} capacity health
[{currentValue}] because it crossed the threshold
[{configuredThreshold}].

Description

This event occurs when the AP is flagged because the radio has crossed
the capacity health threshold configured by the administrator.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

169

Events Types
AP State Change Events

AP health high connection failure flag
Table 182. AP health high connection failure flag event
Event

AP health high connection failure flag

Event Type

apHealthConnectionFailureFlag

Event Code

330

Severity

Warning

Attribute

”apName”=“xxxxx”, ”apMac”=“xx:xx:xx:xx:xx:xx”,
”currentValue”=“xxxxx”,”configuredThreshold”=“xxxxx”,
"radio" = "X.XG"

Displayed on the web
interface

AP [{apName&&apMac}] flagged {{radio}} capacity health
[{currentValue}] because it crossed the threshold
[{configuredThreshold}].

Description

This event occurs when AP is flagged because the AP has crossed the
connection failure health threshold configured by the administrator.

AP health high client count flag
Table 183. AP health high client count flag event
Event

AP health high client count flag

Event Type

apHealthClientCountFlag

Event Code

331

Severity

Warning

Attribute

”apName”=“xxxxx”, ”apMac”=“xx:xx:xx:xx:xx:xx”,
”currentValue”=“xxxxx”,”configuredThreshold”=“xxxxx”,

Displayed on the web
interface

AP [{apName&&apMac}] flagged client count health [{currentValue}]
because it crossed the threshold [{configuredThreshold}].

Description

This event occurs when an AP is flagged because the AP has crossed
the client count health threshold configured by the administrator.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

170

Events Types
AP State Change Events

AP health high latency clear
Table 184. AP health high latency clear event
Event

AP health high latency clear

Event Type

apHealthLatencyClear

Event Code

332

Severity

Informational

Attribute

”apName”=“xxxxx”, ”apMac”=“xx:xx:xx:xx:xx:xx”,
”currentValue”=“xxxxx”,”configuredThreshold”=“xxxxx”,
"radio" = "X.XG",

Displayed on the web
interface

AP [{apName&&apMac}] cleared {{radio}} latency health
[{currentValue}], which is no longer past the threshold
[{configuredThreshold}].

Description

This event occurs when an AP health flag is cleared because it is no
longer past the capacity threshold configured by the administrator.

AP health low capacity clear
Table 185. AP health low capacity clear event
Event

AP health low capacity clear

Event Type

apHealthCapacityClear

Event Code

333

Severity

Informational

Attribute

”apName”=“xxxxx”, ”apMac”=“xx:xx:xx:xx:xx:xx”,
”currentValue”=“xxxxx”,”configuredThreshold”=“xxxxx”,
"radio" = "X.XG"

Displayed on the web
interface

AP [{apName&&apMac}] cleared {{radio}} capacity health
[{currentValue}], which is no longer past the threshold
[{configuredThreshold}].

Description

This event occurs when an AP's health flag is cleared because it is no
longer past the capacity threshold configured by the administrator.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

171

Events Types
AP State Change Events

AP health high connection failure clear
Table 186. AP health high connection failure clear event
Event

AP health high connection failure clear

Event Type

apHealthConnectionFailureClear

Event Code

334

Severity

Informational

Attribute

”apName”=“xxxxx”, ”apMac”=“xx:xx:xx:xx:xx:xx”,
”currentValue”=“xxxxx”,”configuredThreshold”=“xxxxx”,
"radio" = "X.XG"

Displayed on the web
interface

AP [{apName&&apMac}] flagged {{radio}} connection failure health
[{currentValue}], which is no longer past the threshold
[{configuredThreshold}].

Description

This event occurs when an AP's health flag is cleared because it is no
longer past the connection failure threshold configured by the
administrator.

AP health high client count clear
Table 187. AP health high client count clear event
Event

AP health high client count clear

Event Type

apHealthClientCountClear

Event Code

335

Severity

Informational

Attribute

”apName”=“xxxxx”, ”apMac”=“xx:xx:xx:xx:xx:xx”,
”currentValue”=“xxxxx”,”configuredThreshold”=“xxxxx”,

Displayed on the web
interface

AP [{apName&&apMac}] cleared client count health [{currentValue}],
which is no longer past the threshold [{configuredThreshold}].

Description

This event occurs when an AP's health flag is cleared because it is no
longer past the capacity threshold configured by the administrator.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

172

Events Types
AP State Change Events

Primary DHCP AP is down
Table 188. Primary DHCP AP is down event
Event

Primary DHCP AP is down detected by secondary DHCP AP. Starting
DHCP service on secondary.

Event Type

apDHCPFailoverDetected

Event Code

336

Severity

Warning

Attribute

”primaryServerMac”=“xx:xx:xx:xx:xx:xx”, ”apMac”=“xx:xx:xx:xx:xx:xx”

Displayed on the web
interface

Primary DHCP server [{primaryServerMac}] is down detected by
secondary DHCP server [{apMac}].

Description

This event occurs when the secondary DHCP AP detects that the
primary DHCP service has failed and starts the DHCP service.

Primary DHCP AP is up
Table 189. Primary DHCP AP is up event
Event

Primary DHCP AP is up detected by secondary DHCP AP. Stopping
DHCP service on secondary.

Event Type

apDHCPFallbackDetected

Event Code

337

Severity

Informational

Attribute

”primaryServerMac”=“xx:xx:xx:xx:xx:xx”, ”apMac”=“xx:xx:xx:xx:xx:xx”

Displayed on the web
interface

Primary DHCP server [{primaryServerMac}] is up detected by secondary
DHCP server [{apMac}].

Description

This event occurs when the secondary DHCP AP detects that primary
DHCP AP is UP and stops DHCP service.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

173

Events Types
AP State Change Events

Secondary DHCP AP is down
Table 190. Secondary DHCP AP is down event
Event

Secondary DHCP AP is down detected by primary DHCP AP.

Event Type

apSecondaryDHCPAPDown

Event Code

338

Severity

Major

Attribute

”secondaryServerMac”=“xx:xx:xx:xx:xx:xx”,
”apMac”=“xx:xx:xx:xx:xx:xx”

Displayed on the web
interface

Secondary DHCP server [{secondaryServerMac}] is down detected by
primary DHCP server [{apMac}].

Description

This event occurs when the primary DHCP AP detects that the
secondary DHCP AP is down.

Secondary DHCP AP is up
Table 191. Secondary DHCP AP is up event
Event

Secondary DHCP AP is up detected by primary DHCP AP.

Event Type

apSecondaryDHCPAPUp

Event Code

339

Severity

Informational

Attribute

”secondaryServerMac”=“xx:xx:xx:xx:xx:xx”,
”apMac”=“xx:xx:xx:xx:xx:xx”

Displayed on the web
interface

Secondary DHCP server [{secondaryServerMac}] is up detected by
primary DHCP server [{primaryServerMac}].

Description

This event occurs when the primary DHCP AP detects that secondary
DHCP AP is UP.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

174

Events Types
AP State Change Events

Primary or secondary DHCP AP detects 90% of the
configured total IPs
Table 192. Primary or secondary DHCP AP detects 90% of the configured total IPs event
Event

Primary or secondary DHCP AP detects 90% of the configured total IPs

Event Type

apDHCPIPPoolMaxThresholdReached

Event Code

340

Severity

Warning

Attribute

"zoneName"="ZoneName", "poolId"="xxxx","vlanId"="1",
"allocatedIPNum"="5", "totalIPNum"="10",
"apMac"="xx:xx:xx:xx:xx:xx"

Displayed on the web
interface

In zone [{zoneName}] DHCP IP pool [{poolId}] reached 90% threshold
detected by AP MAC [{apMac}]. VLAN ID: [{vlanId}] Allocated
IPs:[{allocatedIPNum}], Total IPs:[{totalIPNum}].

Description

This event occurs when the primary or secondary DHCP AP reports that
the IP pool has reached 90% of the total number of allocated IP
addresses.

Both primary and secondary DHCP server APs are
down
Table 193. Both primary and secondary DHCP server APs are down event
Event

Both primary and secondary DHCP server APs are down

Event Type

apDHCPServiceFailure

Event Code

341

Severity

Critical

Attribute

”primaryServerMac”=“xx:xx:xx:xx:xx:xx”,
“secondaryServerMac”=“xx:xx:xx:xx:xx:xx”

Displayed on the web
interface

AP DHCP service failure. Both primary DHCP AP [{primaryServerMac}]
and secondary DHCP server AP [{secondaryServerMac}] are down.

Description

This event occurs when the controller detects that the primary and
secondary DHCP APs have failed.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

175

Events Types
AP State Change Events

AP NAT gateway IP failover detected for particular
VLAN pool
Table 194. AP NAT gateway IP failover detected for particular VLAN pool event
Event

AP NAT gateway IP failover detected for particular VLAN pool

Event Type

apNATFailoverDetected

Event Code

342

Severity

Major

Attribute

"natGatewayIP"=”10.1.2.2", "vlanId”=”2”,
”natGatewayMac”=“xx:xx:xx:xx:xx:xx”, “apMac”=”xx:xx:xx:xx:xx:xx”

Displayed on the web
interface

NAT failover detected for [{natGatewayIP}], VLAN [{vlanId}], AP
[{natGatewayMac}]. Bringing up interface and switching traffic to AP
[{apMac}].

Description

This event occurs when any NAT gateway AP detects that a monitored
NAT gateway IP has failed.

AP NAT gateway IP fall back detected for particular
VLAN pool
Table 195. AP NAT gateway IP fall back detected for particular VLAN pool event
Event

AP NAT gateway IP fall back detected for particular VLAN pool

Event Type

apNATFallbackDetected

Event Code

343

Severity

Informational

Attribute

"vlanId"="1", ”natGatewayMac”=“xx:xx:xx:xx:xx:xx”,
“apMac”=“xx:xx:xx:xx:xx:xx”

Displayed on the web
interface

NAT fallback detected for VLAN [{vlanId}] by AP [{apMac}]. Bringing
down interface and switching traffic to AP [{natGatewayMac}].

Description

This event occurs when any NAT gateway AP detects that other
monitored NAT gateway AP IP is up.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

176

Events Types
AP State Change Events

NAT VLAN capacity affected detected by NAT gateway
AP at zone due to three (3) consecutive NAT gateway
AP IPs are down for particular VLAN pool
Table 196. NAT VLAN capacity affected detected by NAT gateway AP at zone due to three (3)
consecutive NAT gateway AP IPs are down for particular VLAN pool event
Event

NAT VLAN capacity affected detected by NAT gateway AP at zone due
to three (3) consecutive NAT gateway AP IPs are down for particular
VLAN pool

Event Type

apNATVlanCapacityAffected

Event Code

344

Severity

Critical

Attribute

"natGatewayIP1"=192.168.10.2", "natGatewayIP2"=192.168.10.3",
"natGatewayIP3"=192.168.10.4","vlanId”=”2”,
"apMac"="xx:xx:xx:xx:xx:xx"

Displayed on the web
interface

NAT VLAN capacity affected is detected by NAT gateway AP [{apMac}]
since three (3) consecutive NAT gateway IPs
[{natGatewayIP1&&natGatewayIP2&&natGatewayIP3}] are down. The
NAT traffic for some of the clients may get affected for VLAN [{vlanId}].

Description

This event occurs when NAT VLAN capacity affected is detected by NAT
gateway AP at zone. This is due to three (3) consecutive NAT gateway
AP IP failure for a particular VLAN pool.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

177

Events Types
AP State Change Events

NAT VLAN capacity restored detected by NAT gateway
AP due to (at least) one out of the three (3) consecutive
NAT gateway AP IP were down is now up
Table 197. NAT VLAN capacity restored detected by NAT gateway AP due to (at least) one out
of the three (3) consecutive NAT gateway AP IP were down is now up event
Event

NAT VLAN capacity restored detected by NAT gateway AP due to (at
least) one out of the three (3) consecutive NAT gateway AP IP were down
is now up

Event Type

apNATVlanCapacityRestored

Event Code

345

Severity

Informational

Attribute

”natGatewayIP”=“192.168.10.2”, "apMac"="xx:xx:xx:xx:xx:xx"

Displayed on the web
interface

NAT VLAN capacity restored detected by DHCP NAT AP [{apMac}] one
of the NAT gateway IP [{natGatewayIP}] is now up, out of three (3)
consecutive NAT gateway IPs which were down. The NAT traffic for
affected clients is restored back.

Description

This event occurs when the AP detects at least one of the three (3)
consecutive gateway APs IPs that had failed is now UP.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

178

Events Types
AP State Change Events

AP NAT failure detected by SZ due to three (3)
consecutive NAT gateway APs are down
Table 198. AP NAT failure detected by SZ due to three (3) consecutive NAT gateway APs are
down event
Event

AP NAT failure detected by SZ due to three (3) consecutive NAT gateway
APs are down

Event Type

apNATFailureDetectedbySZ

Event Code

346

Severity

Critical

Attribute

”apMac1”=“xx:xx:xx:xx:xx:xx”, ”apMac2”=“xx:xx:xx:xx:xx:xx”,
”apMac3”=“xx:xx:xx:xx:xx:xx”

Displayed on the web
interface

NAT failure detected by SZ since three (3) consecutive NAT gateway IPs
are down AP1=[{apMac1}] AP2=[{apMac2}] AP3=[{apMac3}] (All
consecutive NAT APs are down in case of less than 3 NAT Gateway APs
configured). The NAT traffic for some of the clients may get affected for
the respective VLANs.

Description

This event occurs when the controller detects three (3) consecutive
failures of NAT server APs.

AP health high airtime utilization flag
Table 199. AP health high airtime utilization flag event
Event

AP health high airtime utilization flag

Event Type

apHealthAirUtilizationFlag

Event Code

347

Severity

Warning

Attribute

”apName”=“xxxxx”, ”apMac”=“xx:xx:xx:xx:xx:xx”,
”currentValue”=“xxxxx”,”configuredThreshold”=“xxxxx”, "radio" =
"X.XG"

Displayed on the web
interface

AP [{apName&&apMac}] flagged {{radio}} airtime utilization health
[{currentValue}] because it crossed the threshold
[{configuredThreshold}].

Description

This event occurs when an AP is flagged because the radio has crossed
the latency health threshold configured by the administrator.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

179

Events Types
AP State Change Events

AP health high airtime utilization clear
Table 200. AP health high airtime utilization clear event
Event

AP health high airtime utilization clear

Event Type

apHealthAirUtilizationClear

Event Code

348

Severity

Informational

Attribute

”apName”=“xxxxx”, ”apMac”=“xx:xx:xx:xx:xx:xx”,
”currentValue”=“xxxxx”,”configuredThreshold”=“xxxxx”,
"radio" = "X.XG"

Displayed on the web
interface

AP [{apName&&apMac}] cleared {{radio}} airtime utilization health
[{currentValue}], which is no longer past the threshold
[{configuredThreshold}].

Description

This event occurs when an AP's health flag is cleared because it is no
longer past the latency threshold configured by the administrator.

NOTE: Refer to AP State Change Alarms.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

180

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 201. 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.5, 800-71290-001 Rev A

181

Events Types
AP Authentication Events

Radius server unreachable
Table 202. 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 an 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 203. 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.5, 800-71290-001 Rev A

182

Events Types
AP Authentication Events

LDAP server unreachable
Table 204. 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 205. 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 the AP is able to reach the active directory server
successfully.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

183

Events Types
AP Authentication Events

AD server unreachable
Table 206. 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 the AP is unable 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 207. 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 the AP successfully reaches the WeChat ESP
authentication server.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

184

Events Types
AP Authentication Events

WeChat ESP authentication server unreachable
Table 208. 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 the AP fails to reach the 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 209. 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 the AP successfully resolves the WeChat ESP
authentication server domain name.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

185

Events Types
AP Authentication Events

WeChat ESP authentication server unresolvable
Table 210. 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 the AP fails to resolves the 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 211. 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 the AP successfully reaches the WeChat ESP
DNAT server.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

186

Events Types
AP Authentication Events

WeChat ESP DNAT server unreachable
Table 212. 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 the AP fails to reach the 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 213. 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 the AP successfully resolves the WeChat ESP
DNAT server domain name.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

187

Events Types
AP Authentication Events

WeChat ESP DNAT server unresolvable
Table 214. 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 the AP fails to resolve the WeChat ESP DNAT
server domain name.

Auto Clearance

This event triggers the alarm 2164, which is auto cleared by the event
code 2163.

NOTE: Refer to AP Authentication Alarms.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

188

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 215. 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 an AP successfully downloads a USB software
package.

AP USB software package download failed
Table 216. 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 the USB software
package.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

189

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
• Successfully established the TLS tunnel with AD/LDAP
• Fails to establish TLS tunnel with AD/LDAP

Authentication server not reachable
Table 217. 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 primary or secondary authentication servers
are not reachable.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

190

Events Types
Authentication Events

Authentication failed over to secondary
Table 218. Authentication failed over to secondary event
Event

Authentication failed over to secondary

Event Type

authFailedOverToSecondary

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
becomes available after the primary server becomes unreachable.

Authentication fallback to primary
Table 219. 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 authentication server failover recovery has
occurred.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

191

Events Types
Authentication Events

AD/LDAP connected successfully
Table 220. 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 the RADIUS connection to the AD/LDAP server
is successful.

AD/LDAP connectivity failure
Table 221. 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 the RADIUS fails to connect to an AD/LDAP
server.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

192

Events Types
Authentication Events

Bind fails with AD/LDAP
Table 222. Bind fails with AD/LDAP event
Event

Bind fails with AD/LDAP

Event Type

racADLDAPBindFail

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 the RADIUS binding to the AD/LDAP server fails.

Bind success with LDAP, but unable to find clear text
password for the user
Table 223. 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 the LDAP using root
credentials but the controller is unable to retrieve the clear text password
for the user.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

193

Events Types
Authentication Events

RADIUS fails to connect to AD NPS server
Table 224. 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

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 an AD NPS server.

RADIUS fails to authenticate with AD NPS server
Table 225. 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 the RADIUS fails to authenticate with an AD
NPS server.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

194

Events Types
Authentication Events

Successfully established the TLS tunnel with AD/LDAP
Table 226. Successfully established the TLS tunnel with AD/LDAP event
Event

Successfully established the TLS tunnel with AD/LDAP

Event Type

racADNPSFailToAuthenticate

Event Code

1761

Severity

Debug

Attribute

“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “mvnoId”=12,
“srcProcess”=”radiusd”, “authSrvrIp”=“1.1.1.1”, “authSrvrPort”=“636”
"SCGMgmtIp"="2.2.2.2",
“desc”=”Successfully established TLS Tunnel with LDAP/AD”

Displayed on the web
interface

[{srcProcess}] Established the TLS connection with AD/
LDAP[{authSrvrIp}] successfully from SCG[{SCGMgmtIp}]

Description

This event occurs when the TLS connection between the controller and
AD/LDAP is successfully established.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

195

Events Types
Authentication Events

Fails to establish TLS tunnel with AD/LDAP
Table 227. Fails to establish TLS tunnel with AD/LDAP event
Event

Fails to establish TLS tunnel with AD/LDAP

Event Type

racADLDAPTLSFailed

Event Code

1762

Severity

Major

Attribute

“ctrlBladeMac”=”aa:bb:cc:dd:ee:ff”, “mvnoId”=12
“srcProcess”=”radiusd”, “authSrvrIp”=“1.1.1.1”
“authSrvrPort”=“636”, “SCGMgmtIp“="2.2.2.2"
“desc”=”Fails to establish TLS Tunnel with LDAP/AD”

Displayed on the web
interface

[{srcProcess}] Establishs the TLS connection with AD/
LDAP[{authSrvrIp}] fails from SCG[{SCGMgmtIp}]

Description

This event occurs when the TLS connection between the controller and
AD/LDAP fails.

Auto Clearance

This event triggers the alarm 1762, which is auto cleared by the event
code 1761.

NOTE: Refer to Authentication Alarms.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

196

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 228. 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.5, 800-71290-001 Rev A

197

Events Types
Authorization Events

DM NACK sent to AAA
Table 229. 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 230. 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.5, 800-71290-001 Rev A

198

Events Types
Authorization Events

DM NACK received from NAS
Table 231. 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 a disconnect
message, which is not acknowledged from the NAS server.

CoA received from AAA
Table 232. 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.5, 800-71290-001 Rev A

199

Events Types
Authorization Events

CoA NACK sent to AAA
Table 233. 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 234. 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.5, 800-71290-001 Rev A

200

Events Types
Authorization Events

CoA NAK received NAS
Table 235. 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 236. 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.5, 800-71290-001 Rev A

201

Events Types
Authorization Events

CoA RWSG MWSG notification failure
Table 237. 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.5, 800-71290-001 Rev A

202

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 238. 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 the control plane successfully completes the
configuration procedure.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

203

Events Types
Control and Data Plane Interface Events

GtpManager (DP) disconnected
Table 239. 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 240. 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.5, 800-71290-001 Rev A

204

Events Types
Control and Data Plane Interface Events

Session update at DP failed
Table 241. 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 242. 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.5, 800-71290-001 Rev A

205

Events Types
Control and Data Plane Interface Events

Table 242. Session deleted at DP event
Description

This event occurs when the session delete request (C-D-SESS-DELREQ) is successfully acknowledged.

Session delete at DP failed
Table 243. 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.5, 800-71290-001 Rev A

206

Events Types
Control and Data Plane Interface Events

C2d configuration failed
Table 244. 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.5, 800-71290-001 Rev A

207

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 client.
• 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
• Client is blocked because of barring UE rule
• Client is unblocked because of barring UE rule
• Start CALEA mirroring client
• Stop CALEA mirroring client

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

208

Events Types
Client Events

Client authentication failed
Table 245. 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 a WLAN on an AP due to
an authentication failure.

Client joined
Table 246. 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 a WLAN on an AP.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

209

Events Types
Client Events

Client failed to join
Table 247. Client failed to join event
Event

Client failed to join

Event Type

clientJoinFailure

Event Code

203

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 a WLAN on an AP.

Client disconnected
Table 248. 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 a WLAN on an AP.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

210

Events Types
Client Events

Client connection timed out
Table 249. Client connection timed out event
Event

Client connection timed out

Event Type

clientInactivityTimeout

Event Code

205

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"="",, “userId”=”uuid"

Displayed on the web
interface

Remediation of type [{remediationType}] failed on client
[{clientIP||clientMac}] for user [{userName}].

Description

This event occurs when a client disconnects from a WLAN due to
inactivity.

Client authorization successfully
Table 250. 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 is authorized successfully.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

211

Events Types
Client Events

Client authorization failed
Table 251. 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 authorization fails.

Client session expired
Table 252. 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.5, 800-71290-001 Rev A

212

Events Types
Client Events

Client roaming
Table 253. 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 has roamed from
one AP to another.

Client logged out
Table 254. 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 logs out.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

213

Events Types
Client Events

Client roaming disconnected
Table 255. 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 256. 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.5, 800-71290-001 Rev A

214

Events Types
Client Events

Client grace period
Table 257. 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 reconnects to a WLAN within
the grace period.

Onboarding registration succeeded
Table 258. 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.5, 800-71290-001 Rev A

215

Events Types
Client Events

Onboarding registration failed
Table 259. 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 260. 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.5, 800-71290-001 Rev A

216

Events Types
Client Events

Remediation failed
Table 261. 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 262. 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 is disconnected from a WLAN due to
a force-DHCP trigger.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

217

Events Types
Client Events

WDS device joined
Table 263. 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 264. 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.5, 800-71290-001 Rev A

218

Events Types
Client Events

Client is blocked because of barring UE rule
Table 265. Client is blocked because of barring UE rule event
Event

Client is blocked because of barring UE rule

Event Type

clientBlockByBarringUERule

Event Code

228

Severity

Informational

Attribute

“apMac”=“xx:xx:xx:xx:xx:xx”, “clientMac”=“xx:xx:xx:xx:xx:xx”

Displayed on the web
interface

Client is blocked because of barring UE rule. Client [clientMac}] of WLAN
[{ssid}] from AP [{apName&&apMac}] was blocked because of barring
UE rule

Description

This event occurs when a client is blocked due to blocking of user
equipment rule.

Client is unblocked because of barring UE rule
Table 266. Client is unblocked because of barring UE rule event
Event

Client is unblocked because of barring UE rule

Event Type

clientUnblockByBarringUERule

Event Code

229

Severity

Informational

Attribute

“apMac”=“xx:xx:xx:xx:xx:xx”, “clientMac”=“xx:xx:xx:xx:xx:xx”

Displayed on the web
interface

Client [clientMac}] of WLAN [{ssid}] from AP [{apName&&apMac}] was
unblocked

Description

This event occurs when a client is allowed by the user equipment rule.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

219

Events Types
Client Events

Start CALEA mirroring client
Table 267. Start CALEA mirroring client event
Event

Start CALEA mirroring client

Event Type

caleaMirroringStart

Event Code

230

Severity

Informational

Attribute

“userName”=“xxxxx”, “clientMac”=”xx:xx:xx:xx:xx:xx”, “ssid”=”xxxxx”,
“apName”=”xxxxx”, “apMac”=”xx:xx:xx:xx:xx:xx”

Displayed on the web
interface

Start CALEA mirroring client [{userName||IP||clientMac}] on WLAN
[{ssid}] from AP [{apName&&apMac}].

Description

This event occurs when CALEA is started for mirroring the client image.

Stop CALEA mirroring client
Table 268. Stop CALEA mirroring client event
Event

Stop CALEA mirroring client

Event Type

caleaMirroringStop

Event Code

231

Severity

Informational

Attribute

“userName”=“xxxxx”, “clientMac”=”xx:xx:xx:xx:xx:xx”, “ssid”=”xxxxx”,
“apName”=”xxxxx”, “apMac”=”xx:xx:xx:xx:xx:xx”, ”authType”=”xxxxx”,
”txBytes”=”xxxxx”, ”rxBytes”=”xxxxx”

Displayed on the web
interface

Stop CALEA mirroring client [{userName||IP||clientMac}] on WLAN
[{ssid}] with authentication type [{authType}] from AP
[{apName&&apMac}]. TxBytes[{txBytes}], RxBytes[{rxBytes}].

Description

This event occurs when CALEA stops mirroring the client image.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

220

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

Disk usage exceed threshold

Cluster out of service

Initiated moving APs in node to Cluster upload vSZ-D firmware
a new cluster
started

Cluster upload vSZ-D firmware
completed

Cluster upload vSZ-D firmware Cluster upload AP firmware started
failed

Cluster upload AP firmware
completed

Cluster upload AP firmware
failed

Cluster add AP firmware
completed

Cluster add AP firmware started

Cluster add AP firmware failed Cluster name is changed

Unsync NTP time

Cluster upload KSP file started Cluster upload KSP file completed

Cluster upload KSP file failed

Configuration backup started

Configuration backup succeeded

Configuration backup failed

Configuration restore
succeeded

Configuration restore failed

AP Certificate Expired

AP Certificate Updated

Configuration restore started

Upgrade SSTable failed

Reindex Elastic Search finished Initiated APs contact APR

Node IPv6 address added

Node IPv6 address deleted

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

221

Events Types
Cluster Events

Cluster created successfully
Table 269. 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 270. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

222

Events Types
Cluster Events

New node failed to join
Table 271. New node failed to join event
Event

New node failed to join

Event Type

newNodeJoinFailed

Event Code

803

Severity

Critical

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 272. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

223

Events Types
Cluster Events

Node removal failed
Table 273. 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}].

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.

Node out of service
Table 274. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

224

Events Types
Cluster Events

Cluster in maintenance state
Table 275. 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 maintenance state.

Auto Clearance

This event triggers the alarm 804, which is auto cleared by the event
code 808.

Cluster back in service
Table 276. 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 277. Cluster backup completed event
Event

Cluster backup completed

Event Type

backupClusterSuccess

Event Code

809

Severity

Informational

Attribute

“clusterName”=”xxx”

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

225

Events Types
Cluster Events

Table 277. Cluster backup completed event
Displayed on the web
interface

Cluster [{clusterName}] backup completed

Description

This event occurs when a cluster backup is complete.

Cluster backup failed
Table 278. 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}].

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 279. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

226

Events Types
Cluster Events

Cluster restore failed
Table 280. 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.

Cluster node upgrade completed
Table 281. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

227

Events Types
Cluster Events

Entire cluster upgraded successfully
Table 282. 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.

Cluster upgrade failed
Table 283. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

228

Events Types
Cluster Events

Cluster application stopped
Table 284. 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.

Cluster application started
Table 285. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

229

Events Types
Cluster Events

Cluster backup started
Table 286. 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.

Cluster upgrade started
Table 287. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

230

Events Types
Cluster Events

Cluster leader changed
Table 288. 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.

Node bond interface down
Table 289. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

231

Events Types
Cluster Events

Node bond interface up
Table 290. 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.

Node IP address changed
Table 291. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

232

Events Types
Cluster Events

Node physical interface down
Table 292. 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.

Node physical interface up

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

233

Events Types
Cluster Events

Table 293. 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 294. 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.

Auto Clearance

This event triggers the alarm 811, which is auto cleared by the event
code 826.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

234

Events Types
Cluster Events

NTP time synchronized
Table 295. 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 are
synchronized with the NTP server.

Cluster node shutdown
Table 296. 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.5, 800-71290-001 Rev A

235

Events Types
Cluster Events

Cluster upload started
Table 297. 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 298. 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.5, 800-71290-001 Rev A

236

Events Types
Cluster Events

Cluster upload failed
Table 299. 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 300. 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.5, 800-71290-001 Rev A

237

Events Types
Cluster Events

Cluster remove node started
Table 301. 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 removal from a cluster is started.

Node back in service
Table 302. 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.5, 800-71290-001 Rev A

238

Events Types
Cluster Events

Disk usage exceed threshold
Table 303. 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%.

Auto Clearance

This event triggers the alarm 834, which is auto cleared by the event
code 838.

Cluster out of service
Table 304. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

239

Events Types
Cluster Events

Initiated moving APs in node to a new cluster
Table 305. 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 tor SZ.

Cluster upload vSZ-D firmware started
Table 306. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

240

Events Types
Cluster Events

Cluster upload vSZ-D firmware completed
Table 307. 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 vSZ Data Plane firmware upload for a cluster is
completed successfully.

Cluster upload vSZ-D firmware failed
Table 308. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

241

Events Types
Cluster Events

Cluster upload AP firmware started
Table 309. 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.

Cluster upload AP firmware completed
Table 310. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

242

Events Types
Cluster Events

Cluster upload AP firmware failed
Table 311. 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.

Auto Clearance

This event triggers the alarm 850, which is auto cleared by the event
code 851.

Cluster add AP firmware started
Table 312. Cluster add AP firmware started event
Event

Cluster add AP firmware started

Event Type

clusterAddAPFirmwareStart

Event Code

851

Severity

Informational

Attribute

"clusterName"="xxx"

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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

243

Events Types
Cluster Events

Cluster add AP firmware completed
Table 313. 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

Starting add AP firmware in cluster [{clusterName}]

Description

This event occurs when the cluster add process to the AP firmware is
successful.

Cluster add AP firmware failed
Table 314. 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.

Auto Clearance

This event triggers the alarm 853, which is auto cleared by the event
code 852.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

244

Events Types
Cluster Events

Cluster name is changed
Table 315. 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.

Unsync NTP time
Table 316. Unsync NTP time event
Event

Unsync NTP time

Event Type

unsyncNTPTime

Event Code

855

Severity

Major

Attribute

"reason"="xxx", "clusterName"="xxx, "status"="xxx"

Displayed on the web
interface

Node [{nodeName}] time is not synchronized because of [{reason}]. The
time difference is [{status}] seconds.

Description

This event occurs when the cluster time is not synchronized.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

245

Events Types
Cluster Events

Cluster upload KSP file started
Table 317. Cluster upload KSP file started event
Event

Cluster upload KSP file started

Event Type

clusterUploadKspFileStart

Event Code

856

Severity

Informational

Attribute

"clusterName"="xxx"

Displayed on the web
interface

Starting upload KSP file in cluster [{clusterName}]

Description

This event occurs when the KSP file uploads to a cluster.

Cluster upload KSP file completed
Table 318. Cluster upload KSP file completed event
Event

Cluster upload KSP file completed

Event Type

clusterUploadKspFileSuccess

Event Code

857

Severity

Informational

Attribute

"clusterName"="xxx"

Displayed on the web
interface

Cluster [{clusterName}] upload KSP file completed.

Description

This event occurs when the KSP file upload is successful to the cluster.

Cluster upload KSP file failed
Table 319. Cluster upload KSP file failed event
Event

Cluster upload KSP file failed

Event Type

clusterUploadKspFileFailed

Event Code

858

Severity

Major

Attribute

"clusterName"="xxx"

Displayed on the web
interface

Cluster [{clusterName}] upload KSP file failed.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

246

Events Types
Cluster Events

Table 319. Cluster upload KSP file failed event
Description

This event occurs when the cluster fails to upload the ksp file.

Auto Clearance

This event triggers the alarm 858, which is auto cleared by the event
code 857.

Configuration backup started
Table 320. 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.

Configuration backup succeeded
Table 321. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

247

Events Types
Cluster Events

Configuration backup failed
Table 322. 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 323. Configuration restore succeeded event
Event

Configuration restore succeeded

Event Type

clusterCfgRestoreSuccess

Event Code

863

Severity

Informational

Attribute

"clusterName"="xxx"

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 324. Configuration restore failed event
Event

Configuration restore failed

Event Type

clusterCfgRestoreFailed

Event Code

864

Severity

Major

Attribute

"clusterName"="xxx"

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

248

Events Types
Cluster Events

Table 324. Configuration restore failed event
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 325. 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.

AP Certificate Updated
Table 326. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

249

Events Types
Cluster Events

Configuration restore started
Table 327. Configuration restore started event
Event

Configuration restore started

Event Type

clusterCfgRestoreStarted

Event Code

867

Severity

Informational

Attribute

"clusterName"="xxx"

Displayed on the web
interface

Cluster [{clusterName}] configuration restore started.

Description

This event occurs when the configuration restore starts.

Upgrade SSTable failed
Table 328. Upgrade SSTable failed event
Event

Upgrade SSTable failed

Event Type

upgradeSSTableFailed

Event Code

868

Severity

Major

Attribute

"nodeName"="xxx"

Displayed on the web
interface

Node [{nodeName}] upgrade SSTable failed.

Description

This event occurs when the upgrade to SS table fails.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

250

Events Types
Cluster Events

Reindex Elastic Search finished
Table 329. Reindex Elastic Search finished event
Event

Reindex Elastic Search finished

Event Type
Event Code

869

Severity

Major

Attribute
Displayed on the web
interface
Description

This event occurs when the re-index elastic search is completed.

Initiated APs contact APR
Table 330. Initiated APs contact APR event
Event

Initiated APs contact APR

Event Type

clusterInitContactApr

Event Code

870

Severity

Major

Attribute

"clusterName"="xxx"

Displayed on the web
interface

Cluster [{clusterName}] initiated APs contact APR

Description

This event occurs on receiving APs contact APR configuration
command.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

251

Events Types
Cluster Events

Node IPv6 address added
Table 331. 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.

Node IPv6 address deleted
Table 332. 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.5, 800-71290-001 Rev A

252

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
• VLAN configuration mismatch on non-DHCP/NAT WLAN
• VLAN configuration mismatch on a DHCP/NAT WLAN

Configuration updated
Table 333. 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 334. Configuration update failed event
Event

Configuration update failed

Event Type

cfgUpdFailed

Event Code

1008

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

253

Events Types
Configuration Events

Table 334. Configuration update failed event
Severity

Debug

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 335. 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 336. Incorrect flat file configuration event
Event

Incorrect flat file configuration

Event Type

incorrectFlatFileCfg

Event Code

1012

Severity

Major

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

254

Events Types
Configuration Events

Table 336. Incorrect flat file configuration event
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”

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 337. 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 338. 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}].

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

255

Events Types
Configuration Events

Table 338. AP configuration generation failed event
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.5, 800-71290-001 Rev A

256

Events Types
Configuration Events

End-of-life AP model detected
Table 339. 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.

VLAN configuration mismatch on non-DHCP/NAT
WLAN
Table 340. VLAN configuration mismatch on non-DHCP/NAT WLAN event
Event

VLAN configuration mismatch detected between configured and
resolved VLAN with DVLAN/VLAN pooling configuration on non-DHCP/
NAT WLAN.

Event Type

apCfgNonDhcpNatWlanVlanConfigMismatch

Event Code

1024

Severity

Critical

Attribute

"ssid"="xxxx", "configuredVlan"="5", "vlanId"="11",
"apMac"="xx:xx:xx:xx:xx:xx"

Displayed on the web
interface

DHCP/NAT gateway AP [{apMac}] detected VLAN configuration
mismatch on non-DHCP/NAT WLAN [{ssid}]. Configured VLAN is
[{configuredVlan}] and resolved VLAN is [{vlanId}]. Clients may not be
able to get IP or access Internet.

Description

This event occurs when the AP detects a non DHCP/NAT WLAN. VLAN
configuration mismatches with DVLAN/VLAN pooling configuration on
gateway AP.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

257

Events Types
Configuration Events

VLAN configuration mismatch on a DHCP/NAT WLAN
Table 341. VLAN configuration mismatch on a DHCP/NAT WLAN event
Event

VLAN configuration mismatch detected between configured and
resolved VLAN with DVLAN/VLAN pooling configuration on a nonDHCP/NAT WLAN

Event Type

apCfgDhcpNatWlanVlanConfigMismatch

Event Code

1025

Severity

Critical

Attribute

“ssid”=”xxxx”, “vlanID”=”xxxx”, “configuredVlan”=”5”,
“vlanId”=”11”, "apMac"="xx:xx:xx:xx:xx:xx"

Displayed on the web
interface

DHCP/NAT gateway AP [apMac}] detected VLAN configuration
mismatch on DHCP/NAT WLAN [{ssid}]. Configured VLAN is
[{configuredVlan}] and resolved VLAN is [{vlanId}]. Clients may not be
able to get IP or access Internet.

Description

This event occurs when the AP detects a DHCP/NAT WLAN. VLAN
configuration mismatches with DVLAN/VLAN pooling configuration on
gateway AP.

NOTE: Refer to Configuration Alarms.
show upgrade-state

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

258

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 of data center side
successfully connects to the
CALEA server

Data plane of data center side Data plane successfully connects Data plane fails to connects to
fails to connect to the CALEA to the other data plane
the other data plane
server
Data plane disconnects to the Start CALEA mirroring client
other data plane
Data plane DHCP IP pool
usage rate is 100 percent

Stop CALEA mirroring client

Data plane DHCP IP pool usage
rate is 80 percent

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

259

Events Types
Data Plane Events

Data plane discovered
Table 342. 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}].

Description

This event occurs when the data plane successfully connects to the
controller.

Data plane discovery failed
Table 343. 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 344. 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"

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

260

Events Types
Data Plane Events

Table 344. Data plane configuration updated event
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.5, 800-71290-001 Rev A

261

Events Types
Data Plane Events

Data plane configuration update failed
Table 345. 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 to SZ.
Table 346. 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”, "reason"="xxxxx"

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.5, 800-71290-001 Rev A

262

Events Types
Data Plane Events

Data plane heartbeat lost
Table 347. 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 348. 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 349. 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.5, 800-71290-001 Rev A

263

Events Types
Data Plane Events

Table 349. 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 350. 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 351. 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.5, 800-71290-001 Rev A

264

Events Types
Data Plane Events

Data plane connected
Table 352. 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 353. 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.5, 800-71290-001 Rev A

265

Events Types
Data Plane Events

Data plane physical interface down
Table 354. 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 355. 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.5, 800-71290-001 Rev A

266

Events Types
Data Plane Events

Data plane packet pool is under low water mark
Table 356. 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 357. 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 falls below the critical
water mark level.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

267

Events Types
Data Plane Events

Data plane packet pool is above high water mark
Table 358. 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 above the highwater mark.

Data plane core dead
Table 359. 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.5, 800-71290-001 Rev A

268

Events Types
Data Plane Events

Data plane process restarted
Table 360. 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 to SZ.

Data plane discovery succeeded
Table 361. 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
controller successfully.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

269

Events Types
Data Plane Events

NOTE: Event 532 is not applicable to SZ.

Data plane managed
Table 362. 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 the data plane is approved by the controller.

NOTE: Events 537 to 553 are not applicable to SZ.

Data plane deleted
Table 363. 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 the data plane is deleted.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

270

Events Types
Data Plane Events

Data plane license is not enough
Table 364. 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 365. 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 the data plane starts the upgrade process.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

271

Events Types
Data Plane Events

Data plane upgrading
Table 366. 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 the data plane starts to upgrade programs and
configuration.

Data plane upgrade succeeded
Table 367. 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 the data plane upgrade is successful.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

272

Events Types
Data Plane Events

Data plane upgrade failed
Table 368. 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 the data plane upgrade fails.

Auto Clearance

This event triggers the alarm 553, which is auto cleared by the event
code 552.

Data plane of data center side successfully connects to
the CALEA server
Table 369. Data plane of data center side successfully connects to the CALEA server event
Event

Data plane of data center side successfully connects to the CALEA
server

Event Type

dpDcToCaleaConnected

Event Code

1257

Severity

Informational

Attribute

“dpKey”=“xx:xx:xx:xx:xx:xx”, “caleaServerIP”=“xxx.xxx.xxx.xxx”,
"dpIP"="xx.xx.xx.xx", "reason"="xxxxxx"

Displayed on the web
interface

Data Plane of Data Center side[{dpName&&dpKey}] successfully
connects to the CALEA server[{caleaServerIP}].

Description

This event occurs when the data plane successfully connects to the
CALEA server.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

273

Events Types
Data Plane Events

Data plane of data center side fails to connect to the
CALEA server
Table 370. Data plane of data center side fails to connect to the CALEA server.event
Event

Data plane of data center side fails to connect to the CALEA server.

Event Type

dpDcToCaleaConnectFail

Event Code

1258

Severity

Major

Attribute

“dpKey”=“xx:xx:xx:xx:xx:xx”, “caleaServerIP”=“xxx.xxx.xxx.xxx”,
"dpIP"="xx.xx.xx.xx", "reason"="xxxxxx"

Displayed on the web
interface

Data Plane of Data Center side[{dpName&&dpKey}] fails to connects to
the CALEA server[{caleaServerIP}]

Description

This event occurs when the data plane fails to connect to the CALEA
server.

Auto Clearance

This event triggers the alarm 1258, which is auto cleared by the event
code 1257.

Data plane successfully connects to the other data
plane
Table 371. Data plane successfully connects to the other data plane event
Event

Data plane successfully connects to the other data plane

Event Type

dpP2PTunnelConnected

Event Code

1260

Severity

Informational

Attribute

“dpKey”=“xx:xx:xx:xx:xx:xx”, "dpIP"="xx.xx.xx.xx",
“targetDpKey”=“xx:xx:xx:xx:xx:xx”, “targetDpIp”=“xxx.xxx.xxx.xxx”

Displayed on the web
interface

Data Plane[{dpName&&dpKey}] successfully connects to the other Data
Plane[{targetDpKey&&targetDpIp}]

Description

This event occurs when the data plane connects to another data plane.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

274

Events Types
Data Plane Events

Data plane fails to connects to the other data plane
Table 372. Data plane fails to connects to the other data plane event
Event

Data plane fails to connects to the other data plane

Event Type

dpP2PTunnelConnectFail

Event Code

1261

Severity

Warning

Attribute

“dpKey”=“xx:xx:xx:xx:xx:xx”, "dpIP"="xx.xx.xx.xx",
“targetDpKey”=“xx:xx:xx:xx:xx:xx”, “targetDpIp”=“xxx.xxx.xxx.xxx”

Displayed on the web
interface

Data Plane[{dpName&&dpKey}] fails connects to the other Data
Plane[{targetDpKey&&targetDpIp}]

Description

This event occurs when the data plane fails to connect to another data
plane.

Auto Clearance

This event triggers the alarm 1261, which is auto cleared by the event
code 1260.

Data plane disconnects to the other data plane
Table 373. Data plane disconnects to the other data plane event
Event

Data plane disconnects to the other data plane

Event Type

dpP2PTunnelDisconnected

Event Code

1262

Severity

Informational

Attribute

“dpKey”=“xx:xx:xx:xx:xx:xx”, "dpIP"="xx.xx.xx.xx",
“targetDpKey”=“xx:xx:xx:xx:xx:xx”,“targetDpIp”=“xxx.xxx.xxx.xxx”

Displayed on the web
interface

Data Plane[{dpName&&dpKey}] disconnects to the other Data
Plane[{targetDpKey&&targetDpIp}]

Description

This event occurs when the data plane disconnects from another data
plane.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

275

Events Types
Data Plane Events

Start CALEA mirroring client
Table 374. Start CALEA mirroring client event
Event

Start CALEA mirroring client

Event Type

dpStartMirroringClient

Event Code

1263

Severity

Informational

Attribute

"clientMac"="xx:xx:xx:xx:xx:xx", "ssid"="xxxxx",
"apMac"="xx:xx:xx:xx:xx:xx", "apIpAddress"="xx.xx.xx.xx",
"dpKey"="xx:xx:xx:xx:xx:xx", "dpIP"="xx.xx.xx.xx"

Displayed on the web
interface

Start CALEA mirroring client [{userName||IP||clientMac}] on WLAN
[{ssid}] from AP [{apName&&apMac}]

Description

This event occurs when the Calea server starts mirroring the client
image.

Stop CALEA mirroring client
Table 375. Stop CALEA mirroring client event
Event

Stop CALEA mirroring client

Event Type

dpStopMirroringClient

Event Code

1264

Severity

Informational

Attribute

"clientMac"="xx:xx:xx:xx:xx:xx", "ssid"="xxxxx",
"apMac"="xx:xx:xx:xx:xx:xx", "apIpAddress"="xx.xx.xx.xx",
"dpKey"="xx:xx:xx:xx:xx:xx", "dpIP"="xx.xx.xx.xx"

Displayed on the web
interface

Stop CALEA mirroring client [{userName||IP||clientMac}] on WLAN
[{ssid||authType}] from AP [{apName&&apMac}]. TxBytes[{txBytes}]

Description

This event occurs when the Calea server stops mirroring the client
image.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

276

Events Types
Data Plane Events

Data plane DHCP IP pool usage rate is 100 percent
Table 376. Data plane DHCP IP pool usage rate is 100 percent event
Event

Data plane DHCP IP pool usage rate is 100 percent

Event Type

dpDhcpIpPoolUsageRate100

Event Code

1265

Severity

Critical

Attribute

“dpKey”=“xx:xx:xx:xx:xx:xx”

Displayed on the web
interface

Data Plane[{dpName&&dpKey}] DHCP IP Pool usage rate is 100
percent

Description

This event occurs when the data plane DHCP pool usage rate is 100%.

Data plane DHCP IP pool usage rate is 80 percent
Table 377. Data plane DHCP IP pool usage rate is 80 percent event
Event

Data plane DHCP IP pool usage rate is 80 percent

Event Type

dpDhcpIpPoolUsageRate80

Event Code

1266

Severity

Warning

Attribute

“dpName="xxxxxxxx", “dpKey”=“xx:xx:xx:xx:xx:xx”

Displayed on the web
interface

Data Plane[{dpName&&dpKey}] DHCP IP Pool usage rate is 80 percent

Description

This event occurs when the data plane DHCP pool usage rate is 80%.

•

NOTE: Refer to Data Plane Alarms.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

277

Events Types
IPMI Events

IPMI Events
NOTE: This section is not applicable to vSZ-E.
Following are the events related to IPMIs.
• ipmiThempBB
• ipmiThempP
• ipmiFan
• ipmiFanStatus
• ipmiREThempBB
• ipmiREThempP
• ipmiREFan
• ipmiREFanStatus

ipmiThempBB
Table 378. 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.5, 800-71290-001 Rev A

278

Events Types
IPMI Events

ipmiThempP
Table 379. 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 occurs when the processor temperature on the control plane
reaches the threshold value. The threshold value is 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 380. 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.5, 800-71290-001 Rev A

279

Events Types
IPMI Events

ipmiFanStatus
Table 381. 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 382. 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.5, 800-71290-001 Rev A

280

Events Types
IPMI Events

ipmiREThempP
Table 383. 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 384. 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.5, 800-71290-001 Rev A

281

Events Types
IPMI Events

ipmiREFanStatus
Table 385. 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 normal status.

NOTE: Refer to IPMI Alarms.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

282

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 386. 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.5, 800-71290-001 Rev A

283

Events Types
Licensing Interface Events

License sync failed
Table 387. 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 388. 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.5, 800-71290-001 Rev A

284

Events Types
Licensing Interface Events

License import failed
Table 389. 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 390. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

285

Events Types
Licensing Interface Events

License going to expire
Table 391. 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}].

Description

This event occurs when the validity of the license is going to expire.

Insufficient license capacity
Table 392. 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.5, 800-71290-001 Rev A

286

Events Types
SCI Events

SCI Events
Following are the events related to SCI (Small Cell Insight).
• Connect to SCI
• Disconnect to SCI
• Connect to SCI failure
• SCI has been disabled
• SCI and FTP have been disabled

Connect to SCI
Table 393. Connect to SCI event
Event

Connect to SCI

Event Type

connectedToSci

Event Code

4001

Severity

Informational

Attribute

"id"="SCI Server","ip"="2.2.2.2","port"="8883","userName"="admin"

Displayed on the web
interface

Connect to SCI with system id [{id}], address [{ip}:{port}] and login user
[{userName}].

Description

This event occurs when the controller connects to SCI.

Disconnect to SCI
Table 394. Disconnect to SCI event
Event

Disconnect to SCI (Smart Cell Insight)

Event Type

disconnectedFromSci

Event Code

4002

Severity

Warning

Attribute

id="SCI Server","ip"="2.2.2.2","port"="8883","userName"="admin"

Displayed on the web
interface

Disconnect to SCI with system id [{id}], address [{ip}:{port}] and login
user [{userName}].

Description

This event occurs when the controller disconnects from SCI.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

287

Events Types
SCI Events

Connect to SCI failure
Table 395. Connect to SCI failure event
Event

Connect to SCI failure (Smart Cell Insight)

Event Type

connectToSciFailure

Event Code

4003

Severity

Major

Displayed on the web
interface

Try to connect to SCI with all SCI profiles but failure.

Description

This event occurs when the controller tries connecting to SCI with its
profiles but fails.

Auto Clearance

This event triggers the alarm 4003, which is auto cleared by the event
code 4002.

SCI has been disabled
Table 396. SCI has been disabled event
Event

SCI has been disabled

Event Type

disabledSciDueToUpgrade

Event Code

4004

Severity

Warning

Displayed on the web
interface

SCI has been disabled due to SZ upgrade, please reconfigure SCI if
need

Description

This event occurs when the SCI is disabled due to controller upgrade.
This could require reconfiguration of SCI.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

288

Events Types
SCI Events

SCI and FTP have been disabled
Table 397. SCI and FTP have been disabled event
Event

SCI and FTP have been disabled

Event Type

disabledSciAndFtpDueToMutuallyExclusive

Event Code

4005

Severity

Warning

Displayed on the web
interface

SCI and FTP have been disabled. It is recommended to enable SCI
instead of FTP

Description

This event occurs when the SCI and FTP are disabled.

NOTE: Refer to SCI Alarms.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

289

Events Types
Session Events

Session Events
Following event is related to user equipment TTG session.

Delete all sessions
Table 398. 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, RWSG or CLI.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

290

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

Data plane of data center side
successfully connects to the
CALEA server

{produce.short.name} sent query
venues report

Data plane of data center side Data plane successfully
Data plane successfully connects
fails to connect to the CALEA connects to the other data plane to the other data plane
server
Data plane fails to connects to Data plane disconnects to the
the other data plane
other data plane

Start CALEA mirroring client in
data plane

Stop CALEA mirroring client in Data plane DHCP IP pool usage Data plane DHCP IP pool usage
data plane
rate is 100 percent
rate is 80 percent

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

291

Events Types
System Events

All data planes in the zone
affinity profile are
disconnected

CALEA UE Matched

ZD AP migrating

ZD AP migrated

ZD AP rejected

ZD AP migration failed

Database error

Database error

No LS responses
Table 399. 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 400. 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 when SmartZone tries
connecting to the location based service.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

292

Events Types
System Events

{produce.short.name} connected to LS
Table 401. {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”=““

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 402. {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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

293

Events Types
System Events

{produce.short.name} received passive request
Table 403. {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.

{produce.short.name} sent controller information report
Table 404. {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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

294

Events Types
System Events

{produce.short.name} received management request
Table 405. {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.

{produce.short.name} sent AP info by venue report
Table 406. {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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

295

Events Types
System Events

{produce.short.name} sent query venues report
Table 407. {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.

{produce.short.name} sent associated client report
Table 408. {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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

296

Events Types
System Events

{produce.short.name} forwarded calibration request to
AP
Table 409. {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.

{produce.short.name} forwarded footfall request to AP
Table 410. {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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

297

Events Types
System Events

{produce.short.name} received unrecognized request
Table 411. {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 412. Syslog server reachable event
Event

Syslog server reachable

Event Type

syslogServerReachable

Event Code

750

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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

298

Events Types
System Events

Syslog server unreachable
Table 413. 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 414. 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”

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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

299

Events Types
System Events

Generate AP config for plane load rebalance succeeded
Table 415. 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 416. 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.5, 800-71290-001 Rev A

300

Events Types
System Events

FTP transfer
Table 417. 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 418. 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 419. 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.5, 800-71290-001 Rev A

301

Events Types
System Events

Table 419. File upload event
Description

This event occurs when the backup file upload fails.

Email sent successfully
Table 420. 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 the system sends mail successfully.

Email sent failed
Table 421. 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.5, 800-71290-001 Rev A

302

Events Types
System Events

SMS sent successfully
Table 422. 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 SMS successfully.

SMS sent failed
Table 423. 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 SMS.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

303

Events Types
System Events

Process restart
Table 424. 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 425. 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.5, 800-71290-001 Rev A

304

Events Types
System Events

Keepalive failure
Table 426. 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 427. 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.5, 800-71290-001 Rev A

305

Events Types
System Events

NOTE: Events 1257 to 1267 are not applicable for SCG.

Data plane of data center side successfully connects to
the CALEA server
Table 428. Data plane of data center side successfully connects to the CALEA server event
Event

Data plane of data center side successfully connects to the CALEA
server

Event Type

dpDcToCaleaConnected

Event Code

1257

Severity

Informational

Attribute

“dpKey”=“xx:xx:xx:xx:xx:xx”, “caleaServerIP”=“xxx.xxx.xxx.xxx”,
"dpIP"="xx.xx.xx.xx", "reason"="xxxxxx"

Displayed on the web
interface

Data Plane of Data Center side[{dpName&&dpKey}] successfully
connects to the CALEA server[{caleaServerIP}].

Description

This event occurs when data plane successfully connects to the CALEA
server.

Data plane of data center side fails to connect to the
CALEA server
Table 429. Data plane of data center side fails to connect to the CALEA server event
Event

Data plane of data center side fails to connect to the CALEA server.

Event Type

dpDcToCaleaConnectFail

Event Code

1258

Severity

Major

Attribute

“dpKey”=“xx:xx:xx:xx:xx:xx”, “caleaServerIP”=“xxx.xxx.xxx.xxx”,
"dpIP"="xx.xx.xx.xx", "reason"="xxxxxx"

Displayed on the web
interface

Data Plane of Data Center side[{dpName&&dpKey}] fails to connects to
the CALEA server[{caleaServerIP}]

Description

This event occurs when the data plane fails to connect to the CALEA
server.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

306

Events Types
System Events

Table 429. Data plane of data center side fails to connect to the CALEA server event
Auto Clearance

This event triggers the alarm 1258, which is auto cleared by the event
code 1257.

Data Plane of data center side disconnects to CALEA
server
Table 430. Data Plane of data center side disconnects to CALEA server event
Event

Data Plane of data center side disconnects to CALEA server.

Event Type

dpDcToCaleaDisconnected

Event Code

1259

Severity

Informational

Attribute

“dpKey”=“xx:xx:xx:xx:xx:xx”, “caleaServerIP”=“xxx.xxx.xxx.xxx”,
"dpIP"="xx.xx.xx.xx", "reason"="xxxxxx"

Displayed on the web
interface

Data Plane of Data Center side[{dpName&&dpKey}] fails to connects to
the CALEA server[{caleaServerIP}]

Description

This event occurs when the data plane disconnects from the CALEA
server.

Data plane successfully connects to the other data
plane
Table 431. Data plane successfully connects to the other data plane event
Event

Data plane successfully connects to the other data plane

Event Type

dpP2PTunnelConnected

Event Code

1260

Severity

Informational

Attribute

“dpKey”=“xx:xx:xx:xx:xx:xx”, "dpIP"="xx.xx.xx.xx",
“targetDpKey”=“xx:xx:xx:xx:xx:xx”, “targetDpIp”=“xxx.xxx.xxx.xxx”

Displayed on the web
interface

Data Plane[{dpName&&dpKey}] successfully connects to the other Data
Plane[{targetDpKey&&targetDpIp}]

Description

This event occurs when the data plane connect to another data plane.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

307

Events Types
System Events

Data plane fails to connects to the other data plane
Table 432. Data plane fails to connects to the other data plane event
Event

Data plane fails to connects to the other data plane

Event Type

dpP2PTunnelConnectFail

Event Code

1261

Severity

Warning

Attribute

“dpKey”=“xx:xx:xx:xx:xx:xx”, "dpIP"="xx.xx.xx.xx",
“targetDpKey”=“xx:xx:xx:xx:xx:xx”, “targetDpIp”=“xxx.xxx.xxx.xxx”

Displayed on the web
interface

Data Plane[{dpName&&dpKey}] fails connects to the other Data
Plane[{targetDpKey&&targetDpIp}]

Description

This event occurs when the data plane fails to connect to another data
plane.

Auto Clearance

This event triggers the alarm 1261, which is auto cleared by the event
code 1260.

Data plane disconnects to the other data plane
Table 433. Data plane disconnects to the other data plane event
Event

Data plane disconnects to the other data plane

Event Type

dpP2PTunnelDisconnected

Event Code

1262

Severity

Major

Attribute

“dpKey”=“xx:xx:xx:xx:xx:xx”, "dpIP"="xx.xx.xx.xx",
“targetDpKey”=“xx:xx:xx:xx:xx:xx”,“targetDpIp”=“xxx.xxx.xxx.xxx”

Displayed on the web
interface

Data Plane[{dpName&&dpKey}] disconnects to the other Data
Plane[{targetDpKey&&targetDpIp}]

Description

This event occurs when the data plane disconnects from another data
plane.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

308

Events Types
System Events

Start CALEA mirroring client in data plane
Table 434. Start CALEA mirroring client in data plane event
Event

Start CALEA mirroring client in data plane

Event Type

dpStartMirroringClient

Event Code

1263

Severity

Informational

Attribute

"clientMac"="xx:xx:xx:xx:xx:xx", "ssid"="xxxxx",
"apMac"="xx:xx:xx:xx:xx:xx", "apIpAddress"="xx.xx.xx.xx",
"dpKey"="xx:xx:xx:xx:xx:xx", "dpIP"="xx.xx.xx.xx"

Displayed on the web
interface

Start CALEA mirroring client [{userName||IP||clientMac}] on WLAN
[{ssid}] from AP [{apName&&apMac}]

Description

This event occurs when the Calea server starts mirroring the client
image.

Stop CALEA mirroring client in data plane
Table 435. Stop CALEA mirroring client in data plane event
Event

Stop CALEA mirroring client in data plane

Event Type

dpStopMirroringClient

Event Code

1264

Severity

Warning

Attribute

"clientMac"="xx:xx:xx:xx:xx:xx", "ssid"="xxxxx",
"apMac"="xx:xx:xx:xx:xx:xx", "apIpAddress"="xx.xx.xx.xx",
"dpKey"="xx:xx:xx:xx:xx:xx", "dpIP"="xx.xx.xx.xx"

Displayed on the web
interface

Stop CALEA mirroring client [{userName||IP||clientMac}] on WLAN
[{ssid||authType}] from AP [{apName&&apMac}]. TxBytes[{txBytes}]

Description

This event occurs when the Calea server stops mirroring the client
image.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

309

Events Types
System Events

Data plane DHCP IP pool usage rate is 100 percent
Table 436. Data plane DHCP IP pool usage rate is 100 percent event
Event

Data plane DHCP IP pool usage rate is 100 percent

Event Type

dpDhcpIpPoolUsageRate100

Event Code

1265

Severity

Critical

Attribute

“dpKey”=“xx:xx:xx:xx:xx:xx”

Displayed on the web
interface

Data Plane[{dpName&&dpKey}] DHCP IP Pool usage rate is 100
percent

Description

This event occurs when the data plane DHCP pool usage rate is 100%.

Data plane DHCP IP pool usage rate is 80 percent
Table 437. Data plane DHCP IP pool usage rate is 80 percent event
Event

Data plane DHCP IP pool usage rate is 80 percent

Event Type

dpDhcpIpPoolUsageRate80

Event Code

1266

Severity

Warning

Attribute

“dpName="xxxxxxxx", “dpKey”=“xx:xx:xx:xx:xx:xx”

Displayed on the web
interface

Data Plane[{dpName&&dpKey}] DHCP IP Pool usage rate is 80 percent

Description

This event occurs when the data plane DHCP pool usage rate is 80%.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

310

Events Types
System Events

All data planes in the zone affinity profile are
disconnected
Table 438. All data planes in the zone affinity profile are disconnected event
Event

All data planes in the zone affinity profile are disconnected

Event Type

zoneAffinityLastDpDisconnected

Event Code

1267

Severity

Major

Attribute

“dpName="xxxxxxxx",“dpKey”=“xx:xx:xx:xx:xx:xx”,
"zoneAffinityProfileId"="xxxxxxxx"

Displayed on the web
interface

The Last one Data Plane[{dpName&&dpKey}] is disconnected Zone
Affinity profile[{zoneAffinityProfileId}] .

Description

This event occurs when all the data planes disconnect from the zone
affinity profile.

CALEA UE Matched
Table 439. CALEA UE Matched event
Event

CALEA UE Matched

Event Type

dpCaleaUeInterimMatched

Event Code

1268

Severity

Informational

Attribute

"clientMac"="xx:xx:xx:xx:xx:xx", "ssid"="xxxxx",
"apMac"="xx:xx:xx:xx:xx:xx", "apIpAddress"="xx.xx.xx.xx",
"dpKey"="xx:xx:xx:xx:xx:xx", "dpIP"="xx.xx.xx.xx", "txBytes"="xxxxx",
"rxBytes"="xxxxx"

Displayed on the web
interface

CALEA matches client [{clientMac}] on WLAN [{ssid||authType}] from AP
[{apName&&apMac}]. TxBytes[{txBytes}], RxBytes[{rxBytes}].

Description

This event occurs when data plane CALEA user equipment and client
matches.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

311

Events Types
System Events

ZD AP migrating
Table 440. 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 being upgraded to a
SmartZone firmware image.

ZD AP migrated
Table 441. 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 successfully completed
upgrading its firmware to SmartZone controller firmware.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

312

Events Types
System Events

ZD AP rejected
Table 442. 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 has not been upgraded
with the SmartZone controller AP firmware because of an ACL setting.

ZD AP migration failed
Table 443. 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 the ZoneDirector AP fails to upgrade to the
SmartZone AP firmware image.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

313

Events Types
System Events

Database error
Table 444. 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 445. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

314

Events Types
System Events

NOTE: Refer to System Alarms.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

315

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 446. 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 as
60% to 90%.

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.5, 800-71290-001 Rev A

316

Events Types
Threshold Events

Memory threshold exceeded
Table 447. 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.
The disk threshold value for SZ-100 is 85% and 90% for vSZ-E.

Auto Clearance

This event triggers the alarm 951, which is auto cleared by the event
code 954.

Disk usage threshold exceeded
Table 448. 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.5, 800-71290-001 Rev A

317

Events Types
Threshold Events

CPU threshold back to normal
Table 449. 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 450. 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 451. 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.5, 800-71290-001 Rev A

318

Events Types
Threshold Events

Table 451. Disk threshold back to normal event
Description

This event occurs when the disk usage comes back to normal.

License threshold exceeded
Table 452. 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 453. 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.5, 800-71290-001 Rev A

319

Events Types
Threshold Events

Rate limit threshold restored
Table 454. 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.5, 800-71290-001 Rev A

320

Events Types
Threshold Events

Rate limit for TOR surpassed
Table 455. 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 456. 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.5, 800-71290-001 Rev A

321

Events Types
Threshold Events

The number of devices exceeded its limit
Table 457. 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.5, 800-71290-001 Rev A

322

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
Table 458. 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.5, 800-71290-001 Rev A

323

Events Types
Tunnel Events - Access Point (AP)

Data plane rejected a tunnel request
Table 459. 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
Table 460. 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.5, 800-71290-001 Rev A

324

Events Types
Tunnel Events - Access Point (AP)

AP created a tunnel
Table 461. 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
Table 462. 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.5, 800-71290-001 Rev A

325

Events Types
Tunnel Events - Access Point (AP)

AP SoftGRE tunnel fails over primary to secondary
Table 463. 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 an AP moves from a primary to a secondary
GRE.

AP SoftGRE tunnel fails over secondary to primary
Table 464. 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 an AP moves from a secondary to a primary
GRE.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

326

Events Types
Tunnel Events - Access Point (AP)

AP SoftGRE gateway reachable
Table 465. 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 an AP builds a soft GRE tunnel successfully.

AP SoftGRE gateway not reachable
Table 466. 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 an 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.5, 800-71290-001 Rev A

327

Events Types
Tunnel Events - Access Point (AP)

Data plane set up a tunnel
NOTE: This event is not applicable to vSZ-E.
Table 467. 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 468. 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.5, 800-71290-001 Rev A

328

Events Types
Tunnel Events - Access Point (AP)

AP is disconnected from secure gateway
Table 469. 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 the secure
gateway.

AP secure gateway association failure
Table 470. 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.5, 800-71290-001 Rev A

329

Events Types
Tunnel Events - Data Plane

Tunnel Events - Data Plane
NOTE: Events 618, 619 and 623 are applicable to SZ-100.

Following are the events related to tunnel events on the data plane.
• DP Core GW unreachable
• DPs GRE keep alive timeout
• DP Core GW inactive
• DP DHCPRelay no response
• DP DHCPRelay failover
• DP sGRE new tunnel
• DP sGRE keepalive recovery
• DP DHCPRelay response recovery
• DP Core GW reachable
• DP Core GW active

DP Core GW unreachable
Table 471. DP Core GW unreachable event
Event

DP Core 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 data plane detects that a core network
gateway is unreachable.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

330

Events Types
Tunnel Events - Data Plane

DPs GRE keep alive timeout
Table 472. DPs GRE keep alive timeout event
Event

DPs GRE 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 Core GW inactive
Table 473. DP Core GW inactive event
Event

DP Core 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.5, 800-71290-001 Rev A

331

Events Types
Tunnel Events - Data Plane

DP DHCPRelay no response
Table 474. 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 475. 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
failure.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

332

Events Types
Tunnel Events - Data Plane

DP sGRE new tunnel
Table 476. DP sGRE new tunnel event
Event

DP sGRE new tunnel

Event Type

dpSgreNewTunnel

Event Code

620

Severity

Informational

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 an AP.

DP sGRE keepalive recovery
Table 477. 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

333

Events Types
Tunnel Events - Data Plane

DP DHCPRelay response recovery
Table 478. 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.

DP Core GW reachable
Table 479. DP Core GW reachable event
Event

DP Core 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.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

334

Events Types
Tunnel Events - Data Plane

DP Core GW active
Table 480. DP Core GW active event
Event

DP Core 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 the core gateway changes to active mode.

NOTE: Refer to Tunnel Alarms - Access Point.

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71290-001 Rev A

335

Index

A
accounting alarms 48
accounting server not reachable 48, 126
accSrvrNotReachable 48, 126
ad server unreachable 50
ad/LDAP connected successfully 192
ad/ldap connectivity failure 68
ad-hoc network device 140
ad-hoc-networkRogueAPDetecte 140
adServerUnreachable 50
alarm 42, 43
alarm and event management 42
AP 171
ap account message drop while no accounting start message 128
ap accounting response while invalid config 127
AP Brownout 163
ap cable modem interface down 64, 163
ap cable modem power-cycled by user

164
ap cable modem set to factory default by
user 168
ap cable modem soft-rebooted by user

168
ap capacity reached 166
ap capacity recovered 167
ap certificate expired 90, 249
ap certificate updated 249
ap change control plane 161
ap channel updated 159
ap channel updated dfs detected a radar

160
ap client load balancing limit reached 165
ap client load balancing limit recovered

165
ap communication alarms 54
ap communication events 130, 189
ap configuration generation failed 92, 255
AP configuration get failed 137
ap configuration update failed 55, 134
ap configuration updated 134
ap connected 161
ap connected to ls 142

ap country code updated 160
ap created a tunnel 325
ap deleted 63, 162
AP disconnected 158
ap disconnected 63
ap discovery succeeded 130
aP failed to connect to LS 61
ap failed to connect to ls 143
ap firmware update failed 57, 132
ap firmware updated 132
AP health high airtime utilization clear 180
AP health high airtime utilization flag 179
AP health high client count clear 172
AP health high client count flag 170
AP health high connection failure clear

172
AP health high connection failure flag 170
AP health high latency clear 171
AP health high latency flag 169
AP health low capacity clear 171
AP health low capacity flag 169
ap heartbeat lost 162
ap illegal to change country code 136
ap ip address updated 158
ap is disconnected from secure gateway

123, 329
ap managed 131
ap mesh events 146
AP NAT failure detected by SZ due to
three (3) consecutive NAT gateway APs
are down 179
AP NAT gateway IP failover detected for
particular VLAN pool 176
AP NAT gateway IP fall back detected for
particular VLAN pool 176
ap pre-provision model mismatched 56,

135
ap rebooted by system 62, 157
ap rebooted by user 157
ap received passive calibration request

144
ap received passive footfall request 145
AP received unrecognized request 145
ap rejected 54, 131
ap reset to factory default settings 159

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71374-001 Rev A

336

Index
ap secure gateway association failure 329
ap secure gateway association success

328
ap smart monitor turn off wlan 164
ap softgre gateway not reachable 122,

327
ap softgre gateway reachable 327
ap softgre tunnel fails over primary to secondary 326
ap softgre tunnel fails over secondary to
primary 326
ap started location service 143
ap state change alarms 62
ap state change events 156
ap stopped location service 144
ap swap model mismatched 55, 135
ap tagged as critical 162
ap tunnel disconnected 325
ap USB software package download failed

189
ap USB software package downloaded

189
ap WLAN oversubscribed 58
ap wlan oversubscribed 136
ap wlan state changed 166
apAcctMsgDropNoAcctStartMsg 128
apAcctRespWhileInvalidConfig 127
apBrownout 163
apBuildTunnelSuccess 325
apCapacityReached 166
apCapacityRecovered 167
apCertificateExpire 90, 249
apCertificateExpireClear 249
apCfgDhcpNatWlanVlanConfigMismatch

24, 26, 95, 258
apCfgGenFailed 92, 255
apCfgNonDhcpNatWlanVlanConfigMismatch 24, 26, 94, 257
apChangeControlBlade 161
apChannelChanged 159
apCLBlimitReached 165
apCLBlimitRecovered 165
apConfApplying 133
apConfUpdated 134
apConfUpdateFailed 55, 134
apConnected 161
apConnectionTerminatedDueToInsufficientLicense 286
apCountryCodeChanged 160
apDeleted 162

apDfsRadarEvent 160
apDHCPFailoverDetected 25, 173
apDHCPFallbackDetected 25, 173
apDHCPIPPoolMaxThresholdReached

25, 175
apDHCPServiceFailure 24, 25, 64, 175
apDiscoverySuccess 130
apFirmwareApplying 133
apFirmwareUpdated 132
apFirmwareUpdateFailed 57, 132
apGetConfigFailed 25, 137
apHealthAirUtilizationClear 25, 180
apHealthAirUtilizationFlag 25, 179
apHealthCapacityClear 25, 171
apHealthCapacityFlag 25, 169
apHealthClientCountClear 25, 172
apHealthClientCountFlag 25, 170
apHealthConnectionFailureClear 25, 172
apHealthConnectionFailureFlag 25, 170
apHealthLatencyClear 25, 171
apHealthLatencyFlag 25, 169
apHeartbeatLost 162
apIPChanged 158
apLBSAuthFailed 60, 142
apLBSConnectFailed 61, 143
apLBSConnectSuccess 142
apLBSNoResponses 59, 141
apLBSRcvdPassiveCalReq 144
apLBSRcvdPassiveFFReq 145
apLBSRcvdUnrecognizedRequest 145
apLBSStartLocationService 143
apLBSStopLocationService 144
apModelDiffWithPreProvConfig 56, 78,

135, 225
apModelDiffWithSwapOutAP 55, 135
apNATFailoverDetected 25, 176
apNATFailureDetectedbySZ 24, 25, 65,

179
apNATFallbackDetected 25, 176
apNATVlanCapacityAffected 25, 177
apNATVlanCapacityRestored 25
apP cable modem interface up 167
apRebootBySystem 62, 157
apSecondaryDHCPAPDown 25, 174
apSecondaryDHCPAPUp 25, 174
apSoftGREGatewayNotReachable 122,

327
apSoftGREGatewayReachable 327
apSoftGRETunnelFailoverPtoS 326
apSoftGRETunnelFailoverStoP 326

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71374-001 Rev A

337

Index
apStatusManaged 131
apStatusRejected 54, 131
apTaggedAsCritical 162
apTunnelDisconnected 325
apUsbSoftwarePackageDownloaded 189
apUsbSoftwarePackageDownloadFailed

189
apWlanOversubscribed 58, 136
apWLANStateChanged 166
authentication alarms 66
authentication events 190
authentication failed over to secondary

67, 191
authentication fallback to primary 67, 191
authentication server not reachable 66,

190
authFailedOverToSecondary 67, 191
authFallbackToPrimary 67, 191
authorization events 197
authSrvrNotReachable 66, 190
auto cleared 49, 50, 51, 52, 53, 54, 55,

57, 61, 63, 64, 74, 76, 77, 78, 79, 80,
81, 82, 83, 84, 86, 87, 88, 89, 90, 96,
97, 103, 104, 105, 111, 112, 117,
118, 120, 122, 124, 131, 132, 134,
141, 142, 143, 158, 163, 182, 183,
184, 185, 186, 187, 188, 196, 204,
223, 224, 225, 226, 227, 228, 229,
231, 233, 234, 235, 239, 243, 244,
247, 248, 249, 262, 265, 266, 267,
273, 274, 275, 278, 279, 280, 288,
293, 299, 307, 308, 316, 317, 321,
327, 329
aystem alarms 110

B
backupClusterFailed 79, 226
backupClusterSuccess 225
bind fails with AD/LDAP 69
bind success with LDAP 70, 193
Both primary and secondary DHCP server
APs are down 64, 175

C
c2d configuration failed 207
c2dCfgFailed 207
cableModemDown 163
cableModemUp 167

CALEA UE Matched 311
caleaMirroringStart 220
caleaMirroringStop 220
cassandraError 314
cfgGenSkippedDueToEolAp 257
cfgRcvFailed 254
cfgUpdFailed 253
cfgUpdSuccess 253
client authentication failed 209
client authorization failed 212
client authorization successfully 211
client blocked 214
client connection timed out 211
client disconnected 210
client events 208
client failed to join 210
client grace period 215
client is blocked because of barring UE
rule 219
client is unblocked because of barring UE
rule 219
client joined 209
client logged out 213
client roaming 213
client roaming disconnected 214
client session expired 212
clientAuthFailure 209
clientAuthorization 211
clientAuthorizationFailure 212
clientBlockByBarringUERule 25, 219
clientBlockByDeviceType 214
clientDisconnect 210
clientGracePeriod 215
clientInactivityTimeout 211
clientJoin 209
clientJoinFailure 210
clientRoaming 213
clientSessionExpiration 212
clientSessionLogout 213
clientUnblockByBarringUERule 25, 219
cluster add AP firmware completed 244
Cluster add AP firmware failed 87
cluster add AP firmware failed 244
cluster add AP firmware started 243
cluster application started 229
cluster application stopped 82, 229
cluster back in service 225
cluster backup completed 225
cluster backup failed 79, 226
cluster backup started 230

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71374-001 Rev A

338

Index
cluster created successfully 222
cluster events 221
cluster in maintenance state 78, 225
cluster leader changed 231
cluster name is changed 245
cluster node rebooted 84, 234
cluster node shut down 84
cluster node shutdown 235
cluster node upgrade completed 227
cluster out of service 86, 239
cluster remove node started 238
cluster restore completed 226
cluster restore failed 80, 227
Cluster upgrade failed 81
cluster upgrade failed 228
cluster upgrade started 230
cluster upload AP firmware completed

242
cluster upload AP firmware failed 86, 243
cluster upload AP firmware started 242
cluster upload completed 236
cluster upload failed 237
cluster upload KSP file completed 246
Cluster upload KSP file failed 87
cluster upload KSP file failed 246
cluster upload KSP file started 246
cluster upload started 236
cluster upload vSZ-D firmware failed 241
clusterAddAPFirmwareFailed 87, 244
clusterAddAPFirmwareStart 243
clusterAddAPFirmwareSuccess 244
clusterAppStart 229
clusterAppStop 82, 229
clusterBackToInService 225
clusterBackupStart 230
clusterCfgBackupFailed 88, 248
clusterCfgBackupStart 247
clusterCfgBackupSuccess 247
clusterCfgRestoreFailed 89, 248
clusterCfgRestoreStarted 250
clusterCfgRestoreSuccess 248
clusterCreatedSuccess 222
clusterInitContactApr 25, 251
clusterLeaderChanged 231
clusterNameChanged 245
clusterOutOfService 86, 239
clusterUpgradeStart 230
clusterUploadAPFirmwareFailed 86, 243
clusterUploadAPFirmwareStart 242
clusterUploadAPFirmwareSuccess 242

clusterUploadKspFileFailed 24, 88, 246
clusterUploadKspFileStart 246
clusterUploadKspFileSuccess 246
cmRebootByUser 164
cmResetByUser 168
cmResetFactoryByUser 168
coA authorize only access reject 201
coA nack sent to AAA 200
coA NAK received NAS 201
coA received from AAA 199
coA RWSG MWSG notification failure 202
coA sent NAS 200
coaAuthorizeOnlyAccessReject 201
coaNackSntAAA 200
coaNakRcvdNas 201
coaRcvdAAA 199
coaRWSGMWSGNotifFailure 202
coaSentNas 200
configuration 91
Configuration backup failed 88
configuration backup failed 248
configuration backup started 247
configuration backup succeeded 247
configuration events 253
configuration receive failed 254
configuration restore failed 88, 248
configuration restore started 250
configuration restore succeeded 248
configuration update failed 253
configuration update success 253
configuration-change events 42
connect to SCI 287
Connect to SCI failure 108
connect to SCI failure 288
connectedToDblade 203
connectedToSci 26, 287
connectToSciFailure 108, 288
control and data plane 74, 203
cpu threshold back to normal 318
cpu threshold exceeded 117, 316
cpuThresholdBackToNormal 318
cpuThresholdExceeded 117, 316
csvDiskMaxCapacityReached 24, 26
csvDiskThreshholdExceeded 24, 26
csvFtpTransferMaxRetryReached 24, 26

D
data plane 96, 259
data plane accepted a tunnel request 323

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71374-001 Rev A

339

Index
data plane configuration update failed 96,

262
data plane configuration updated 260
data plane connected 265
data plane core dead 268
data plane deleted 270
data plane disconnected 97, 265
data plane discovered 260
data plane discovery failed 260
data plane discovery succeeded 269
Data Plane fails to connects to the other
Data Plane 101
data plane heartbeat lost 263
data plane ip address updated 263
data plane license is not enough 98, 271
data plane managed 270
data plane of data center side disconnects
to CALEA server. 307
data plane of data center side fails to connect to the CALEA server 100
Data plane of data center side fails to connect to the CALEA server. 274
data plane packet pool is above high water
mark 268
data plane packet pool is under critical low
water mark 267
data plane packet pool is under low water
mark 267
data plane physical interface down 97,

sive 24, 26, 289
disabledSciDueToUpgrade 24, 26, 288
disconnect to SCI 287
disconnectedFromSc 287
disconnectedFromSci 26
disk threshold back to normal 318
disk usage exceed threshold 85, 239
disk usage threshold exceeded 118, 317
diskUsageExceed 85, 239
diskUsageThresholdExceeded 118, 317
dm nack received from NAS 199
dm nack sent to AAA 198
dm received from AAA 197
dm sent to NAS 198
dmNackRcvdNAS 199
dmNackSntAAA 198
dmRcvdAAA 197
dmSntNAS 198
dp connected 203
dp DHCPRelay failover 332
dp DHCPRelay no response 332
dp dhcprelay response recovery 334
dp sGRE keep alive timeout 331
dp sGRE new tunnel 333
dpAcceptTunnelRequest 323
dpCaleaUeInterimMatched 26, 311
dpCoreDead 268
dpDcToCaleaConnected 26
dpDcToCaleaConnectFail 24, 26, 100,

266

274

data plane physical interface up 266
data plane process restarted 98, 269
data plane rebooted 262
data plane rejected a tunnel request 324
data plane set up a tunnel 328
data plane statistics update failed 264
data plane status update failed 264
data plane terminated a tunnel 324
data plane updated to a new control plane

dpDcToCaleaDisconnected 26, 307
dpDeleted 270
dpDhcpIpPoolUsageRate100 24, 26
dpDhcpIpPoolUsageRate80 26
dpDhcpRelayFailOver 332
dpDhcpRelayNoResp 332
dpDhcpRelayRespRecovery 334
dpDisconnected 97
dpDiscoverySuccess 269
dpLicenseInsufficient 98, 99, 271
dpP sGRE keepalive recovery 333
dpP2PTunnelConnected 26
dpP2PTunnelConnectFail 24, 26
dpP2PTunnelDisconnected 26
dpPhyInterfaceDown 97
dpPktPoolCriticalLow 267
dpPktPoolLow 267
dpPktPoolRecover 268
dpProcessRestart 98, 269
dpRejectTunnelRequest 324

263
data plane upgrade failed 99, 273
data plane upgrade started 271
data plane upgrade succeeded 272
data plane upgrading 272
database error 314
datablade alarms 96
debug 43
delAllSess 290
delete all sessions 290
disabledSciAndFtpDueToMutuallyExclu-

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71374-001 Rev A

340

Index
dpSetUpTunnel 328
dpSgreGWAct 335
dpSgreGWInact 331
dpSgreGWReachable 334
dpSgreKeepAliveRecovery 333
dpSgreKeepAliveTimeout 331
dpSgreNewTunnel 333
dpStartMirroringClient 26, 309
dpStatusManaged 270
dpStopMirroringClient 26, 309
dpTearDownTunnel 324
dpUpdateStatisticFailed 264
dpUpgradeFailed 273
dpUpgradeStart 271
dpUpgradeSuccess 272
dpUpgrading 272

force DHCP disconnected 217
forceDHCPDisconnect 217
ftp transfer 301
ftp transfer error 301
ftpTransfer 301
ftpTransferError 301

G
generate AP config for plane load rebalance failed 300
generate AP config for plane load rebalance succeeded 300
generation of event and alarm 43
gtpManager (DP) disconnected 74, 204

H
E
email sent failed 302
email sent successfully 302
emapDlinkConnectWithMap 146
emapDlinkDisconnectWithMap 147
emapUlinkConnectWithMap 147
emapUlinkDisconnectWithMap 148
end -of-life AP model detected 93, 257
entire cluster upgraded successfully 228
espAuthServerReachable 184
espAuthServerResolvable 185
espAuthServerUnreachable 51, 185
espAuthServerUnResolvable 52, 186
espDNATServerReachable 186
espDNATServerResolvable 187
espDNATServerUnreachable 52, 187
espDNATServerUnresolvable 188
event 43
event attributes 43
event categories 42
event detail information 43
event severity 43
event source 43
event type 43

hIP failed over 115
hipFailover 115

I
incorrect flat file configuration 254
informational 43
Initiated APs contact APR 251
insufficient license capacity 286
ipmi alarms 103
ipmi events 278
ipmiFan 104, 279
ipmiFanStatus 105, 280
ipmiREFan 281
ipmiREFanStatus 282
ipmiREThempBB 280
ipmiREThempP 281
ipmiThempBB 103, 278
ipmiThempP 104, 279
ipsecTunnelAssociated 328
ipsecTunnelAssociateFailed 329
ipsecTunnelDisassociated 123, 329

K

F

keepalive failure 113, 305
keepAliveFailure 113, 305

failed to connect to LS 111
fails to establish TLS tunnel with AD/LDAP

L

73, 196
file upload 301
fileUpload 301

ldap server unreachable 50
ldapServerUnreachable 50
license data changed 285

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71374-001 Rev A

341

Index
license going to expire 106, 286
license import failed 285
license import succeeded 284
license sync failed 284
license sync succeeded 283
license threshold exceeded 119, 319
licenseChanged 285
licenseGoingToExpire 106, 286
licenseImportFail 285
licenseImportSuccess 284
licenseSyncFail 284
licenseSyncSuccess 283
licenseThresholdExceeded 119, 319
licensing alarms 106
licensing interface events 283
logging events 42
lostCnxnToDblade 74, 204
LS authentication failure 111
lS authentication failure 60
ls authentication failure 142, 292

M
mac-spoofing rogue ap 139
mac-spoofingRogueAPDetected 139
mailSendFailed 302
mailSendSuccess 302
map disconnected 148
map downlink connected 148
map downlink connected to emap 149
map downlink connected to map 154
map downlink disconnected from emap

149
map downlink disconnected from map

155
map uplink connected to emap 150
map uplink connected to map 152
map uplink connected to rap 151
map uplink disconnected from emap 151
mapDisconnected 148
mapDlinkConnected 148
mapDlinkConnectWitheMap 149
mapDlinkConnectWithMap 154
mapDlinkDisconnectWitheMap 149
mapDlinkDisconnectWithMap 155
mapUlinkConnectToeMap 150
mapUlinkConnectToMap 152
mapUlinkConnectToRap 151
mapUlinkDisconnectToeMap 151
memory threshold back to normal 318

memory threshold exceeded 118, 317
memoryThresholdBackToNormal 318
memoryThresholdExceeded 118, 317
Mesh state update to rap no channel 154
mesh state updated to map 152
mesh state updated to map no channel

153
mesh state updated to rap 153
meshStateUpdateToMap 152
meshStateUpdateToMapNoChannel 153
meshStateUpdateToRap 153
meshStateUpdateToRapNoChannel 154

N
new node failed to join 76, 223
new node joined successfully 222
newNodeJoinFailed 76, 223
newNodeJoinSuccess 222
No LS responses 141
no LS responses 59, 110
no ls responses 292
node back in service 238
node bond interface down 82, 231
node bond interface up 232
Node ip address changed 232
node out of service 77, 224
node physical interface down 83, 233
node physical interface up 234
node removal completed 223
node removal failed 77, 224
nodeBondInterfaceDown 82, 231
nodeBondInterfaceUp 232
nodeIPChanged 232
nodeOutOfService 77, 224
nodePhyInterfaceUp 234
nodeShutdown 84, 235
ntp time synchronized 235
ntpTimeSynched 235
number of devices exceeded it’s limit 121
number of users exceeded it’s limit 120

O
onboarding registration failed 216
onboarding registration succeeded 215
onboardingRegistrationFailure 216
onboardingRegistrationSuccess 215
overview 42

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71374-001 Rev A

342

Index

P
planeLoadingRebalancingFailed 300
planeLoadingRebalancingSucceeded

300
Primary DHCP AP is down detected by
secondary DHCP AP. Starting DHCP service on secondary 173
Primary DHCP AP is up detected by secondary DHCP AP. Stopping DHCP service on secondary. 173
Primary or secondary DHCP AP detects
90% of the configured total IPs 175
process restart 112, 304
processRestart 112, 304

R
racADLDAPBindFail 69
racADLDAPFail 68
racADLDAPSuccess 192
racADLDAPTLSFailed 24, 26, 73, 196
racADLDAPTLSSuccess 26
racADNPSFail 71, 194
racADNPSFailToAuthenticate 72, 194,

195
racLDAPFailToFindPassword 70, 193
radius fails to authenticate with AD NPS
server 72, 194
radius fails to connect to AD NPS server

71, 194
radius server reachable 181
radius server unreachable 49, 182
radiusServerUnreachable 49
rap downlink connected to map 150
rap downlink disconnected from map 155
rapDlinkDisconnectWithMap 155
rate limit for MOR surpassed 321
rate limit for TOR surpassed 120
rate limit threshold restored 320
rate limit threshold surpassed 319
rateLimitMORSurpassed 120
rateLimitThresholdRestored 320
rateLimitThresholdSurpassed 319
rateLimitTORSurpassed 321
recoverCassandraError 314
Reindex ElasticSearch finished 25
remediation failed 217
remediation succeeded 216
remediationFailure 217
remediationSuccess 216

removeNodeFailed 77, 224
removeNodeSuccess 223
resource unavailable 114, 305
resourceUnavailable 114, 305
restoreClusterFailed 80, 227
restoreClusterSuccess 226
resyncNTPTime 33
rmapDlinkConnectWithMap 150
Rogue AP 137
rogue AP disappeared 140

S
same network rogue ap 139
same-networkRogueAPDetected 139
scgLBSAuthFailed 111, 292
scgLBSConnectFailed 111, 293
scgLBSConnectSuccess 293
scgLBSFwdPassiveCalReq 297
scgLBSFwdPassiveFFReq 297
scgLBSNoResponse 110, 292
scgLBSRcvdMgmtRequest 295
scgLBSRcvdUnrecognizedRequest 298
scgLBSSendAPInfobyVenueReport 295
scgLBSSendClientInfo 296
scgLBSSendVenuesReport 296
scgLBSStartLocationService 294
SCI and FTP have been disabled 109,

289
SCI has been disabled 108, 288
Secondary DHCP AP is down detected by
primary DHCP AP 174
Secondary DHCP AP is up detected by
primary DHCP AP 174
service unavailable 113, 304
serviceUnavailable 113, 304
sessDeletedAtDblade 205
sessDeleteErrAtDblade 206
session delete at DP failed 206
session deleted at DP 205
session interface events 108, 287, 290
session update at DP failed 205
session updated at DP 204
sessUpdatedAtDblade 204
sessUpdateErrAtDblade 205
smartMonitorTurnOffWLAN 164
smartRoamDisconnect 214
SmartZone 296
SmartZone connected to LS 293
SmartZone failed to connect to LS 293

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71374-001 Rev A

343

Index
SmartZone forwarded calibration request
to AP 297
SmartZone forwarded footfall request to
AP 297
SmartZone received management request

295
SmartZone received passive request 294
SmartZone received unrecognized request 298
SmartZone sent AP info by venue report

295
SmartZone sent associated client report

296
SmartZone sent controller information report 294
sms sent failed 303
sms sent successfully 303
smsSendFailed 303
smsSendSuccess 303
ssid-spoofing rogue AP 137
ssid-spoofingRogueAPDetected 137
start CALEA mirroring client 220
Start CALEA mirroring client in data plane

309
stop CALEA mirroring client 220
Stop CALEA mirroring client in data plane

309
successfully established the TLS tunnel
with AD/LDAP 195
syslog server reachable 298
syslog server switched 299
syslog server unreachable 112, 299
syslogServerReachable 298
syslogServerSwitched 299
syslogServerUnreachable 112, 299
system interface events 291

129
unauthorizedCoaDmMessageDropped

129
Unsync NTP time 87, 245
unsyncNTPTime 87, 245
updating ap configuration 133
updating ap firmware 133
upgrade SSTable failed 250
upgradeClusterFailed 81, 228
upgradeClusterNodeSuccess 227
upgradeEntireClusterSuccess 228
upgradeSSTableFailed 250
uploadClusterVDPFirmwareFailed 241

W
wds device joined 218
wds device left 218
wdsDeviceJoin 218
wdsDeviceLeave 218
wechat ESP authentication server reachable 184
weChat ESP authentication server resolvable 185
WeChat ESP authentication server unreachable 185
weChat ESP authentication server unreachable 51
weChat ESP authentication server unresolvable 52, 186
weChat ESP DNAT server reachable 186
weChat ESP DNAT server resolvable 187
weChat ESP DNAT server unreachable

52, 187
weChat ESP DNAT server unresolvable

188

T

Z

threshold alarms 117
threshold events 316
threshold-crossing alerts 42
timestamp 43
tooManyUsers 120
tunnel alarms 122
tunnel events - datablade 330

zD AP Migrated 312
ZD AP Migrating 312
ZD AP Migration Failed 313
zD AP Rejected 313
zdAPMigrated 312
zdAPMigrating 312
zdAPMigrationFailed 313
zdAPRejected 313
zone configuration preparation failed 91,

U
unauthorized COA/DM message dropped

255
zoneAffinityLastDpDisconnected 24

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71374-001 Rev A

344

Index
zoneCfgPrepareFailed 91, 92, 255

SZ-100 and vSZ-E Alarm and Event Reference Guide for SmartZone 3.5, 800-71374-001 Rev A

345

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                      : Yes
Author                          : Ruckus Wireless™, Inc.
Create Date                     : 2017:04:07 12:37:37Z
Modify Date                     : 2017:04:07 12:43:58+05:30
Subject                         : SZ™ 100 and vSZ-E™ Alarm and Event Reference Guide for SmartZone 3.5
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
Metadata Date                   : 2017:04:07 12:43:58+05:30
Producer                        : Acrobat Distiller 11.0 (Windows)
Format                          : application/pdf
Title                           : SZ™ 100 and vSZ-E™ Alarm and Event Reference Guide for SmartZone 3.5
Creator                         : Ruckus Wireless™, Inc.
Description                     : SZ™ 100 and vSZ-E™ Alarm and Event Reference Guide for SmartZone 3.5
Document ID                     : uuid:903bf683-69fe-4a02-be99-831c0964664f
Instance ID                     : uuid:c8c07109-d150-41b1-a176-0ca0fbf79bb3
Page Mode                       : UseOutlines
Page Count                      : 346

EXIF Metadata provided by EXIF.tools