Professional Documents
Culture Documents
SpiderNet Administrator Guide R2.2 PDF
SpiderNet Administrator Guide R2.2 PDF
© 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
1 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
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.
• 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.
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.
4
1
2
3
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
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.
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.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.
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
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.
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.
./SpiderNet_unix_2_2_0_33_x86.sh
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.
Port
[3306]
Step 7 Do one of the following:
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]
Step 8 Do one of the following:
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 ~]#
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.
standby server, which in turn assumes the active role. Figure 3 shows a high-level logical view of
SpiderNet redundancy.
Active Standby
DB DB
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
• 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.
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.
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.
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 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:
service spidernet_server start
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.
This chapter contains the following sections:
• 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.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
Element Description Valid Options Default
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
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.
To delete a user
Step 1 Click the user name.
Step 2 Click Delete. A confirmation screen opens.
Step 3 Click Yes.
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.
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.
To modify a profile
Step 1 Select the profile and edit as needed.
Step 2 Click Apply.
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
Element Description Valid Options
View Name Name of the current view. String(100)
Related Profiles Profile to associate with the view. Defined user profiles
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.
To delete a view
Step 1 Select the view.
Step 2 Click Delete. A confirmation screen displays.
Step 3 Click Yes.
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
Element Description Valid Options Default
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.
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
Element Description Valid Options
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.
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.4 Email
The Email panel contains tabs for managing email groups and Simple Mail Transfer Protocol (SMTP)
parameters.
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
Element Description Valid Options
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)
The Events Configuration tab contains the following parameters, descriptions, and valid options:
Table 18: Event Configuration Tab Parameters
Element Description Valid Options
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.
Find It: Administration >> Server Settings >> File Transfer Settings
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.
Find It: Administration >> Server Settings >> File Transfer Settings
Find It: Administration >> Server Settings >> File Transfer Settings
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.
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
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
Element Description Valid Options
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.
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:
service spidernet_server stop
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.
service spidernet_server start
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.
The Database Settings panel contains the following parameters, descriptions, and valid options:
Table 24: Database Settings Tab Parameters
Element Description Valid Options
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.
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:
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.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.
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.
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.
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.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.
• 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.
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.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
Element Description Valid Options
Group Name Group name String
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.
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.
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
Element Description Valid Options
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
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.
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.
To delete a site
Step 1 Right-click on the site and select Delete. A confirmation screen opens.
Step 2 Click OK.
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
Zooms in
Zooms out
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.
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.
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
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
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
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
Button Button Function
Adds an object
Deletes an object
Refreshing the screen erases any unsaved configuration changes. To retain configuration
changes, save the configuration before refreshing the screen.
Note
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.
Step 3 Complete the form on the right of the screen and click Save.
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.
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.
Step 4 Complete the form on the right of the screen and click Save.
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.
Find It: Network Control >> Configuration >> IP >> Forwarding Table
Find It: Network Control >> Configuration >> IP >> Forwarding Table
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
Element Description Valid Options
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 >> UMTS >> RAN
The UMTS/RAN tab contains the following parameters, descriptions, and valid options:
Table 42: UMTS/RAN Tab Parameters
Element Description Valid Options
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
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
Element Description Valid Options
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
• 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.
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.
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.
• 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
Element Description Valid Options
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.
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.
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 1 Click Add Task. The Schedule Task screen opens.
Step 2 Select the Reboot radio button and click Next.
Step 3 Select the services node or nodes to apply the template, click >..
Step 4 In the Max Simultaneous Devices text box, enter the number of simultaneous services
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.
Step 7 Complete the Name and Description text boxes.
Step 8 From the Dependency Task drop-down menu, select Next or a previously defined task.
Step 9 Select the Start At time.
Step 10 In the Repeats drop down list, select the schedule regularity.
Step 11 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 12 Click Finish.
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.
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.
Step 9 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 10 Click Finish.
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.
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.
You can manually rotate log file simultaneously for up to fifty services nodes. Optionally can add a
comment to the new log file.
Step 9 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 10 Click Finish.
Note
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.
To edit a task
Step 1 Select the task from the Task List.
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.
To remove a task
Step 1 Select the task from the Task List.
Step 2 Click Remove. A confirmation screen opens.
Step 3 Click OK.
• 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
• eranNotifRanapPsConnectionTerm
• eranNotifRfMgmtFaulted
• eranNotifSoftwareMismatch
• eranNotifSystemMaxSessionRateExceeded
• eranNotifSystemNearingMaxSessionRate
• eranNotifUarfcndlChanged
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.
Syslog settings are configured in the Administration tab. Refer to Section 4.6.2, Syslog Server on
page 62 for more information.
Annotate: opens the Comment dialog box for adding a note and assigning
an action to a user. Alarms screen only
Choose columns: opens the Choose Columns dialog box to select the
columns to display in the report
The Alarm and Events tabs contain the following parameters, descriptions, and valid options:
Table 50: Alarm and Event Parameters
Element Description Valid Options
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
Alarm and event screens are static and do not dynamically refresh. To refresh the screen,
click the Events or Alarms tab again.
Note
Step 3 Select one or more attributes to group. Options are Severity, Ack, Source, Managed
Object, Type, and Group.
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 Yes to save the file in CSV format.
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
• Trap Number: 101
• Description: A new device has been added to SpiderNet.
• Default Severity: Info
• Entered Event: N/A
• 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.
• Corrective Action: None
7.10.3 spiderNetDeviceDiscovered
• Trap Number: 102
• Description: The devices that was added to SpiderNet has been successfully discovered.
• Default Severity: Info
• Entered Event: N/A
• Exit Event: N/A
• Managed Objects: ServicesNode, third-party devices
• System Actions: The SpiderNet system discovered and connected to this device.
• Operational State Changes: Device becomes either IS or OSS.
• Corrective Action: None
7.10.4 spiderNetDeviceDisconnected
• Trap Number: 103
• Description: SpiderNet lost connection to the managed device.
• Default Severity: Major
• Entered Event: N/A
• Exit Event: N/A
• Managed Objects: ServicesNode, third-party devices
• 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.
• Corrective Action: None
7.10.5 spiderNetDeviceDeleted
• Trap Number: 104
• Description: The managed devices was deleted from the system.
• Default Severity: Info
• Entered Event: N/A
• Exit Event: N/A
• Managed Objects: ServicesNode, third-party devices
• System Actions: The device was deleted from the SpiderNet database.
• Operational State Changes: N/A
• Corrective Action: None
7.10.6 spiderNetServerStarted
• Trap Number: 105
• Description: SpiderNet service has started.
• Default Severity: Info
7.10.7 spiderNetServerShutdown
• Trap Number: 106
• Description: SpiderNet service has stopped.
• Default Severity: Major
• Entered Event: N/A
• Exit Event: N/A
• Managed Objects: SpiderNet
• System Actions: The SpiderNet services has stopped. Heartbeat notifications cease.
• Operational State Changes: Server becomes OSS in the NBI OSS.
• Corrective Action: None
Note
To clear PM data
Step 1 Right-click the services node and select Clear PM. A confirmation screen opens.
Step 2 Click Yes.
• 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
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
Button Button Function
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
Button Button Function
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
Zooms in
Zooms out
Scrollbar that adjusts the start or end time of the KPI display
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.
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
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
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/
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
This chapter contains the following sections:
• Section 11.1, System KPIs on page 153
• Section 11.2, Cell KPI on page 156
• Section 11.3, Equipment Counters on page 158
Local Switching Rate The number of locally switched inbound and outbound Bytes/second
bytes.
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.