SpiderNet Administrator Guide R2.2 PDF

SpiderNet® Management System
Installation and Administration Guide,

Release 2.2
Part number: DOC-NMS-ADM-02, Rev. 3

Published: May, 2013
Revision History
Revision Date Summary of Changes
1 4/12/2013 Initial release for SpiderNet R2.2
2 5/14/2013 Clarified installation procedures and performance chart behavior
3 5/15/2013 Clarified user password behavior
© 2013 SpiderCloud Wireless, Inc. and SpiderCloud are registered trademarks of SpiderCloud Wireless,
Inc. All Rights Reserved.
SpiderCloud Wireless
408 East Plumeria Drive
San Jose, CA 95134, USA
http://www.spidercloud.com
Tel: +1 408 567-9165
Email: info@spidercloud.com
2
Table of Contents
Chapter 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1 About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3 The SpiderNet Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.3.1 The File Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.3.2 Network Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.3.2.1 The Work Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.3.2.2 Tree View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.3.2.3 Alarm Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.3.3 Personalizing the Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.4 Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.4.1 Find It . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.5 Parameter Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.5.1 Parameter Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.5.2 Regular Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.5.2.1 Regular Expression Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.6 The SpiderCloud Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Chapter 2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.1 Installation Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2 High-Level Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.3 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4 Installing the Server Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4.1 Installing the Server Software with the Wizard . . . . . . . . . . . . . . . . . . . . . . 23
2.4.2 Installing the Server Software through the Command Line . . . . . . . . . . . . 24
2.4.3 Installing New Data Model Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.4.4 Installing a New Default Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.5 Installing the Java Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.5.1 Installing the Java Software on a Microsoft Windows Client . . . . . . . . . . . 27
2.5.2 Installing the Java Software on a Linux Client . . . . . . . . . . . . . . . . . . . . . . 28
2.6 Configuring MySQL Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.7 Configuring Linux System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.8 Redundant Server Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.8.1 Installation and Initial Configuration Requirements . . . . . . . . . . . . . . . . . . 31
2.8.2 Network Topology Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.8.3 Failover Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.9 Preparing the Services Node for SpiderNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.9.1 Editing the SpiderNet Configuration through the LCI . . . . . . . . . . . . . . . . . 33
2.9.2 Editing SpiderNet Configuration Parameters on a Services Node . . . . . . . 34
2.9.3 Editing the SpiderNet Configuration through the CLI . . . . . . . . . . . . . . . . . 34
SpiderCloud Wireless, Inc. 3

Contents
Chapter 3 Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

3.1 Launching the SpiderNet Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.2 SpiderNet Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.2.1 Copying the SpiderNet Registration Key. . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.2.2 Installing a SpiderNet License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.3 Exiting SpiderNet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Chapter 4 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.1 Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.1.1 Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.1.1.1 Creating a User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.1.1.2 Editing Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.1.1.3 Logging Out Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.1.1.4 Deleting Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.1.2 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.1.2.1 Creating a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.1.2.2 Modifying a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.1.2.3 Deleting a Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.1.3 Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.1.3.1 Creating a View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.1.3.1 Deleting a View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.1.4 Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.1.4.1 Setting Password Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.1.5 Connected Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.1.5.1 Logging Users Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.2 Audit Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.2.1 Refreshing the Audit Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.2.2 Filtering the Audit Trail Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.2.3 Saving the Audit Trail to File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.2.4 Printing the Audit Trail Screen Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.3 Northbound Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.3.1 Alarm Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.3.1.1 Creating an SNMP Managers Group . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.3.1.2 Editing an SNMP Managers Group. . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.3.1.3 Deleting an SNMP Managers Group . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.3.2 SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.3.2.1 Configuring the Northbound Interface SNMP Agent . . . . . . . . . . . . . . 51
4.3.2.2 Modifying the Northbound Interface SNMP Agent Settings . . . . . . . . 52
4.4 Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.4.1 Email Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.4.1.1 Creating an Email Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.4.1.2 Editing an Email Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.4.1.3 Deleting an Email Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.4.2 SMTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.4.2.1 Configuring SMTP Email Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4 SpiderCloud Wireless, Inc.

SpiderNet Management System Installation and Administration Guide
4.4.2.2 Editing SMTP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

4.5 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.5.1 Events Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.5.1.1 Configuring Fault Management Settings . . . . . . . . . . . . . . . . . . . . . . 57
4.5.1.2 Editing Fault Management Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.5.2 Trap Receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.5.2.1 Configuring the SNMP Trap Reception . . . . . . . . . . . . . . . . . . . . . . . 58
4.5.2.2 Modifying SNMP Trap Reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.6 Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.6.1 File Transfer Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.6.1.1 Configuring File Transfer Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
4.6.1.2 Editing File Transfer Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.6.1.3 Enabling the SCP on the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.6.2 Syslog Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.6.2.1 Editing Syslog Server Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.6.2.2 Refreshing the Syslog Server Screen . . . . . . . . . . . . . . . . . . . . . . . . 63
4.6.3 Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.6.3.1 SpiderNet Server Redundancy Preconditions . . . . . . . . . . . . . . . . . . 64
4.6.3.2 Configuring SpiderNet Server Redundancy . . . . . . . . . . . . . . . . . . . . 64
4.6.3.3 Disabling SpiderNet the Redundancy Mode . . . . . . . . . . . . . . . . . . . 65
4.7 Database Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
4.7.1 Configuring Dual Database Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.7.2 Configuring Single Database Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.8 Geographical Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.8.1 Uploading a Map Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.8.2 Removing a Map Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.9 Performance Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.9.1 Modifying KPI Polling Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.9.1.1 Resetting the Performance Collection Interval Screen. . . . . . . . . . . . 68
4.9.2 Configuring PM Collection on a Services Node . . . . . . . . . . . . . . . . . . . . . 68
Chapter 5 The Tree View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5.1 Configuring the Tree View Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
5.2 Network Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
5.3 Subnets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
5.3.1 Creating a Subnet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5.3.2 Editing a Subnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.3.3 Pre-Provisioning a Services Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.3.4 Applying a Map to a Subnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.4 Subnet Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
5.4.1 Creating a Subnet Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
5.4.2 Editing a Subnet Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
5.4.3 Deleting a Subnet Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
5.5 Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
5.5.1 Configuring the Remote Connection Applications . . . . . . . . . . . . . . . . . . . 76

Contents
5.5.2 Opening a Remote Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

5.5.3 Deleting a Services Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
5.6 Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
5.6.1 Adding a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
5.6.2 Adding Services Nodes to a Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
5.6.3 Moving a Services Node to a Different Group. . . . . . . . . . . . . . . . . . . . . . . 78
5.6.4 Removing a Services Node from a Group . . . . . . . . . . . . . . . . . . . . . . . . . 78
5.6.5 Deleting a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
5.7 Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
5.7.1 Adding a Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
5.7.2 Adding a Services Node to a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
5.7.3 Moving a Services Node to a Different Site . . . . . . . . . . . . . . . . . . . . . . . . 79
5.7.4 Removing a Services Node from a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
5.7.5 Editing a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
5.7.6 Deleting a Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Chapter 6 The Work Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6.1 Geographical Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6.2 Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
6.2.1 Selecting the Display Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.2.2 Adjusting Column Widths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.2.3 Sorting Inventory Screen Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.2.4 Saving the Inventory Data to File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
6.2.5 Printing Inventory Screen Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
6.3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
6.3.1 Modifying Configuration Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
6.3.2 Refreshing Configuration Screen Displays . . . . . . . . . . . . . . . . . . . . . . . . . 86
6.3.3 The Equipment Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
6.3.3.1 Creating a Radio Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
6.3.3.2 Deleting a Radio Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
6.3.3.3 Creating a Radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
6.3.3.4 Deleting a Radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
6.3.4 The IP Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
6.3.4.1 Configuring an Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
6.3.4.2 Deleting an Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
6.3.4.3 Creating an IP Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
6.3.4.4 Deleting an IP Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
6.3.4.5 Creating a Forwarding Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
6.3.4.6 Deleting a Forwarding Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
6.3.4.7 Creating a DHCP Server Subnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
6.3.4.8 Deleting a DHCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
6.3.4.9 Creating a QoS Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
6.3.4.10 Deleting a QoS Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
6.3.5 The UMTS Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
6.3.6 The System Management Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

6.3.7 The Advanced Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

6.4 Configuration Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
6.4.1 Creating a Configuration Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
6.4.2 Editing a Configuration Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
6.4.3 Importing a Configuration Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
6.4.4 Exporting a Configuration Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
6.4.5 Deleting a Configuration Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
6.5 Scheduled Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
6.5.1 Adding a Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
6.5.1.1 Scheduling a File Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
6.5.1.2 Scheduling a Configuration Template Application . . . . . . . . . . . . . . . 109
6.5.1.3 Scheduling a Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
6.5.1.4 Scheduling a Software Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
6.5.1.5 Scheduling a Software Revert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
6.5.1.6 Scheduling a Services Node Database Backup. . . . . . . . . . . . . . . . . 112
6.5.1.7 Scheduling a Services Node Database Restoration . . . . . . . . . . . . . 112
6.5.1.8 Modifying the Scheduled SpiderNet Backup . . . . . . . . . . . . . . . . . . . 113
6.5.1.9 Modifying the Scheduled SpiderNet Database Integrity Validation . . 114
6.5.1.10 Scheduling a UMTS REM Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
6.5.1.11 Scheduling a UMTS REM Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
6.5.1.12 Scheduling a UMTS Self Configuration . . . . . . . . . . . . . . . . . . . . . . 115
6.5.1.13 Scheduling a Services Node Log Bundle. . . . . . . . . . . . . . . . . . . . . 115
6.5.1.14 Scheduling a Services Node Log Mark . . . . . . . . . . . . . . . . . . . . . . 116
6.5.1.15 Scheduling a Services Node Log Rotate . . . . . . . . . . . . . . . . . . . . . 116
6.5.1.16 Scheduling a Reset Services Node Statistics . . . . . . . . . . . . . . . . . 117
6.5.1.17 Scheduling Disabling a UMTS Cell . . . . . . . . . . . . . . . . . . . . . . . . . 118
6.5.2 Cloning a Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
6.5.3 Editing a Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
6.5.4 Removing a Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
6.5.5 Removing All Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
6.5.6 Immediately Running Scheduled Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
6.5.7 Retrying Failed Scheduled Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
6.5.8 Aborting a Running Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Chapter 7 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
7.1 Fault Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
7.1.1 Supported Traps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
7.1.2 Syslog Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
7.1.3 SpiderNet Internal Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
7.1.4 Event Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
7.1.5 Alarm Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
7.2 Alarms and Event Screen Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
7.3 Managing Alarm and Event Screen Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
7.3.1 Navigating Alarm or Event Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
7.3.2 Selecting the Display Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Contents
7.3.3 Adjusting Column Widths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

7.3.4 Sorting Alarm and Event Screen Displays . . . . . . . . . . . . . . . . . . . . . . . . . 127
7.3.5 Filtering Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
7.3.6 Grouping Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
7.4 Viewing Alarm and Event Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
7.5 Manually Clearing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
7.6 Acknowledging Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
7.7 Annotate an Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
7.8 Saving Events to a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
7.9 Printing the Alarm and Event Screen Display . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
7.10 SpiderNet Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
7.10.1 spiderNetHeartBeat. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
7.10.2 spiderNetDeviceAdded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
7.10.3 spiderNetDeviceDiscovered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
7.10.4 spiderNetDeviceDisconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
7.10.5 spiderNetDeviceDeleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
7.10.6 spiderNetServerStarted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
7.10.7 spiderNetServerShutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Chapter 8 Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
8.1 Performance Monitoring Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
8.1.1 Configuring Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
8.1.1.1 Enabling and Disabling System-Wide Performance Data Collection . 135
8.1.1.2 Enabling and Disabling Cell Performance Data Collection . . . . . . . . . 135
8.1.1.3 Clearing PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
8.1.2 Data Compaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
8.2 The Performance Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
8.2.1 Creating a Performance View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
8.2.2 Setting the Performance View Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
8.2.3 Refreshing the Performance View Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
8.2.4 Using the Performance View Chart Scrollbar . . . . . . . . . . . . . . . . . . . . . . . 140
8.2.5 Sorting the Performance View Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
8.2.6 Exporting Performance View Data to a CSV File . . . . . . . . . . . . . . . . . . . . 141
8.2.7 Exporting Raw Performance View Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
8.2.8 Saving the Performance View Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
8.2.9 Printing Performance View Graph. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
8.2.10 Performance View Graph Markers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
8.2.10.1 Adding Performance View Graph Markers . . . . . . . . . . . . . . . . . . . . 142
8.2.10.2 Editing Performance View Graph Markers . . . . . . . . . . . . . . . . . . . . 142
8.2.10.3 Deleting Performance View Graph Markers . . . . . . . . . . . . . . . . . . . 142
8.2.11 Deleting a Performance View Graph. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Chapter 9 SpiderNet Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
9.1 Restoring the SpiderNet Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
9.2 Managing SCOS Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

9.2.1 Uploading a New Data Model File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

9.3 Upgrading the SpiderNet Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
9.4 Upgrading Redundant Server Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . 147
9.5 Downgrading Redundant Server Configurations . . . . . . . . . . . . . . . . . . . . . . . . 148
Chapter 10 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
10.1 MySQL Database Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
10.2 SpiderNet Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
10.3 Linux Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
10.4 Redundant Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Chapter 11 SpiderNet Performance Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
11.1 System KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
11.2 Cell KPI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
11.3 Equipment Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Contents

1 Overview
This chapter contains the following sections:

• Section 1.1, About this Manual on page 11
• Section 1.2, Product Overview on page 11
• Section 1.3, The SpiderNet Interface on page 12
• Section 1.4, Document Conventions on page 16
• Section 1.5, Parameter Tables on page 17
• Section 1.6, The SpiderCloud Documentation Set on page 20
1.1 About this Manual

This document is a guide for installing the SpiderNetsm network manager on a server and using it to
manage one or more SpiderCloud® services node controller. It contains specific procedures and examples
needed to configure and administer the system. This guide assumes that the managed services nodes and
their radio nodes have been installed, turned up, tested, and are ready to carry user traffic.
Use this guide in conjunction with the SpiderCloud OS (SCOS) Administrator Guide that contains system
feature overviews, detailed provisioning procedures, and sample configurations and the SCOS NB Data
Model Reference Guide that contains details about objects, their parameters, and valid options in the
SpiderCloud system. Refer to the SpiderCloud Services Node Hardware Installation Guide and the
SpiderCloud Radio Node Hardware Installation Guide for hardware specifications and installation
instructions.
The primary audience for this guide includes system administrators, network operators, and other
personnel responsible for configuring, operating, and administering SpiderCloud services nodes. In writing
this document, SpiderCloud Wireless assumes that you have an understanding of the Internet, networking
principles, networking configuration, network management, and experience in cellular networks.
1.2 Product Overview

SpiderNet is a centralized network management system that enables mobile operators to rapidly provision,
deploy, and administer SpiderCloud Enterprise Radio Access Networks (E-RAN) systems. SpiderNet is
installed on a dedicated server in the mobile operator’s core network and enables up to ten network
administrators to remotely configure, monitor, and upgrade E-RAN systems through an easy to use
Graphical User Interface (GUI).
SpiderNet uses the TR-069 standard protocol defined by the Broadband Forum to remotely manage
SpiderCloud services nodes. Each services node is responsible for managing all the SpiderCloud radio
nodes connected to it in an E-RAN.

Overview
Services nodes connect with the SpiderNet server through secure IPsec connections. The server
authenticates each services node through a configurable username/password combination. Figure 1
shows a logical view of the SpiderNet architecture:
MSC SGSN
DB
HNB-GW
SpiderNet
Client
Sessions
Security
Gateway
IP Backhaul
Services Nodes
Enterprise 1 Enterprise 2 Enterprise 3

Radio Nodes Radio Nodes Radio Nodes
Figure 1 SpiderNet Architecture
Network administrators access the management server through the GUI available through a Java-enabled
web browser or as standalone desktop application. Contents of the SpiderNet interface are context-
sensitive. Different elements display and functions become available depending upon the element selected
and user permissions.
Unless otherwise specified, the elements and functions discussed in this manual apply to those with top-
level permissions. Actions may be restricted and elements may not display for users without sufficient
permissions.
The SpiderNet application requires a license to manage networks of E-RANs. Licenses are based on the
number of services nodes managed. Refer to Section 3.2, SpiderNet Licensing on page 38 for more
information about obtaining and managing licenses.
1.3 The SpiderNet Interface

The SpiderNet GUI contains the file menu, a search function, and three types of work areas represented by
tabs on the top of the screen:
• File Menu: Tasks common to all applications.
• Search: A search function for locating network equipment by specifying identifiers such as
serial number, IP address, and hostname.
• Network Control: The primary workspace of the interface.
• Faults: Displays current alarms and the event log. Refer to Chapter 7, “Fault Management” on
page 121 for more information.

• Administration: Contains numerous screens and tabs related to administering the SpiderNet
system, including access control, audit trails, northbound interface event notification, email
settings, fault management, server and database settings, geographical maps and
performance configuration. Refer to Chapter 4, “Administration” on page 41 for more
information.
• Performance: Displays snapshots of collected performance monitoring data for a selected
services node. A page can display one or more views. A view is the computation of a single KPI
for a selected time period. It can toggle between a chart and a table. The chart can be saved to
file and the data exported for external computation. Refer to Chapter 8, “Performance
Monitoring.” on page 135 for more information.
1.3.1 The File Menu

The file menu contains the following menu and submenu items:
• File
   Exit: closes the SpiderNet session
• View
   Topology: opens or focuses upon the tree view
   Geographical Map: opens or focuses upon the Geographical Map panel in the work
area
   Inventory: opens or focuses upon the Inventory panel in the work area
   Configuration: focuses upon the Configuration panel in the work area when open
  Scheduled Tasks: opens or focuses upon the Scheduled Tasks panel in the work area.
   Events: opens or focuses upon the Events panel in the work area
   Alarms: opens or focuses upon the Alarms panel in the work area
   Configuration Templates: opens or focuses upon the Configuration Templates panel
in the work area
• Tools
   ICMP Ping: opens the ICMP Ping screen
   Traceroute: opens the Traceroute screen
   SNMP Ping: opens the SNMP Ping screen
   Options: opens the Options screen that contains two tabs. The Topology tab
configures device label options. The Network tab contains text boxes and browse
buttons to define paths to the applications to use to open an SSH connection to a
services node or other device. Enter the path or browse to the location of the executable
file of the terminal application on your computer to select the program.
  Upload XSD: opens the Upload dialog box for navigating to and uploading a data model
file for support for a different version of the SpiderCloud operating system
   Upload File: opens the Upload dialog box for navigating to and uploading a file
• Window
   Load Default Layout: presents the factory or defined default screen layout
   Load Custom Layout: presents the defined custom screen layout
   Save as Default Layout: saves current view as the default screen layout
   Save as Custom Layout: saves the current view as the custom layout
   Reset Layout: resets the screen layout to the factory default
• Help
  License: opens the License Details screen that displays license information (maximum
number of supported clients, maximum number of supported devices, and license
expiration date) and tools for managing your SpiderNet license. Refer to 3.2 SpiderNet
Licensing on page 38 for more information about SpiderNet licensing.

Overview
   About: opens the About screen that contains information about the SpiderNet software
version, the date the software was created, current system uptime, maximum available
memory, allocated heap memory, heap memory in use, and additional available heap
memory. It also contains a link to the SpiderCloud Wireless web site.
1.3.2 Network Control

Figure 2 shows the Network Control view of the SpiderNet interface. It consists of the following main
screen elements:
1. work area
2. tree view
3. alarm summary
4. SpiderNet software version
4
1
2
3
Figure 2 The Network Control Interface
1.3.2.1 The Work Area

The work area screen is context sensitive. The display and actions that can be performed in the workspace
will vary depending upon the task selected. The view is user configurable, up to two views per defined user
can be configured and saved for later use. A button bar runs across the top of the work area. Clicking a

button activates the corresponding panel in the work area. The work area button bar contains the following
buttons:
Table 1: Work Area Button Bar Items
Button Tab Name
Network Topology (Tree View)
Geographical Map
Logical Map
Inventory
Configuration
Scheduled Tasks
Events
Alarms
Configuration Templates
Refer to Chapter 6, “The Work Area” on page 81 for detailed information about this screen area.
1.3.2.2 Tree View

The tree view provides the ability to navigate through all managed services nodes in the network and
launch configuration screens, inventory views, or scheduled tasks that are displayed in the workspace
area. The tree view features includes:
• Displaying the network structure hierarchy as a tree. Different types of network elements can
have their own icons. The tree structure can be modified by dragging and dropping network
elements.
• Monitoring the network health by using separate colors and icons to indicate the status of the
different network elements.
• Controlling network elements from a right-click menu. The right-click menu can be modified by
adding, removing, and renaming of menu items.
The tree view contains two subnets by default:
• ServicesNodes: Contains all properly discovered services nodes. All services nodes in this
subnet have properly registered their Hardware ID (serial number), Customer ID, Location ID,
and Cluster ID.
• Unknown ServicesNodes: Preprovisioned services nodes or those that did not properly
register their Hardware ID, Customer ID, Location ID, and Cluster ID.
The tree view also contains two folders:
• Groups: logical collections of services nodes with some common attribute
• Sites: logical collections of services nodes in the same location
A search bar runs across the top of the tree view. A drop-down list allows you to search for services nodes
in the network serial number, IP address, or hostname. Type your search criterion in the text box and press

Overview
Enter from your keyboard. Services nodes that match the text are highlighted in the tree view, display in
the Inventory tab of the work area, and any related alarms display in the alarm summary. Refer to Chapter
5, “The Tree View” on page 69 for detailed information about this screen area.
1.3.2.3 Alarm Summary

The alarm summary indicates fault conditions in individual services nodes and reachability issues between
the server and managed services nodes. It has separate tabs that display the most current alarms and
events. You can sort the display, configure the displayed properties, acknowledge alarms and events, and
filter the output by a number of criteria. Refer to Chapter 7, “Fault Management” on page 121 for detailed
information about this screen area.
1.3.3 Personalizing the Interface

The SpiderNet interface is configurable. Interface panels can be resized relative to each other by inserting
the cursor between the sections and dragging the divisor to the new location. Additionally, each panel
contains a button bar in the upper-right corner. Table 2 shows the buttons on the button bar and their
behaviors:
Table 2: Button Bar Items
Button Button Behavior
Toggles the panel between being stationary and free-floating
Toggles the panel between being visible and auto-hide mode
Closes the pane
1.4 Document Conventions

This document uses the following typographical conventions:
Bold text signifies any of the following:
• names of SpiderNet tabs, panels, and screens
• names of screen fields such as text boxes, drop-down lists, and radio buttons
• names of screen elements such as buttons and icons
• names of other visible screen components
• other important concepts
Italicized text indicates a system element that can be configured in the procedure. In parameter tables it
can indicate permitted characters in the Valid Options column.
Monospaced bold text indicates information the user inputs into the system. Plain monospaced
text indicates system output.
All post-installation procedures assume that the client interface is running.

1.4.1 Find It
This document uses the Find It: visual shortcut to indicate how to navigate to a screen or screen element
of the user interface. Find It: elements may include menus, sub-menus, selections from a list, tabs, or
button selections.
Find It: Network Control >> Configuration >> System Management
Interpret Find It: instructions as follows:

• Separate steps or items in a navigation sequence are separated by the >> characters.
• A separate step in a Find It: instruction requires one of the following actions:
   selecting one of the main menus (for example, tabs)
   selecting a menu item
   selecting a sub-menu
   selecting a panel, screen, or tab
   clicking a button or icon
The example above is interpreted as follows:
Step 1 Select the Network Control tab.
Step 2 Select the Configuration panel or button.
Step 3 Select the System Management tab.
1.5 Parameter Tables

Each chapter contains one or more parameter tables that show, at a minimum, the name of the element, its
description, and valid options. Relevant tables display the default value. Table 3 shows a portion of a
sample parameter table:
Table 3: System Information
Element Description Valid Options Default
Name Services node name. String. May contain spaces. Hostname
Hostname Services node hostname. Regex(24). Valid characters: None
^$|^([0-9a-zA-Z])[-0-9a-zA-
Z]*([0-9a-zA-Z])$
Description System description. String. May contain spaces. If None
not explicitly specified here,
Description value defaults to
the form of the following
example: SpiderCloud
Wireless, Inc. ServicesNode,
SCOS: 3.1.0.141.5117, Build
date: 2013-03-18T00:52:30Z
Copyright (c) 2013
Contact System point of contact. String. May contain spaces. None

Overview
Table 3: System Information (continued)

Location System location. String. May contain spaces. None
NameServer IP address of each DNS name server One to three valid IP None
referenced in order during hostname addresses
resolution.
1.5.1 Parameter Values

Objects of the SpiderCloud data model configured with the SpiderNet interface may have the following
value types:
• Array: a collection of similar objects
• Enum: is a string with fixed valid values
• String: a string of printable ANSI characters
• Regex: is a string with pattern restrictions on valid values. Refer to Section 1.5.2, Regular
Expressions on page 18.
• Unsigned integer: a non-negative whole number
• (min:max): min <= character length of string <= max
• [min:max]: min <= integer value <= max
• {min:max}: min <= number of items in array <= max
• <min:max>: min <= character length of array as comma separated string <= max
• (units): units of measurement of an integral type
1.5.2 Regular Expressions

A regular expression is a text string describing a text pattern. SpiderNet supports the following regular
expressions:
Table 4: Supported Regular Expressions
Expression Description
. (period) Matches any character
^ Matches the beginning of a string

$ Matches the end of a string
[abc...] Character class, which matches any of the characters “abc...” Character ranges are
specified by a pair of characters separated by a -.
[^abc...] Negated character class, which matches any character except “abc...”
{x} Pattern repeated exactly “x” number of times
r1 | r2 Alternation. It matches either r1 or r2
r1r2 Concatenation. It matches r1 and then r2
r+ Matches one or more r’s
r* Matches zero or more r’s

Table 4: Supported Regular Expressions (continued)

Expression Description
r? Matches zero or one r’s
(r) Grouping. It matches r
1.5.2.1 Regular Expression Examples

A MAC address has the format of six pairs of hexadecimal characters separated by colons, for example
00:24:48:00:31:00. The regular expression defining the MAC address reads:
([0-9a-fA-F][0-9a-fA-F]:){5}([0-9a-fA-F][0-9a-fA-F]), where:
• ([0-9a-fA-F][0-9a-fA-F]:) refers to the first hexadecimal pair (the integers 0 through 9, lower
case letters a through f, and upper case letters A through F)
• {5} explains that this pattern repeats exactly five times
• and ([0-9a-fA-F][0-9a-fA-F]) refers to the last hexadecimal pair

Overview
1.6 The SpiderCloud Documentation Set

The SpiderCloud documentation set includes:
• The SpiderCloud System Description provides an overview of how the SpiderCloud system fits
within an operator’s network and in an enterprise, describes key features of the system, and
provides specifications for the services and radio nodes.
• The SpiderCloud Feature Description provides high-level descriptions of the E-RAN system
features, their impact on the product components (services nodes and radio nodes),
manageability considerations, and feature benefits.
• The SpiderCloud OS (SCOS) Administrator Guide provides procedures for configuring the
software environment and internetworking between the services node and radio node devices.
• The SpiderCloud Services Node Hardware Installation Guide provides hardware specifications
and installation instructions.
• The SpiderCloud Radio Node Hardware Installation Guide provides hardware specifications and
installation instructions.
• The E-RAN Deployment Planning Guide provides information about planning and dimensioning
E-RAN systems.
• The SpiderCloud OS (SCOS) CLI User Guide provides an introduction to the key features and
functionalities of the SpiderCloud Command Line Interface (CLI).
• The SCOS NB Data Model Reference Guide provides details about the objects and parameters
that comprise the system configuration and operational state.
• The SpiderCloud System Commissioning Guide provides information about turning up a
SpiderCloud E-RAN with the Local Configuration Interface (LCI) graphical user interface.
• The Performance Measurements for SpiderCloud Small-Cell E-RAN provides a reference guide
to Key Performance Indicators (KPI) that monitor the health and state of the E-RAN system.
• The E-RAN Troubleshooting Guide provides information about diagnosing and correcting
problems with installing, provisioning, administering, and maintaining SpiderCloud equipment
and services.
• The SpiderNet Management System Installation and Administration Guide provides information
about installing the SpiderNet network management server and client and using it to remotely
manage E-RAN deployments.
• The SpiderCloud Time Zone Reference Guide provides the information required to configure
the time zone for SpiderCloud services nodes.

2 Installation

• Section 2.1, Installation Prerequisites on page 21
• Section 2.2, High-Level Installation Overview on page 22
• Section 2.3, Before You Begin on page 23
• Section 2.4, Installing the Server Software on page 23
• Section 2.5, Installing the Java Client Software on page 27
• Section 2.6, Configuring MySQL Database Parameters on page 28
• Section 2.7, Configuring Linux System Parameters on page 29
• Section 2.8, Redundant Server Overview on page 30
• Section 2.9, Preparing the Services Node for SpiderNet on page 33
2.1 Installation Prerequisites

SpiderNet must run on a dedicated server with the following recommended minimum specifications. Note
that the MySQL database that maintains the system configuration can run on the same physical server.
Table 5: Server Recommended Minimum Specifications
Element Recommended Minimum Specification
Hardware
CPU Intel Xeon 6-core 2.4 GHz or equivalent, 64-bit
Network interface card 2 Gigabit Ethernet
Memory 16 GB RAM (expandable configuration recommended)
Disk 1 TB free disk space
Display 1024 x 768 pixels, 32-bit color
Miscellaneous Keyboard, mouse
Software
Operating system Linux CentOS 5.8 Server or RedHat Enterprise (RHE) 6.3
Java Runtime Environment 1.6 Update 24 and 1.7
MySQL Database Latest fully supported version

Installation
Up to ten concurrent users can access the SpiderNet application through a web browser or a stand-alone
Java application. The operator’s computer has the following recommended requirements:
Table 6: Client Recommended Minimum Requirements
Element Recommended Minimum Specification
Hardware
CPU Pentium dual core x86 1.3 GHz or equivalent
Memory 2 GB RAM
Disk 2 GB free disk space
Display 1024 x 768 pixels, 32-bit color
Miscellaneous Keyboard, mouse, 100Mb network interface card
Software
Operating system Microsoft Windows XP/2000/Vista/7, RedHat Linux Desktop 4, CentOS 5 Desktop,
Ubuntu 9
Java Runtime Environment 1.6 Update 24 and above; 1.7
Browser Internet Explorer 7, Firefox 3.6, Chrome 3, or Safari 5
The following table shows ports that must be opened when there is a firewall between the services nodes
and the SpiderNet server:
Table 7: Required Open Firewall Ports
From To Source Destination Protocol Usage
Services Node SpiderNet Server Any 8080 TCP TR-069
SpiderNet Server Services Node Any 7547 TCP TR-069
Services Node SpiderNet Server Any 514 UDP Syslog
Services Node SpiderNet Server 162 162 UDP SNMP
Services Node SpiderNet Server Any 21 TCP FTP
Services Node SpiderNet Server Any 221 TCP SCP
SpiderNet Server Services Node Any 161 UDP SNMP keepalive
SpiderNet Server DNS Server Any 53 UDP DNS
SpiderNet Server NTP Server Any 123 UDP NTP
SpiderNet Client SpiderNet Server Any 443 TCP HTTPS
PC Client Services Node Any 22 TCP SSH
2.2 High-Level Installation Overview

The SpiderNet server and client software and affiliated MySQL database software installation involves the
following high-level steps:
• Install and configure the MySQL database software.
• Install and configure the SpiderNet server software.
• (Optional) Install new data model files.

• (Optional) Install a new default data model file.

• (Optional) Install the SpiderNet client software.
2.3 Before You Begin

Before you begin software installation, ensure the following:
• The dedicated server hardware is installed, configured, running, and assigned an IP address.
• The latest supported version of MySQL database is installed and configured on the same
server as the SpiderNet server software or on a separate server. Refer to the MySQL
documentation for information about downloading, installing, and configuring the database. Be
sure to document the database configuration and administrator user name and password.
• Sufficient valid SpiderNet licenses are available for the number of services nodes to be
managed.
SpiderCloud Wireless strongly recommends using same Network Time Protocol (NTP)
server as its services nodes as the timing source of the Linux server to ensure proper
Note synchronization.
2.4 Installing the Server Software

The SpiderNet server software installs on the Linux CentOS or RedHat Enterprise Server operating system
using either a graphical wizard or through a command line. The MySQL database must be installed
separately before the SpiderNet installation.
2.4.1 Installing the Server Software with the Wizard

There are separate server installation files for AMD (SpiderNet_unix_a_b_c_d_amd64.sh) and x86
(SpiderNet_unix_a_b_c_d_x86.sh) server chipsets, where a, b, c, and d are the version numbers.
To install the server software with the wizard
Step 1 As a root user, modify the installation file permission to add execute permissions:
chmod +x <installer_file_name>
Step 2 Run the installation file. For example:
./SpiderNet_unix_2_1_0_34_x86.sh

Installation
The wizard opens:
Step 3 Follow the wizard through accepting the license agreement, selecting the installation
directory and components to install. The installer will then copy the files and install them on
your server. When this process completes, click Next.
Step 4 Complete the form by entering database hostname or IP address and port, and your
username and password.
Step 5 Click Next on this screen and Finish on the next screen to complete the installation.
Step 6 Reboot the server. The SpiderNet server application launches automatically.
2.4.2 Installing the Server Software through the Command Line

The command line server installation essentially mirrors the wizard version, but uses text input rather than
mouse clicks. Bolded text in this procedure refers to user input. Some screen text is truncated for brevity
and clarity.
To install the server software with the command line
Step 1 As a root user, modify the installation file permission to add execute permissions:
chmod +x <installer_file_name>
Step 2 Run the installation file. For example:

Unpacking JRE ...
Preparing JRE ...
Starting Installer ...
This will install SpiderNet on your computer.
OK [o, Enter], Cancel [c]
Step 3 Enter o. The end user licence agreement displays. Read the multi-page licence agreement
using the Enter key to navigate to the next page once you have read the current one.
Please read this document as it contains important information on the legal
terms and conditions governing the use of SpiderCloud's network management
system software (the "SOFTWARE"). This EULA constitutes a legally
enforceable agreement between the purchaser (the "Licensee" or "you"), and
SpiderCloud Wireless, Inc. ("SpiderCloud"). It applies to all SOFTWARE
[truncated]
I accept the agreement
Yes [1], No [2]
1
Where should SpiderNet be installed?
[/usr/local/SpiderNet]
Step 4 Do one of the following:
   Press Enter to accept the default location.
   Type the name and location of the installation directory and press Enter.
Which components should be installed?

1: Server
2: Client
3: Database Restore
Please enter a comma-separated list of the selected values or [Enter] for the
default selection:
[1,2,3]
1
Create symlinks?
Yes [y, Enter], No [n]
y
Select the folder where you would like SpiderNet to create symlinks, then click
Next.
[/usr/local/bin]
   Press Enter to accept the default location.
   Type the name and location of the symlink directory and press Enter.
Uninstalling previous version

Extracting files...
Downloading ...
Extracting files...
bin/
bin/tnameserv
bin/java
bin/jcontrol
bin/rmiregistry
bin/ControlPanel
bin/pack200
[truncated}
Please provide existing database parameters.
Please enter the address and port of the database server
Host Name
[localhost]

Installation

   Press Enter to accept the default host name.
   Type the host name and press Enter.
Port
[3306]
   Press Enter to accept the default port number.
   Type the port number and press Enter.
Please enter the user details which has CREATE and GRANT permissions
User Name
[root]
   Press Enter to accept the default user name.
   Type the user name and press Enter.
User Password
Step 9 Type the user password and press Enter.
Wed Apr 03 14:25:09 PDT 2013 : AWT-EventQueue-0 - java.io.Reader.<init>:78 : -
Setup has finished installing SpiderNet on your computer.
Wed Apr 03 14:25:09 PDT 2013 : Timer-1 - java.io.Reader.<init>:78 : -
Finishing installation ...
[root@localhost ~]#
2.4.3 Installing New Data Model Files

SpiderNet installation files contain a default version of the data model in a file called spidercloud.xsd. Each
services node software version will have a corresponding version of an XSD file. For example SCOS
version 2.0.5 would have also produced a file named scos-2.0.5-data-model.xsd. SpiderNet will use the
XSD file corresponding to the services node SCOS version if it is loaded onto the server, otherwise it will
use the default XSD file to manage the services node.
This section describes how to add new versions of the XSD files to the SpiderNet system using the Secure
Copy Protocol (SCP). Therefore the user computer must have a program that supports that protocol.
To install new data model files into the SpiderNet server
Step 1 As root user, stop the SpiderNet server.
service spidernet_server stop
Step 2 Copy the new XSD file to the schema directory of the root SpiderNet installation folder. In
this example, the user name is admin and the SpiderNet server has the IP address
10.2.2.2:
scp scos-2.0.5-data-model.xsd admin@10.2.2.2:/usr/local/SpiderNet/schema/Scos-
2.0.5-data-model.xsd
Step 3 You will be prompted for the password. Type the password and press the Enter key.
Step 4 Restart the SpiderNet server.
service spidernet_server start

2.4.4 Installing a New Default Data Model

The following procedure installs a new XSD file and renames the file spidernet.xsd to make this the default
data model.
To install a new default data model
Step 1 As root user, stop the SpiderNet server.
Step 2 Copy the new XSD file to the schema directory of the root SpiderNet installation folder. In
this example, the user name is admin and the SpiderNet server has the IP address
10.2.2.2:
scp scos-2.0.5-data-model.xsd admin@10.2.2.2:/usr/local/SpiderNet/schema/
spidercloud.xsd
Step 3 You will be prompted for the password. Type the password and press the Enter key.
Step 4 Restart the SpiderNet server.
2.5 Installing the Java Client Software

The SpiderNet Java client software runs on either the Microsoft Windows or Linux operating system. The
Java client is identical to the server software, and must be the same version as the server it connects to.
Accessing the server through a Java-enabled browser offers identical functionality to that of the Java client
software and is an alternative to managing client-side software versions.
2.5.1 Installing the Java Software on a Microsoft Windows Client

To install the Java software on a Microsoft Windows client
Step 1 Transfer the installation software file to the server.
Step 2 Locate and double-click the installation file (SCNM_windows_a_b_c_d.exe, where a, b, c,
and d are the version number) to load the setup wizard.
Step 3 Follow the wizard through accepting the license agreement, selecting the installation
directory, selecting the components to install, the Windows Start menu group name, and
whether or not to create a desktop icon. The installer will then copy the files and install
them on your server.
Step 4 Click Next on this screen and Finish on the next screen to complete the installation.

Installation
2.5.2 Installing the Java Software on a Linux Client

To install the Java software on a Linux client
Step 1 Transfer the installation software file your computer.
Step 2 With root user privileges, navigate to the location of the installation file directory and launch
the executable. For example:
Unpacking JRE ...
Preparing JRE ...
Starting Installer ...
This will install SpiderNet on your computer.
OK [o, Enter], Cancel [c]
Step 3 Enter o.
At this point the screen prompts for input at various points. Bolded text refers to user input.
Some screen text is truncated for brevity and clarity.
I accept the agreement
Yes [1], No [2]
1
Where should SpiderNet be installed?
[/usr/local/SpiderNet]
Which components should be installed?

1: Server
2: Client
3: Database Restore
Please enter a comma-separated list of the selected values or [Enter] for the
default selection:
[1,2,3]
2
Create symlinks?
Yes [y, Enter], No [n]
y
Select the folder where you would like SpiderNet to create symlinks, then click
Next.
[/usr/local/bin]
Uninstalling previous version
Extracting files...
Downloading ...
Extracting files...
bin/
bin/tnameserv
bin/java
bin/jcontrol
bin/rmiregistry
bin/ControlPanel
bin/pack200
[truncated}
2.6 Configuring MySQL Database Parameters

After the MySQL database has been installed, you must configure some of the database parameters
before installing the SpiderNet server. If the SpiderNet server software has already been installed, stop the
SpiderNet process on the server before configuring the MySQL database parameters.

To configure the MySQL database parameters

Step 1 If SpiderNet is running, log onto the SpiderNet server as root user and issue the following
command to stop the SpiderNet server process:
Step 2 Log onto the MySQL server as root user and issue the following command to open the
MySQL configuration file in a text editor:
vi /etc/my.cnf
Step 3 Locate the line that contains [mysqld] and add the following text immediately after the line:
key_buffer_size = 256M
max_allowed_packet = 100M
sort_buffer_size = 1M
read_buffer_size = 1M
read_rnd_buffer_size = 4M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size= 16M
# CPU's*2 for thread_concurrency
thread_concurrency = 4
Step 4 Save the changes to the configuration file.
Step 5 Issue the following command to restart the MySQL database and apply the changes to the
configuration file:
/etc/init.d/mysqld restart
Step 6 If the SpiderNet server software was installed before this procedure, issue the following
command to restart the SpiderNet server process:
2.7 Configuring Linux System Parameters

You must configure the maximum allowable number of MySQL database connections and maximum
number of open files before starting the SpiderNet server. If the SpiderNet server software has already
been started, stop the SpiderNet process on the server before configuring the number of MySQL database
connections and maximum number of open files.
To configure the maximum number of MySQL database connections
Step 1 If SpiderNet is running, log onto the SpiderNet server as root user and issue the following
command to stop the SpiderNet server process:
Step 2 Log onto the SpiderNet server as root user and issue the following command to open the
system.properties file in a text editor. The system.properties file resides in the SpiderNet
root installation directory.
vi system.properties
Step 3 Locate the line that contains database.connection.pool.max.size and edit the value to
500. If there is no database.connection.pool.max.size line, enter it:
database.connection.pool.max.size=500
Step 4 Save the changes to the system.properties file.

Installation
Step 5 Issue the following command to open the limits.cof file:

vi /etc/security/limits.conf
Step 6 Locate the lines that contain the maximum soft and hard number of open files and edit the
values of both lines to 65000. If those lines are not present, add them to the file.
* soft nofile 65000
* hard nofile 65000
Step 7 Save the changes to the configuration file.
Step 8 Issue the following command to reboot the Linux server:
reboot
Step 9 If needed, issue the following command to restart the SpiderNet server process after the
Linux server boots:
2.8 Redundant Server Overview

SpiderNet supports running in a redundant server configuration with fail-over capability to a standby server
to offer a highly available mode of operation that provides services across a single point of failure. In a
redundant scenario, two servers with identical hardware specifications, identical database installations,
and with IP connectivity, run in active/standby mode to mitigate unexpected service outage due to either
server failure or connectivity issues. Both SpiderNet servers must run the same version of SpiderNet
software and MySQL database. The standby server maintains a mirror image of the active server
database.
During normal conditions, both the active and standby servers are operational with the active server
handling all network management tasks. Such tasks include sessions with managed services nodes,
polling for statistics, alarm forwarding to a North-Bound Network Management System (NB-NMS), and
providing access to connected clients, The active server is also responsible for all database set actions,
and forwards replicated SQL statements to the standby server using a secure SSL connection.
The standby server continually monitors the health of the active server. In the event of an active server
failure, the standby server automatically assumes all functions of the active server. All services nodes that
were connected to the active server reconnect to the standby server, which now becomes active. The
switching is transparent to managed services nodes, but not to any connected client sessions. During
failover connected SpiderNet clients are forced to re-login to the SpiderNet server.
Each SpiderNet server has a unique static IP address or hostname (if a DNS server is configured in the
mobile core network). Both servers commonly share a third IP address or hostname called the floating IP
address. All three IP addresses must be in the same subnet. The floating IP address is always assigned to
the currently active server and is used by SpiderNet clients, services nodes, and NB NMS systems to
communicate with the active server. In the event of a failover, the floating IP address is re-assigned to the

standby server, which in turn assumes the active role. Figure 3 shows a high-level logical view of
SpiderNet redundancy.
Active Standby
DB DB
IP Address 1 (Floating) IP Address 1 (Floating)

IP Address 2 IP Address 3
Figure 3 Redundant SpiderNet Server Configuration
The services nodes always use the floating IP address to connect to the SpiderNet server. Functionalities
that require communication with SpiderNet need to be configured with the floating IP address as the target
destination on the services nodes. Common examples are the management server URL (for TR-069),
SNMP target, syslog target, and any file upload functions such as performance management XML reports.
SpiderNet clients and any NB NMS systems must also be configured to access the SpiderNet server by
using the floating IP address. Figure 4 shows a logical view of a network running SpiderNet in redundant
mode:
Northbound
OSS / NMS
SpiderNet SpiderNet 1 SpiderNet 2
Clients Active Standby
10.1.1.2 10.1.1.3
10.1.1.1
(floating)
Security
Gateway
Switch
Services Node
Enterprise
Radio Nodes
Figure 4 Typical Network with SpiderNet Redundancy
2.8.1 Installation and Initial Configuration Requirements

The SpiderNet redundant installation requires the following:
• Two servers with identical hardware configurations.
• One instance of the MySQL database with the same software version per server. The database
may or may not be on the same physical server as SpiderNet.
• Two SpiderNet licenses allowing the same maximum number of services nodes, and having the
same expiration date. Your SpiderCloud representative will provide the required licenses.
• Both servers must be on the same subnet with IP reachability.

Installation
• Both server IP addresses and the floating IP address must be in the same subnet.
• Both servers must be configured to be in the same time zone.
As part of the initial server configuration, the SpiderNet administrator must assign and configure the
following parameters on both SpiderNet servers in order to enable redundancy:
• Hostname or IP address of each server
• Port number of each server
• Username and password for authentication
• Floating IP address
• Connection settings (timeout, number of retries)
Refer to Section 4.6.3, Redundancy on page 63 for information about configuring redundancy through the
SpiderNet client.
2.8.2 Network Topology Requirements

Each SpiderNet server is assigned a unique static IP address or hostname. Both share the configured
floating IP address. The floating IP address must be network reachable by all managed services nodes, by
devices running client sessions, and by any NB-NMS.
By default, the SpiderNet server that comes up first takes the role of the active server, with the server
coming up second assuming the standby role. To designate a specific server as active, the SpiderNet
service on that server must be started first.
Figure 4 on page 31 shows the recommended network topology for deploying SpiderNet in redundancy
mode. SpiderNet1 is in active mode, SpiderNet2 is in standby mode. Both servers in this example have
been configured with a static IP on the same subnet as the floating IP address. In topologies with a firewall
between the two servers, a TCP port (443, by default) must be open for SpiderNet client/server
communication. In redundant configurations each SpiderNet server must be able to reach an IP address
that will respond to ICMP pings.
2.8.3 Failover Behavior

The active server is responsible for MySQL database replication during normal operations. Once a secure
SSL connection with the standby server has been established, the active server begins sending all
executed SQL set queries to its standby, which in turn, runs all the queries on its database instance.
The standby server continuously monitors the health of the active server by checking the SpiderNet server
status at the application level. Monitoring occurs over the client/server interface.
The following are examples of standby server behavior during common failover scenarios when the active
server becomes unresponsive:
• If the active server is still IP reachable, but the SpiderNet application is not responding, the
monitor daemon on the active server releases the floating IP address and the standby server
assumes the active role and claims the floating IP address.
• If the active server is not IP reachable for a configured time interval, but a well-known IP
address responds to pings, the standby server assumes that the active server is down, assigns
itself the floating IP address, and assumes the active role.
• If the active server is not IP reachable for a configured time interval and a well-known IP
address does not respond to pings, the loss of network connectivity is likely impacting only the
standby server, which takes no action.
In all failover scenarios, a server that was previously active but became unreachable for the configured
duration assumes the role of standby after it recovers. To return the formerly active server to its original

active roll, verify that its SpiderNet server is running properly, then stop and restart the SpiderNet server
process to trigger another failover.
Services nodes remain unaware of any failover and continue to communicate with the floating IP address
regardless of which server is active. Connected client sessions are logged off the system after a failover
and must re-log into the SpiderNet client.
Alarm forwarding from SpiderNet to the NB-NMS continues to work, as there is no change to the
destination IP address for SNMP traps sent by the active server. Similarly the heartbeat between
SpiderNet and NB-NMS also continues to work.
2.9 Preparing the Services Node for SpiderNet

When properly configured, each services node in the network automatically attempts to contact the
SpiderNet server application to log in and create a secure connection. If this information has not been
configured or network topology changes require modifying this information, you can manually change the
services node SpiderNet configuration settings through either the Local Configuration Manager (LCI) or
Command Line Interface (CLI).
2.9.1 Editing the SpiderNet Configuration through the LCI

The LCI Manage EMS tab contains the following parameters, descriptions, valid options, and default
values. Refer to the SpiderCloud System Commissioning Guide for more information about connecting to
and configuring the LCI.
Table 8: Manage EMS Tab Parameters in the LCI
URL URL of the SpiderNet server. Valid URL Empty
http://ab.cd.ef.gf:8080/acs
EnableCWMP Enables or disables services node Boolean. true or false false
support for CPE WAN Management
Protocol (TR-069).
ConnectionRequestPort Port the services node will monitor Positive integer 7547
for requests from the SpiderNet
server.
ClusterID Reserved for future use for services String(64) Empty
nodes deployed as a high
availability unit (redundancy).
CustomerID Optional field that can be used to String(64) Empty
specify a customer identifier. For
example: Apple.
LocationID Optional field that can be used to String(64) Empty
specify a deployment location
identifier. For example: Cupertino.
ConnectionRequestURL Read-only IP address used by the Valid IP address Empty
SpiderNet server to connect to the
(0.0.0.0)
services node.

Installation
2.9.2 Editing SpiderNet Configuration Parameters on a Services Node

Follow this LCI path to edit the services node SpiderNet configuration parameters.
Find It: EMS >> Manage EMS
To edit the SpiderNet configuration through the LCI

Step 1 In an approved browser, enter the IP address or fully qualified domain name of the
services node followed by /lci. Note that this must be a secure connection, use https rather
than http. For example, https://10.1.192.25/lci.
Step 2 Enter your user name and password. The defaults are localadmin and lciadmin.
Step 3 Enter or modify the information as needed.
Step 4 Click Submit.
2.9.3 Editing the SpiderNet Configuration through the CLI

You can log into the CLI remotely through the Secure SHell (SSH) protocol. Log into the services node
through the IP address 192.168.168.1. A default route is configured on Interface 1. Connect to this port in
the services node and access the CLI over the network using SSH:
ssh admin@192.168.168.1
The factory default login is set to the following:
• Username is admin
• Password is admin
To edit the SpiderNet configuration through the CLI
Step 1 Log onto the CLI.
Step 2 Enter the Configuration Mode:
Configure
Step 3 Issue the set ManagementServer command to enter the services node SpiderNet
management parameters. Refer to Table 8 on page 33 for information about these
parameters and their descriptions, valid options, and defaults.
set ManagementServer URL 192.168.1.50:8080/acs UpgradesManaged true
ManageableDeviceNotificationLimit 0 EnableCWMP true
DefaultActiveNotificationThrottle 30 ConnectionRequestPort 7547
Step 4 Issue the following command to verify the configuration:
show ManagementServer
URL http://192.168.1.50:8080/acs;
PeriodicInformEnable false;
UpgradesManaged true;
ManageableDeviceNotificationLimit 0;
EnableCWMP true;
DefaultActiveNotificationThrottle 30;
ConnectionRequestPort 7547;
Step 5 Commit the configuration:
Commit

Refer to the SpiderCloud OS (SCOS) CLI User Guide for an introduction to the key features and
functionalities of the SpiderCloud CLI. Refer to the SpiderCloud OS (SCOS) Administrator Guide for
information about configuring the software environment and internetworking between the services node
and radio node devices.

Installation

3 Initial Configuration

• Section 3.1, Launching the SpiderNet Application on page 37
• Section 3.2, SpiderNet Licensing on page 38
• Section 3.3, Exiting SpiderNet on page 38
3.1 Launching the SpiderNet Application

The SpiderNet client application runs in a standard web browser or a stand-alone Java application. Refer
to Section 2.1, Installation Prerequisites on page 21 for a list of supported browsers. SpiderNet supports up
to ten concurrent users. Upon logging in the first time, you are prompted to change your password. First
enter your original password, then twice enter the new password.
To launch the SpiderNet client application through a browser
Step 1 From a LAN capable of reaching the SpiderNet server, direct a supported web browser to
the hostname or IP address of the SpiderNet server. For example: https://servername.
Be sure to use the secure https rather than the insecure http. A login screen opens.
Step 2 Enter your username and password and click Login. The default username and password
are both admin. The SpiderNet opens in a separate window.
Leave the original browser page open for the duration of your SpiderNet session. Closing
this window or navigating from the hostname or IP address of the SpiderNet server
Note automatically terminates the SpiderNet session.
To launch the SpiderNet client Java application on a Windows computer

Step 1 Either double-click the SpiderNet icon on your desktop or follow this path:
Start >> All Programs >> SpiderNet >> SpiderNet Client
Step 2 Enter the username, password, and server hostname and port in the text boxes of the
dialog box that opens and click Login. If the server fields are not visible, click More >> to
expand the dialog box.
To launch the SpiderNet client Java application on a Linux computer

Step 1 With a terminal program, navigate to the SpiderNet directory.
Step 2 Enter the following command and press the Enter key:
spidernet_client
Step 3 Enter the username, password, and server hostname and port in the text boxes and the
dialog box that opens. Click Login. If the server fields are not visible, click More >> to
expand the dialog box.

Initial Configuration
3.2 SpiderNet Licensing

The SpiderNet application requires a license to manage networks of E-RANs. Licenses are based on the
number of services nodes managed. New licenses are also required when the existing licensing period
expires, additional services nodes have been added to the system, or additional management features
require it. Contact your SpiderCloud representative for information about purchasing SpiderNet licenses.
From the SpiderNet Help menu, select License, then Copy Registration to Clipboard and send this in
an email to your SpiderCloud representative. SpiderCloud will generate a license key and return this key as
a file, which you then upload to the SpiderNet server. Then reboot the server.
3.2.1 Copying the SpiderNet Registration Key
Find It: Help >> License
To copy the SpiderNet registration key

Step 1 Click Copy Registration Key to Clipboard.
Step 2 Paste the registration key into an email and send it to your SpiderCloud representative.
SpiderCloud will generate a license file and send it back to you.
3.2.2 Installing a SpiderNet License

Once the proper licenses are obtained, they must be loaded onto the SpiderNet server.
Find It: Help >> License
To install a license
Step 1 Obtain a license from your SpiderCloud Wireless representative as described in Section
3.2.1, Copying the SpiderNet Registration Key.
Step 2 Save the license file to a local or network drive.
Step 3 Click Select License File. A file browser opens.
Step 4 Navigate to the license file and click OK. The SpiderNet loads the license file. The
SpiderNet server shuts down.
Step 5 Restart the SpiderNet server by logging into the server as root user and entering the
following command:
3.3 Exiting SpiderNet

Find It: Any Screen
To exit the SpiderCloud application

Step 1 From the Menu Bar, click File >> Exit. A confirmation screen opens.

Step 2 Click Yes to exit the application.

Initial Configuration

4 Administration
SpiderNet administration consists of managing access control, audit logs, the northbound interface to the
provider core network, users, the database, network maps, and the SpiderNet configuration itself. Client
sessions are username/password authenticated and encrypted. The administrator can create user profiles
and set user privileges, restricting or allowing access to configuration changes, upgrades, and other
management operations.
Separate user accounts can be activated and mapped to defined user profiles. All client sessions are
subject to administrative control and can be restricted to specific workstations defined by their IP address.
All user operations are securely logged on the server, and audit trails are available for future inspection.
• Section 4.1, Access Control on page 41
• Section 4.2, Audit Trail on page 47
• Section 4.3, Northbound Interface on page 49
• Section 4.4, Email on page 52
• Section 4.5, Fault Management on page 54
• Section 4.6, Server Settings on page 59
• Section 4.7, Database Settings on page 65
• Section 4.8, Geographical Maps on page 67
• Section 4.9, Performance Configuration on page 67
4.1 Access Control

Access control tabs define users, their access to system components, and their ability to perform actions
within the system.
4.1.1 Users
All users are assigned a profile that defines their system permissions and determines which equipment
and services they have visibility to. Some administrative users have broad permissions to create and
modify objects. Other users have read-only permissions, perhaps to a small sub-set of the system
configuration.
The Users tab contains the following parameters, descriptions, valid options, and default values:
Table 9: Users Tab Parameters
Username Name of SpiderNet user. String(256) admin
Password/Confirm Password of Username. String(256) admin
Password
Valid options defined in
Section 4.1.4, Password
on page 46

Administration
Table 9: Users Tab Parameters (continued)

Question 1/2 User defined question to validate a user String(200) None
that forgets their password.
Answer 1/2 Answer to Question. String(200) None
Profile Profile to attach to the user. Profiles defined in Section None
4.1.2, Profiles on page 44
Expiration Date Number of days after the first user Integer 1-30, Never 30 days in
activation that the initial password is the future
valid. Afterwards the rules defined in
Section 4.1.4, Password on page 46
apply.
Host IP address that the user must log in Valid IP address None
from.
Lock Account Prevent changes to the account. Check box Cleared
First Name User’s first name. String(128) None
Last Name User’s last name. String(128) None
Department User’s department. String(128) None
Location User’s location. String(128) None
Phone User’s phone number. String(128) None
Email User’s email address. String(128) None
4.1.1.1 Creating a User

Create a new user by adding personal user information, assigning a password and defining password
recovery questions and password expiration date, assigning a profile, and optionally tying the user to a
specific IP address.
Find It: Administration >> Access Control >> Users
To create a user
Step 1 Click New User.
Step 2 Enter a user name in the Username text box.
Step 3 Enter the user password in both the Password and Confirm Password text boxes. Refer
to Section 4.1.4, Password on page 46 for information about valid password parameters.
Step 4 To add user-defined password challenge questions, select the Add/Change Password
Recovery Questions check box and complete the two question/answer pairs below.
Step 5 Select the defined user profile from the Profile drop-down list. Refer to Section 4.1.2.1,
Creating a Profile on page 44 for information about profiles.
Step 6 Either select the Password Never Expires check box or select a date from the Expiration
Date drop-down list to define the password expiration date.
Step 7 (Optional) Enter the IP address of the user’s PC in the Host text box to restrict access to
that PC.

Step 8 In the Additional Information area, enter the user information.

Step 9 Click Apply.
4.1.1.2 Editing Users
To edit user details

Step 1 Click the user name.
Step 2 Edit the information as needed.
Step 3 Click Apply.
4.1.1.3 Logging Out Users
To log a user out

Step 2 Click Force Logout. A confirmation screen opens.
Step 3 Click OK.
4.1.1.4 Deleting Users
To delete a user
Step 2 Click Delete. A confirmation screen opens.
Step 3 Click Yes.

Administration
4.1.2 Profiles
A user profile is a set of common operation permissions that can be assigned to a group of administrators
and other users. New users are assigned to a profile when they are added to the system. Administrators
can be allowed to add and modify user permissions, profiles, and views.
The Profiles tab contains the following parameters, descriptions, and valid options:
Table 10: Profiles Tab Parameters
Element Description Valid Options
Profile Name Name of the user profile. String(100)
Admin Operations Administrative privileges available System Administration, Users
to the user with this profile. Management, Profiles Management,
Views Management
Application Operations Applications available to the user Events Edit, Events View, Topology
with this profile. Change, Topology View, Tasks
Configuration, Tasks View, Discovery
View, Discovery Configuration,
Performance View
Note that the following application operations are not supported in this release: Discovery View, Discovery
and Configuration.
4.1.2.1 Creating a Profile
Find It: Administration >> Access Control >> Profiles
To create a profile
Step 1 Click New Profile.
Step 2 In the Profile Name text box, enter the user profile name.
Step 3 In the Admin Operations area, select one or more check boxes for user administrative
privileges.
Step 4 In the Application Operations area, select one or more check boxes for user application
privileges.
Step 5 Click Apply.
4.1.2.2 Modifying a Profile

Default profiles are read-only, they cannot be modified. Custom profiles can be edited by administrators
with sufficient permissions.
To modify a profile
Step 1 Select the profile and edit as needed.
Step 2 Click Apply.

4.1.2.3 Deleting a Profile

Default profiles are read-only, they cannot be deleted. Custom profiles can be deleted by administrators
with sufficient permissions.
To delete a profile
Step 1 Select the profile and click Delete. A confirmation box opens.
Step 2 Click OK.
4.1.3 Views
Views control which sections of the network topology tree are visible for each user profile. A view can be
linked to any node (Subnet Group or Subnet) in the network topology tree to control which users can see
the node. If a node is not linked to any view, then it is visible to all users.
When you create a view, use the selection boxes at the left to select which user profiles will be able to see
the nodes linked to the view. To link a view to a subnet, right-click the subnet in the network topology tree
and select Edit Subnet.
The Views tab contains the following parameters, descriptions, and valid options:
Table 11: Views Tab Parameters
View Name Name of the current view. String(100)
Related Profiles Profile to associate with the view. Defined user profiles
4.1.3.1 Creating a View
Find It: Administration >> Access Control >> Views
To create a view
Step 1 Click New View.
Step 2 In the View Name text box, enter the name of the new view.
Step 3 In the Related Profiles area, select one or more user profiles to apply to the view.
Step 4 Click Apply.
4.1.3.1 Deleting a View
Find It: Administration >> Access Control >> Views
To delete a view
Step 1 Select the view.
Step 2 Click Delete. A confirmation screen displays.
Step 3 Click Yes.

Administration
4.1.4 Password
Use the Password tab to set user password requirements. Password policies are subject to the following
conditions:
• The admin user password can be changed in the Administration >> Access Control >>
Users tab, but does not expire. This behavior is not configurable.
• A global password policy configured in the Administration >> Access Control >> Password
tab by default applies to all other users. Any changes to this policy apply to all users other than
the admin.
• If the global password policy does not set the expiry to Password Never Expires, individual
users other than admin can have an individual password expiry policy defined in the
Administration >> Access Control >> Users tab provided the expiry date is sooner than the
global policy. SpiderNet validates this rule and will not permit an individual password policy
expiry date to exceed the global password policy.
The Password tab contains the following parameters, descriptions, valid options, and default values:
Table 12: Password Tab Parameters
Minimum password The minimum number of characters Integer. Valid options: 6 8
length required to form a valid password. through 15
Require English upper Whether or not English upper case Check box Checked
case characters in characters are required in the
password password.
Require English lower Whether or not English lower case Check box Checked
case characters in characters are required in the
password password.
Require digits in Whether or not numbers are required Check box Checked
password in the password.
Require non- Whether or not characters other than Check box Checked
alphanumeric letters and numbers are required in the
characters in password password.
Password never expires Whether or not the password has an Check box Cleared
expiration date.
Number of days before The number of days a password is Integer. Valid options: 1 30
password expires valid before it needs to be changed. through 90
Number of login tries The number of times the user can Integer. Valid options: 1 5
before user is locked incorrectly enter login information through 10
before being locked out of the system.
The login is exclusive Whether or not multiple users can log Check box Cleared
in with the same username.
4.1.4.1 Setting Password Parameters
Find It: Administration >> Access Control >> Password

To set password parameters

Step 1 Complete the form by selecting numbers and checking or clearing the check boxes.
Step 2 Click Apply.
4.1.5 Connected Users

The Connected Users tab is a read-only display of currently logged in users and their attributes. It
displays the logged in user, associated profile, IP address of the user’s computer, and length of time
connected. Administrators can log users out of the system.
4.1.5.1 Logging Users Out

You can log out a current SpiderNet user.
Find It: Administration >> Access Control >> Connected Users
To log another user out

Step 1 Select one or more user.
Step 2 Click Force Logout.
4.2 Audit Trail

The Audit Trail panel is a read-only display of system activities and who performed them. It tracks all user
operations that change a services node or SpiderNet configuration. The audit trail contains the 1000 most
current activities per page. Activities attempted that were not permitted are highlighted in red. The
information can be filtered, exported to a Comma Separated Value (CSV) file, refreshed and printed. If the
screen has been filtered, the exported file and the printout will contain only results of that filter.
The Audit Trail panel contains the following parameters, descriptions, and valid options:
Table 13: Audit Trail Parameters
Seq No. Index number of the activity. Positive integer
Operation Time & Date The date and time the activity in ISO In the format: mm/dd/yyyy hh:mm:ss
8601 format. AM/PM timezone
Username Name of the SpiderNet user. Defined system user
Operation Name System activity. N/A
Client IP Address IP address of the user that performed Valid IP address
the action.
Operation Status Whether or not the activity was Enum: Valid options: Allowed, Denied
performed.

Administration
4.2.1 Refreshing the Audit Trail
Find It: Administration >> Audit Trail
To refresh the Audit Trail panel

Step 1 Click Refresh.
4.2.2 Filtering the Audit Trail Display
To filter the Audit Trail display

Step 1 Click Filter. The Audit Filter Dialog screen opens.
Step 2 To filter by time, select the Operation Date & Time check box and select From and To
date and time.
Step 3 To filter by operation type, select the Operation Name check box, select Contains or
Equals from the drop-down list, and enter the filtering text in the text box.
Step 4 To filter by status, select the Operation Status check box and select Allowed or Denied.
Step 5 To filter by the IP address of the user, select the User Address check box, select
Contains or Equals from the drop-down list, and enter the filtering text in the text box.
Step 6 To filter by user, select the Action Username check box and select the user from the drop-
down list.
Step 7 (Optional) Click the Select All check box to filter by all the criteria. Only data that meets all
the defined criteria will display.
Step 8 Click OK.
4.2.3 Saving the Audit Trail to File
To save the audit trail to a file

Step 1 Click the Export to CSV button. The Export to CSV dialog box opens.
Step 2 Navigate to the file location on your local or network drive, name the file, and click Save. A
confirmation screen displays.
Step 3 Click OK to save the file in CSV format.

4.2.4 Printing the Audit Trail Screen Display
To print the audit trail screen display

Step 1 From the administration button bar, click the Print button. The Print dialog box opens.
Step 2 Select the printer and print options.
Step 3 Click Print.
4.3 Northbound Interface

The Northbound Interface panel configures SNMP trap forwarding functionality for northbound alarm
notification and SpiderNet SNMP agent settings. The Northbound Interface panel contains the Alarm
Forwarding, and SNMP Agent tabs.
4.3.1 Alarm Forwarding

SpiderNet alarm forwarding consists of forwarding events that mark alarms or clear them to a trap target. It
forwards traps generated by its managed services nodes and by SpiderNet itself.
You can forward SNMP traps to multiple targets by creating an SNMP managers group. An SNMP
managers group is a collection of one or more trap targets that share the same SNMP configuration.
SpiderNet maps the trap to match the type used by the trap target.
Existing SNMP manager groups display on the main screen with the configured SNMP trap target IP
addresses. Refer to Section 4.5, Fault Management on page 54 for information about configuring the
events to forward.
The Alarm Forwarding tab contains the following parameters, descriptions, and valid options:
Table 14: Alarm Forwarding Tab Parameters
Name Name of the SNMP manager group. String(255)
Port UDP port number of the SNMP trap target. Valid port number. Default is 162.
Enable/Disable Enables the SNMP manager group. Check box. Default is checked
IP Addresses IP address of the SNMP trap target. Valid IP addresses separated by commas
Enable Enables a periodic heartbeat to the trap Check box. Default is cleared.
heartbeat trap target to indicate that it is currently
running.
Heartbeat Number of minutes between keepalive Non-negative integer. Default is 5.
Interval heartbeat messages.
SNMP Version Supported SNMP version. V2C or V3. Default is V2C.
Community SNMP community string. String(255). Default is public.

Administration
4.3.1.1 Creating an SNMP Managers Group
Find It: Administration >> Northbound Interface
To create an SNMP managers group

Step 1 Click New SNMP Managers Group. The New SNMP Managers Group screen opens.
Step 2 Enter the name of the SNMP managers group in the Name text box.
Step 3 Enter the SNMP trap target port number in the Port text box.
Step 4 Select the Enable/Disable check box to enable SNMP alarm forwarding. Clear the check
box to disable it.
Step 5 Enter one or more SNMP trap target IP addresses in the IP Addresses text box. Separate
multiple addresses with commas.
Step 6 (Optional) Select the Enable the heartbeat trap check box and enter the heartbeat
interval. The heartbeat sends a simple keepalive message to the trap target to indicate that
it is still running.
Step 7 Select the SNMP version.
Step 8 Enter the SNMP community string in the Community text box.
Step 9 Click OK.
4.3.1.2 Editing an SNMP Managers Group
To edit an SNMP managers group

Step 1 From the main screen, select the group and click Edit. The SNMP Managers Group
screen opens.
Step 2 Edit the screen as needed.
Step 3 Click OK.
4.3.1.3 Deleting an SNMP Managers Group
To delete an SNMP managers group

Step 1 From the main screen, select the group and click Delete. A confirmation screen opens.
Step 2 Click OK.
4.3.2 SNMP Agent

The SpiderNet SNMP agent supports SNMP V2C and V3 versions with WALK, GET, GET-NEXT, and GET-
TABLE in the SpiderNet MIB. It supports SET only for the System group in MIB-II and SpiderNet MIB. The

agent will not serve as an SNMP proxy to the services nodes. SNMP requests containing OIDs from the
ERAN MIBs will return an SNMP No such name error.
At least one of the SNMP V2C or SNMP V3 check boxes must be selected or the configuration will be
rejected. The SNMP Agent tab contains the following parameters, descriptions, and valid options:
Table 15: SNMP Agent Tab Parameters
Enable Internal SNMP Whether or not to enable the internal Check box. Default is
Agent SNMP agent to manage SNMP GET/ checked.
WALK/SET commands.
Listen Port The port that listens for SNMP traps from Valid port number. Default is
the northbound interface. 162.
SNMP V2C Whether or not to enable SNMP V2C. Check box. Default is
checked.
Read Community The SNMP read community string. Valid SNMP community.
Default is public.
Write Community The SNMP read community string. Valid SNMP community.
Default is public.
SNMP V3 Enables or disables SNMP V3 inform Check box. Default is cleared.
reception.
Engine ID The identifier of the remote SNMP protocol Valid SNMP engine ID.
engine Maximum 256 alphanumeric
characters.
User Name User name of the northbound interface. Up to 32 alphanumeric
characters. Preferred length is
8.
Authentication Protocol Selects the authentication protocol. None, MD5, SHA
Privacy Protocol Selects the privacy protocol. None, DES, AES-128
Change Password Allows administrators to change the Valid passwords.
authentication or privacy protocol.
4.3.2.1 Configuring the Northbound Interface SNMP Agent
Find It: Administration >> SNMP Agent
To configure the northbound interface SNMP agent

Step 1 Select or clear the Enable Internal SNMP Agent check box.
Step 2 If appropriate, enter the SNMP port that will listen for traps.
Step 3 Select or clear the SNMP V2C or check box. At least one of the SNMP V2C or SNMP V3
check boxes must be selected or the configuration will be rejected. If selected, enter the read
and write community names.

Administration
Step 4 Select or clear the SNMP V3 check box. At least one of the SNMP V2C or SNMP V3 check
boxes must be selected or the configuration will be rejected. If selected, complete the text
boxes and select the protocols with the drop-down lists.
Step 5 (Optional) Click Change Password and enter and confirm the new password.
Step 6 Click Save.
4.3.2.2 Modifying the Northbound Interface SNMP Agent Settings

After saving modifications to the northbound interface SNM agent settings, you will be prompted to restart
the SpiderNet server before the changes take effect.
Find It: Administration >> SNMP Agent
To modify the northbound interface SNMP agent settings

Step 2 Click Save.
4.4 Email
The Email panel contains tabs for managing email groups and Simple Mail Transfer Protocol (SMTP)
parameters.
4.4.1 Email Groups

The Email Groups tab contains settings for managing email distribution lists. The Email Groups tab
contains the following parameters, descriptions, and valid options:
Table 16: Email Group Tab Parameters
Name Name of the email distribution list. String(100)
Email Addresses Email addresses of the users or groups in the Valid email addresses. Separate
distribution list. multiple addresses with commas.
4.4.1.1 Creating an Email Group
Find It: Administration >> Email >> Email Groups
To create an email group

Step 1 Click New. The Add Email(s) Group dialog box opens.
Step 2 Enter the group name in the Name text box.
Step 3 Enter the email addresses of group members in the Email Addresses text box. Separate
multiple addresses with commas.
Step 4 Click OK.

4.4.1.2 Editing an Email Group

The email group name cannot be changed. You can modify the group member email addresses.
To edit an email group

Step 1 Select the group to edit from the main screen and click Edit. The Edit Email(s) Group
dialog box opens.
Step 2 Edit the email addresses as needed.
Step 3 Click OK.
4.4.1.3 Deleting an Email Group
To delete an email group

Step 1 Select the group to delete from the main screen and click Delete. A confirmation screen
opens.
Step 2 Click Yes.
4.4.2 SMTP
Use the SMTP tab to configure SMTP server settings. The SMTP tab contains the following parameters,
descriptions, and valid options:
Table 17: SMTP Tab Parameters
Enable Enables or disables SMTP email. Check box. Default is cleared.
From Email Name displayed in the email message From field. String(256) in email format
SMTP Server SMTP server IP address. Valid IP address or host name
of the SMTP server
SMTP Port SMTP server port number. Valid port number.
Security Data transmission security protocol. None, TLS, SSL
Use Authentication Whether or not to use SSL authentication. Check box. Default is cleared.
Username Username of SMTP server that requires String(65)
authentication
Password Password of Username. String(32)
4.4.2.1 Configuring SMTP Email Settings

In network configurations with firewalls, you may need to open firewall port 25.

Administration
Find It: Administration >> Email >> SMTP
To configure SMTP email settings

Step 1 To enable the SMTP server, check the Enable check box.
Step 2 In the From text box, enter the name that displays in the email message From field in
email format.
Step 3 Enter the SMTP server IP address or hostname in the SMTP Server text box.
Step 4 Enter the SMTP port number in the SMTP Port text box.
Step 5 In the Security area, select the radio button of the data transmission security protocol.
Step 6 To authenticate the user name and password, check the User Authentication check box.
Step 7 Enter the authentication user name in the Username text box.
Step 8 Enter the authentication password in the Password text box.
Step 9 Click Save.
4.4.2.2 Editing SMTP Settings
Find It: Administration >> Email >> SMTP
To edit SMTP settings

Step 2 Click Save to save the new configuration. Click Reset to return to the last saved
configuration.
4.5 Fault Management

The Fault Management panel configures SpiderCloud event forwarding and SpiderNet-specific fault
management parameters. Refer to Chapter 7, “Fault Management” on page 121 for information about
SpiderCloud equipment and networking fault management.
4.5.1 Events Configuration

The top section of the Event Configuration tab contains check box/drop-down list combinations configure
actions for all events in the system. Configure individual event actions in the lower section of the screen.
The Fault Management panel contains the Event Configuration and Trap Receive tabs.

The Events Configuration tab contains the following parameters, descriptions, and valid options:
Table 18: Event Configuration Tab Parameters
Forward to SNMP Forwards all events to the SNMP Drop-down list
Managers Group managers groups defined in Section 4.3.1,
Alarm Forwarding on page 49.
Forward to Email Forwards all events to an email address Drop-down list
defined in Section 4.4, Email on page 52.
Severity Used in conjunction with Forward to IP Drop-down list. Valid options are
and/or Forward to Email, sets the minimum Warning, Minor, Major, Critical
event severity to forward.
Set to All Change the value for all entries in the Check box. Default is cleared.
table.
Event Type of event to configure. Enum: Valid options are: Reboot,
Server Shutdown, Table Cleanup,
Device Connected, Device
Disconnected, Device Discovered,
Configuration Error, Threshold
Exceeded, Server Startup, Threshold
Back to Normal
Severity Reset the severity of the event. Enum: Valid options are: Info, Cleared,
Warning, Minor, Major, Critical
Forward to SNMP SNMP managers group to forward event Drop-down list. Defined SNMP
Managers Group to. managers group or None
Forward to Email Email address to forward event to. Drop-down list. Defined email address
or None.
Play Audible Tone Whether or not to activate an audible tone Check box
when an event occurs.
Table 19 shows SpiderNet fault management events, their default severities and configurability, and
whether or not an audible tone can be enabled. The event severities can be modified.
Table 19: Event Parameters
Default Audible Tone
Event Severity Enabled? Description
RANAP CS Connection Major Yes The RANAP connection to the CS domain of the
Terminated core network has been terminated.
Over Temperature Major Yes This condition is used to indicate an object in the
system is in the process of overheating. The severity
of the condition increases as the temperature
increases.
Power Supply Missing Major Yes One of the two services node power supply modules
has not been installed or has been removed.
Table Cleanup Major No The events or audit trail table is undergoing
maintenance.

Administration
Table 19: Event Parameters (continued)

Warm Start Warning Yes A services node has had a warm start.
Device Added Info No A new device has been added.
Configuration Mismatch Major Yes SpiderNet failed to configure a services node.
Cell Max Power Delta Major Yes The difference between a cell's
Exceeded MaxFAPTxPowerInUse and MaxTxPowerReference
has exceeded MaxTxPowerDeltaAllowed.
Configuration Error Major Yes The actual equipment type does not match the
configured equipment type.
Cold Start Warning Yes A services node has had a cold start.
System Max Session Warning Yes The system has exceeded the maximum allowed
Rate Exceeded session rate calculated as number of UMTS session
requests received by the services node per minute.
The limit is 600 sessions.
System Near Max Warning Yes The system is nearing the maximum allowed
Session Rate session rate. The threshold is based on a
percentage of maximum allowed session rate. The
percentage is configurable, the default is 90%.
DHCP Allocation Failure Warning Yes A radio node is requesting an IP address, but there
are no more IP addresses in the pool.
Calibration Invalid Major Yes Radio node calibration data is not valid.
DB Invalid Major Yes The startup validation of the database failed.
Link Up Cleared No The previously unavailable Ethernet port link is now
available.
Device Connected Cleared No A previously disconnected device has re-connected
to the system.
Device Discovered Info No SpiderNet has discovered a services node.
Loss of Synchronization Major Yes There was a loss of synchronization on a radio
node.
Services Node Link Major Yes Link is not available on a front panel port.
Down
Reboot Info No A services node has booted.
Authentication Failure Minor Yes A protocol mismatch between SpiderNet and a
services node.
Link Down Major Yes Link is not available on a front panel port.
Neighborhood Minor Yes The current cell neighborhood is not same as the
Reference Delta reference cell neighborhood.
Multiple Cooling Fan Critical Yes Two or more services node fans have failed.
Failures

Table 19: Event Parameters (continued)

Forwarded Notification Major Yes Messages from a third-party device forwarded to the
Message OSS.
Device Disconnected Major Yes A previously connected services node has been
disconnected.
Provisioning Fault Major Yes An error was detected during the provisioning of an
object in the system.
Core Network IPsec Major Yes An IPsec tunnel to an radio node has been
Tunnel Terminated terminated.
RANAP PS Connection Minor Yes The RANAP connection to the PS domain of the
Terminated core network has been terminated.
Missing Equipment Major Yes Indicates a provisioned object in the system is not
present or is missing.
Server Shutdown Major No The SpiderNet server has shut down.
UARFCNDL Changed Major Yes The UARFCNDL has changed, provisioned UMTS
externals cells have be recreated.
Device Deleted Info No A services node has been deleted from the
SpiderNet database.
Notify Message Major Yes Reserved for future use.
Software Mismatch Major Yes Internal Software Mismatch has been detected.
Power Supply Failed Major Yes A power supply module has failed.
IPsec Down Major Yes An IPsec tunnel to an radio node has been
terminated.
RF Management Faulted Major Yes The cell was faulted by the RF management
subsystem.
Server Startup Info No The SpiderNet server has started.
4.5.1.1 Configuring Fault Management Settings
Find It: Administration >> Fault Management >> Events Configuration
To configure SpiderNet fault management settings

Step 1 In the top section of check box/drop-down list pairs, select the box and drop-down option to
apply to all events. Options are Forward to SNMP Managers Group (a managers group
defined in Section 4.3.1.1, Creating an SNMP Managers Group on page 50), Forward to
Email (defined in Section 4.4, Email on page 52), minimum Severity level, and whether or
not to Play Audible Tone.
Step 2 In the lower section, configure actions that apply to individual event types. Options are
Forward to IP, Forward to Email, and Play Audible Tone. Refer to Table 19 on page 55
for configuration options.

Administration
Step 3 Click Save.
4.5.1.2 Editing Fault Management Settings
Find It: Administration >> Fault Management >> Events Configuration
To edit SpiderNet fault management settings

Step 2 Click Save to save the new configuration. Click Reset to return to the last saved
configuration.
4.5.2 Trap Receive

You can enable SNMP V1/2, V3, or both, but must select at least one version. The Trap Receive tab sets
the parameters for SNMP V2 and V3, and the parameters required by SpiderNet to be able to authenticate
received SNMP V3 traps.
Table 20: Trap Receive Tab Parameters
Trap Receive Port The port that SpiderNet will listen to on Valid ports. Default is 162.
startup for incoming traps. Changes
require server restart.
SNMP V1/V2 Enables or disables SNMP trap Check box. Default is checked.
reception for SNMP V1 and V2.
Filter by Trap Community Accepts traps only from this SNMP Check box. Default is cleared.
community string.
Trap Community Trap community string to filter by. Community string of trap
target.
SNMP V3 Enables or disables SNMP V3 inform Check box. Default is cleared.
reception.
Engine ID The identifier of the remote SNMP Valid SNMP engine ID.
protocol engine Maximum 256 alphanumeric
characters.
User Name User name of the northbound interface. Up to 32 alphanumeric
characters. Preferred length is
8.
Authentication Protocol Selects the authentication protocol. None, MD5, SHA
Privacy Protocol Selects the privacy protocol. None, DES, AES-128
Change Password Allows administrators to change the Valid passwords.
authentication or privacy protocol.
4.5.2.1 Configuring the SNMP Trap Reception
Find It: Administration >> Fault Management >> Trap Receive

To configure SNMP trap reception

Step 1 Select one or both of the SNMP V1/V2 and SNMP V3 check boxes. At least one of the
SNMP V2C or SNMP V3 check boxes must be selected or the configuration will be rejected.
Step 2 To filter by SNMP V1/V2 trap community, select the Filter by Trap Community check box
and enter the community name in the text box.
Step 3 To enable SNMP V3, select the check box and complete the text boxes and select the
protocols with the drop-down lists.
Step 4 (Optional) Click Change Password and enter and confirm the new password.
Step 5 Click Save.
4.5.2.2 Modifying SNMP Trap Reception
Find It: Administration >> Fault Management >> Trap Receive
To modify SNMP trap reception parameters

Step 2 Click Save.
4.6 Server Settings

The Server Settings panel contains tabs for configuring file transfer settings, the syslog server, and
redundancy.
4.6.1 File Transfer Settings

SpiderNet supports two file transfer protocols: FTP and SCP. It contains an integrated FTP server, but can
be configured to work with an external FTP server. The SCP server must be installed on the SpiderNet
hardware server. The File Transfer Settings tab contains settings for configuring these two file transfer
servers. The File Transfer Settings tab contains the following parameters, descriptions, and valid options:
Table 21: File Transfer Tab Parameters
Select the server address IP address of file transfer clients to IP addresses of the file transfer
used by File Transfer clients send files. server
FTP Server Settings
Enable Enables or disables the SpiderNet FTP Check box. Default is cleared.
server.
Auto Start Whether or not to start the FTP server Check box. Default is disabled.
when SpiderNet boots.
Status Read-only status of the FTP server. Running, Stopped, disabled.
Default is Stopped.
Start/Stop Toggle to start or stop the FTP server. Default is disabled
Password/Confirm Password New FTP server password. Valid FTP server password

Administration
Table 21: File Transfer Tab Parameters (continued)

External File Transfer Server Settings
Hostname Hostname of the external file transfer Valid IP address or hostname
server.
Port Port number of the external file transfer Valid port number. Default is
server. 21.
Server requires authentication Whether or not the external file transfer Check box. Default is cleared.
server requires authentication.
Username External file transfer server user name Valid user name
when authentication is required.
Password External file transfer server password Valid password
when authentication is required.
SCP Server
Enable Enables or disables the SpiderNet SCP Check box. Default is cleared.
server.
Auto Start Whether or not to start the SCP server Check box. Default is disabled.
when SpiderNet boots.
Status Status of the SCP server. Running, Stopped, disabled.
Default is Stopped.
Port SCP server port. Valid port number. Default is
221.
Start/Stop Toggle to start or stop the SCP server. Default is disabled
4.6.1.1 Configuring File Transfer Settings
Find It: Administration >> Server Settings >> File Transfer Settings
To configure file transfer settings

Step 1 In the Address Settings area, select the IP address of the file transfer clients to send files
and click Apply.
Step 2 In the FTP Server Settings area, select the Enable check box to enable the SpiderNet
FTP server. When enabled, configure the following:
   Select the Auto Start check box to automatically start the FTP server upon
SpiderNet server reboot.
   Select the Start/Stop toggle button to start or stop the FTP server.
   In the Change Password section, enter and reenter the new password, then click
Apply.
Step 3 In the External FTP Server Settings area, enter the parameters for the optional external
file transfer server:
   Enter the IP address or hostname in the Hostname text box.
   If needed, edit the file transfer server port number in the Port text box.

   For authenticated servers, select the Server requires authentication check box,
enter the Username and Password in the text boxes, and click Apply.
Step 4 In the SCP Server area, select the Enable check box to enable the SpiderNet SCP server.
When enabled, configure the following:
   Select the Auto Start check box to automatically start the SCP server upon
SpiderNet server reboot.
   Enter the scp port number on the SpiderNet server in the Port text box.
   Select the Start/Stop toggle button to start or stop the SCP server.
   Click Apply.
4.6.1.2 Editing File Transfer Settings
To edit file transfer settings

Step 2 Click Apply when appropriate to save the new configuration.
4.6.1.3 Enabling the SCP on the Server

The SpiderNet server uses the SCP protocol in its syslog communication with services nodes.
SpiderCloud recommends and has verified OpenSSH that ships with the CentOS or RedHat Enterprise
Server bundle. Refer to the manufacturer's documentation for information about how to install, configure,
and run the SSH server software.
Step 1 On the SpiderNet server, as a root user, install and configure the SSH server.
Step 2 Create a non-root user with no shell privileges.
Step 3 In the SpiderNet graphical interface, open the Administration tab and navigate to the
Server Settings screen.
Step 4 Complete the settings in the External File Transfer Server Settings area of the File
Transfer Settings tab. Set Port to 221.
Step 5 Configure and enable the SCP Server area.
Step 6 In the Network Control tab, schedule a File Download task with the scp protocol,
External Server, and enter the full path to the file to transfer. Refer to Section 6.5.1.1,
Scheduling a File Download on page 108 for more information about scheduling a task.

Administration
4.6.2 Syslog Server

This screen configures the SpiderNet server options for receiving syslog events from managed services
nodes. The Syslog Server tab contains the following parameters, descriptions, and valid options:
Table 22: Syslog Server Tab Parameters
Enable Enables or disables the ability of SpiderNet to Check box. Default is checked.
receive syslog events from its services node.
Port Port number to receive syslog events. Valid port number. Default is 514.
Protocol Protocol used in sending syslog traffic. Enum. Valid options are: UDP.
Auto Start Whether or not to start the syslog server when Check box. Default is checked.
SpiderNet boots.
Status Read-only status of the syslog server. Running, Stopped, disabled. Default is
Running.
Start/Stop Toggle to start or stop the syslog server. Default is Stopped.
If you change the syslog server port to one other than 514, be sure to make corresponding
changes to your firewall settings.
Note
Configuring the Syslog Server
Find It: Administration >> Server Settings >> Syslog Server
To configure the syslog server

Step 1 Select the Enable check box to enable receiving syslog events. When enabled, configure
the following:
   If needed, edit the default syslog port number in the Port text box.
   Select the protocol from the Protocol drop-down list.
   Select the Auto Start check box to automatically start receiving syslog messages
upon SpiderNet server reboot.
   Select the Start/Stop toggle button to start or stop receiving syslog events.
Step 2 Click Apply.
4.6.2.1 Editing Syslog Server Settings
To edit syslog server settings

Step 2 Click Apply.

4.6.2.2 Refreshing the Syslog Server Screen
To refresh the syslog server screen

Step 1 Click Refresh.
4.6.3 Redundancy
You can configure a standby SpiderNet server that can control the network in the event that the active
server fails. In a redundant configuration, the standby server maintains a mirror image of the active server
database with both servers maintaining an identical user-facing IP address. After the standby server
becomes active, it continues to monitor the health of the former active server.
Once the former active server becomes reachable again, it reassumes the role of active server, returning
the other server to its original standby role. Refer to Section 2.6, Configuring MySQL Database
Parameters on page 28 for more information about redundancy. Refer to Section 4.7, Database Settings
on page 65 for more information about configuring database settings.
The Redundancy tab contains the following parameters, descriptions, and valid options:
Table 23: Redundancy Tab Parameters
Disable redundancy mode Whether or not to configure a redundant Check box. Default is
SpiderNet server. checked.
Server 1 Settings
Hostname Hostname of the primary SpiderNet server. Valid IP address or
hostname
Port Port number of the primary SpiderNet server. Valid port number. Default
is 443.
Server 2 Settings
Hostname Hostname of the backup SpiderNet server. Valid IP address or
Must be in the same subnet as Server 1. hostname
Port Port number of the backup SpiderNet server. Valid port number. Default
is 443.
Authentication
Username SpiderNet server user name when Valid user name
authentication is required between the
primary and backup servers.
Password SpiderNet server password when Valid password
authentication is required between the
primary and backup servers.
Connection Settings
NMS IP Address (Floating) IP address shared by both the primary and Valid IP address or
backup server for user access. Must be in the hostname
same subnet as Server 1 and Server 2.

Administration
Table 23: Redundancy Tab Parameters (continued)

Retries Number of times the secondary server is Integer. Valid options are 1
allowed to try and log into the primary server through 999. Default is 3.
before it becomes the active server.
Timeout Number of seconds the secondary server is Integer. Valid options are 1
allowed to try and log into the primary server through 999. Default is 10.
before it becomes the active server.
Redundancy Status A visual display of the status of the two N/A
configured SpiderNet servers.
Test Connection A button, that when clicked, test the N/A
connection between the two configured
SpiderNet servers.
4.6.3.1 SpiderNet Server Redundancy Preconditions

Ensure that the following conditions have been met before configuring redundant SpiderNet servers:
• Both SpiderNet servers have identical hardware specifications and database installations.
• The backup server must be running a clean installation of the same version of the SpiderNet
server software as the primary server with licenses applied. Refer to Section 3.2.2, Installing a
SpiderNet License on page 38.
• The two servers are in the same subnet and have IP connectivity.
Refer to Section 2.6, Configuring MySQL Database Parameters on page 28 for more information about
SpiderNet server redundancy
4.6.3.2 Configuring SpiderNet Server Redundancy

The following procedure uses the terminology server A and server B to differentiate the two SpiderNet
servers. At various points in the procedure each will be the active and standby server.
Find It: Administration >> Server Settings >> Redundancy
To configure SpiderNet server redundancy

Step 1 If needed, issue the following command as root user on each SpiderNet servers to shut
them down:
Step 2 Issue the following command on server A to start the SpiderNet server software:
Step 3 Using the SpiderNet Java client or browser, log into SpiderNet and configure the database
redundancy settings. If needed, clear the Disable redundancy mode check box.
Step 4 In the Server 1 Settings area, fill in the Hostname and Port text boxes for the primary
server.
Step 5 In the Server 2 Settings area, fill in the Hostname and Port text boxes for the backup
server. The IP address or hostname must be in the same subnet as in Step 4.

Step 6 In the Authentication area, fill in the Username and Password text boxes when using
authentication between the primary and backup servers.
Step 7 In the Connection Settings area, enter the user-facing shared IP address in the NMS IP
Address (Floating) text box and enter the number of retry attempts and number of
seconds that the backup server attempts to log into the primary server before it assumes
the primary role in the Retries and Timeout text boxes. The IP address or hostname in the
NMS IP Address (Floating) text box must be in the same subnet as in Steps 4 and 5.
Step 8 Click Apply. A confirmation box opens informing that applying the changes requires
restarting the SpiderNet server.
Step 9 Click OK.
Step 10 Issue the following command on server A to shut it down:
Step 11 Repeat Steps 2 through 10 for server B using the same values as for server B. At the
conclusion of this procedure neither server is running.
Step 12 Issue the following command on each server to start the SpiderNet server software. The
first server to become operational will be the active server. If you have a preference for
which server should be active, start that server first and wait for it to become active before
starting the other server.
Step 13 (Optional) Log into SpiderNet at the floating IP address with the client software and
navigate to the database redundancy screen to verify the configuration.
4.6.3.3 Disabling SpiderNet the Redundancy Mode

Once a redundant server is configured, you can disable redundancy mode.
Find It: Administration >> Server Settings >> Redundancy
To disable redundancy mode

Step 14 Select the Disable redundancy mode check box and click Apply. A confirmation box
opens informing that applying the changes requires restarting the SpiderNet server.
Step 15 Click OK.
4.7 Database Settings

The SpiderNet server supports configurations employing one or two databases. In two database
configurations, the first stores security and user-specific information, the second stores application
information such as events, statistics, topology, and configuration.
The default configuration uses a single database. Changing between single- and dual-database
configuration requires a SpiderNet server reboot.

Administration
The Database Settings panel contains the following parameters, descriptions, and valid options:
Table 24: Database Settings Tab Parameters
Security Database
URL Location of the security database. Default: jdbc:mysql://localhost:3306/spidercloud
Username User name to log into the database Default: spidercloud
Password Password to log into the database. Default: spidercloud
Application Database
URL Location of the application Default: jdbc:mysql://localhost:3306/spidercloud
database.
Username User name to log into the database Default: spidercloud
Password Password to log into the database. Default: spidercloud
Use Same As Whether the system uses one or Check box. Default is cleared.
Security two databases.
4.7.1 Configuring Dual Database Settings
Find It: Administration >> Database Settings
To configure dual database settings

Step 1 In the Security Database section, fill in the URL, Username, and Password text boxes to
configure the security database parameters.
Step 2 In the Application Database section, fill in the URL, Username, and Password text
boxes to configure the application database parameters.
Step 3 Click Apply. A confirmation screen opens.
Step 4 Click OK.
Step 5 Reboot the SpiderNet server to apply the changes.
4.7.2 Configuring Single Database Settings
Find It: Administration >> Database Settings
To configure single database settings

Step 1 Select the Use Same As Security check box and click Apply. A confirmation screen
opens.
Step 2 Click OK.
Step 3 Reboot the SpiderNet server to apply the changes.

4.8 Geographical Maps

The Geographical Maps panel contains no configurable parameters. It is used to upload and remove
geographical map images as backgrounds upon which you can drag subnets and services node icons for a
literal representation of the nodes in the network. The system supports TIFF, GIF, JPEG, JPG, and PNG file
formats, with a maximum height and width of 4000 pixels.
4.8.1 Uploading a Map Image

First upload the map file, then apply it to the subnetwork. Refer to Section 5, The Tree View on page 69 for
information about applying the map to network elements.
Find It: Administration >> Geographical Maps
To upload a map image

Step 1 Click New. A file selection dialog box opens.
Step 2 Navigate to the folder on the local or network drive that contains the file.
Step 3 Select the file and click Open. The file uploads and displays in the screen along with its
dimensions.
4.8.2 Removing a Map Image
Find It: Administration >> Geographical Maps
To remove a map image

Step 1 Select the image from the screen and click Remove. The file is deleted from the system.
4.9 Performance Configuration

The Performance Configuration panel configures the polling interval for system and cell performance
counters for each services node. Note that this setting applies to all services nodes in the system.
SpiderNet polls each services node periodically and collects system and cell performance counters used to
calculate Key Performance Indicators (KPIs). By default, system counter polling is enabled and cell polling
is disabled.
The Performance Configuration tab contains the following parameters, descriptions, and valid options:
Table 25: Performance Configuration Tab Parameters
System KPIs The number of minutes between system KPI 5 through 720 (12 hours). Default is 15.
polls.
Cell KPIs The number of minutes between cell KPI polls. 5 through 720 (12 hours). Default is 15.

Administration
4.9.1 Modifying KPI Polling Intervals

Changes to the KPI polling intervals are effective upon saving the configuration. You do not need to restart
the SpiderNet server.
Find It: Administration >> Performance Configuration
To modify the KPI polling interval

Step 1 Enter the new polling interval or use the up and down buttons to set the new value.
Step 2 Click Save.
4.9.1.1 Resetting the Performance Collection Interval Screen
Find It: Administration >> Performance Configuration
To reset the performance collection interval screen

Step 1 Click Reset.
4.9.2 Configuring PM Collection on a Services Node

Enabling and disabling system and cell collection of performance management data, and clearing all
collected data is managed in the tree view. Refer to Section 5.5, Devices on page 75 for more information.

5 The Tree View

• Section 5.1, Configuring the Tree View Display on page 71
• Section 5.2, Network Topology on page 71
• Section 5.3, Subnets on page 71
• Section 5.4, Subnet Groups on page 74
• Section 5.5, Devices on page 75
• Section 5.6, Groups on page 77
• Section 5.7, Sites on page 78
The tree view provides a graphical representation of alarms, connectivity, and operational status of the
equipment in the network. Selecting an element of the tree view dynamically filters the contents of the work
area and alarm summary. The tree view offers a powerful, context sensitive series of commands and tools
activated by right-clicking on its elements.
The tree view’s flexible topology lets you logically organize the network into devices, subnets, and subnet
groups allowing you to group services nodes by location, customer, or service. Administrators can access
the configuration of any managed services node to initiate a ping, refresh, or open an SSH connection.

The Tree View
By default, the tree root is labeled Network Topology. Initially, under this root there are four elements
labeled Services Nodes, Unknown Services Nodes, Groups, and Sites that are used to manage user-
defined structures of the network. Figure 5 shows the tree view hierarchy:
Figure 5 The Tree View
Subnet groups, subnets, devices, groups, and sites each have distinct icons that appear in the tree view
and geographical map area. The icons display current equipment connectivity and alarm status. They also
display a color-coded connectivity/status indicator:
• Green check mark (): connected
• Red X: disconnected
• Red exclamation mark (!): pending configuration
• Yellow exclamation mark (!): contains a warning, info, or trace event
• Grey X: unmanaged
Select an object in the tree view, and its direct child elements display on its map in the geographical map in
the work area.
Hovering the mouse over an icon activates a context-sensitive tool tip. Tool tips include:
• Subnet Group, Subnet, Group (specific group), Site
   Name
   Status: the most severe status of the node childs.
   Devices: number of devices.
   Alarms: number of alarms per severity category.
• Device
   Name

   IP Address
   Status: as polled from the device, timeout or unmanaged
   Latitude
   Longitude
   Altitude
   Uptime
Drag and drop tree view element icons in a main subnet to change the tree structure.
5.1 Configuring the Tree View Display

You can configure the level of detail that displays in the tree view by expanding and contracting a parent
element. Expanding the parent element exposes all child elements. Contracting it hides them, displaying
only the parent element. Potential parent elements are Network Topology, ServicesNodes, a subnet, a
subnet group, Unknown ServicesNodes, Groups and Sites.
Find It: Tree View
To configure the tree view display

Step 1 Right-click on a parent element.
Step 2 Select Expand or Contract.
5.2 Network Topology

Network Topology can contain one of the following types:
• Subnet Group: a collection of subnets or other subnet groups. You can create an unlimited
number of subnet groups.
• Subnet: a logical collection of one or more services nodes. Use subnets to create a logical
hierarchy in the network topology by geographical location or subnet mask. You can create an
unlimited number of subnets.
• Devices: services nodes. A device can be a member of only one group.
• Groups: a logical collection of network equipment.
• Sites: services nodes grouped in a common location.
The Network Topology contains the following root-level right-clicking options:
• New Subnet Group: creates new subnet group child.
• Edit Subnet Group: edits the selected subnet group and selects an associated map file.
• New Subnet: creates new subnet child.
• Delete: deletes this subnet group (is enabled only if the group is empty).
• Expand: expands the selected subnet group (if expandable).
• Collapse: collapses the selected subnet group (if expanded).
5.3 Subnets
Subnets are logical collections of services nodes. Subnets contain the following right-clicking options:
• Edit Subnet: opens a screen to edit the subnet.

The Tree View
• New Services Node Device: adds a new services node.

• Delete: deletes a subnet (if empty)
• Expand: expands the selected subnet (if expandable).
• Collapse: collapses the selected subnet (if expanded).
The Add Subnet screen has contains the following parameters, descriptions, and valid options:
Table 26: Add Subnet Screen Parameters
Name Subnet group name. String
View User profiles allowed to access the subnet. View Defined view, None
permissions are defined in Section 4.1.3, Views on
page 45.
Select MAP file Location of the map file used in the geographical maps Reachable network
display. location
Enter map boundaries coordinates
Top Left Corner
Latitude Latitude of the top left corner of the map. Valid latitude
Longitude Longitude of the top left corner of the map. Valid longitude
Bottom Right Corner
Latitude Latitude of the bottom right corner of the map. Valid latitude
Longitude Longitude of the bottom right corner of the map. Valid longitude
5.3.1 Creating a Subnet
Find It: Tree View
To create a subnet
Step 1 Right-click Network Topology or subnet group and select New Subnet. The Add Subnet
screen opens.
Step 2 Enter the subnet name in the Name text box.
Step 3 Select the permissions required to view the subnet from the View drop-down list. Refer to
Section 4.1.3, Views on page 45 for more information about views.
Step 4 In the Select MAP file text box:
   Select the ... icon. The Add Image screen opens.
   Select the image from the previously uploaded image files, and click OK. Refer to
Section 4.8, Geographical Maps on page 67 for information about uploading map
images.
   In the Add Region screen, click OK.
Step 5 In the text boxes beneath the Enter map boundaries coordinates, enter the latitudes and
longitudes of the top left and bottom right corners of the map. Note that the default values
are invalid.

Step 6 Click OK.
5.3.2 Editing a Subnet
Find It: Tree View
To edit a subnet
Step 1 Right-click on the subnet and select Edit Subnet. The Edit Subnet screen opens.
Step 2 Edit as needed.
Step 3 Click OK.
5.3.3 Pre-Provisioning a Services Node

You can pre-provision a services node by entering the four identifiers in Table 27 that map to the
DeviceInfo attribute parameters in the data model:
Table 27: Tree View/Data Model Equivalents
Tree View Field Data Model Equivalent
Hardware ID SerialNumber
Customer ID CustomerID
Location ID LocationID
Cluster ID ClusterID
Find It: Tree View
To pre-provision a services node

Step 1 Right-click on the subnet and select New Services Node Device. The Create Services
Node screen opens.
Step 2 Enter the serial number in the Hardware ID text box.
Step 3 Enter the customer identifier in the Customer ID text box.
Step 4 Enter the location identifier in the Location ID text box.
Step 5 Enter the cluster identifier in the Cluster ID text box.
Step 6 Click OK.
5.3.4 Applying a Map to a Subnet

You can add a previously uploaded map to a subnet or change an existing subnet map. Refer to Section
4.8, Geographical Maps on page 67 for information about uploading map images.
Find It: Tree View

The Tree View
To apply a map to a subnet

Step 1 Right-click the ServicesNode top-level icon and select Edit Subnet. The Edit Subnet
screen opens.
Step 2 In the Select MAP file text box, select the ... icon. The Chose Image screen opens.
Step 3 Navigate to the image file on your local or network drive, select the image, and click OK.
Step 4 In the Edit Subnet screen, click OK.
5.4 Subnet Groups

A subnet group is a collection of subnets or other subnet groups. The Add Subnet screen contains the
following parameters, descriptions, and valid options:
Table 28: Add Subnet Screen Parameters
Name Subnet group name. String
View User profiles allowed to access the subnet. View Defined view
permissions are defined in Section 4.1.3, Views on
page 45.
Select MAP file Location of the map file used in the geographical maps Reachable network
display. location
Enter map boundaries coordinates
Top Left Corner
Latitude Latitude of the top left corner of the map. Valid latitude
Longitude Longitude of the top left corner of the map. Valid longitude
Bottom Right Corner
Latitude Latitude of the bottom right corner of the map. Valid latitude
Longitude Longitude of the bottom right corner of the map. Valid longitude
5.4.1 Creating a Subnet Group
Find It: Tree View
To create a subnet group

Step 1 Right-click Network Topology or subnet group and select New Subnet Group. The Add
Subnet screen opens.
Step 2 Enter the subnet group name in the Name text box.
Step 3 Select the permissions required to view the subnet group from the View drop-down list.
Refer to Section 4.1.3, Views on page 45 for more information about views.
Step 4 In the Select MAP file text box:
   Select the ... icon. The Add Image screen opens.

   Select the image from the previously uploaded image files, and click OK. Refer to
Section 4.8, Geographical Maps on page 67 for information about uploading map
images.
   In the Add Subnet screen, click OK.
Step 5 In the text boxes beneath the Enter map boundaries coordinates, enter the latitudes and
longitudes of the top left and bottom right corners of the map. SpiderNet uses the decimal
coordinate format.
Step 6 Click OK.
5.4.2 Editing a Subnet Group
Find It: Tree View
To edit a subnet group

Step 1 Right-click Network Topology or subnet group and select Edit Subnet Group. The Edit
Subnet screen opens.
Step 2 Edit as needed.
Step 3 Click OK.
5.4.3 Deleting a Subnet Group

You can delete an empty subnet group. If a subnet group contains other subnets or subnet groups, delete
those objects then follow the procedure below.
Find It: Tree View
To delete a subnet group

Step 1 Right-click the empty subnet group and select Delete. A confirmation screen opens.
Step 2 Click OK.
5.5 Devices
Devices contain the following right-clicking options. Note that some items, such as configuration and
inventory, are not available when the device is disconnected.
• ICMP Ping: sends an ICMP ping to the device.
• SNMP Ping: sends an SNMP ping to the device.
• Traceroute: performs a traceroute to the device.
• Network Settings: opens a screen for editing the services node IP address and SNMP
settings, and for adding a short note.
• Refresh: refreshes the services node connectivity status and re-synchronize its configuration.
Refreshing deletes all pending configuration changes.
• Clear Pending Configuration: deletes pending configuration changes.
• Commit Pending Configuration: applies pending configuration changes.

The Tree View
• Show Configuration: opens the configuration view of the device or brings to the front of the
screen.
• OverrideLock/Unlock Location: toggle that locks/unlocks the location of the device. xxx
• Set Node Location: opens the Set Node Location screen to define the services node
location.
• Reset Location: resets the longitude and latitude of the device to the default.
• Groups: opens a secondary menu to add this selected device to a group or to remove it from
a one.
• Sites: opens a secondary menu to add this selected device to a site or to remove it from a
one.
• Open SSH: opens an SSH session to the device for a CLI session. Refer to Section 5.5.2,
Opening a Remote Connection on page 76.
• Delete: deletes the device and device history from the system.
• Not Managed: toggle that changes the management state of the services node. Once marked
as not managed, the services nodes still displays but it will not be managed by SpiderNet.
• Collect PM: enables or disables collection of Performance Management (PM) data for this
services node.
• Collect Cell PM: opens a secondary window to select all or individual cells to enable collection
of per-cell PM data. This option is disabled if there are no defined cells.
• Clear PM: opens a confirmation screen. If Yes is selected, all system and per-cell PM data is
cleared. This option is disabled if there is no PM data to clear.
5.5.1 Configuring the Remote Connection Applications

You can open an SSH connection to a services node to initiate a CLI session after defining the applications
on your computer to use for the terminal connections.
Find It: File Menu
To configure the remote connection

Step 1 From the File Menu, select Tools >> Options >> Network.
Step 2 Click the ... button to define the path to the terminal application used for your SSH and
telnet sessions. Navigate to the folder that contains the terminal application, select the
executable that will open the program, and click Open.
Step 3 Click OK.
5.5.2 Opening a Remote Connection

Once the remote connection applications have been defined, you can open a remote SSH CLI session to a
services node.
Find It: Tree View
To open a remote connection to a services node

Step 1 Right-click the services node to connect to and select Open SSH. The defined terminal
application opens and attempts to contact the services node.

Step 2 If the services node is operational, enter your username and password. If successful, you
will be presented with the Operational Mode command prompt. For example:
admin connected from 10.12.1.230 using ssh on
admin@>
5.5.3 Deleting a Services Node

Services nodes are added at the subnet level of the tree view hierarchy. Refer to Section 5.3.3, Pre-
Provisioning a Services Node on page 73. They are deleted on the device level. Deleting a services node
removes it from the SpiderNet interface and removes all associated alarms and events.
Find It: Tree View
To delete a services node

Step 1 Right-click the services node and select Delete. A confirmation screen opens.
Step 2 Click OK.
5.6 Groups
Groups are logical collections of services nodes with some common attribute. Grouped services nodes can
be from the same geographical location, same enterprise, or any other attribute. Services nodes can be a
member of only one group. Services nodes can be members of both a group and a site. View group
members by selecting the Inventory tab and selecting the group icon in the tree view. The New Group
screen contains the following parameter, description, and valid option.
Table 29: New Group Screen Parameters
Group Name Group name String
5.6.1 Adding a Group
Find It: Tree View
To add a group
Step 1 Right-click Groups and select New Group. The Add Group screen opens.
Step 2 Enter the group name in the Group Name text box.
Step 3 Click OK.
5.6.2 Adding Services Nodes to a Group
Find It: Tree View
To add a services node to a group

Step 1 If needed, expand the subnet containing the services node icon in the tree view.

The Tree View
Step 2 Right-click the services node and select Groups >> Add to Group. A pop-up window
opens.
Step 3 Select the group from the drop-down list and click OK. The services node becomes part of
the group.
5.6.3 Moving a Services Node to a Different Group

A services node can be a member of one group. You can move a services node from one group to another.
Find It: Tree View
To move a services node from one group to another

Step 2 Right-click the services node and select Groups >> Add to Group. A confirmation screen
opens.
Step 3 Select the group from the drop-down list and click OK. The services node becomes part of
the group.
5.6.4 Removing a Services Node from a Group
Find It: Tree View
To remove a services node from a group

Step 2 Right-click the services node and select Groups >> Remove from Group.
5.6.5 Deleting a Group
Find It: Tree View
To delete a group
Step 1 Right-click on the group and select Delete. A confirmation screen opens.
Step 2 Click OK.
5.7 Sites
Sites are logical collections of services nodes in the same location. Services nodes can be a member of
only one site. Services nodes can be members of both a group and a site. View site members by selecting

the Inventory tab and selecting the site icon in the tree view. The Create New Site screen contains the
following parameters, descriptions, and valid options:
Table 30: Create New Site Screen Parameters
Name Site name. String
Common Name Natural language name of the site. String
Address The address of the site. String
City, State/Province Location of the site. String
Country Country of the site. Drop down list
Contact Name Name of the person to contact regarding this site. String
Contact Number Telephone number of the contact. Valid phone number, commas
permitted
Notes Additional text notes. String
Latitude Latitude of the site. Valid latitude
Longitude Longitude of the site. Valid longitude
5.7.1 Adding a Site
Find It: Tree View
To add a site
Step 1 Right-click Sites and select New Site. The Create New Site screen opens.
Step 2 Enter the site characteristics in the text boxes.
Step 3 Click OK.
5.7.2 Adding a Services Node to a Site
Find It: Tree View
To add a services node to a site

Step 1 Right-click the services node icon and select Sites >> Add to Site. A pop-up window
opens.
Step 2 Select a site from the drop-down list and click OK.
5.7.3 Moving a Services Node to a Different Site

A services node can be a member of one site. You can move a services node from one site to another.

The Tree View
Find It: Tree View
To move a services node from one site to another

Step 2 Right-click the services node and select Sites >> Add to Site. The Add to Site window
opens.
Step 3 Select the site from the drop-down list and click OK. The services node becomes part of
the site.
5.7.4 Removing a Services Node from a Site
Find It: Tree View
To remove a services node from a site

Step 2 Right-click the services node and select Sites >> Remove from Site.
5.7.5 Editing a Site
Find It: Tree View
To edit a site
Step 1 Right-click the site and select Edit Site. The EditSite window opens.
Step 2 Edit the parameter text boxes as needed and click OK.
5.7.6 Deleting a Site
Find It: Tree View
To delete a site
Step 1 Right-click on the site and select Delete. A confirmation screen opens.
Step 2 Click OK.

6 The Work Area
The work area in the Network Control tab is the primary workspace of the SpiderNet system. It contains
panels, screens, and tabs for configuring and surveilling the services nodes managed by the system. The
work area contains the following panels:
• 6.1 Geographical Maps on page 81
• 6.2 Inventory on page 82
• 6.3 Configuration on page 85
• 6.4 Configuration Templates on page 104
• 6.5 Scheduled Tasks on page 106
6.1 Geographical Maps

The Geographical Maps panel manages image files intended as a graphical representation of the different
levels of the SpiderCloud network hierarchy. The network topology, subnet groups, and subnets can each
be associated with a separate map reflecting their physical location in the network. Maps are uploaded in
the Administration tab and associated with the network topology, subnet groups, and subnets when they
are created or edited. Refer to Section 4.8, Geographical Maps on page 67 for information about uploading
map files. Table 31 shows the Geographic Map panel buttons:
Table 31: Geographical Map Buttons
Button Button Function
Zooms in
Zooms out
Resets view to the default size
Allows selection of elements
Allows map movement
Return icons to the last saved location
Saves the current view
Displays the longitude and latitude of the mouse when over the map or N/A when the cursor is
elsewhere on the screen
When the network topology is edited, or subnet groups and subnets are created or edited, they can be
associated with maps that can optionally be assigned geographical coordinates as discussed in Section
5.4.2, Editing a Subnet Group on page 75 and Section 5.3.1, Creating a Subnet on page 72.

The Work Area
Subnet groups, subnets, devices, and groups each have distinct icons that appear in the tree view and
geographical map area. Select an object in the tree view, and its direct child elements display on its map.
For example, select network topology and its map displays the icons for ServicesNodes, Unknown
Services Nodes, subnet groups, and subnets that are not in groups. Select a subnet group and its map
displays icons of the subnets in that group. Select a subnet and its map displays its services nodes.
Newly discovered or created services node icons appear in a section of right side of the screen as show in
Figure 6. You can drag and drop an icon onto the appropriate location of the map file. When the mouse
cursor hovers over a map, the longitude and latitude display on the bottom of the map panel next to the
Save icon. Use this information to accurately place the map icons. When icons are in the proper relative
position, click the Save icon and OK in the confirmation screen to save this setting.
Figure 6 No Location Services Nodes
Right-clicking on an icon in the geographical map opens exactly the same menu options as in the tree
view. Refer to Section 5.5, Devices on page 75.
6.2 Inventory
The Inventory panel contains seven tabs near the bottom of the interface that are read-only
representations of the configuration of equipment in the SpiderNet network. The contents of the contents of
the Inventory panels dynamically displays content relevant to the icon selected in the tree view. The
inventory sections contains the following tabs:
• Services Nodes
• IP Interfaces
• Radio Nodes
• Cell
• IntraFreqCells
• InterFreqCells
• InterRATGSMCells

Table 32 shows the buttons in the Inventory panel:

Table 32: Inventory Panel Buttons
Opens the Print dialog box
Opens the Export to CSV dialog box
Opens the Choose Columns dialog box to select the columns to display in the report
The number of elements in each category display in parenthesis to the right of the tab name. Table 33 and
Table 34 show the contents of each inventory tab:
Table 33: Inventory Panel Contents (1 of 2)
Services Nodes IP Interfaces Radio Nodes Cell
Device Device Device Device
index index index index
Node Status IP Address Enabled Enabled
Configuration Status Node Status Name Name
Last Inform EthernetID Description Description
Uptime Description Status CID
Version LANDeviceID EthernetID CellID
Serial # VLANID Radio Node IPAddress Status
Model # BytesSent Outer IP Address RN/Radio
Part # BytesReceived Radio 1 Band PSCInUse
Location PacketsSent Radio 1 Status MaxTxPwrInUse
Contact PacketsReceived Serial # ModeInUse
CLID ConfState
LNID RLs
CNID
Table 34: Inventory Panel Contents (2 of 2)

IntraFreqCells InterFreqCells InterRATGSMCells
Device Device Device
cellid cellid cellid
index index index
PLMNID PLMNID PLMNID
RNCID RNCID LAC

The Work Area
Table 34: Inventory Panel Contents (2 of 2) (continued)

IntraFreqCells InterFreqCells InterRATGSMCells
CustomerID CustomerID bsic
LAC LAC ci
RAC RAC bandIndicator
UAR UAR bcCharFcn
PCPICHScramblingCode UARFCNDL
UARFCNUL
PCPICHScramblingCode
6.2.1 Selecting the Display Columns

Inventory panel displays are user-configurable. You can select which columns to display and which to
hide.
Find It: Network Control >> Inventory
To select the display columns

Step 1 Click the Choose Columns button near the top right of the Inventory panel or right-click a
column heading. The Choose Columns dialog box opens.
Step 2 From the check boxes on the left, check the boxes of the columns to display and clear the
boxes of the columns to hide.
Step 3 Click OK.
6.2.2 Adjusting Column Widths

When the column content exceeds the size of the column, you can adjust the width to view all of the
content.
To adjust the column width

Step 1 Place your cursor to the right of the column heading to resize. The cursor changes to a
two-sided horizontal arrow.
Step 2 Click and hold down the mouse button and adjust the column width as needed.
6.2.3 Sorting Inventory Screen Displays

You can sort alarms and events by any one or more columns in ascending or descending order.

To sort the inventory screen display

Step 1 Click the column heading of the parameter to sort on. The display sorts by this column in
ascending order. An upwardly pointing triangular icon appears in the column heading. Click
the column head again to sort in descending order. The triangular icon points downward.
Step 2 To perform a secondary sort, control click the second column heading to achieve a
secondary sort in ascending order. Control click the column heading again to sort in
descending order.
Step 3 Repeat Step 2 any number of times on other columns to add additional sorting levels.
To clear inventory display sorting

Step 1 Click the heading of the column being sorted upon until the sorting clears. The triangular
icon disappears.
6.2.4 Saving the Inventory Data to File

You can save the contents of the Inventory panel to a CSV file for off-box computation and analysis. If the
current view has inventory columns hidden, the exported file removes those columns as well. The sort
order does not reflect in the file output. When saving the file, you do not need to specify the .csv extension.
When omitted, the extension is automatically added to the file.
To save inventory data to a file

Step 1 From the inventory button bar, click the Export to CSV button. The Export to CSV dialog
box opens.
Step 3 Click Yes to save the file in CSV format.
6.2.5 Printing Inventory Screen Displays

You can print the contents of the open Inventory screen display. If the current view has inventory data
columns hidden, only the displayed results print.
To print inventory screen displays

Step 1 From the inventory button bar, click the Print button. The Print dialog box opens.
Step 3 Click Print.
6.3 Configuration
The Configuration panel displays the various configuration states of the services node selected in the tree
view. Enable up to two configuration screens by right-clicking a services node and selecting Show
Configuration. Users with proper permissions can modify system parameters and add or delete system

The Work Area
objects. Aligning two configuration screens side-by-side enables quick and accurate copying and pasting
of configurations between two services nodes.
The configuration screen contains the following five tabs:
• Equipment
• IP (with Interfaces, Forwarding Table, DHCP, and QoS sub-tabs)
• UMTS (with Core Network, RAN, and Cell sub-tabs)
• System Management
• Advanced
The Equipment and IP tabs in the Configuration panel contain the following buttons:
Table 35: Configuration Panel Buttons
Adds an object
Deletes an object
6.3.1 Modifying Configuration Attributes

The Configuration panel is primarily a read-only display of device attributes. However some parameters
can be modified in these panels.
Find It: Network Control >> Configuration
To modify a configuration attribute

Step 1 Edit the attribute as needed.
Step 2 Click Save.
6.3.2 Refreshing Configuration Screen Displays

Configuration panels are static, they do not reflect any changes to the device after the screen initially
displays. You can refresh the screen to view current attributes.
Refreshing the screen erases any unsaved configuration changes. To retain configuration
changes, save the configuration before refreshing the screen.
Note
Find It: Network Control >> Configuration
To refresh the configuration screen display

Step 1 Click Refresh. The Refresh screen opens.
Step 2 Click Yes to refresh the screen and discard configuration changes. Click No to continue
configuring the system or to save the configuration before refreshing.

6.3.3 The Equipment Tab

The Equipment tab displays information about the radio nodes it controls. The left portion of the screen
displays radio nodes and any radios they contain. The Equipment tab contains the following parameters,
descriptions, and valid options:
Table 36: Equipment Tab Parameters
RadioNode
Name Radio node name. Regex(16). Valid characters:
^$|^[0-9a-zA-Z]([0-9a-zA-Z_-])*
Description Radio node description. String(128)
Enable Whether or not the radio node is enabled. Check box. Default is checked.
Ethernet ID The Ethernet ID of this radio node, it uniquely Regex(17:17). Valid characters:
identifies the radio node in the system.
([0-9a-fA-F][0-9a-fA-F]:){5}([0-9a-fA-
EthernetID must not be 00:00:00:00:00:00 if F][0-9a-fA-F])
Enable is checked.
Oper State The operational state of the radio node. Valid options:
IS-BUSY
IS-DEGRADED
IS-EMERGENCY
IS-IDLE
IS-LOCKED
IS-NETMON
IS-NORMAL
IS-STANDBY
OOS-AUTHENTICATING
OOS-CFGMISMATCH
OOS-DEPROV
OOS-DIAG
OOS-DISABLED
OOS-FAULT
OOS-INDETERMINATE
OOS-INHERITED
OOS-INIT
OOS-NOTPRESENT
OOS-PROVING
OOS-SWMISMATCH
OOS-SYNCING
OOS-UNPROVISIONED
UNKNOWN (Unknown value)
IP Address Radio node IP address. Valid IP address
Outer IP Radio node outer IP address. Valid IP address
Address

The Work Area
Table 36: Equipment Tab Parameters (continued)

Arrive Time Date and time radio node joined the system in Format: yyyy-mmddThh:
ISO 8601 format.
mm:ssZ
Radio
Enable Whether or not the radio is enabled. Check box. Default is checked.
Band Radio node operating band. not-available (UMTS Band value is not
available)
umts-band-I (UMTS Band I)
umts-band-IV (UMTS Band IV)
umts-band-II (UMTS Band II)
Actual Band Actual radio node operating band. not-available (UMTS Band value is not
available)
umts-band-I (UMTS Band I)
umts-band-IV (UMTS Band IV)
umts-band-II (UMTS Band II)
Oper State Operational state of the radio. See Oper State above
6.3.3.1 Creating a Radio Node
Find It: Network Control >> Configuration >> Equipment
To create a radio node

Step 1 Select the add button. A screen opens.
Step 2 Enter the radio index number and click OK.
Step 3 Complete the form on the right of the screen and click Save.
6.3.3.2 Deleting a Radio Node
To delete a radio node

Step 1 On the left side of the screen, right-click the radio node or select the radio node and click
the delete button, then select Delete RadioNode. A screen opens. A confirmation screen
opens.
Step 2 Click Yes.

6.3.3.3 Creating a Radio
To create a radio
Step 1 On the left side of the screen, right-click the radio node or select the radio node and click
add button, then select Add Radio. A screen opens.
Step 2 Enter the radio index number and click OK.
6.3.3.4 Deleting a Radio
To delete a radio
Step 1 On the left side of the screen, right-click the radio or select the radio and click the delete
button, then select Delete Radio. A confirmation screen opens.
Step 2 Click Yes.
6.3.4 The IP Tab

The services node has eight physical Ethernet ports that are mapped to LANDevice index numbers 1
through 8 in the SpiderCloud data model. Ethernet ports can support multiple IP interfaces. The system
supports up to 1024 logical IP interfaces. The IPInterface index numbers must be unique within each port,
but can be reused by different ports on the same services node.
The IP/Interfaces tab defines the configuration of the services node Ethernet ports and their IP interfaces.
It contains the name, status, maximum bitrate, duplex mode, operational state, and MAC address of the
physical port and IP address, subnet mask. VLAN identifier, forwarding group, operational state, and
DHCP server status of the logical IP interface.
The IP/Interfaces tab contains the following parameters, descriptions, and valid options:
Table 37: IP/Interfaces Tab Parameters
LANDevice
LANDevice index Index number of the Ethernet port. Integer. Valid options: 1
through 8
Enable Whether or not the Ethernet port is enabled. Check box. Default is
checked.
Name Name of the LAN interface. String(16)
Status LAN device status. The Error value MAY be used Up
by the system to indicate a locally defined error
NoLink
condition.
Error
Disabled

The Work Area
Table 37: IP/Interfaces Tab Parameters (continued)

MaxBitRate The maximum upstream and downstream bit rate Enum. 100 or 1000
available to this connection. The units of
MaxBitRate are in Mbits/sec.
Duplex The duplex mode available to this connection. Boolean. Half or Full
OperState Operational state of the LAN port. IS-BUSY
IS-DEGRADED
IS-EMERGENCY
IS-IDLE
IS-LOCKED
IS-NETMON
IS-NORMAL
IS-STANDBY
OOS-AUTHENTICATING
OOS-CFGMISMATCH
OOS-DEPROV
OOS-DIAG
OOS-DISABLED
OOS-FAULT
OOS-INDETERMINATE
OOS-INHERITED
OOS-INIT
OOS-NOTPRESENT
OOS-PROVING
OOS-SWMISMATCH
OOS-SYNCING
OOS-UNPROVISIONED
UNKNOWN (Unknown
value)
MACAddress MAC address associated with the IP interface Valid MAC address in the
modeled by this LAN device instance. format of six pairs of
hexadecimal characters
separated by colons
IPInterface
IPInterface index Index number of the IP interface. Integer. Valid options: 1
through 4294967295
Enable Whether or not the IP interface is enabled. Check box. Default is
checked.
Description IP interface description. String
IPInterfaceIPAddress LAN port IP address. Valid IP address
IPInterfaceSubnetMask LAN port subnet mask. Valid subnet mask
VLANID The virtual LAN identifier for this interface. Integer

Table 37: IP/Interfaces Tab Parameters (continued)

ForwardingGroupIndex IP address domain that this route exists in. If the Unsigned integer
referenced object is deleted, the parameter value
MUST be set to 0.
OperState Operational state of the LAN interface. See OperState above
DHCPServerEnable Whether or not the DHCP server is enabled. Check box. Default is
checked.
EgressQosProfile The egress quality of service profile used to rate- Unsigned integer. Valid
limit data transmission on the IP interface. options: 0, 2-1000
6.3.4.1 Configuring an Ethernet Port

The services node contains eight Ethernet ports. Ports 1 (core connection), 2 (radio nodes), and 4 (local
configuration interface) are enabled by default. Additional ports must be manually configured.
Find It: Network Control >> Configuration >> IP >> Interfaces
To configure an Ethernet port

Step 1 Select the add button. A screen opens.
Step 2 Enter the index number of the LAN port and click OK.
6.3.4.2 Deleting an Ethernet Port
To delete an Ethernet port

Step 1 On the left side of the screen, right-click the Ethernet port or select the port and click the
delete button, then select Delete LANDevice. A confirmation screen opens.
Step 2 Click Yes.
6.3.4.3 Creating an IP Interface
To create an IP interface
Step 1 Select the Ethernet port and click the add button. A screen opens.
Step 2 Enter the index number of the IP interface and click OK.
Step 3 (Optional) Select the DHCPServerEnable check box to enable a DHCP server on the
interface.

The Work Area
6.3.4.4 Deleting an IP Interface
Step 1 On the left side of the screen, right-click the IP interface or select the interface and click
the delete button, then select Delete IPInterface. A confirmation screen opens.
Step 2 Click Yes.
6.3.4.5 Creating a Forwarding Table

The forwarding table is a collection of static routes defined by the system administrator. Typical static
routes are defined to the security gateway of the mobile core network and an enterprise router for local
switching. The index number is an arbitrary number of a static route.
The IP/Forwarding Table tab contains the following parameters, descriptions, and valid options:
Table 38: IP/Forwarding Table Tab Parameters
Index The index number in the forwarding table for this static Unsigned integer
route.
Enable Whether or not the IP Layer 3 forwarding is enabled. Check box. Default
is checked.
Description Description of the forwarding group. String(70)
StaticRoute Whether or not this is a static route. Check box. Default
is checked.
DestIPAddress Destination IP address. Value of "0.0.0.0" indicates no Valid IP address
destination address is specified. A Forwarding table
entry for which DestIPAddress and DestSubnetMask
are both "" or "0.0.0.0" is a default route.
DestSubnetMask Destination subnet mask. Value of "0.0.0.0" indicates no Valid subnet mask
destination subnet mask is specified. If a destination
subnet mask is specified, the DestSubnetMask is
ANDed with the destination address before comparing
with the DestIPAddress. Otherwise, the full destination
address is used as is.
A Forwarding table entry for which DestIPAddress and
DestSubnetMask are both "" or "0.0.0.0" is a default
route.
GatewayIPAddress Gateway IP address. Only one of GatewayIPAddress Valid IP address
and Interface should be configured for a route.
If both are configured, GatewayIPAddress and Interface
must be consistent with each other.
LANDevice Together with IPInterface, specifies the egress interface Integer
associated with this route. If a LANDevice and
IPInterface combination are specified, they must be
consistent GatewayIPAddress if specified.

Table 38: IP/Forwarding Table Tab Parameters (continued)

IPInterface Together with LANDevice, specifies the egress interface Integer
associated with this route. If a LANDevice and
IPInterface combination are specified, they must be
consistent with GatewayIPAddress if specified.
ForwardingGroupIndex IP address domain that this route exists in. Unsigned integer
Find It: Network Control >> Configuration >> IP >> Forwarding Table
To create a forwarding table

Step 1 Right-click the screen and select Add Forwarding or select the add button. A screen
opens.
Step 2 Enter the index number of the forwarding table and click OK.
Step 3 Complete the editable fields in the form on the screen and click Save.
6.3.4.6 Deleting a Forwarding Table
Find It: Network Control >> Configuration >> IP >> Forwarding Table
To delete a forwarding table

Step 1 Right-click the forwarding table and select Delete Forwarding or select forwarding table,
then click the delete button. A confirmation screen opens.
Step 2 Click Yes.
6.3.4.7 Creating a DHCP Server Subnet

The SpiderNet system ships with two preconfigured DHCP server subnets. The subnet on the 172.30.30.0
domain is to assign IP addresses to radio nodes to Ethernet port 2. The subnet on the 192.168.168.0
domain is to assign an IP address to a laptop for initial configuration with the LCI on Ethernetthe
management port.
The IP/DHCP tab is typically a read-only view of the attributes of the DHCP subnets, and can also be used
to enable and disable DCHP servers, to change the range of IP addresses to avoid network conflict, or to
assign radio nodes to a different port.
The IP/DHCP tab contains the following parameters, descriptions, and valid options:
Table 39: IP/DHCP Tab Parameters
Index DCHP ID entry. Positive integer. Valid
options: 1 through
4294967295
Enable Whether or not the DHCP server is enabled. Check box. Default.is
checked.

The Work Area
Table 39: IP/DHCP Tab Parameters (continued)

Prefix The prefix of the subnet from which the DHCP Valid IP address
server is receiving requests.
Prefix must not be 0.0.0.0 if Enable is true.
Netmask The subnet mask of the subnet from which the Valid IP address
DHCP server is receiving requests.
Netmask must not be 0.0.0.0 if Enable is true.
Minimum IP Address Minimum IP address in address subnet. Valid IP address
MinimumIPAddress must not be 0.0.0.0 if Enable is
true.
Maximum IP Address Maximum IP address in address subnet. Valid IP address
MaximumIPAddress must not be 0.0.0.0 if Enable is
true.
IP Routers IP addresses of the routers to return to the client. Valid IP address
Find It: Network Control >> Configuration >> IP >> DHCP
To create a DHCP Server Subnet

Step 1 Right-click the screen and select Add DHCP or select the add button. A pop-up screen
opens.
Step 2 (Optional) Select the Enable check box to enable the DHCP server.
Step 3 Enter the index number of the DHCP server subnet and click OK.
Step 4 Enter the prefix, subnet mask, and minimum and maximum assignable IP addresses in the
form on the screen and click Save.
Step 5 Enable the DHCP server on an Ethernet interface. Refer to Section 6.3.4.3, Creating an IP
Interface on page 91.
6.3.4.8 Deleting a DHCP
Find It: Network Control >> Configuration >> IP >> DHCP
To delete a DHCP Server Subnet

Step 1 Right-click the DHCP subnet and select Delete DHCP or select the DHCP subnet, then
click the delete button. A confirmation screen opens.
Step 2 Click Yes.

6.3.4.9 Creating a QoS Profile

If the SpiderNet installation requires a rate limit on the backhaul connection you can create and enable a
Quality of Service (QoS) profile that applies that a limit between 2 Mbps and 1 Gbps on the egress traffic
from that IP interface.
SpiderCloud Wireless strongly recommends not changing queue weights unless instructed to
do so by technical support.
Note
The QoS panel contains the following parameters, descriptions, and valid options:
Table 40: QoS Panel Parameters
Index Egress Quality of Service (QoS) index number. Unsigned integer
ProfileEnable Whether or not the profile is enabled. Check box. Default is
checked.
Description QoS description. String
RateLimit Maximum transmit bit-rate in megabytes per second 0, 2 through 1000
allowed on an IP interface on which this egress QoS
profile is applied. A value of 0 (zero) means that rate
limiting is not present.
Find It: Network Control >> Configuration >> IP >> QoS
To create a QoS Profile

Step 1 Right-click the screen and select Add QoS or select the add button. A pop-up screen
opens.
Step 2 Enter the index number of the QoS Profile and click OK.
Step 3 (Optional) Select the Enable check box to enable the QoS profile.
Step 4 Enter the description and rate limit in the form on the screen and click Save.
Step 5 To enable the Qos profile, enter the Advanced tab, navigate to the following path:
LANDevice 1 LANHostConfigManagement IPInterface 1
select the EgressQoSProfile Enable check box and click Save. Refer to Section 6.3.7,
The Advanced Tab on page 103 for information about using the Advanced tab.
6.3.4.10 Deleting a QoS Profile
Find It: Network Control >> Configuration >> IP >> QoS
To delete a QoS Profile

Step 1 Right-click the Qos profile and select Delete QoS or select the profile, then click the delete
button. A confirmation screen opens.

The Work Area
Step 2 Click Yes.
6.3.5 The UMTS Tab

The UMTS tab contains the Core Network, RAN, and Cell sub-tabs. The Core tab configures parameters
for the Iuh or Iu/IP connection to the mobile core network. You can select the connection protocol and its
connection attributes. Note that the CS Domain and PS Domain sections apply only to Iu/IP connections.
The RAN tab configures radio access network and RF parameters that are mostly provided by the mobile
operator. These parameters should be fairly consistent across deployments. This tab also contains the
REM scan parameters.
The Cell contains parameters for provisioned cells. Select a cell from the list on the left and its configurable
attributes and operating state and maximum transmit power display in the main screen. Consult this screen
for to view cell configuration when troubleshooting.
Find It: Network Control >> Configuration >> UMTS

The UMTS/Core Network tab contains the following parameters, descriptions, and valid options:
Table 41: UMTS/Core Network Tab Parameters
CN Protocol The protocol for interacting with the mobile core Drop down list. Valid
network. options:
Pico, Iu/IP, Iuh
FAPGW Port Port number of Iuh gateway used for initial Iuh Unsigned integer[65535]
SCTP contact.
FAPGW Server 1 First Iuh gateway the services node attempts to String(64)
establish connection with. Either hostname or IP
address.
FAP Local Port The local port being used for SCTP association Unsigned integer[65535]
with the Iuh gateway.
CN Connection Enable Whether or not to enable connection to the core Check box. Default is
network. checked.
SCCP Address Type Type of Signalling Connection Control Part Enum. ITU or ANSI
(SCCP).
CN IP Address The IP address of SCTP endpoint of the core Valid IP address
device.
CN IP Port The port number of SCTP endpoint of the core Unsigned integer[65535]
device.
RNC IP Address The IP address of SCTP endpoint being used by Valid IP address
the FAP.
RNC IP Port The port of SCTP endpoint being used by the Unsigned integer[65535]
FAP.
RNCM3UAPSP Type Peer Server Process (PSP) on the FAP. IPSP or ASP
RNCM2UAPSP ID The M3UA Application Server Process (ASP) Unsigned integer
Identifier of the FAP.
M3UA Routing Context The M3UA Routing Context value. Unsigned integer

Table 41: UMTS/Core Network Tab Parameters (continued)

CNM3UANA The M3UA Network Appearance of the core Unsigned integer
device.
CNM3UANA Included Whether or not the M3UA Network Appearance Check box. Default is
should be included in messages to the peer. checked.
OPC Indicates the SCCP point code of the core Unsigned integer
device.
DPC Indicates the SCCP point code of the FAP. Unsigned integer
Connection State Connection state of SCTP for this domain. Enumeration. Valid
options: None, Idle,
Connecting, Connected.
SCCP State The state of SCCP for this domain. Enumeration. Valid
Connecting, Connected
M3UA State The state of M3UA for this domain. Enumeration. Valid
SCTP State The state of SCTP for this domain. Enumeration. Valid
Find It: Network Control >> Configuration >> UMTS >> RAN
The UMTS/RAN tab contains the following parameters, descriptions, and valid options:
Table 42: UMTS/RAN Tab Parameters
PLMN Type Type of Public Land Mobile Network GSM-MAP or ANSI-41
(PLMN).
SAC Service Area Code (SAC). Unsigned integer[0:65535]
PLMN ID The Mobile Country Code (MCC) and String(6)
Mobile Network Code (MNC).
LACRAC Location Area Code (LAC) and Routing String(256) in the format:
Area Code (RAC). LAC can be up to 5
[<LAC or LACrange>':'<RAC or
numerical characters, RAC can be up to 3
RACrange>]
numerical characters.
CN ID Core network identifier. Unsigned integer
RNC ID Radio Network Controller ID. Unsigned integer[0:4095]
Cell ID Cell identifier in the macro network. Positive integer. Valid options:
Reference 3GPP-TS.25.331 Section
1 through 268435455,
10.3.2.2.
4294967295

The Work Area
Table 42: UMTS/RAN Tab Parameters (continued)

UARFCNDL UTRA Absolute Radio Frequency Channel Unsigned Integer. Valid options:
Number (UARFCN) down link in an FDD
0, 412, 437, 462, 487, 512, 537,
mode cell.
562, 587, 612, 637, 662, 687,
1537 through 1738, 1887, 1912,
1937, 1962, 1987, 2012, 2037,
2062, 2087, 9662 through 9938,
10562 through 10838
NeighborListLockEnable Whether or not the neighbor list of all cells Check box. Default is cleared.
in the system are locked.
Primary Scrambling Cell primary scrambling code. Unsigned integer {1:50}. Valid
Code options: 0 through 511
PrimaryScramblingCode Whether or not the primary scrambling Check box. Default is cleared.
LockEnable codes for all cells in the system are locked.
Max FAP Tx Power The maximum transmission power allowed Integer. Valid options: -100..200
on the cell.
MaxFAPTxPowerLockE Whether or not the maximum transmission Check box. Default is cleared.
nable power for all cells in the system are locked.
Inter Freq Hard Whether or not Inter-Frequency Hard Check box. Default is checked.
Handover Enable Handover is enabled.
RFLockEnable Whether or not system-wide radio Check box. Default is cleared.
frequency parameters are locked.
Intra Freq Hard Whether or not Intra-Frequency Hard Check box. Default is cleared.
Handover Enable Handover is enabled.
Inter RAT Freq Hard Whether or not Inter-RAT Hard Handover Check box. Default is checked.
Handover Enable is enabled.
Self Config Alternate Alternate cell primary scrambling code. Unsigned integer {1:50}. Valid
PSC options: 0 through 511
Scan Periodically Whether or not to schedule a periodic Check box. Default is cleared.
REM scan.
Periodic Interval Frequency of periodic REM scan in Unsigned integer[1:31536000]
seconds.
Periodic Time Time of first periodic REM scan in ISO Format:
8601 format.
yyyy-mm-ddThh:mm:ssZ
UARFCNDLList The downlink UTRA Absolute Radio Unsigned Integer. Valid options:
Frequency Channel Number (UARFCN)
0, 412, 437, 462, 487, 512, 537,
down link.
562, 587, 612, 637, 662, 687,
1537 through 1738, 1887, 1912,
1937, 1962, 1987, 2012, 2037,
2062, 2087, 9662 through 9938,
10562 through 10838

Table 42: UMTS/RAN Tab Parameters (continued)

Periodic Interval Frequency of scan for GSM neighbors in Unsigned integer[1:31536000]
seconds.
REM Band List The GSM band to scan. Enum{}. Valid options:
DCS1800, E-GSM900, GSM450,
GSM480, GSM710, GSM750,
GSM850, GSM900, PCS1900,
P-GSM900, R-GSM900,
T-GSM380, T-GSM410,
T-GSM810, T-GSM900
ARF CN List The GSM Absolute Radio Frequency Unsigned integert[1023]{128}
Channel Numbers (ARFCN) to scan.
UMTSExIntraFreqREM Whether or not to enable scanning for Check box. Default is checked.
ScanEnable external intra-frequency neighbors during
REM scan.
UMTSExtInterFreqREM Whether or not to enable scanning for Check box. Default is checked.
ScanEnable external inter--frequency neighbors during
REM scan.
GSMREMSCanEnable Whether or not to enable scanning for Check box. Default is checked.
GSM neighbors during REM scan.
InternalTopologyDiscove Whether or not to enable scanning the Check box. Default is checked.
ryEnable internal topology during REM scan.
Max Num Cell The maximum number of UEs per cell that Unsigned integer[0:100]
FACHUEs can be in CELL_FACH state
simultaneously.
Find It: Network Control >> Configuration >> UMTS >> Cell
The UMTS/Cell tab contains the following parameters, descriptions, and valid options:
Table 43: UMTS/Cell Tab Parameters
Enable Whether or not to enable this cell. Check box. Default is checked.
Description Description of this cell. String(128)
Radio Node Number of the radio node that Unsigned Integer
contains this cell.
Must not be 0 if Enable is true.
Radio Number of the radio that host the o or 1. Default is 1.
cell. Must not be 0 if Enable is
selected.
Conf State Configured state of the cell. See Oper State

The Work Area
Table 43: UMTS/Cell Tab Parameters (continued)

Oper State Operational state of the cell. IS-BUSY
IS-DEGRADED
IS-EMERGENCY
IS-IDLE
IS-LOCKED
IS-NETMON
IS-NORMAL
IS-STANDBY
OOS-AUTHENTICATING
OOS-CFGMISMATCH
OOS-DEPROV
OOS-DIAG
OOS-DISABLED
OOS-FAULT
OOS-INDETERMINATE
OOS-INHERITED
OOS-INIT
OOS-NOTPRESENT
OOS-PROVING
OOS-SWMISMATCH
OOS-SYNCING
OOS-UNPROVISIONED
UNKNOWN (Unknown value)
Prov State Provisioned state of the cell. See Oper State
CellID Cell identifier in the macro network. Positive integer. Valid options:
Reference 3GPP-TS.25.331
1 through 268435455, 4294967295
Section 10.3.2.2.
UCID UTRA Absolute Radio Frequency Unsigned Integer. Valid options:
Channel Number (UARFCN) in an
0, 412, 437, 462, 487, 512, 537,
FDD mode cell.
562, 587, 612, 637, 662, 687, 1537
through 1738, 1887, 1912, 1937,
1962, 1987, 2012, 2037, 2062,
2087, 9662 through 9938, 10562
through 10838
UARFCN DL In Use UTRA Absolute Radio Frequency Unsigned Integer. Valid options:
Channel Number (UARFCN) in use
0, 412, 437, 462, 487, 512, 537,
in the downlink by the cell.
562, 587, 612, 637, 662, 687, 1537
through 1738, 1887, 1912, 1937,
1962, 1987, 2012, 2037, 2062,
2087, 9662 through 9938, 10562
through 10838


UARFCNUL In Use UTRA Absolute Radio Frequency Unsigned Integer. Valid options:
Channel Number (UARFCN) in use
0, 412, 437, 462, 487, 512, 537,
in the uplink by the cell.
562, 587, 612, 637, 662, 687, 1537
through 1738, 1887, 1912, 1937,
1962, 1987, 2012, 2037, 2062,
2087, 9662 through 9938, 10562
through 10838
PrimaryScramblingCodeCon The cell configured primary Unsigned integer {1:50}. Valid
figured scrambling code. options: 0 through 511.
PrimaryScramblingCodeLoc Whether or not the primary Check box. Default is cleared.
kEnable scrambling code is locked during
REM scan.
MaxFAPTxPowerConfigured The configured maximum power Integer. Valid options: -100..200.
transmitted by this cell in units of
0.1 dBm.
MaxFAPTxPowerLockEnabl Whether or not maximum power Check box. Default is cleared.
e transmitted levels are locked during
REM scan.
RFLockEnable Whether or not all RF parameters Check box. Default is cleared.
are locked during REM scan.
NeighborListLockEnable Whether or not neighbor lists are Check box. Default is cleared.
locked during REM scan.
DLCFreq In Use Absolute center frequency of the Unsigned integer
DL UARFCN in use by the cell in
units of 0.1 MHz.
ULCFreq In Use Absolute center frequency of the Unsigned integer
UL UARFCN in use by the cell in
units of 0.1 MHz.
Use Self Config Alternate Whether or not to use an alternate Check box. Default is cleared.
PSC primary scrambling code for this
cell.
Mode In Use Current RF management mode. Enum. Valid options:
UMTSNodeB (Operational mode)
UMTSNetmon (UMTS scan mode)
GSMNetmon (GSM scan mode)
UARFCNDL UTRA Absolute Radio Frequency Unsigned Integer. Valid options:
Channel Number (UARFCN) down
0, 412, 437, 462, 487, 512, 537,
link in an FDD mode cell.
562, 587, 612, 637, 662, 687, 1537
through 1738, 1887, 1912, 1937,
1962, 1987, 2012, 2037, 2062,
2087, 9662 through 9938, 10562
through 10838

The Work Area

Max FAP Tx Power The maximum power transmitted by Integer. Valid options: -100..200.
this cell in units of 0.1 dBm.
Primary Scrambling Code Cell primary scrambling code. Unsigned integer {1:50}. Valid
options: 0 through 511.
ConfiguredCellMode Configured mode of the cell. See Oper State above
6.3.6 The System Management Tab

The System Management tab contains information about the specific services node such as name,
location, description and contact name, and also information about its connection to the SpiderNet server.
It also contains Network Time Protocol (NTP) server and CLI session management settings.
Find It: Network Control >> Configuration >> System Management

The System Management tab contains the following parameters, descriptions, and valid options:
Table 44: System Management Tab Parameters
Name Services node name. Regex(24). Valid
characters:
^$|^([0-9a-zA-Z])[-0-9a-zA-
Z]*([0-9a-zA-Z])$.
Location Services node location. String(64)
Description Services node description. String(64)
Contact Contact for the services node. String(64)
Name Server IP address of each DNS name server referenced One to three valid IP
in order during hostname resolution. addresses
Domain Search Domain name search list for hostname lookup. One to six strings of up to
256 alphanumeric
characters
Operating Mode Services node operational mode. InService or Maintenance
URL URL of the SpiderNet server. Valid IP address
Connection Request Read-only IP address used by the SpiderNet Valid IP address
URL server to connect to the services node.
Connection Request Port the services node will monitor for requests Valid IP address
Port from the SpiderNet server.
Username SpiderNet server user name when authentication Valid username. Unused
is required between the primary and backup in this release.
servers.
Connection Request User name of the services node when connection Valid username. Unused
Username requires authentication. in this release.

Table 44: System Management Tab Parameters (continued)

Password SpiderNet server password when authentication Valid password. Unused in
is required between the primary and backup this release.
servers.
Connection Request Services node password of the services node Valid password. Unused in
Password when connection requires authentication. this release.
Periodic Inform Enable Whether or not periodic inform calls are Check box. Unused in this
performed. release.
Periodic Inform Interval Maximum number of seconds between periodic Unsigned integer. Unused
inform calls. in this release.
Periodic Inform Time An absolute time reference to determine when Format:
the services node will initiate the periodic inform
yyyy-mm-ddThh:mm:ssZ
method calls in ISO 8601 format.
Unused in this release.
Enable Whether or not to enable NTP servers. Check box. Default is
cleared.
NTP Server 1 IP address of the primary NTP server. Valid IP address
NTP Server 2 IP address of the secondary NTP server. Valid IP address
Customer ID Customer identifier. String(64)
Location ID Customer location. String(64)
Cluster ID Reserved for future use for services nodes String(64)
deployed as a high availability unit (redundancy).
Max Sessions Maximum number of CLI sessions. Positive integer. Valid
Max Sessions Per User Maximum number of CLI sessions per user. Positive integer. Valid
Hostname Services node host name. Regex(24). Valid
characters:
^$|^([0-9a-zA-Z])[-0-9a-zA-
Z]*([0-9a-zA-Z])$
6.3.7 The Advanced Tab

The Advanced tab reflects the entire contents of the SpiderCloud Wireless data model. Refer to the SCOS
NB Data Model Reference Guide for details about the objects and parameters that comprise the system
configuration and operational state of the selected services node.
Since the list of attributes is lengthy, there is a filter text box near the top of the screen. Enter matching text
in the box. For further usability, click the downward triangle in the filter button to open an advanced filtering
window with selections for the following toggles:
• case sensitive/case insensitive
• match from start/match exactly/match anywhere

The Work Area
• match leaf node only/hide nodes without children/keep the children if any of their
ancestors match
You can also enable or disable the ability to use wild cards in searches.
Find It: Network Control >> Configuration >> Advanced
To modify Advanced tab attributes

Step 1 Navigate to the attribute by expanding its successive higher-level parent objects and select
it.
Step 2 In the text boxes to the right of the selected object, edit the attributes as needed.
Step 3 Click Save.
6.4 Configuration Templates

Configuration templates allow you to establish a common equipment configuration and apply it to multiple
services nodes simultaneously. The Configuration Templates panel contains the following buttons:
Table 45: Configuration Template Buttons
Button Button Name
Add
Delete
Edit
Filter
Import
Apply configuration templates through scheduled tasks. Refer to Section 6.5.1.2, Scheduling a
Configuration Template Application on page 109 for more information.
6.4.1 Creating a Configuration Template

Creating a configuration template involves naming the template, selecting the image constraints and
range, adding attributes from a list, and selecting their values. Since the list of attributes is lengthy, there is
a filter text box near the top of the screen. Enter matching text in the box. For further usability, click the
downward triangle in the filter button to open an advanced filtering window with selections for the following
toggles:
• case sensitive/case insensitive
• match from start/match exactly/match anywhere
• match leaf node only/hide nodes without children/keep the children if any of their
ancestors match
You can also enable or disable the ability to use wild cards in searches.

Find It: Network Control >> Configuration Templates
To create a configuration template

Step 1 Click the add button from the bottom left side of the screen. The Configuration Templates
screen opens.
Step 2 Enter the template name in the Template Name text box.
Step 3 Select the image constraint from the radio buttons to select the services node software
version to filter upon. Options are Greater than Version, Between Versions, and Less
than Versions.
Step 4 Complete the To and From text boxes.
Step 5 Click the add button. The Add Attribute screen opens.
Step 6 Select an attribute from the list. Use the filter text box near the top of the screen to quickly
locate the attribute. Depending upon the attribute selected, text boxes and drop-down lists
open at the bottom of the screen.
Step 7 Enter or select the values in the context-sensitive text boxes and drop-down lists and click
OK.
Step 8 Repeat steps 5 through 7 as needed to add additional attributes to complete the template.
Step 9 Click Close.
Step 10 Click Save.
6.4.2 Editing a Configuration Template

You can edit a configuration template by adding, modifying, and deleting attributes.
To edit a configuration template

Step 1 Select the template from the Configuration Templates list.
Step 2 Click the edit button.
Step 3 Edit the template as needed and click OK.
6.4.3 Importing a Configuration Template

For ease and consistency, you can import a configuration template in XML format and then apply it to
multiple services nodes to ensure that known and trusted configuration parameters are uniformly applied
across the network. SpiderNet validates the file for proper XML formatting and valid attribute configuration.
Invalid formats or configurations are rejected and an error message displays. Once successfully imported,
you can add, modify, or delete entries to this configuration template in the same manner as other
templates.

The Work Area
SpiderNet ships with a number of default templates for common provisioning scenarios. Be sure to inspect
the attributes of these default templates before applying them and verify that the properties, such as IP
addresses, are valid for your environment. If needed, edit the template before applying it.
To import a configuration template

Step 1 Click Import. The Upload dialog box opens.
Step 2 Click Upload. A standard Microsoft Windows Choose File to Upload dialog box opens.
Step 3 Navigate to the file location, select the file, and click Upload.
6.4.4 Exporting a Configuration Template

You can export a configuration template to a local or network drive and import it to other SpiderNet servers
for convenience and configuration consistency.
To export a configuration template

Step 2 Click the edit button.
Step 3 Click Export. The Save dialog box opens.
Step 4 Click Save. A standard Microsoft Windows Save dialog box opens.
6.4.5 Deleting a Configuration Template

Deleting a configuration template completely removes it from the system. If you later need a deleted
template, create a new one with the same attributes and values.
To delete a configuration template

Step 2 Click the delete button. A confirmation screen opens.
Step 3 Click OK.
6.5 Scheduled Tasks

Scheduled tasks allow for bulk configuration changes and software upgrades across multiple services
nodes that require similar configurations. Typical scheduled task include remote software upgrades,
system configuration, and database backups.
The system has two default scheduled tasks that can be modified but not deleted:
• Database Backup: backs up the SpiderNet server database.

• Database Integrity: validates the integrity of the current database and repairs errors if
possible.
Each scheduled task contains different configurable parameters. Space considerations prohibit listing all
parameters in this section. Table 46 shows the most common elements of the Scheduled Task tab and
their descriptions and valid options:
Table 46: Scheduled Task Parameters
Name Task name. String(255)
Type Type of scheduled task. Enum. Valid options: File Download, Apply
Configuration Template, Reboot, Software
Update, Software Revert, SN Database
Backup, SN Database Restore, UMTS REM
Start, UMTS REM Stop, UMTS Self
Configuration, SN Log Bundle, SN Log Mark,
SN Log Rotate, Reset SN Statistics, UMTS
Cell Disable.
Description Task description. Running, Successful, Failed
Start At Scheduled task start time in ISO In the format: mm/dd/yyyy hh:mm:ss AM/PM
8601 format. timezone
Last Completed Time task last completed in ISO In the format: mm/dd/yyyy hh:mm:ss AM/PM
8601 format. timezone
Repetition Scheduled repetition interval. Enum. Valid options: Does not repeat,
Hourly, Daily (Same hour), Weekly (Same
day & hour).
Status Status of the task. Enum. Valid options: Idle, Successful, Failed.
Dependency Task Task that must complete before this Defined scheduled task, None
task begins.
Mail to Group Group to email task results. Defined email group, None
Last execution log of the scheduled task
Name Name of the scheduled task. String
Status Status of the task. Enum. Valid options: Idle, Successful, Failed
Progress What percentage of the task Percentage
progressed.
Last Updated Date and time the task was last run In the format: mm/dd/yyyy hh:mm:ss AM/PM
in ISO 8601 format. timezone
Details Details about the success or failure String
of the scheduled task execution.
6.5.1 Adding a Task

SpiderNet supports the following scheduled tasks:
• 6.5.1.1 Scheduling a File Download on page 108
• 6.5.1.2 Scheduling a Configuration Template Application on page 109

The Work Area
• 6.5.1.3 Scheduling a Reboot on page 110

• 6.5.1.4 Scheduling a Software Update on page 110
• 6.5.1.5 Scheduling a Software Revert on page 111
• 6.5.1.6 Scheduling a Services Node Database Backup on page 112
• 6.5.1.7 Scheduling a Services Node Database Restoration on page 112
• 6.5.1.8 Modifying the Scheduled SpiderNet Backup on page 113
• 6.5.1.9 Modifying the Scheduled SpiderNet Database Integrity Validation on page 114
• 6.5.1.10 Scheduling a UMTS REM Start on page 114
• 6.5.1.11 Scheduling a UMTS REM Stop on page 114
• 6.5.1.12 Scheduling a UMTS Self Configuration on page 115
• 6.5.1.13 Scheduling a Services Node Log Bundle on page 115
• 6.5.1.14 Scheduling a Services Node Log Mark on page 116
• 6.5.1.15 Scheduling a Services Node Log Rotate on page 116
• 6.5.1.16 Scheduling a Reset Services Node Statistics on page 117
• 6.5.1.17 Scheduling Disabling a UMTS Cell on page 118
6.5.1.1 Scheduling a File Download

The SpiderCloud Operating System (SCOS) is a binary file residing in the services node containing the
system software images for the services node and the radio nodes. It can be downloaded from the
SpiderNet server, an external server, or other device and placed in the following location on the SpiderNet
server:
/usr/local/SpiderNet/res/home/spidercloud
A radio node retrieves its software image from its master services node.
The following rules apply when performing software upgrades:
• Upgrades are supported only to a newer software version.
• To fallback to a previously release, revert the software as described in Section 6.5.1.5,
Scheduling a Software Revert on page 111.
• You cannot upgrade to the same software version that is currently running on an services
node.
Schedule a file download to transfer a the SCOS binary file to one or more services nodes. The file
download supports FTP and SCP file transfer protocols. Refer to Section 6.5.1.4, Scheduling a Software
Update on page 110 for information about installing the new software version.
Find It: Network Control >> Scheduled Tasks
To schedule a file download

Step 1 Click Add Task. The Schedule Task screen opens.
Step 2 Select the File Download radio button and click Next.
Step 3 Select the services node or nodes to download files to, click >.
Step 4 In the Max Simultaneous Devices text box, enter the number of simultaneous services
nodes files to and click Next.
Step 5 From the Protocol drop-down list, select the download protocol. Options are ftp and scp.

Step 6 In the Server Type drop-down list, select the type of server to download from. Options are
Internal Server, External Server, and Other.
Step 7 If applicable, enter the IP address and port of the external server in the Hostname and
Port text boxes. The system does not support DNS-resolved addresses.
Step 8 If applicable, enter the file name in the File Name text box.
Step 9 If the server requires authentication, select the Use Credentials check box and complete
the Username and Password text boxes.
Step 10 Click Next.
Step 11 Complete the Name and Description text boxes.
Step 12 From the Dependency Task drop-down menu, select Next or a previously defined task.
Step 13 Select the Start At time.
Step 14 In the Repeats drop down list, select the schedule regularity.
Step 15 To email the task results to a group, select the group from the Mail to Group drop-down
list. Options are None and groups defined in Section 4.4.1, Email Groups on page 52.
Step 16 Click Finish.
6.5.1.2 Scheduling a Configuration Template Application

Configuration templates are a series of defined attributes that can be applied to one or more services
nodes to create a uniform service environment. Templates can be restricted to specific software versions
and be applied to one or multiple installed systems. Advanced screens, allowing access to all attributes of
the data model including all SpiderCloud extensions to TR-196, enable fine-tuning of RF and system
parameters to accommodate deployment-specific requirements.
To schedule applying a configuration template

Step 2 Select the Apply Configuration Template radio button and click Next.
Step 3 Select the services node or nodes to apply the template, click >.
nodes to apply the template to and click Next.
Step 5 Select a template defined in Section 6.4.1, Creating a Configuration Template on page 104
and click Next.

The Work Area
6.5.1.3 Scheduling a Reboot

You can schedule a reboot of either one or more services nodes or a single radio node.
When the services node reboots, all associated client radio nodes also reboot. Therefore
rebooting a services node is service-affecting. SpiderCloud Wireless recommends rebooting
Note services nodes during a maintenance window. Rebooting a radio node takes approximately
one minute.
To schedule a reboot
Step 2 Select the Reboot radio button and click Next.
Step 3 Select the services node or nodes to apply the template, click >..
nodes to reboot and click Next.
Step 5 (Optional) Select one of the following:
   The Selected Radio Node ID check box.
   The Clean Option check box and select the option from the drop-down list.
Options are none, db, data, and configuration.
Step 6 Click Next.
6.5.1.4 Scheduling a Software Update

Once a new version of the SCOS software has been downloaded to the services nodes as described in
Section 6.5.1.1, Scheduling a File Download on page 108, you can schedule software updates on up to
fifty services nodes simultaneously to install the new software image.
After software installation, the services nodes reboots. When the services node reboots, all
associated client radio nodes also reboot. Therefore updating software is service-affecting.
Note SpiderCloud Wireless recommends updating software versions during a maintenance
window.

To schedule a software update

Step 2 Select the Software Update radio button and click Next.
nodes to update and click Next.
Step 5 Enter the software update file name in the Package text box.
Step 6 (Optional) Select the Clean Option check box and select the option from the drop-down
list. Options are none, db, data, and configuration.
Step 7 Click Next.
6.5.1.5 Scheduling a Software Revert

When the services node performs an update, it records a snapshot of the database and saves it. When a
revert is issued, the system is brought back to the exact point before the update and the services node
reboots. All configuration changes made after the update will be lost after a revert. You can schedule a
software revert for up to fifty services nodes simultaneously.
After a software revert, the services nodes reboots. When the services node reboots, all
associated client radio nodes also reboot. Therefore reverting software is service-affecting.
Note SpiderCloud Wireless recommends performing this activity during a maintenance window.
To schedule a software revert

Step 2 Select the Software Revert radio button and click Next.
nodes to revert and click Next.

The Work Area
6.5.1.6 Scheduling a Services Node Database Backup

Each services node maintains a database that contains the current system configuration of provisioned
and learned elements. This file can be backed up to the SpiderNet server, an external server or other
device on a one-time basis or scheduled a periodic backup. The backup does not restore certificates used
for IPsec authentication. By default, the database is backed up to the following SpiderNet server directory:
/usr/local/SpiderNet
The database backup includes data and configurations entered manually and information learned by the
system as it runs. For example, the database backup includes information learned from a REM scan, such
as primary scrambling codes, cell power, and neighborhood topology. It can optionally contain logged
events and historical alarms.
To schedule a services node database backup

Step 2 Select the SN Database Backup radio button and click Next.
nodes databases to backup and click Next.
Step 5 Enter the database file name in the File Name text box.
Step 6 (Optional) Select the Include Database Logging check box to include logged events and
historical alarms.
Step 7 Click Next.
6.5.1.7 Scheduling a Services Node Database Restoration

Database restoration triggers a services node reboot. Do not modify the backed up database. The system
performs a database validation before the system boots, and will not attempt restoration with an
incompatible or modified backup.
The backup database is not merged with the current persistent database. It replaces it and all data in the
current database is permanently deleted.

Once a database has been restored, it cannot be reverted to the previous configuration. In the event of a
major error in the restoration process, the restore process is aborted and the system continues using the
current database and the system generates a DB_BACKUP_FAILED error message.
After database restoration, the services nodes reboots. When the services node reboots, all
associated client radio nodes also reboot. Therefore reverting the database is service-
Note affecting. SpiderCloud Wireless recommends reverting the databases during a maintenance
window.
To schedule a services node database restoration

Step 2 Select the SN Database Restore radio button and click Next.
Step 3 Select the services node or nodes to restore and click >. The default backup location is /
user/local/SpiderNet/backup.
nodes databases to restore and click Next.
Step 5 Enter the database file name in the File Name text box and click Next.
6.5.1.8 Modifying the Scheduled SpiderNet Backup

SpiderNet has a default task that backs up the SpiderNet database. This task is the only task in the Type
column named Backup. The task cannot be deleted, but you can modify the default parameters.
Refer to Chapter 9, “SpiderNet Maintenance.” on page 145 for information about restoring the SpiderNet
database.
To modify the scheduled SpiderNet database backup

Step 1 Select the task named Database Backup of the type Backup and click Edit. The
Schedule Task-Database Backup screen opens.
Step 2 (Optional) Edit backup location in the Database Backup Folder text box.
Step 3 Click Next.
Step 4 Edit the Task Details screen as needed and click Finish.

The Work Area
6.5.1.9 Modifying the Scheduled SpiderNet Database Integrity Validation

SpiderNet has a default task that verifies the integrity of the SpiderNet database. If it encounters errors, it
attempts to repair the database. The task cannot be deleted, but you can modify the default parameters.
To modify the scheduled SpiderNet database integrity validation

Step 1 Select the task named Database Integrity of the type Database Integrity and click Edit.
The Schedule Task-Database Backup screen opens.
Step 2 Edit the Task Details screen as needed and click Finish.
6.5.1.10 Scheduling a UMTS REM Start

A Radio Environment Measurement (REM) scan discovers system topology, assigns cells primary
scrambling codes and initial power levels, and constructs the neighbor lists for all cells controlled by the
services node.
REM scanning is service-affecting. SpiderCloud Wireless recommends scheduling REM

scans during a maintenance window.
Note
To schedule a UMTS REM start

Step 2 Select the UMTS REM Start radio button and click Next.
nodes to schedule a REM scan and click Next.
6.5.1.11 Scheduling a UMTS REM Stop

You can manually stop a running REM scan that you do not want to complete. For example, if you notice
that the configuration is incorrect while the scan is in progress, rather than waiting for the scan to complete,
you can abort the scan, change the configuration, and start a new scan.
Aborting a REM scan will typically leave the system in an inoperable state. Use this command
with care and sparingly. After making configuration changes, be sure to start a new scan to
Caution bring the system into operation.


To schedule a UMTS REM stop
Step 2 Select the UMTS REM Stop radio button and click Next.
nodes to stop REM scanning and click Next.
6.5.1.12 Scheduling a UMTS Self Configuration

UMTS Self Configuration scans the network and reassigns cell transmit power levels based upon historical
data obtained from user devices over time.
To schedule a UMTS REM self configuration

Step 2 Select the UMTS Self Configuration radio button and click Next.
nodes to schedule UMTS REM scans and click Next.
6.5.1.13 Scheduling a Services Node Log Bundle

It is often convenient in troubleshooting to bundle a number of related error log files for off-services node
processing and evaluation. You can schedule log bundles simultaneous for up to fifty services nodes.

The Work Area
To schedule a services node log bundle

Step 2 Select the SN Log Bundle radio button and click Next.
nodes to bundle log files and click Next.
6.5.1.14 Scheduling a Services Node Log Mark

A log mark is text string that identifies the beginning and ending of a test in a log file. This assists
troubleshooting problems.
To schedule a services node log mark

Step 2 Select the SN Log Mark radio button and click Next.
nodes to mark logs and click Next.
Step 5 (Optional) Select the Marker check box and enter the marker name in the check box and
click Next.
6.5.1.15 Scheduling a Services Node Log Rotate

The services node supports one current and up to ten previous debug log files. Each log file is identified by
a timestamp. When the current log file reaches 50 megabytes, it is automatically closed (rotated) and a
new log begins. If there are already ten old log files, the system deletes the oldest log file.

You can manually rotate log file simultaneously for up to fifty services nodes. Optionally can add a
comment to the new log file.
To schedule a services node log rotate

Step 2 Select the SN Log Rotate radio button and click Next.
nodes rotate log files and click Next.
Step 5 (Optional) Select the Marker check box and enter the marker name in the check box.
Step 6 (Optional) Select the Max Values check box and enter the maximum number of files. Valid
options are 1 through 10.
Step 7 Click Next.
6.5.1.16 Scheduling a Reset Services Node Statistics

Reset the Gigabit Ethernet port and IP interface statistics simultaneously for up to fifty services nodes.
Resetting the statistics sets the counters of all services node Ethernet ports and IP interfaces to zero. The
system does not maintain a history of reset statistics.
To schedule a services node statistics reset

Step 2 Select the Reset SN Statistics radio button and click Next.
nodes to reset statistics and click Next.

The Work Area
6.5.1.17 Scheduling Disabling a UMTS Cell

You can disable a single cell or all cells in up to 50 services nodes simultaneously.
Disabling a cell is service-affecting.
Note
To schedule disabling a UMTS cell

Step 2 Select the UMTS Cell Disable radio button and click Next.
nodes to disable UMTS cells and click Next.
Step 5 (Optional) Select the CellId check box and enter the cell identifier in the check box.
Step 6 (Optional) Select the isAll check box to disable all cells.
Step 7 Click Next.
6.5.2 Cloning a Task

Clone a task and modify the parameters when you need to create a task similar, but not identical, to an
existing one.
To clone a task
Step 1 Select the task from the Task List.
Step 2 Click Clone. The Clone Task screen opens.
Step 3 Select the task to clone and follow the steps for that task.

6.5.3 Editing a Task

You can edit an existing scheduled task.
To edit a task
Step 2 Click Edit. The Scheduled Task screen opens with the defined task configuration
parameters.
Step 3 Edit the screens as needed and click Finish.
6.5.4 Removing a Task

Removing a task permanently deletes it from the list of scheduled tasks.
To remove a task
Step 2 Click Remove. A confirmation screen opens.
Step 3 Click OK.
6.5.5 Removing All Tasks

You can remove all successfully completed tasks not scheduled to run again.
To remove all completed tasks

Step 4 Click Remove All. A confirmation screen opens.
Step 5 Click OK.
6.5.6 Immediately Running Scheduled Tasks

You can immediately run a task scheduled for a later time.
To immediately run a scheduled task

Step 1 From the Task List area, select a task to run.
Step 2 Click Run Now.

The Work Area
6.5.7 Retrying Failed Scheduled Tasks

A scheduled task may fail for any number of reasons. You can rerun the task for all services nodes that
failed the task without having to schedule it again. It does not run the task on services nodes that the task
successfully executed on the original try.
To rerun a failed task.

Step 1 From the Task List area, select a task to rerun.
Step 2 Click Retry Failed Task Targets.
6.5.8 Aborting a Running Task

You can abort a scheduled task while it is running.
To abort a running task.

Step 1 From the Task List area, select a task to abort.
Step 2 Click Abort Task.

7 Fault Management

• Section 7.1, Fault Management Overview on page 121
• Section 7.2, Alarms and Event Screen Elements on page 125
• Section 7.3, Managing Alarm and Event Screen Displays on page 127
• Section 7.4, Viewing Alarm and Event Details on page 129
• Section 7.5, Manually Clearing Alarms on page 129
• Section 7.6, Acknowledging Alarms and Events on page 130
• Section 7.7, Annotate an Alarm on page 130
• Section 7.8, Saving Events to a File on page 130
• Section 7.9, Printing the Alarm and Event Screen Display on page 131
• Section 7.10, SpiderNet Traps on page 131
7.1 Fault Management Overview

Fault management refers to SpiderNet generated alarms, such as connection loss to a managed services
node or to the database and alarms generated by individual services nodes and their managed cells.
SpiderNet uses the following fault management protocols:
• SNMP: Services nodes send SNMPv2c and SNMPv3 trap and inform messages to the
SpiderNet server. The SpiderNet server can be configured to forward these to one or more
northbound interfaces.
• TR-069: The SpiderNet server and the services nodes use this protocol to synchronize current
alarms and events upon the server startup and the services node joining the system or
rebooting. It also periodically uses this protocol to synchronize current alarms and events while
the system is in normal service mode.
SpiderNet displays alarms and events based upon four sources:
• SNMP traps sent by services nodes
• The current alarm table contained in the services node data model
• Internal alarms and events generated by internal modules of the SpiderNet server
• Syslog events
SpiderNet must be configured as a trap target by services nodes and third-party equipment through the
Advanced tab in the work area or with a configuration template. It does not configure the equipment to add
itself as a trap target. Refer to Section 6.3.7, The Advanced Tab on page 103 and Section 6.4.2, Editing a
Configuration Template on page 105.
Upon startup, the SpiderNet server listens on a configurable port (162 by default) to incoming traps.
Received traps are inspected and treated as follows:
• Traps from a known source are accepted and processed.

Fault Management
• Traps from an unknown source of a known type are added to the event log. An unknown
source is an IP address not found in the SpiderNet topology. The event parent key is the IP
address. No further action is taken up on this trap.
• Unknown trap types are rejected. Refer to Section 7.1.1, Supported Traps on page 122 for lists
of supported standard and proprietary traps.
Services node current alarms are stored in its data model. SpiderNet reads each services node current
alarms in the following occasions:
• the first time a services node manually or automatically connects to SpiderNet
• upon SpiderNet startup or reboot
• each time a services node is detected as disconnected and reconnected
• during periodic polling
7.1.1 Supported Traps

SpiderNet supports the following standard traps for services nodes and third-party equipment:
• authenticationFailure
• coldStart
• linkDown
• linkUp
• warmStart
It also supports the following proprietary ERAN-TRAP-MIB trap messages from services nodes:
• eranNotifCalibrationInvalid
• eranNotifCellMaxPowerDeltaExceeded
• eranNotifConfigMismatch
• eranNotifCoreIpsecTerm
• eranNotifDbInvalid
• eranNotifDhcpAllocationFailure
• eranNotifFwdMsg
• eranNotifIpsecDown
• eranNotifLinkDown
• eranNotifLossOfSync
• eranNotifMissingEquipment
• eranNotifMsg
• eranNotifMultipleCoolingFanFailures
• eranNotifNeighborhoodReferenceDelta
• eranNotifOverTemperature
• eranNotifPowerSupplyFailed
• eranNotifPowerSupplyMissing
• eranNotifProvFault
• eranNotifRanapCsConnectionTerm

• eranNotifRanapPsConnectionTerm
• eranNotifRfMgmtFaulted
• eranNotifSoftwareMismatch
• eranNotifSystemMaxSessionRateExceeded
• eranNotifSystemNearingMaxSessionRate
• eranNotifUarfcndlChanged
7.1.2 Syslog Events

In addition to traps, SpiderNet can be configured to receive syslog events. Upon startup SpiderNet listens
for incoming syslog events. All syslog events have the event type Syslog Event. When received they are
converted to SpiderNet’s internal event format. Table 47 shows the standard syslog event to SpiderNet
event conversion rules:
Table 47: Syslog to SpiderNet Conversion Rules
Syslog Field SpiderNet Event
Host Parent Key
Level Severity
Message Description
Date Occurred Date and Time
Table 48 shows the mapping between system severity levels and syslog levels. The severity value for
syslog messages equals 24 plus the syslog severity code.
Table 48: Syslog Severity

System Severity Syslog Severity Syslog Severity Code Severity Value
Critical Critical 2 26
Major Error 3 27
Minor Error 3 27
Warning Warning 4 28
Info Informational 6 30
Trace Debug 7 31
Syslog settings are configured in the Administration tab. Refer to Section 4.6.2, Syslog Server on
page 62 for more information.
7.1.3 SpiderNet Internal Alarms

In addition to services node alarms and events, SpiderNet can generate the following proprietary alarms
and events:
• configurationError: the pending configuration is not valid and will not be applied
• deviceAdded: a services node was added to the system
• deviceConnected: a services node that was disconnected reconnects

Fault Management
• deviceDeleted: a services node was deleted from the system

• deviceDisconnected: a services node is disconnected
• deviceDiscovered: a services node has been detected
• serverDown: SpiderNet service is stopped
• serverUp: SpiderNet service is started
• tableCleanup: the events or audit trail tables are maintained
7.1.4 Event Handling

The event table will grow over time. To prevent overtaxing the SpiderNet server resources such as disk
space, the event table is limited to a fixed number of rows (the default is 1,000,000). SpiderNet monitors
the size of the event table, and as it approaches the limit it takes the following actions:
• When it reaches 70% of the threshold it generates an event that says that it has reached 70%
of its capacity.
• When it reaches 80% of the threshold it generates an event that says that it has reached 80%
of its capacity.
• When it reaches 90% of the threshold it will:
   Export all older events up to the 70% capacity to a CSV file.
   Generate an event that the event table was cleaned and older events were
exported to file. The event description includes the full file name and path.
SpiderNet inspects all incoming events. When the severity is a Warning or greater it generates an alarm. If
the event is Cleared it clears the corresponding existing alarm.
7.1.5 Alarm Handling

A generated alarm causes SpiderNet to take the following actions:
• The services node status changes to the severity of the alarm.
• The services node icon in the tree view displays the severity appropriate icon.
• The new alarm displays in the alarm table.
Alarms are active until the services node clears them, they are manually cleared by an administrator,
SpiderNet loses connectivity to a services node, or the services node reboots. After a reboot SpiderNet
reads the alarms from each connected services node to create a new alarm table.
SpiderNet periodically reads the current alarm table of each connected services node and compares the
results with the current SpiderNet alarm table and takes the following actions:
• Generates a new SpiderNet alarm for each services node alarm it discovers that is not in the
SpiderNet current alarm list.
• Clears a SpiderNet alarm for each services node alarm it did not discover on the services node
current alarm list. It does not clear it from the events table. The services node icon in the tree
view displays a Cleared icon.
• Compares all parameters for alarms found in the current alarms list of both SpiderNet and the
services nodes and update to SpiderNet alarm table to match the alarm information in the
services node alarm if needed. If it discovers an alarm previously cleared by an administrator,
it will be treated as a new alarm and display in the SpiderNet current alarm table.

7.2 Alarms and Event Screen Elements

The Faults tab and the Alarm Summary panel in the Network Control tab contain separate panels for
server-related events and alarms. The two sections are functionally identical except that the results in the
Alarm Summary panel are automatically filtered by the topology tree selection. Both of these elements
dynamically react to changes in the alarm environment and update as events are added and alarms are
opened and cleared.
As described in Chapter 5, “The Tree View” on page 69, selecting an element in the tree view filters the
output in the work area and Alarm Summary panel. Select the top level root directory to view all events
and alarms in the system. Select a subnet group, subnet, or device to filter out all alarms and events that
are not part of that element.
The Events and Alarms panels contain identical button bars on the top of their screens. Table 49 shows
the buttons on the alarm and event button bar and their behaviors:
Table 49: Alarm and Event Button Bar Items
First page: navigates to the first results page
Previous page: navigates to the previous results page
Next page: navigates to the next results page
Acknowledge/Unacknowledge: toggle that acknowledges or

unacknowledges the selected event or alarm
Clear: clears the selected alarm or alarms. Alarms screen only
Filter: displays the Event Filter or Alarm Filter dialog box
Filter: toggle that shows whether display is filtered or not
Comment: indicates an alarm or event has been annotated
Annotate: opens the Comment dialog box for adding a note and assigning
an action to a user. Alarms screen only
Print: opens the Print dialog box
Export to CSV: opens the Export to CSV dialog box
Choose columns: opens the Choose Columns dialog box to select the
columns to display in the report
Critical: displays the number of critical alarms. Alarms screen only

Fault Management
Table 49: Alarm and Event Button Bar Items (continued)

Major: displays the number of major alarms. Alarms screen only
Minor/Warning: displays the number of minor alarms and warnings. Alarms

screen only
The Alarm and Events tabs contain the following parameters, descriptions, and valid options:
Table 50: Alarm and Event Parameters
Seq. No. The sequence number is an N/A
incremented integer assigned to an
event.
Time & Date The date and time the alarm or Format: mm/dd/yyyy hh:mm:ss AM/PM
event was received by the timezone
SpiderNet server in ISO 8601
format.
Time Occurred The date and time the alarm Format: mm/dd/yyyy hh:mm:ss AM/PM
occurred in ISO 8601 format. timezone
Severity Alarm or event severity. Enum. Valid options are: Info, Cleared,
Warning, Minor, Major, Critical
Ack Whether or not the alarm has been Marked check box, empty
acknowledged.
Ack Details The user that acknowledged the User, date, and time of the acknowledgement
alarm or event and the date and
time.
Description Description of the alarm or event. N/A
Source Hostname or IP address of the Valid host name or IP address
source of the alarm or event.
Managed Object The type of object causing the IP address of the server or empty
alarm or event.
Type Type of alarm or event. Configuration Error, Device Connected, Device
Disconnected, Device Discovered, Reboot,
Server Shutdown, Server Startup, Table
Cleanup, Threshold Back to Normal, Threshold
Exceeded
Group Type of the source of the alarm. Communications, Server

7.3 Managing Alarm and Event Screen Displays

Managing alarm and event screen displays consists of selecting the display column contents, adjusting
column widths, sorting the display, and filtering and grouping alarms and events.
Alarm and event screens are static and do not dynamically refresh. To refresh the screen,
click the Events or Alarms tab again.
Note
7.3.1 Navigating Alarm or Event Screens

Each alarm and event screen contains approximately 200 entries. To view entries from a different screen,
page through the screens.
To view different alarm or event screens
Step 1 From the alarm button bar, do one of the following:
   Click the first page button to navigate to the first page.
   Click the previous page button to navigate to the previous page.
   Click the next page button to navigate to the next page.
7.3.2 Selecting the Display Columns

Alarm and event screen displays are user-configurable. You can select which columns to display and
which to hide.
To select the display columns
Step 1 Click the Choose Columns button beneath the Print button or right-click a column
heading. The Choose Columns dialog box opens.
Step 2 From the check boxes on the left, check the boxes of the columns to display and clear the
boxes of the columns to hide.
Step 3 Click OK.
7.3.3 Adjusting Column Widths

When the column content exceeds the size of the column, you can adjust the width to view all of the
content.
To adjust the column width
Step 1 Place your cursor to the right of the column heading to resize. The cursor changes to a
two-sided horizontal arrow.
Step 2 Click and hold down the mouse button and adjust the column width as needed.
7.3.4 Sorting Alarm and Event Screen Displays

You can sort alarms and events by any one or more columns in ascending or descending order.

Fault Management
To sort alarm and event screen displays

Step 2 To perform a secondary sort, control click the second column heading to achieve a
secondary sort in ascending order. Control click the column heading again to sort in
descending order.
Step 3 Repeat Step 2 any number of times on other columns to add additional sorting.
To clear alarm and events sorting

icon disappears.
7.3.5 Filtering Alarms and Events

Alarm and event lists can be filtered by a number of criteria. One or more filtering criteria are required to
filter alarms or events. If more than one filter element is selected, there must be a result from each filter
element to produce filter results.
For example, if you select critical Severity, and an Event Time within the last week, all alarms that appear
must be of critical severity AND have been triggered in the last week. Refer to Table 50 on page 126 for
information about valid parameter options.
To filter alarms and events
Step 1 From the alarm button bar, click the filter button. The Alarm/Event Filter dialog box opens.
Step 2 Select one or more criteria to filter by. Seq. ID and Severity support the options Equals or
Lesser, Equals, and Equal or Greater. Managed Ob... supports the options of Equals,
and Contains.
Step 3 Click OK.
To remove an alarm or event filter

Step 1 From the alarm button bar, click the filter button.
7.3.6 Grouping Alarms and Events

Alarms and events can be grouped together such that all of the attributes selected for grouping display
together. Groups can be subgrouped by selecting another grouping attribute.
Each group of similar items are separated from other groups by one or more horizontal white rows.
Subgroups are separated by a one less horizontal white row than are groups.
To group alarms and events
Step 1 Right click inside the alarm or event display. The Group By screen opens.
Step 2 Click Group By. The grouping options dialog box opens.

Step 3 Select one or more attributes to group. Options are Severity, Ack, Source, Managed
Object, Type, and Group.
Figure 7 The Group By Screen and Options
To remove alarm and event grouping

Step 1 Right click inside the alarm or event display. The Group By screen opens.
Step 2 Click Group By. The grouping options dialog box opens.
Step 3 Click Remove All.
7.4 Viewing Alarm and Event Details

You can view the details of each alarm and event.
Step 1 Double-click the alarm or event. The read-only Details screen opens with information
about the alarm or event.
7.5 Manually Clearing Alarms

Manually clearing an alarm removes it from the Alarm Summary screen. It does not clear it from the
Events Log screen, nor does clearing it add an event to the log.
To manually clear an alarm
Step 1 From the Alarm Summary screen, select an alarm to clear. To make multiple adjacent
selections, click the topmost selection, then hold down the Shift key and click the
lowermost selection. To make multiple nonadjacent selections, click a selection, then
control click the other selections.
Step 2 Click Clear.

Fault Management
7.6 Acknowledging Alarms and Events

Acknowledging an alarm or event marks it as being noticed. It does not suppress further status
notifications.
To acknowledge an alarm or event
Step 1 Select the alarm or event to acknowledge. To make multiple adjacent selections, click the
topmost selection, then hold down the Shift key and click the lowermost selection. To
make multiple nonadjacent selections, click a selection, then control click the other
selections.
Step 2 From the alarm button bar, click Acknowledge.
To unacknowledge an alarm or event

Step 1 Select the alarm or event to unacknowledge.
Step 2 From the alarm button bar, click Unacknowledge.
7.7 Annotate an Alarm

Add annotations to alarms for troubleshooting purposes, assigning them to a user, and attaching
comments.
To annotate an alarm
Step 1 Select the alarm to annotate. To make multiple adjacent selections, click the topmost
selection, then hold down the Shift key and click the lowermost selection. To make multiple
nonadjacent selections, click a selection, then control click the other selections.
Step 2 Click the Annotate button. The Comment dialog box opens.
Step 3 Complete the Comment dialog box as needed. Available fields are Ticket ID, Assignee,
and Comment.
Step 4 Click OK. The Comment button displays on the left side of the Description field for each
annotated alarm.
To clear an alarm annotation

Step 1 Select the alarm with the annotation.
Step 2 Click the Comment button. The Comment dialog box opens.
Step 3 Delete the annotations and click OK.
7.8 Saving Events to a File

You can save the contents of the alarm or event screen to a CSV file for off-box computation and analysis.
If the current view has alarms or events filtered, the exported file contains only the filtered results. The sort
order does not affect the sort order of the output. When saving the file, you do not need specify the .csv
extension. When omitted, the extension is automatically added to the file.
To save events to a file
Step 1 From the alarm button bar, click the Export to CSV button. The Export to CSV dialog box
opens.

Step 3 Click Yes to save the file in CSV format.
7.9 Printing the Alarm and Event Screen Display

You can print the contents of the open alarm or event screen. If the content of the event log or current
alarm list spans multiple pages, only the currently displayed page prints. If the current view has alarms or
events filtered, only the filtered results print.
To print the alarm or event screen display
Step 1 From the alarm button bar, click the Print button. The Print dialog box opens.
Step 3 Click Print.
7.10 SpiderNet Traps

SpiderNet sends the following traps to the NBI Operations Support System (OSS):
7.10.1 spiderNetHeartBeat
• Trap Number: 100
• Description: Heartbeat trap with configurable frequency sent to the NBI OSS when in service.
• Default Severity: Minor
• Entered Event: N/A
• Exit Event: N/A
• Managed Objects: SpiderNet
• System Actions: The SpiderNet system is able to connect to NBI OSS.
• Operational State Changes: N/A
• Corrective Action: None
7.10.2 spiderNetDeviceAdded
• Description: A new device has been added to SpiderNet.
• Default Severity: Info
• Exit Event: N/A
• Managed Objects: ServicesNode, third-party devices
• System Actions: The SpiderNet system will begin discovery of this device.
• Operational State Changes: Device becomes either IS or OSS.

Fault Management
7.10.3 spiderNetDeviceDiscovered
• Description: The devices that was added to SpiderNet has been successfully discovered.
• Exit Event: N/A
• System Actions: The SpiderNet system discovered and connected to this device.
• Operational State Changes: Device becomes either IS or OSS.
7.10.4 spiderNetDeviceDisconnected
• Description: SpiderNet lost connection to the managed device.
• Default Severity: Major
• Exit Event: N/A
• System Actions: The SpiderNet system will try periodically to connect to this device. After re-
connect a Clear event will be sent.
• Operational State Changes: Device becomes OOS.
7.10.5 spiderNetDeviceDeleted
• Description: The managed devices was deleted from the system.
• Exit Event: N/A
• System Actions: The device was deleted from the SpiderNet database.
• Operational State Changes: N/A
7.10.6 spiderNetServerStarted
• Description: SpiderNet service has started.


• Exit Event: N/A
• System Actions: The SpiderNet service has started.
• Operational State Changes: Sever becomes IS in the NBI OSS.
7.10.7 spiderNetServerShutdown
• Description: SpiderNet service has stopped.
• Default Severity: Major
• Exit Event: N/A
• System Actions: The SpiderNet services has stopped. Heartbeat notifications cease.
• Operational State Changes: Server becomes OSS in the NBI OSS.

Fault Management

8 Performance Monitoring

• Section 8.1, Performance Monitoring Overview on page 135
• Section 8.2, The Performance Tab on page 136
8.1 Performance Monitoring Overview

Performance management enables system administrators and network operators to monitor the health of
the network, detect and locate problems in radio components, and determine long-term performance
trends. The E-RAN supports the collection of a wide-range of performance counters needed to remotely
monitor and manage the performance of the system.
8.1.1 Configuring Performance Monitoring

Performance monitoring is enabled and disabled for a selected services node on a system-wide and per-
cell basis from the tree view. System-wide data collection is enabled by default. Per-cell data collection is
disabled by default and must be explicitly enabled. Additionally, existing performance data can be deleted
from the tree view.
8.1.1.1 Enabling and Disabling System-Wide Performance Data Collection

System-wide data collection is enabled by default. You can disable system-wide data collection or re-
enable data collection for a services node that has had data collection previously disabled.
Find It: Tree View
To disable system-wide performance data collection.

Step 1 Right-click the services node and select Collect PM. A confirmation screen opens.
Step 2 Click Yes.
To enable system-wide performance data collection.

Step 1 Right-click the services node and select Collect PM.
8.1.1.2 Enabling and Disabling Cell Performance Data Collection

Cell data collection is disabled by default. You can enable cell-level data collection for selected cells
configured in the services node or all cells.
Find It: Tree View
To enable cell performance data collection.

Step 1 Right-click the services node and select Collect Cell PM. the Cell PM Collection
Configuration screen opens.
Step 2 To select all cells, click Select/Deselect All.
Step 3 To select one or more individual cells, select the check box next to its name or number.

Performance Monitoring
Step 4 Click OK.
To disable cell performance data collection.

Step 1 Right-click the services node and select Collect Cell PM. the Cell PM Collection
Configuration screen opens.
Step 2 To deselect all cells, click Select/Deselect All.
Step 3 To deselect one or more individual cells, select the check box next to its name or number.
Step 4 Click OK.
8.1.1.3 Clearing PM Data

You can clear all existing system-wide and cell PM data from the SpiderNet database. This option is
disabled if there is no PM data to clear.
Deleting performance data is permanent. There is no method for restoring it.
Note
To clear PM data
Step 1 Right-click the services node and select Clear PM. A confirmation screen opens.
Step 2 Click Yes.
8.1.2 Data Compaction

SpiderNet automatically compacts older data to prevent the performance management database from
becoming unmanageable. Compacted older data is still available for recall for reporting and performance
charts and tables.
8.2 The Performance Tab

The Performance tab displays snapshots of collected performance monitoring data for a selected services
node. A page can display one, four, or nine views. A view is the computation of a one or more KPI for a
selected time period. The display can toggle between a chart and a table. A total of 18 charts and tables
can be maintained concurrently. With the performance monitoring dashboard you can:
• display multiple charts and tables in the same window
• arrange views
• determine whether one, four, or nine views display simultaneously per page
• navigate between pages
• save views per user such that they restore on next login
The chart X axis shows the time increments. The Y axis shows the KPI. Each KPI is color-coded with a
color key on the bottom for ease of viewing. Charts contain a scrollbar on their button bar to adjust the
displayed start or end period. The scrollbar does not adjust the data in the associated table.
A number of cell statistics display more than one measured KPIs. For example, the statistic RRC
Connection Statistics per Cell contains the following KPIs as shown in Figure 8:
• RRC Connection Rejects due to Congestion per Cell

• RRC Connection Establishment Attempts due to InterRAT Cell Resection per Cell
• RRC Connection Establishment Successes due to InterRAT Cell Reselection per Cell
• RRC Connection Establishment Attempts due to Registration per Cell
• RRC Connection Establishment Successes due to Registration per Cell
Figure 8 Graph with Multiple Color-Coded KPIs
Refer to the Performance Measurements for SpiderCloud Small-Cell E-RAN manual for more information
about SpiderCloud system measurements and KPI computation. Refer to Chapter 11, “SpiderNet
Performance Counters” on page 153 for a list of SpiderNet supported KPIs, their descriptions, and
measurement units.
Table 52 shows the Performance tab buttons:
Table 51: Performance Dashboard Buttons
Creates a new performance graph
Deletes an existing performance graph
Deletes all performance graphs
Navigates to the previous page

Table 51: Performance Dashboard Buttons (continued)

Returns to the home page
Navigates to the next page
Displays a single panel per page
Displays four panels per page
Displays nine panels per page
Each individual performance view panel contains its own set of buttons. Table 52 shows the performance
view panel buttons:
Table 52: Performance View Panel Buttons
Export to CSV: opens the Export to CSV dialog box and exports the
KPIs after calculation
Export raw data: opens the Save dialog box and creates a file with the
raw KPI values
Save As: opens the Save dialog box
Print: opens the Print dialog box
Zooms in
Zooms out
Resets view to the default size
Scrollbar that adjusts the start or end time of the KPI display
Refreshes the performance view

8.2.1 Creating a Performance View
Find It: Performance
To create a performance view

Step 1 Click the New button. The Create a new performance graph dialog opens.
Step 2 Select the radio button for system, cell specific, or equipment KPIs and click Next.
Step 3 Select a performance category (KPI) to display and click Next.
Step 4 Select the services node or nodes to view, click >, and click Next.
Step 5 For cell KPIs, select one or more cells, click >, and click Next.
Step 6 For equipment KPIs for radio nodes, select a radio node, click >, and click Next.
   Select the From and use the drop-down calenders to define the view time frame.
  Select the Last radio button and select the unit of time measurement and enter the
number of units in the view. Options are hours, days, weeks, or months.
8.2.2 Setting the Performance View Display

You can display performance views either in graphical or tabular format by selecting a tab on the bottom of
the graph to toggle the display.
To set toggle performance view display

Step 1 In the bottom of the performance view graph, click either the Chart or Table tab.
Step 2 (Optional) Drag the scrollbar on the performance view panel button bar to adjust the start
or end time of the graph.
8.2.3 Refreshing the Performance View Data

When the performance view is computed for the latest defined period of time rather than for a defined time
period, you can refresh the view to recompute the KPI with the latest statistics. In other words, if the
performance view is set for the last 3 hours, refreshing the view every three hours will display completely
new data. A two-week performance view from March 1, 2013 to March 14, 2013 cannot be refreshed, as
there would be no new data.
To refresh the performance view data

Step 1 In the performance view chart or table select the refresh button.

8.2.4 Using the Performance View Chart Scrollbar

The performance view chart scrollbar on the Performance View Button Bar has two features:
• It allows you to adjust the beginning or end time of the chart view.
• It allows you to configure a viewing period shorter than the total chart time that you can slide to
give performance snapshots for comparison purposes. For example, in a six-month chart you
can configure a seven day period to give weekly data collection snapshots as you slide it along
the chart timeline.
Figure 9 shows an example a scrollbar with both the beginning and ending times adjusted:
Figure 9 The Performance View Chart Scrollbar
To adjust the performance view chart scrollbar

Step 1 Click and drag the beginning or ending slider to its new location. The starting or ending
time display next to the slider dynamically changes to reflect the new timeline location.
Step 2 (Optional) Drag the other slider to its new location.
Step 3 (Optional) When both sliders have been adjusted, click inside the sliders and drag the
sliders forward or backwards in the timeline to view data over time.
8.2.5 Sorting the Performance View Table

The performance view tabular view can be sorted either by time or equipment in ascending or descending
order.
To sort the performance view table


To clear the performance view table sorting

icon disappears.
8.2.6 Exporting Performance View Data to a CSV File

You can save the contents of the performance view panel, which contains the calculated KPI values, to a
CSV file for off-box computation and analysis. When saving the file, you do not need to specify the .csv
extension. When omitted, the extension is automatically added to the file.
To save performance view data to a file

Step 1 From the performance view button bar in either the Chart or Table tab, click the Export to
CSV button. Alternatively, right-click on the chart view and select Export. The Export to
CSV dialog box opens.
8.2.7 Exporting Raw Performance View Data

You can save the raw data used to compute the KPIs to a CSV file for off-box computation and analysis.
When saving the file, you do not need to specify the .csv extension. When omitted, the extension is
automatically added to the file.
To save raw performance view data to a file

Step 1 From the performance view button bar in either the Chart or Table tab, click the Export
raw data button. The Export to CSV dialog box opens.
8.2.8 Saving the Performance View Graph

You can save the performance view graph to a PNG file for analysis or archival purposes. When saving the
file, you do not need to specify the .png extension. When omitted, the extension is automatically added to
the file.
To save performance view graph

Step 1 From the performance view button bar in the Chart tab, click the Save As button.
Alternatively, right-click on the chart view and select Save As. The Save dialog box opens.
Step 2 Navigate to the file location on your local or network drive, name the file, and click Save.

8.2.9 Printing Performance View Graph

You can print the performance view graph.
To print the performance view graph

Step 1 From the performance view button bar in the Chart tab, click the Print button. Alternatively,
right-click on the chart view and select Print. The Page Setup dialog box opens.
Step 2 Select the print options and click OK. The Print dialog box opens.
Step 3 Select the printer options and click OK.
8.2.10 Performance View Graph Markers

Performance view graph markers are configurable vertical lines used to quickly locate a specific time in the
graph. Graph markers do not persist when the performance view refreshes.
8.2.10.1 Adding Performance View Graph Markers

You can add one or more performance view graph markers to a chart.
To add a performance view graph marker

Step 1 Right-click the spot on the chart to mark.
Step 2 Select Add Marker. The marker appears.
8.2.10.2 Editing Performance View Graph Markers

You can change the marker color and width or a performance view graph marker.
To edit a performance view graph marker

Step 1 Right-click the chart and select Edit Marker. A list of markers opens.
Step 2 Select the marker to edit.
Step 3 Modify the color and width attributes as needed and click OK.
8.2.10.3 Deleting Performance View Graph Markers

You can delete a performance view graph marker.
To delete a performance view graph marker

Step 1 Right-click the chart and select Remove Marker. A list of markers opens.
Step 2 Select the marker to delete and click OK.

8.2.11 Deleting a Performance View Graph
To delete a performance view graph

Step 1 Select the graph to delete. A selected graph displays with a black border.
Step 2 Click the Delete button.


9 SpiderNet Maintenance

• Section 9.1, Restoring the SpiderNet Database on page 145
• Section 9.2, Managing SCOS Versions on page 146
• Section 9.3, Upgrading the SpiderNet Server on page 146
9.1 Restoring the SpiderNet Database

The SpiderNet database restore operation involves returning the server configuration to that of one
previously saved in a file by a backup procedure. Restoring a SpiderNet database erases the database
that was on the system prior to restoring. Any configuration changes since the previous backup are lost.
The SpiderNet restore utility is invoked from the command line but runs in a graphical environment. Ensure
that your SpiderNet server has an X Windows environment installed and enabled.
To restore the SpiderNet database
Step 1 From the SpiderNet server, log in as root user, and navigate to the server installation
directory. The following is a typical installation directory hierarchy:
cd /usr/local/SpiderNet/
Step 2 Issue the following command to stop the SpiderNet server:
Step 3 Execute the Database Restore command to open the Database Restore screen:
Database Restore
Step 4 From the Database Restore screen, click Database >> Configure to open the Database
Details sub-screen.
Step 5 Complete the URL, Username, and Password text boxes. Ignore the Driver text box.
Step 6 Click OK to return to the Database Restore screen.
Step 7 Select the ... button and navigate to the directory that contains the SpiderNet database
backup files. Typically this is the /backup directory in the server installation directory.
Step 8 Select the backup file and click OK.
Step 9 Click Restore.
Step 10 Close the Database Restore screen and restart the SpiderNet server after restoration
completes.

SpiderNet Maintenance
9.2 Managing SCOS Versions

SpiderNet must contain a data model file for each SCOS software version run by services nodes that it
manages. The file is named in the format scos-x.y.z-data-model.xsd, where x.y.z is SCOS software
version. All data model files reside in the server schema/ directory.
SpiderNet installation files contain a default version of the data model in a file called spidercloud.xsd. Each
services node software version will have a corresponding version of an XSD file. For example SCOS
version 2.0.5 would have also produced a file named scos-2.0.5-data-model.xsd. SpiderNet will use the
XSD file corresponding to the services node SCOS version if it is loaded onto the server, otherwise it will
use the default XSD file to manage the services node.
9.2.1 Uploading a New Data Model File

You can upload a new data model file to the SpiderNet server. When running SpiderNet in a redundant
configuration, you must execute this process for each server.
Find It: Tools >> Upload XSD
To upload a new data model file

Step 1 Navigate to the data model file location on your local drive and select the file.
Step 2 (Optional) To set this file as the default data model file, select the Set as default check
box.
Step 3 Enter the SCOS version in the XSD Version text box. If needed, open the file in a text
editor and view the version number near the top of the file. The version is identified on the
line beginning SCW XML schema definition. Use the first three integers, omit the trailing
fourth integer.
Step 4 Click Upload.
Step 5 From the Linux prompt, issue the following command to stop SpiderNet service.
Step 6 Issue the following command to restart SpiderNet service:
9.3 Upgrading the SpiderNet Server

Use the following procedure to upgrade a SpiderNet server that is not running in a redundant configuration.
To upgrade the SpiderNet software
Step 1 Upload the new software image to the SpiderNet server. As a best practice, create a
directory exclusively for SpiderNet software images. For example:
/root/SpiderNet_build
Step 2 Install the SpiderNet software. Refer to Section 2.4, Installing the Server Software on
page 23 for detailed instructions about how to install the SpiderNet software.

9.4 Upgrading Redundant Server Configurations

Use the following procedure to upgrade SpiderNet server software when running SpiderNet in redundant
mode. Figure 10 shows a high-level view of the redundant server upgrade process:
Stop the SpiderNet Stop the SpiderNet

Stop the SpiderNet Upgrade server A
process on server A process on server B
process on server A
Stop the SpiderNet Stop the SpiderNet

Upgrade server B
process on server B process on server A
Reboot server A Reboot server B
Figure 10 Redundant Configuration Upgrade Flowchart
In this procedure, server A is the original active server and server B is the original standby server. At the
conclusion of this procedure both servers will be running in redundant mode with server A again taking the
active role.
Upgrading the SpiderNet software in a redundant configuration requires taking both servers
out of service at the same time. SpiderCloud Wireless recommends upgrading software
Note versions during a maintenance window.
To upgrade SpiderNet software in a redundant server configuration

Step 1 Log into the Linux prompt of server A as root user and enter the following command to stop
the SpiderNet monitoring process:
Service spidernet_monitor stop
Step 2 Issue the following command to stop SpiderNet service:
Service spidernet_server stop
Step 3 Log into the Linux prompt of server B as root user and enter the following command to stop
the SpiderNet monitoring process:
Service spidernet_monitor stop
Step 4 Issue the following command to stop SpiderNet service:
Service spidernet_server stop
Step 5 Upgrade server A. Refer to Section 2.4, Installing the Server Software on page 23
Step 6 Upgrade server B.
Step 7 After both installations complete, issue the following command on each server to verify that
the SpiderNet monitoring process is running:
service spidernet_monitor status
Step 8 Issue the following command to reboot server A:

SpiderNet Maintenance
reboot
Step 9 After server A has rebooted, issue the following command to reboot server B:
reboot
Step 10 Issue the following command on both servers to ensure that the SpiderNet server is
running:
service spidernet_server status
9.5 Downgrading Redundant Server Configurations

Downgrading a redundant SpiderNet server configuration is identical to upgrading the server configuration.
Follow the procedure in Section 9.4, Upgrading Redundant Server Configurations on page 147 selecting
the a lower SpiderNet software version rather than a higher version. The system retains the redundant
configuration after both servers have rebooted.
Downgrading the SpiderNet software in a redundant configuration requires taking both

servers out of service at the same time. SpiderCloud Wireless recommends downgrading
Note software versions during a maintenance window.

10 Troubleshooting
Log into the SpiderNet server a root user to perform the diagnostic and troubleshooting procedures in this
chapter. In viewing log files, look for operational errors and take the appropriate remedial corrective
actions. This chapter contains the following sections:
• Section 10.1, MySQL Database Status on page 149
• Section 10.2, SpiderNet Server on page 149
• Section 10.3, Linux Operating System on page 150
• Section 10.4, Redundant Server on page 150
10.1 MySQL Database Status

View the status of the MySQL database. If the database is down, restart the database.
To view the status of the MySQL database
Step 1 From the Linux prompt, issue the following command to view the status of the MySQL
database:
/etc/init.d/mysqld status
If the results show that the database down or not running, restart the MySQL database.
To restart the MySQL database
Step 1 From the Linux prompt, issue the following command to restart the MySQL database:
/etc/init.d/mysqld start
Step 2 Re-issue the following command to view the status of the MySQL database:
/etc/init.d/mysqld status
Step 3 If the database is still down, issue the following command to view the MySQL database log
file:
vi /var/log/mysqld.log
10.2 SpiderNet Server

To determine the status of the SpiderNet server
Step 1 From the Linux prompt, issue the following command to determine the status of the
SpiderNet server:
service spidernet_server status
If the results show that the SpiderNet server is down or not running, restart the SpiderNet server.
To start the SpiderNet server
Step 1 Issue the following command to start the SpiderNet server:

Troubleshooting
After thirty seconds, determine the SpiderNet server status again. If the server is not running, view the
SpiderNet log files for more information.
To view the SpiderNet log files
Step 1 Issue the following commands to view the SpiderNet log files for more detailed information
about the status of the SpiderNet server and to view error messages:
cd /usr/local/SpiderNet/logs/
vi /usr/local/SpiderNet/logs/stderr_server.log.0
vi /usr/local/SpiderNet
cd /usr/local/SpiderNet
vi error.log output.log server.startup
cd /usr/local/SpiderNet/logs/
10.3 Linux Operating System

To view the Linux operating system log file
Step 1 From the Linux prompt, issue the following command to view the Linux operating system
log file:
vi /var/log/messages
10.4 Redundant Server

Use the following procedures to determine the cause of a SpiderNet server failover. In this procedure,
server A is the previously active server and server B is the previously standby server.
To troubleshoot a SpiderNet server failover
Step 1 Determine the status of the MySQL server and restart as needed. Refer to Section 10.1,
MySQL Database Status on page 149.
Step 2 Verify that there are no physical issues with the server hardware such as a failed hard
drive or network card. Replace as needed.
Step 3 Verify that there are no firewall issues preventing IP connectivity.
Step 4 Verify that there is no physical connectivity issue with server A. Check all wiring and
connections between the server and switch.
Step 5 Determine the status of the server and restart as needed. Refer to Section 10.2, SpiderNet
Server on page 149.
To return a previously active server to active state

Step 1 From the Linux prompt on server A, issue the following command to start the SpiderNet
server. The server will detect that server B is in active mode. Therefore it will start in
standby mode.
Step 2 From the Linux prompt on server B, issue the following command to stop SpiderNet
service. Server A will detect that server B is not running and now become active again.
Step 3 From the Linux prompt on server B, issue the following command to start SpiderNet
service. Server B will detect that server A is in active mode and become the standby again.


Troubleshooting

11 SpiderNet Performance Counters
SpiderNet supports system-wide, individual cell, and equipment performance counters. System and cell
counters are calculated to produce Key Performance Indicators (KPI) for analysis. KPI definitions may
include one or more of the following abbreviations and notations:
• {i}: an indexed number
• CS: circuit switched voice session
• GTP: GPRS Tunnelling Protocol
• InterRAT: handover between two cells with different radio access technologies
• MSC: mobile switching center
• PS: packet switched session
• RAB: radio access bearer
• RAT: radio access technology
• RNC: radio node controller
• RRC: radio resource control
• RTP: real-time transport protocol
• SHO: soft hand over
• SRB: signalling radio bearer
• Section 11.1, System KPIs on page 153
• Section 11.2, Cell KPI on page 156
• Section 11.3, Equipment Counters on page 158
11.1 System KPIs

System KPIs represent the aggregate performance of UMTS across the entire E-RAN and are used for
monitoring the health of the deployment. The system supports a large set of UMTS system KPIs. These
KPIs are generated from statistics that are available in the UMTS reports. Table 53 shows the system KPI
and their categories:
Table 53: System KPI
Metric Definition Units
Accessibility
CS RRC Connection The ratio of successful RRC connection establishments Fraction
Establishment Success Rate related to the total number of RRC connection
establishment attempts, filtered to include only the
causes used by the CS domain.

SpiderNet Performance Counters
Table 53: System KPI (continued)

PS RRC Connection The ratio of successful RRC connection establishments Fraction
Establishment Success Rate related to the total number of RRC connection
establishment attempts, filtered to include only the
causes used by the PS domain.
CS SRB Drop Rate The ratio of the number of sessions that are expected Fraction
to establish a CS RAB but are disconnected prior to
doing so.
PS SRB Drop Rate The ratio of the number of sessions that are expected Fraction
to establish a PS RAB but are disconnected prior to
doing so.
CS RAB Establishment The ratio of all successful CS RAB establishments Fraction
Success Rate related to the total number of CS RAB establishment
attempts. A RAB establishment is successful if UE
indicates a successful establishment of a CS radio
bearer.
PS RAB Establishment The ratio of all successful PS RAB establishments Fraction
Success Rate related to the total number of PS RAB establishment
indicates a successful establishment of a PS radio
bearer.
CS Call Setup Success Rate The overall success rate when trying to establish a CS Fraction
connection on a UE in Idle state.
PS Call Setup Success Rate The overall success rate when trying to establish a PS Fraction
connection on a UE in Idle state.
Active Sessions The number of active UE session records. Count
Active CS Sessions The number of active CS sessions. Count
Active PS Sessions The number of active PS sessions. Count
Session Rate
Availability
CS System Availability The fraction of time the system had a connection to the Fraction
CS core network. This KPI is measured since the time
of last reset of statistics.
PS System Availability The fraction of time the system had a connection to the Fraction
PS core network. This KPI is measured since the time
of last reset of statistics.
Cell Status
Mobility
CS Outgoing InterRNC The ratio of unsuccessful UE handouts to InterRNC Fraction
Handover Failure Rate handover attempts.
CS Outgoing InterRAT The ratio of unsuccessful UE handouts to InterRAT Fraction
Handover Failure Rate handover attempts.


SHO Addition Success Rate The ratio of successful additions of a new cell into the Fraction
active set to the total number of attempts by all UEs.
InterRAT Handover towards Count
the Core Network
InterRAT Handover towards Count
the UE
Retainability
CS Call Drop Rate The ratio of UE connections dropped in the CS domain. Fraction
PS Call Drop Rate The ratio of UE connections dropped in the PS domain. Fraction
Session Abnormal Release The average per minute number of master sessions Sessions/
Rate terminated due to abnormal event triggers from the minute
system.
Sessions Lost due to The number of instances of sessions that were Count
Congestion prevented from connection due to admission control
policies.
Utilization
Fraction of Established RABs The fraction of successfully established CS speech Fraction
for CS Speech RABs to the total of RABs of all types successfully
established.
Backhaul Data Rate The rate of the total traffic on the downlink and uplink Bytes/second
over the backhaul.
Fraction of Backhaul used by The fraction of the total traffic on both the uplink and the Fraction
DSCP Classification downlink that is used by traffic with a specific DSCP
classification.
CS Traffic Volume The aggregated CS traffic, in Erlangs, carried by the Erlangs (user-
system over the measurement period. hours)
Total UMTS Throughput The rate of transmission of UMTS data on the downlink Bytes/second
and uplink.
Total UMTS Traffic Volume The aggregated UMTS data bytes transmitted on the Bytes
downlink and uplink over the measurement period.
Fraction of Traffic Locally The fraction of the total PS data traffic that is being Fraction
Switched locally switched and not being sent to the core.
Number of CS Calls The total number of CS mobile originated and Count
terminated calls acknowledged by the MSC.
RRC Connection Statistics The number of RRC connection that were attempted, Count
rejected, and successful.
GTP Rate The number of inbound and outbound bytes in the PS Bytes/second
domain.


RTP Rate The number of inbound and outbound bytes in the CS Bytes/second
domain.
Local Switching Rate The number of locally switched inbound and outbound Bytes/second
bytes.
11.2 Cell KPI

Table 54 shows the individual cell KPIs can be used for localization and validation of performance issues.
Table 54: Cell KPI
Accessibility
CS RRC Connection The ratio of successful RRC connection establishments Fraction
Establishment Success Rate per related to the total number of RRC connection
Cell establishment attempts, filtered to include only the
causes used by the CS domain.
CS SRB Drop Rate per Cell The ratio of the number of sessions that are expected to Fraction
establish a CS RAB but are disconnected prior to doing
so.
CS RAB Establishment Success The ratio of all successful CS RAB establishments Fraction
Rate CS per Cell related to the total number of CS RAB establishment
attempts. A RAB establishment is successful if RNC
indicates a successful establishment of a CS radio
bearer to the UE.
CS Call Setup Success Rate per The overall success rate when trying to establish a CS Fraction
Cell connection on a UE in Idle state.
PS RRC Connection The overall success rate when trying to establish a CS Fraction
Establishment Success Rate per connection on a UE in Idle state.
Cell
PS SRB Drop Rate per Cell The ratio of the number of sessions that are expected to Fraction
establish a PS RAB but are disconnected prior to doing
so.
PS RAB Establishment Success The ratio of all successful PS RAB establishments Fraction
Rate per Cell related to the total number of PS RAB establishment
indicates a successful establishment of a PS radio
bearer.
PS Call Setup Success Rate per The overall success rate when trying to establish a PS Fraction
Cell connection on a UE in Idle state.
Sessions in FACH per Cell The number of users in Cell_FACH state. Count
Sessions in PCH per Cell The number of users in Cell_PCH state. Count
Airlink

Table 54: Cell KPI (continued)

Transmit Power per Cell The maximum cell transmit power. dBm
Availability
Cell Availability The fraction of time that the cell was in service. This KPI Fraction
is measured since the time of last reset of statistics.
Mobility
CS Handover Rate per Cell
SHO Addition Success Rate per The likelihood of a UE connected to the cell being able Fraction
Cell to add another cell to the active set of the UE.
InterRAT Handover Failure Rate The number of handover attempts that result in a failure Fraction
towards the UE per Cell response from the UE to the RRC message sent with
the reconfiguring information, per cell.
Serving Cell Change Rate per The rate at which UEs with PS sessions on the system 1/second
Cell select the given cell as the serving cell.
InterRAT Handover Statistics per The number of interRAT handover attempts towards the Count
Cell core network, and number of interRAT handovers
towards the UE that were successful.
Retainability
CS Call Drop Rate per Cell The ratio of dropping a CS call abnormally normalized Fraction
by the total number of unique CS RABs hosted by the
cell.
PS Call Drop Rate per Cell The ratio of dropping a PS call abnormally normalized Fraction
by the total number of unique PS RABs hosted by the
cell.
CS RRC Reestablishment The ratio of a UE attempting a cell reestablishment, and Fraction
Attempt Rate per Cell the ratio of a CS Session going into RRC
reestablishment, on a given cell as a fraction of the total
number of radio links created on the cell. Also the ratio
of successful RRC connection reestablishments related
to the total number of RRC connection reestablishment
attempts.
Admission Control Failures per The number of instances a radiolink could not be added Count
Cell or reconfigured on a cell.
Utilization
CS Traffic per Cell The average CS load on the cell in Erlangs. Erlangs
PS Throughput per Cell The average rate of transmission on the uplink for Bytes/
HSUPA and downlink for HSDPA. second
CS RAB Load per Cell The average rate at which CS RABs are attached 1/second
through a cell.
PS RAB Load per Cell The average rate at which PS RABs are attached 1/second
through a cell.

Table 54: Cell KPI (continued)

Network Traffic Rate per Radio The average network load for each radio node. Bytes/
Node second
Active Radio Links per Cell The number of active radiolinks on the cell. Count
RRC Connection Statistics per The number of RRC connection: Count
Cell 1) establishment attempts during InterRAT cell
reselection
2) successfully established during InterRAT cell
reselection
3) attempted during UE registration
4) successfully established during UE registration
5) rejects due to congestion.
11.3 Equipment Counters

SpiderNet supports services node and individual radio node counters for Ethernet ports and their IP
interfaces, and environmental, CPU usage, and memory usage. The services node common equipment
card contains integrated circuits related to switching, front panel connectivity, and the power supply. The
master mezzanine card handles UMTS services.
Table 55: Equipment KPI
KPI Description Units
LAN Device (Ethernet Port)
LAN Device/IP Interface Bytes The total number of bytes transmitted from and Bytes/second
received from this interface.
LAN Device/IP Interface The total number of packets sent from and received by Packets/
Packets this interface. second
LAN Device/IP Interface Errors The total number of outbound packets that could not Errors/
be transmitted because of errors or inbound packets second
that contained errors preventing them from being
deliverable.
Radio Node
Radio Node Interface Bytes The total number of bytes transmitted and received by Bytes/second
this radio node.
Radio Node Interface Packets The total number of packets transmitted and received Packets/
by this radio node. second
Radio Node Interface Errors The total number of errors transmitted and received by Errors/

this radio node. second
Radio Node CPU The percentage of time the radio node CPU is in user‐ Errors/

mode, idle, waiting for IO, in kernel‐mode, and second
swapping.

Table 55: Equipment KPI (continued)

KPI Description Units
Radio Node CPU Load The average load on the CPU of the radio node over Load
Average the last 1, 5, and 15 minutes.
Radio Node Memory Free The percent of the radio node memory available for Percent
use.
Radio Node Memory The percent of the radio node memory in‐use, and free Percent
but not reclaimed.
Radio Node Ambient The ambient temperature of the radio node digital Degrees
Environment baseband card in degrees Celsius. Celsius
Services Node
Common Equipment Card The ambient temperature, and critical, major, and Degrees
Ambient Environment minor overheat thresholds, of the common equipment Celsius
card in degrees Celsius.
Common Equipment Card Core The temperature, and critical, major, and minor Degrees
Environment overheat thresholds, of the common equipment card in Celsius
degrees Celsius.
Mezzanine Card Ambient The ambient temperature, and critical, major, and Degrees
Environment minor overheat thresholds, of the master mezzanine Celsius
card in degrees Celsius.
Services Node CPU Utilization The percentage of time that the master mezzanine card Percent
CPU is in user‐mode, idle, waiting for IO, in kernel‐
mode, and swapping.
Services Node CPU Load The average load on the CPU of the master mezzanine Load
Average card over the last 1, 5, and 15 minutes.
Services Node Memory The percent of memory of the master mezzanine card Percent
Utilization available for use, is in‐use, and free but not reclaimed.


SpiderNet Administrator Guide R2.2 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SpiderNet Administrator Guide R2.2 PDF

Uploaded by

Copyright:

Available Formats

SpiderNet® Management System

Installation and Administration Guide,

Part number: DOC-NMS-ADM-02, Rev. 3

SpiderCloud Wireless, Inc. 3

Chapter 3 Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4 SpiderCloud Wireless, Inc.

4.4.2.2 Editing SMTP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

SpiderCloud Wireless, Inc. 5

5.5.2 Opening a Remote Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

6 SpiderCloud Wireless, Inc.

6.3.7 The Advanced Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

SpiderCloud Wireless, Inc. 7

7.3.3 Adjusting Column Widths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

8 SpiderCloud Wireless, Inc.

9.2.1 Uploading a New Data Model File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

SpiderCloud Wireless, Inc. 9

10 SpiderCloud Wireless, Inc.

This chapter contains the following sections:

1.1 About this Manual

1.2 Product Overview

SpiderCloud Wireless, Inc. 11

Enterprise 1 Enterprise 2 Enterprise 3

1.3 The SpiderNet Interface

12 SpiderCloud Wireless, Inc.

1.3.1 The File Menu

SpiderCloud Wireless, Inc. 13

1.3.2 Network Control

Figure 2 The Network Control Interface

1.3.2.1 The Work Area

14 SpiderCloud Wireless, Inc.

Network Topology (Tree View)

1.3.2.2 Tree View

SpiderCloud Wireless, Inc. 15

1.3.2.3 Alarm Summary

1.3.3 Personalizing the Interface

Toggles the panel between being stationary and free-floating

Toggles the panel between being visible and auto-hide mode

Closes the pane

1.4 Document Conventions

16 SpiderCloud Wireless, Inc.

Find It: Network Control >> Configuration >> System Management

Interpret Find It: instructions as follows:

1.5 Parameter Tables

SpiderCloud Wireless, Inc. 17

Table 3: System Information (continued)

1.5.1 Parameter Values

1.5.2 Regular Expressions

. (period) Matches any character

^ Matches the beginning of a string

18 SpiderCloud Wireless, Inc.

Table 4: Supported Regular Expressions (continued)

1.5.2.1 Regular Expression Examples

SpiderCloud Wireless, Inc. 19

1.6 The SpiderCloud Documentation Set

20 SpiderCloud Wireless, Inc.

This chapter contains the following sections:

2.1 Installation Prerequisites

SpiderCloud Wireless, Inc. 21

2.2 High-Level Installation Overview

22 SpiderCloud Wireless, Inc.

• (Optional) Install a new default data model file.

2.3 Before You Begin

2.4 Installing the Server Software