7signal Sapphire Deployment Guide Release 8.2 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
PREFACE Document scope This document is aimed at people familiarizing themselves with the 7signal Sapphire system before deployment and to aid with the actual deployment. After completion of this document, 7signal Sapphire is installed, up and running and ready for Wi-Fi Performance Management. This document does not describe how the software operates, how to configure testing or how to read the measurements.
Part 15 This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications.
7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
Industry Canada Compliance ● The Industry Canada ID for 7signal Sapphire Eye, Model 2001 (802.11a/b/g/n) is 11766A-INEY2001 ● The 7signal Sapphire Eye Model 2100 (802.11a/b/g/n/ac) Contains IC: 11766A-2100WL. ● The 7signal Sapphire Eye Model 500 (802.11a/b/g/n/ac) Contains IC: 11766A-2100WL. ● The 7signal Sapphire Eye Model 2200 (802.11a/b/g/n/ac) Contains IC: 11766A-2200WL. This Class A digital apparatus complies with Canadian ICES-003.
(i) (ii) (i) (ii) the maximum antenna gain permitted for devices in the bands 5250-5350 MHz and 5470-5725 MHz shall comply with the EIRP limit; and the maximum antenna gain permitted for devices in the band 5725-5825 MHz shall comply with the EIRP limits specified for point-to-point and non point-to-point operation as appropriate. le gain maximal d’antenne permis pour les dispositifs utilisant les bandes 5 250-5 350 MHz et 5 470-5 725 MHz doit se conformer à la limite de p.i.r.e.
7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
EU DECLARATION OF CONFORMITY With regard to the Radio Equipment Directive 2014/53/EC We: 7signal Solutions, Inc. 6155 Rockside Rd, Suite 110 Independence, OH 44131 Declare under our sole responsibility that the products, Sapphire Eye 2200 Sapphire Eye 2100 Sapphire Eye 500 Fulfill the essential requirements of the Radio Equipment Directive/53/EC. The following standards were applied: Radio EN 300.328-2 V2.1.1 (2016); EN 301 893 V2.1.0 (2017-03); EN 302 502 V1.2.1 (2008-07) EMC EN 301 489-17 v3.1.
Safety EN60950-1:2013, A2; LVD 2006/95/EC The conformity assessment procedure referred to in Article 3 and Annex II of the Radio Equipment Directive 2014/53/EC has been followed.
7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
Compliance statements for India, Singapore, China for the manual INDIA: Model 2100 operating at 2400-2483.5MHz: ETA #: 2923/17-RLO(WR) Model 2100 operating at 5180-5320MHz & 5745-5825MHz: ETA #: 2935/17-RLO(WR) Singapore: Model 2100: Complies with IMDA Standards DA103787 China: Model 2100: CMIIT ID: 2018AJ1640 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
Contact information Contact us at 7signal ● by mail: ● by email: ● by phone: ● support: 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA info@7signal.com 216-777-2900 support@7signal.com 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
TABLE OF CONTENTS 1 7signal Sapphire solution 1.1 Solution Overview 1.2 Hardware 1.2.1 802.11a/b/g/n Indoor Eye (Sapphire Eye 2000) 1.2.2 802.11a/b/g/n/ac wave-1 Gigabit Indoor Eye (Sapphire Eye 2100) 1.2.3 802.11a/b/g/n/ac wave-1 Gigabit Indoor Eye (Sapphire Eye 500) 1.2.4 802.11a/b/g/n/ac wave-2 Gigabit Indoor Eye (Sapphire Eye 2200) 1 2 2 2 2 3 3 2 Requirements 2.1 Carat server requirements 2.2 Sonar server requirements 2.3 Firewall settings 2.4 Database configuration 2.4.
3 7signal Sapphire Connectivity 3.1 Communication security 3.2 Supportive connections 3.2.1 SSH for Eye 4 Installing 7signal Sapphire 4.1 Operating System installation tips 4.1.1 Required packages 4.1.2 Hard disk partitioning 4.1.3 Server security 4.1.4 Operating system limits 4.1.5 SELinux and nginx HTTP server 4.2 Setting up Eyes 4.2.1 Change default SSH password 4.2.2 Static IP address configuration 4.3 Configuring Eyes to connect a Carat server 4.3.1 Manual configuration 4.3.
4.4 Mounting Eyes 4.4.1 Indoor Eye (Eye 2000/Eye 2100/Eye 2200) Ceiling Installation 4.4.2 Eye Model 500 Table Top or Wall Mount Installation 4.4.3 Eye Model 500 Ceiling Mount Option 4.4.4 Eye installation examples 4.5 Installing 7signal Sapphire software 4.5.1 Installation from VM templates 4.5.2 Java installation 4.5.3 DB2 and Sapphire DBMS installation 4.5.4 Carat server installation 4.5.5 Application server and web app installation 4.5.
5.3.5 Sonar upgrade 5.4 Start Sapphire solution (Linux) 5.5 Eye upgrade 5.5.1 Eye upgrade (Configurator) 5.5.2 Eye upgrade (command line) 5.6 Start Automated Testing 31 31 32 32 34 35 6 Uninstalling Sapphire 6.1 Pre 8.2 releases 6.1.1 Uninstall Analyzer server 6.1.2 Uninstall Carat server 6.1.3 Uninstall DBMS 6.1.4 Uninstall Sonar 36 36 36 36 37 37 7 Log Settings 7.1 Carat server log 7.2 Eye 1000/2000 log 7.3 Eye 2100/500/2200 log 7.3.1 Application logs 7.3.
7.4 Application server log 7.5 Sonar log (Linux) 7.6 Eye 2100/500/2200 remote syslog configuration 39 39 40 8 Sapphire Process Management 8.1 Carat 8.2 Application server 8.3 Sonar 8.4 Eye 44 44 44 44 44 9 Troubleshoot 9.1 Cannot add Eye unit 9.2 No access to Sonar server, active test failed 9.3 Web app cannot connect to Carat server 9.4 Eye IP address forgotten 9.4.1 Reset Eye IP configuration 9.5 Collecting information for further analysis 45 45 45 45 45 45 46 10 Command-line utility for Eye 10.
10.2 7config ip command group 10.3 Keys command group 10.4 AP command group 10.5 Conn command group 10.6 Run command group 10.7 Txp command group 10.8 Log command group 47 48 48 48 49 50 51 11 Command-line tool for database management 11.1 Logsetup command 11.2 Backup command group 11.3 Show command group 11.4 Reinit command group 11.5 Reorg command group 53 53 53 54 55 55 12 Command-line tool for carat server 12.1 License command group 12.2 Integritycheck command group 12.3 Ip command group 12.
12.5 Memoryconf command group 57 13 Updating encryption certificates 13.1 Updating Carat server certificates 13.2 Updating web app certificates 13.3 Updating Eye certificates 13.4 Installing custom HTTPS certificate to Application server 58 58 58 58 59 14 Database maintenance 14.1 Online data purge 14.1.1 Required database indexes 14.1.2 Executing data purge 14.2 Table / index reorganization 14.2.1 Executing online reorganization 14.2.2 Executing offline table reorganization 14.2.
14.3.4 Scheduling backups 14.3.5 Deleting old backups on the remote storage server 14.4 Collecting statistics 14.4.1 Executing statistics collection 14.4.2 Scheduling statistics collection 14.5 Watching DB and log filesystem usage 14.5.1 Example configurations 14.5.2 Scheduling DB2 watchdog 14.6 All together 68 69 69 69 70 70 71 71 71 Appendix A. Logical connections 73 Appendix B. Bandwidth requirements 14.6.1 Eye – Sonar 14.6.2 Eye – Carat/Carat – Eye 14.6.
1 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
7SIGNAL SAPPHIRE SOLUTION 7signal Sapphire provides you a new way to continuously and automatically measure the health and quality of a wireless network from the user's perspective. Companies and their business processes are becoming increasingly dependent on the performance and service quality of their wireless networks. Thanks to the Sapphire solution, companies can integrate the quality management of wireless networks with their existing IT and communications technology services.
detect network performance and quality-of-service (QoS) issues. The solution can also produce proactive statistics on the predicted user experience of network performance, which enables the company to increase network capacity before the users notice a loss of performance. In user emulation tests, also known as active tests, the Eye connects to the Sonar over the wireless network and uses it like an ordinary production service.
retransmissions, and packet loss are taken into account, in addition to other commonly measured parameters. 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
1.1 Solution Overview The 7signal Sapphire quality monitoring solution consists of the Sapphire Eye monitoring sensors, Sonar test servers, the Sapphire Carat management software, and Sapphire web applications for viewing and reporting on the results. 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
1.2 Hardware The 7signal Sapphire Eye is a wireless probe or a monitoring station that is installed in a central position within the WLAN network. Currently there are five different hardware variants: the Standard Eye supporting 802.11a/b/g standards, Standard Eye supporting 802.11a/b/g/n standards, Indoor Eye supporting 802.11a/b/g/n standards and Gigabit Indoor Eyes supporting 802.11a/b/g/n/ac standards. 1.2.1 802.11a/b/g/n Indoor Eye (Sapphire Eye 2000) 802.
1.2.2 802.11a/b/g/n/ac wave-1 Gigabit Indoor Eye (Sapphire Eye 2100) 802.11a/b/g/n/ac version of the Eye has the following main features (partly optional): ● Mechanical parts injection molded polycarbonate plastic ● Linux computer, 1GB (2GB Optional) Flash memory, 512MB (1GB Optional) DDR3 SDRAM ● Gigabit Ethernet port (RJ-45) ● Power Over Ethernet (PoE+) ● Gigabit WLAN radio module, 802.11 a/b/g/n/ac support (2.4 GHz, 5.180 GHz - 5.
● Reset button 1.2.4 802.11a/b/g/n/ac wave-2 Gigabit Indoor Eye (Sapphire Eye 2200) 802.11a/b/g/n/ac wave-2 version of the Eye has the following main features (partly optional): ● Mechanical parts injection molded polycarbonate plastic ● Linux computer, 1GB (2GB Optional) Flash memory, 512MB (1GB Optional) DDR3 SDRAM ● Gigabit Ethernet port (RJ-45) ● Power Over Ethernet (PoE+) ● 1.733 Gigabit WLAN radio module, 802.11 a/b/g/n/ac wave2 support (2.4 GHz, 5.180-5.
REQUIREMENTS 2.1 Carat server requirements A cloud-based deployment is preferable because it ensures your software is always kept up to date. However, if you need to install a servers inside your network for security reasons, then you must follow the requirements specified in the table below. Basic server dimensioning guidelines: # of Sapphire Eyes CPU Cores CPU Type RAM DB Disc Space / IOPS Logfile Disc Space / IOPS Backup Disc Space / IOPS 1-25 2 Intel Xeon E5-2640 @ 2.
51-100 4 Intel Xeon E5-2640 @ 2.50GHz (Sandy Bridge) or newer 64GB 300GB / 5000 300GB / 300 600GB / 150 101-150 6 Intel Xeon E5-2697 v2 @ 2.70GHz (Ivy Bridge) or newer 96GB 450GB / 7500 450GB / 500 900GB / 150 151-200 6 Intel Xeon E5-2697A v4 @ 2.60GHz (Broadwell) or newer 128GB 600GB / 10000 450GB / 750 1.2TB / 150 201-250 6 Intel Xeon Gold 6144 @ 3.50GHz (Skylake SP) or newer 176GB 750GB / 12500 750GB / 850 1.
2.2 Sonar server requirements Sonar is the end-point software for Sapphire active tests. The Sonar server software runs on the Linux operating system and can be installed on dedicated server or virtual environment. Basic server dimensioning guidelines: Other generic requirements are: • Intel and AMD processors • 1Gpbs Ethernet • CentOS 6/7 or Red Hat Enterprise Linux 6/7 • When the same Sonar is used also by significant amount of Mobile Eye traffic, resource requirements are higher.
2.3 Firewall settings The following ports should be opened in firewalls: Source IP/Mask Destination IP/Mask Protocol/Port Comments Eye Ethernet IP Addr/32 redirector.7signal.
Browser (host) IP Addr/32 Carat IP Addr/32 TCP/443 Configurator/Analyzer/EyeQ (HTTPS) Eye Wi-Fi IP Addr/32 Sonar server IP Addr/32 TCP/80 Sonar tests Eye Ethernet IP Addr/32 Sonar server IP Addr/32 TCP/80 Sonar Ethernet tests Eye Wi-Fi IP Addr/32 Sonar server IP Addr/32 UDP/50000-50300 Sonar VoIP (UL) Eye Ethernet IP Addr/32 Sonar server IP Addr/32 UDP/50000-50300 Sonar Ethernet VoIP (UL) Eye Wi-Fi IP Addr/32 Sonar server IP Addr/32 ICMP Sonar RTT Eye Ethernet IP Addr/32 Sonar serve
Carat IP Addr/32 NTP server IP Addr/32 UDP/123 NTP Sonar server IP Addr/32 DNS server IP Addr/32 TCP/UDP/53 DNS Carat IP Addr/32 DNS server IP Addr/32 TCP/UDP/53 DNS Carat IP Addr/32 SNMP server IP Addr/32 UDP/162 SNMP Trap Carat IP Addr/32 SYSLOG server IP Addr/32 UDP/514 SYSLOG Carat IP Addr/32 Webhook receiver IP Addr/32 TCP/XXX Webhook alarm (e.g. Slack) 2.4 Database configuration For optimal performance, 7signal suggests the following DB2 database configuration settings: 2.4.
2.4.2 Database configuration for MEAS7 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
2.4.3 Database configuration for MGMT7 2.5 GDPR compliance Important: If GDPR mode is set on, the Sapphire server must be located in an EU country, or be otherwise certified compliant, e.g. Privacy Shield in US. Important compliance GDPR information can be found in Carat User Guide. 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
Due to EU General Data Protection Regulation (GDPR), it is extremely important that, in addition to other measures you take to comply with the GDPR, you configure Sapphire so that your compliance with GDPR is not adversely affected. Sapphire provides two modes for GDPR operation: on or off: ● When GDPR is off, Sapphire does not collect any client data from Eyes located in EU countries. This is the default mode. ● When GDPR is on, Sapphire collects client data from all countries, including EU.
● ● ● Carat server is in US, Privacy Shield compliant organization, some Eyes are in US, some Eyes are in EU o GDPR mode can be “on”. Client data will be collected from Eyes located in EU. Carat server in EU, all Eyes are in EU o GDPR mode should be “on” Carat server in EU, some Eyes are in US, some Eyes are in EU o GDPR mode should be “on” 3 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
7SIGNAL SAPPHIRE CONNECTIVITY 3.1 Communication security All connections containing meaningful traffic are encrypted. The cryptographic protocols used are TLS and SSL. The PKI infrastructure (certificates) are used throughout the solution. Every customer has a unique set of certificates, delivered within containers called certificate packages. It is not possible to use the delivered certificates to decrypt traffic on other 7signal Sapphire systems.
3.2 Supportive connections 3.2.1 SSH for Eye Static IP address configuration can be done with the Eye CLI 7config utility. Eye firmware can also be managed with SSH (not recommended normally). 4 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
INSTALLING 7SIGNAL SAPPHIRE 4.1 Operating System installation tips 4.1.1 Required packages A minimal Linux installation is recommended – just installing the packages that are required by the Sapphire software. For example, the CentOS Minimal CD distribution is suitable: http://wiki.centos.org/Manuals/ReleaseNotes/CentOSMinimalCD6.5 or the near equivalent “Minimal” installation set radio button.
# yum install pam.
# yum install rh-nginx112 Install the following packages by using yum: # yum install pam.i686 numactl unzip system-config-firewall-tui xorg-x11-server-Xvfb libXtst libXrender policycoreutils-python Sonar installations: Install the following packages by using yum: # yum install system-config-firewall-tui 4.1.2 Hard disk partitioning This chapter gives some guidelines for hard disk partitioning. It is assumed that readers have comprehensive knowledge about Linux file systems, RAID, LVM and disk partitioning.
Default partitioning suggested by the OS installer is suitable for most cases. As laptops are rarely equipped with multiple hard drives, RAID configurations are not possible. Server installations At least one RAID array is recommended: 7signal databases and database log files should reside on a file system on top of RAIDed disks (RAID level 1 or higher, LVM on top of RAID).
o Sapphire databases are installed to /opt/7signal/databases (on LV2) (7signal DBMS installer asks for location of databases and database log files) Sapphire database backups will be placed on /opt/7signal/backups (on LV3) o Example #2 ● Five physical disks ● Boot and swap partitions ● RAID1 on top of two disks, RAID5 on top of three disks, all formatted as LVM physical volumes ● Physical volume on RAID1 has two logical volumes o 50% of space for OS installation, mount point “/” (LV1) o 50% of space for d
In CentOS/Red Hat Enterprise Linux, the firewall configuration is /etc/sysconfig/iptables (configured via system-config-firewall-tui). The file could look like the following: Restricting Analyzer/EyeQ/Configurator access: It might make sense to restrict Analyzer/EyeQ/Configurator access to certain IP addresses or IP networks. Edit the rules of TCP ports 80 and 443 by adding a source address filter (-s option). -A INPUT -m state --state NEW -m tcp -p tcp -s 199.95.207.
Example 2: Allow access from address 199.95.207.0/24 network only: -A INPUT -m state --state NEW -m tcp -p tcp -s 199.95.207.0/24 --dport 80 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp -s 199.95.207.0/24 --dport 443 -j ACCEPT If any changes were made to iptables configuration rules, the added/modified rules need to be reloaded: # service iptables reload SSH connectivity Disable SSH root logins Super user (root) SSH logins are enabled by default in CentOS and RHEL.
Save the file and restart SSH daemon: # service sshd restart Consider using SSH keys instead of password login Generally, an SSH public key login is more secure than password logins. 4.1.4 Operating system limits The default number of allowed OS threads may not be sufficient for larger Sapphire installations. It is suggested to double the allowed “carat7” process threads from 1024 to 2048. Open the file /etc/security/limits.d/90-nproc.conf in an editor. Add the line in red to the file and save the file.
4.1.5 SELinux and nginx HTTP server If SELinux is in enforcing mode, you may see ”502 Bad Gateway” error when trying to access web apps. In order to avoid this error, execute the following commands: # sudo cat /var/log/audit/audit.log | grep nginx | grep denied | audit2allow -M mynginx # sudo semodule -i mynginx.pp 4.2 Setting up Eyes 4.2.1 Change default SSH password The Eye root default password is ‘7signal’. It is strongly advised to change this password as it is a factory default for every Eye unit.
# passwd Enter new password 4.2.2 Static IP address configuration By default, The Eyes have DHCP enabled on their Ethernet interface. In order to configure a static IP address to an Eye: Step 1: Connect to the Eye unit # ssh root@ Step 2: Configure IP settings Set the IP address of the Eye management interface. DO NOT REBOOT between configuration steps below. Type N to “IP configuration changed.
Set the port of the Eye management interface (optional – default is TCP/7999): # 7config ip set port Verify all the entered settings with the ‘show’ command: # 7config ip show Disable DHCP #7config ip set dhcp off Step 3: Reboot Eye unit Reboot the Eye unit to make the changes effective: # reboot 4.3 Configuring Eyes to connect a Carat server Starting with Sapphire release 5.2, it is now possible to configure the Eyes to connect to the Carat server (before release 5.
2. DHCP based configuration. The Eyes obtain the Carat IP address, port numbers and organization name by utilizing DHCP options 60 and 43 as described below. 3. DNS redirector based configuration. The Eyes obtain Carat IP address, port numbers and organization name by utilizing specially configured DNS server as described below. If the Eye is not already provisioned in the Carat server configuration, the Carat server will add the Eye automatically to its network topology configuration.
3. Reboot Eye unit: # reboot An example: # 7config conn carat set 192.168.10.10:7799:7800:7SignalSolutionsInc After reboot, the Eye establishes a connection to the Carat server on IP address 192.168.10.10 in the example above. If the Eye is not already in the Carat server configuration, it will be added to the organization 7signalSolutionsInc. 4.3.2 DHCP based configuration Eyes can obtain Carat server connection information by utilizing DHCP options 60 and 43.
For ISC DHCP server, the content of the DHCP server configuration file would be like the following: 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
For DHCP server in Windows Server 2012 R2 Standard, below are the steps to configure the DHCP server. The premise is that DHCP is already installed on Windows server and DHCP scope is setup. 1. Define Vendor Classes ● In Server Manager, navigate to “Tools -> DHCP” to launch DHCP server window. ● From left-side navigation bar, select the windows server. Right-click “IPv4” and select “Define Vendor Classes”.
● Add another vendor class “SevenSignal”, which was used by DHCP server to send Carat server configurations to Eyes. 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
2. Set Predefined Options ● Right-click “IPv4” and select “Set Predefined Options”. ● Choose “SevenSignal” from Option Class pull-down menu. Add the following four policies under this class: Name Data type Code Value ddress ess _server_IP_address> ort efault-port 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
ganization ization_name> 3. Add policy ● From left-side navigation bar, select “Policies” under “Scope”. Right-click it and select “New Policies”. ● Type in a Policy name, for example, “Send Carat configuration to Eyes”. Click Next. ● Add the following condition: Criteria: Vendor Class Operator: Equals Value: “SevenSignal-Eye” 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
● ● Click Ok and then Next. Configure an IP address range for the Policy. Configure Settings for the policy. 1) Select “006 DNS servers” under “DHCP Standard Options”. Add DNS servers according to your network configurations. 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
2) Select “043 Vendor Specific Info” under “DHCP standard Options”. Option 43 is in TLV format: (byte) (byte) . For example, is options set in Step 2 are: Code Data type ess value 21 st In TLV format, they are: Tag ID Tag length data vector 0 15 3 74 54 65 73 74 Binary value to input in 043 is “01 08 01 09 00 15 02 02 1e 77 03 02 1e 78 04 08 54 65 73 74 54 65 73 74”. 7signal Solutions Inc.
3) Choose “SevenSignal” from Vendor class pull-down menu, select options 001, 002, 003, and 004 under this class. Click Next, and then click Finish. The policy is added. 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
4.3.3 DNS redirector based configuration The Eyes can obtain their Carat server connection information from a specially configured DNS server, called a DNS redirector service. DNS redirector service can be hosted by the Carat server itself, or any other (Linux) host accessible for Eye monitoring stations. The DNS redirector service has a record for each Eye. The record contains the IP address of the Carat server as an A record, and port numbers and organization name as TXT records.
Example named configuration file /etc/named.conf: 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
3. Create zone configuration file. Zone information files are located in directory /var/named. In this example, the name of the zone information file must be eye.7signal.com.zone. Example eye.7signal.com zone file /var/named/eye.7signal.com.zone 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
When configuring an Eye that should receive Carat connection information from the DNS redirector, add a new record to the end of the file: Eye-. eye.7signal.com. IN A IN TXT "carat-port=7799" IN TXT "carat-default-port=7800" IN TXT "carat-organization=" 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
After adding a new record to zone file, the named server needs to be restarted: # service named restart Configuring Eyes to obtain Carat connection information from DNS redirector service By default, the Eyes try to obtain Carat connection information from the DNS redirector service dns.7signal.com. The default DNS redirector service can be changed by using 7config utility. 1. 2. Login to Eye by using SSH. Issue command: 3.
Removing Eye from DNS redirector configuration 1. 2. Remove Eye records from zone file Restart named server 3. 4. # service named restart Login to Eye by using SSH Remove DNS redirector configuration by issuing a command: 5. # 7config conn dns remove Remove Carat connection configuration by using a command: 6. # 7config conn carat remove Reboot the Eye: # reboot 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
4.4 Mounting Eyes Mount Sapphire Eyes in the most centralized location of the WLAN area. The Eye can be installed on the ceiling, wall (in a horizontal orientation) or mast. Sapphire Eyes have extremely sensitive radio technology inside 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
● ● The receiving signal is 10-20dB stronger than the basic WLAN end-user The transmitted signal is 5-6dB stronger at the access point side than with the basic WLAN end-user For best accuracy of the WLAN performance, the Sapphire Eye location should be selected so that: ● The average signal level for the managed WLAN access points are between -65dBm and -30dBm. The distance from any access point should be > 10ft/3m.
7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
4.4.1 Indoor Eye (Eye 2000/Eye 2100/Eye 2200) Ceiling Installation Attach the Indoor Eye sliding bracket onto a suspended ceiling T-rail using the two Twist Clips included with the Eye, and two ¼-inch nuts. Or, secure the bracket with screws to any solid ceiling structure. Slide the Indoor Eye onto the bracket and secure it with the #6-32 x 5/16” Phillips head screw. 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
4.4.2 Eye Model 500 Table Top or Wall Mount Installation The Model 500 sits on 4 rubber feet on a table top 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
Or, mounts on a wall in any one of 4 orientations using two wall anchors with two #6 screw heads inserted in the two 4-way keyhole slots on the bottom of the unit. 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
4.4.3 Eye Model 500 Ceiling Mount Option The Model 500 may also be mounted on suspended ceiling. The standard clips are for 1” T-rail. 4.4.4 Eye installation examples The Site Survey results are valuable for Eye location estimation. The Eye location is good if the Site Survey heat map shows >-80dBm signal level from all the access points. 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
The Site Survey results are valuable for Eye location selection 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
Verify the signal levels from the far end access points 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
The external antenna is useful in the environment where shafts or thick walls are attenuating radio too much. 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
4.5 Installing 7signal Sapphire software The 7signal Sapphire software can be downloaded from 7signal Share File. Root privileges are needed for installation of Sapphire components. Installation steps: 1. Install DB2 and Sapphire DBMS 2. Install Carat server software 3. Install Application Server and web applications 4.5.1 Installation from VM templates The 7signal Sapphire software can be installed from pre-installed VM templates.
The username and password for both the Carat Server and Sonar Server VM’s are shown below: Username: 7admin (with sudo access) Password: 7admin NOTE! It is recommended to change VM’s default passwords. Root password can be found from the VM template Readme document 3. 4. Specifications Settings of the virtual images are listed below. Carat Server VM (1-25 Eyes): CPU 4 RAM 6114MB HD 450GB (thin provisioned) Sonar Server VM: CPU 4 RAM 6114MB HD 40GB (thin provisioned) This is default configuration.
# system-config-network Fill in the Static IP, Netmask, Default gateway IP, Primary DNS Server and/or Sedondary DNS Server according to your network settings: If VM is logged in via SSH, please execute a reboot after network configuration is saved. After a reboot, eth0 IP address is changed to the Static IP.
Step 6: To this point, configurations on Carat server VM is done. Please launch and login to Carat Configurator using the default username and password “admin”. Step 8: Sonar VM configuration: Please follow steps 1 and 2 to login to Sonar VM and assign a static IP address to Sonar VM. After this, please use command “7sonar status” to check if Sonar service is running: # 7sonar status 7signal Sonar is running Done! 4.5.2 Java installation 7signal Sapphire requires Orace Java Runtime Environment.
Please verify the following items: ● The IP address of the server must be resolvable to its DNS name. This can be achieved by the following procedures: o Server has been added to DNS o Hosts file contains the DNS name. ▪ cat /etc/hosts ▪ edit the hosts file if needed Installation The DB2 database and Sapphire DBMS are available in two RPM files. Copy 7signal-DB2 and 7signal-DBMS RPMs from delivery medium to for example /root directory.
Enter location for databases [/home/db7sign]: (See NOTE below) The database location defaults to the /home file system just like the database logs that are configured below. NOTE! This default database location is not recommended, if the /home file system is not backed up or otherwise replicated, or does not have enough disk space. The logs and the actual database should always reside in separate file systems, preferably on RAIDed, separate physical devices.
Enter location for Management DB log files [/home/db7sign/db7sign/NODE0000/SQL00001/SQLOGDIR/]: OK. Using default. Enter location for Measurement DB log files [/home/db7sign/db7sign/NODE0000/SQL00002/SQLOGDIR/]: OK. Using default. Enter location for Security DB log files [/home/db7sign/db7sign/NODE0000/SQL00003/SQLOGDIR/]: OK. Using default. The install is now complete. The DB2 is now installed, up and running. 4.5.
If you wish to install sensor softwares to SW repository of the Carat server, issue the command: # yum install 7signal-Eye-x.x-y.el7.centos.noarch.rpm Step 2: Install the certificate bundle and license file: The certificate package can be downloaded from 7signal Share File. Install the certificates by issuing the command: # 7carat certificate set The license file is created for each customer individually. It is in the same delivery medium with the certificate packages.
# 7carat start 4.5.5 Application server and web app installation Copy 7signal-Application-Server, 7signal-nginx-conf, 7signal-AnalyzerApp, 7signal-ConfiguratorApp, 7signal-EmeraldApp and 7signal-EyeQApp RPMs from the delivery medium to e.g. /root directory. Step 1: Install Application Server Issue command: # yum install 7signal-Application-Server-x.x.x.x-y.el7.noarch.rpm Step 2: Install web apps: Issue command: # yum install 7signal-ConfiguratorApp-x.x.x.x-y.el7.noarch.rpm 7signal-AnalyzerApp-x.x.x.x-y.
Step 4: Setup maximum memory Configure maximum memory (RAM) that Carat server can use by issuing command: # 7analyzer memoryconf Step 5: Restart Application Server Issue command: # 7analyzer restart Notice: If you see “502 Bad Gateway” error when trying to access web apps, see chapter 4.1.5. Step 6: Install nginx configuration Sapphire uses nginx web server as a proxy. The Sapphire nginx configation can be installed by issuing command: # yum install 7signal-nginx-conf-x.x.x.x-y.el7.noarch.
On RHEL, the nginx server configuration directory is not necessarily /etc/nginx. You may need to find out the correct configuration directory and copy the /etc/nginx/conf.d/tomcat-proxy.conf to conf.d directory of the RHEL ngihx configuration directory. 4.5.6 Sonar Installation Copy 7signal-Sonar RPM from the delivery medium e.g. to /home directory. Step 1: Install Sonar Issue command: # yum install 7signal-Sonar-x.x.x.x-y.el7.centos.x86_64.
# 7sonar loglevel Log level is INFO Use “7sonar config set” to change the configuration parameters: ● 7sonar config set name : change the Sonar name ● 7sonar config set port : change the Sonar TCP port number ● 7sonar config set maxclients : change the maximum number of concurrent clients ● 7sonar mosstart : change the first UDP port number in MOS UDP port pool ● 7sonar mossize : change the MOS UDP port pool size Use
UPGRADING SAPPHIRE 5.1 Copy the latest Sapphire release to the hard disk Step 1: Download new Sapphire version from 7signal Share File Step 2: Copy Sapphire software to the Carat server IMPORTANT: When upgrading between major versions a new Sapphire Software license file will be required. 5.2 Stop Sapphire solution (Linux) Step 1: Stop the Carat server: Stop the Carat server by issuing the command: # 7carat stop 7signal Solutions Inc.
Step 2: Stop the Application Server server: Stop the Analyzer server by issuing the command: # 7analyzer stop 5.3 Upgrade from 8.1 to 8.2 Sapphire installers have been changed from proprietary binary installers to standard RPM installers in release 8.2. All components except DBMS must be re-installed. 5.3.1 Java installation 7signal Sapphire requires Orace Java Runtime Environment. Download the Java 8 Runtime from Oracle website https://www.oracle.com/technetwork/java/javase/downloads/index.html .
Important: Backup the databases prior to upgrade, either by using “7db backup” command or 7BUtool.sh utility script. When upgrading to 8.2, you must install 7signal-DB2 and 7signal-DBMS RPMs: ● Installing DB2 by using 7signal-DB2 RPM does not actually install the DB2, but it updates RPM database, and all future dependencies will be handled correctly by RPM.
Issue command: # 7db upgrade 5.3.3 Carat server upgrade Step 1: Uninstall Carat Uninstall Carat as described in the chapter 6.1.2 Step 2: Install Carat Install Carat as described in the chapter 4.5.4 5.3.4 Analyzer server upgrade Step 1: Uninstall Analyzer Uninstall Analyzer as described in the chapter 6.1.1 Step 2: Install Application server and web appps Install Application server and web apps as described in the chapter 4.5.5 7signal Solutions Inc.
5.3.5 Sonar upgrade Step 1: Uninstall Sonar Uninstall Sonar as described in the chapter 6.1.4 Step 2: Install Sonar Install Sonar as described in the chapter 4.5.6 5.4 Start Sapphire solution (Linux) After all components have been upgraded, start the Carat and Application servers. Step 1: Start the Carat server: Start the Carat server by issuing the command: # 7carat start Step 2: Start the Application server: Start the Application server by issuing the command: 7signal Solutions Inc.
# 7analyzer start 5.5 Eye upgrade 5.5.1 Eye upgrade (Configurator) Note: The Eye SW version number in these instructions may not be the one that is going to be installed. However, the instructions are applicable to all SW versions. Step 1: Start the Configurator: Step 2: If necessary, install new software version: This step needs to be executed only if Carat was updated without in-bundled Eye software packages (i.e. “full” version was not used). Login as solution admin user.
- o MPU1 installers are for 802.11a/b/g/n/ac Eyes Select the desired installer, select “Open” 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
- Eye software versions available is Carat are populated on the list: 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
- Import installers for all needed platforms Close the “Eye SW repository management” view. Step 3: Upgrade Eye software to Eye units: Login as configurator user. Open the “Manage | Eye Software Management | Eye software update” view If a software update is available for some Eyes, the software version and the name of the Eye unit appear on a pop-up window: 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
- To update the software version to Eye, select “OK” Software is uploaded and installed to Eye units 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
- After the installation is complete, close the “Eye software update view” 5.5.2 Eye upgrade (command line) Step 1: Change to the Eye installer directory: # cd /root/SapphireXXYY/ Carat_CD/Eye Step 2: Copy the SW to Eye unit: 802.11a/b/g/n units (E2000): # scp 7signal-eye-v0X.YY- APU3– installer.bin root@:/nand 802.11a/b/g/n/ac units (E2100, E2200 and E500): # scp 7signal-eye-v0X.YY- MPU1– installer.
Step 4: Install the Eye new SW package: 802.11a/b/g unit and 802.11a/b/g/n units: [root@Eye]# cd /nand 802.11a/b/g/n unit: [root@Eye]# ./7signal-eye-v0X.YY-APU3–installer.bin 802.11a/b/g/n/ac unit: [root@Eye]# ./7signal-eye-v0X.YY-MPU1–installer.bin Step 5: Restart: 802.11a/b/g unit and 802.11a/b/g/n units (E1000 / E2000): [root@Eye]# reboot 5.6 Start Automated Testing 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
Automated testing is in a stopped state after the Sapphire has been upgraded. Step 1: Start Configurator: Step 2: Start Automated Testing: Select “Tools | Start Automated Testing”. 6 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
UNINSTALLING SAPPHIRE 6.1 Pre 8.2 releases 6.1.1 Uninstall Analyzer server Step 1: Stop Analyzer server: Login to Carat host and stop the Analyzer server by issuing the command: # 7analyzer stop Step 2: Uninstall Analyzer server: Change to Analyzer installation directory: # cd Uninstall the Analyzer server by issuing the command: # ./analyzer_server_uninstall.sh 7signal Solutions Inc.
The uninstaller script starts. Confirm uninstall by entering “y”: 7signal Sapphire Analyzer server will be removed (/opt/7signal/Analyzer). Are you sure [y/N]? y The uninstallation is finished when the script is ready. 6.1.2 Uninstall Carat server Step 1: Stop Carat server: Login to Carat host and stop the Carat server by issuing the command: # 7carat stop Step 2: Uninstall Carat server: Change to Carat installation directory: # cd //vX.X-Y.
The uninstaller script starts. Confirm uninstall by entering “y”: 7signal Sapphire Carat, related user account and home directory will be removed. Are you sure [y/N]? y The uninstallation is finished when the script is ready. 6.1.3 Uninstall DBMS The Carat and Application servers must be uninstalled before DBMS can be uninstalled. See sections 6.1.1 and 6.1.2. Login to Carat host 6and change to DBMS installation directory.
The uninstaller script starts. Confirm uninstall by entering “y”: The uninstallation is finished when the script is ready. 6.1.4 Uninstall Sonar Step 1: Stop Sonar server: Login to Sonar host and stop the Sonar server by issuing the command: # service 7signalSonar stop Step 2: Uninstall Sonar server: Change to Sonar installation directory (e.g. /opt/7signal/Sonar): # cd / Uninstall Sonar by issuing the command: # ./sonar_uninstall.sh The uninstaller script starts.
7 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
LOG SETTINGS All 7signal Sapphire elements have logging capability. 7.1 Carat server log The log file - server.log - is located in /opt/7signal/Carat/7signal. The directory contains older log files as well, named server.log.* where by default the asterisk (*) is in range of 1..5. Altogether, there is one active log file named server.log and five files for circulating the files. The oldest log gets overwritten.
Notice that Carat server has to be restarted in order to bring the changed log level into use. 7.2 Eye 1000/2000 log NOTE: As this is for Eye logging, all the below commands are to be entered at the prompt of the Eye, not on the Carat or Sonar server.
To change logging back to ring buffer, use the following command: # 7config log set target buffer The following command shows the log level and log target information: # 7config log show 7.3 Eye 2100/500/2200 log NOTE: As this is for Eye logging, all the below commands are to be entered at the prompt of the Eye, not on the Carat or Sonar server. 7.3.1 Application logs By default, application logs are stored to rotating log files in RAM file system /tmp directory.
In order to change logging to persistent storage, issue the following command: # 7config log set target persistent To change logging back to RAM file system, use the following command: # 7config log set target buffer The following command shows the log level and log target information: # 7config log show 7.3.2 System logs Eye 2100/500/2200 store system logs always to persistent storage. The name of the log file is /var/log/syslog. 7.
# 7analyzer log and for continuous log monitoring: # 7analyzer log -f 7.5 Sonar log (Linux) The log file - sonar-server.log - is located by default in // Sonar/log. 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
7.6 Eye 2100/500/2200 remote syslog configuration Eye 2100/500/2200 support remote syslogging. The following instructions show how to configure it.
Sep 18 10:58:33 localhost rsyslogd: [origin software="rsyslogd" swVersion="7.4.10" x-pid="5860" x-info="http://www.rsyslog.com"] start Step 2: Create TLS certificates Create TLS certificates for remote syslogging. Use 7signalSyslogCertTool.sh, the tool will create server and client certificates. It also creates a CA if necessary. You cand find the 7signalSyslogCertTool.sh on the distribution media “Utilities/Script/Syslog” directory. Install gnutls.utils first, 7signalSyslogCertTool.
For example, the command below creates a CA (if it is not already created in directory /root/newcerts), CA will be valid about 10 years, certificates will be valid about 5 years, and both client and the server certificates will be created. Syslog server IP address will be 10.10.10.147. $ ./7signalSyslogCertTool.sh -a 3650 -v 1800 -s 10.10.10.147 -c \ /
/ newcerts The following directory structure will be created in //newcerts: |---- CA | |---- 7signal-syslog-ca-key.Copy the server certificate, private key and CA certificate to the logging server, in this example 10.10.10.147: $ scp /
/ newcerts/CA/7signal-syslog-ca.pem // newcerts/syslog-server/2017-09-18_130448/7signal-syslog-server-cert.pem // newcerts/syslog-server/2017-09-18_130448/7signal-syslog-server-key.pem 10.10.10.$DefaultNetstreamDriver gtls $DefaultNetstreamDriverCAFile /etc/ssl/7signal/7signal-syslog-ca.pem $DefaultNetstreamDriverCertFile /etc/ssl/7signal/7signal-syslog-server-cert.pem $DefaultNetstreamDriverKeyFile /etc/ssl/7signal/private/7signal-syslog-server-key.
$ sudo semanage port -a -t syslogd_port_t -p tcp 10514 Restart rsyslog and verify that there are no errors reported in /var/log/messages: $ sudo service rsyslog restart $ sudo tail -f /var/log/messages Sep 18 11:46:31 localhost rsyslogd: [origin software="rsyslogd" swVersion="7.4.10" x-pid="5860" x-info="http://www.rsyslog.com"] exiting on signal 15. Sep 18 11:46:31 localhost rsyslogd: [origin software="rsyslogd" swVersion="7.4.10" x-pid="9838" x-info="http://www.rsyslog.
A configuration file example: /var/log/EyeLogs { missingok sharedscripts postrotate /bin/kill -HUP `cat /var/run/syslogd.pid 2> /dev/null` 2> /dev/null || true endscript } Step 7: Configure Eyes to start logging to the logging server Copy the client certificates to the Carat server. In this example, Carat and syslog server are running on the same host. $ scp /
/ newcerts/CA/7signal-syslog-ca.pem // newcerts/syslog-client/2017-09-18_130448/7signal-syslog-client-cert.Edit Carat configuration file /opt/7signal/Carat/7signal/conf/server_conf.prop. Set up certificates, remote server and syslog mode: # Eye syslog mode: "local", “udp”, "tcp" or "tls" eye.syslog.method=tls # Eye remote syslog server address (if syslog mode is "tcp" or "tls") eye.syslog.remote.server.address=10.10.10.147 # Eye remote syslog server port (if syslog mode is "tcp" or "tls") eye.syslog.remote.server.
8 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
SAPPHIRE PROCESS MANAGEMENT 8.1 Carat Carat is a service on Linux systems. However, the Carat process is supposed to be used by 7signal tool called 7carat: # 7carat o o o o start stop restart status 8.2 Application server Application server is a service on Linux systems. However, the Application server process is supposed to be used by 7signal tool called 7analyzer: # 7analyzer o o o start stop restart 7signal Solutions Inc.
o status 8.3 Sonar Sonar is a service on Linux systems: # 7sonar o o o o start stop restart status 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
8.4 Eye NOTE: The following command requires an SSH session into the Eye (monitoring station). The utility 7config controls the Eye configuration. See more details for the tool in chapter 10. The process is controlled with command group run. # 7config run o o o o start stop restart status 9 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
TROUBLESHOOT 9.1 Cannot add Eye unit 1. 2. 3. 4. Check that license.xml file is located in the Carat server a. Check the Carat server log for possible license errors b. Check the existence of the file i. The default location for the license file is /opt/7signal/Carat/7signal/conf c. The file permission should be 744. d. Check the contents of the file to look for any anomalies Run 7 config verify command in Eye unit Check that maximum number of Eye’s (license defines) is not exceeded. Check that carat.
One can remotely telnet or http i. Sonar opens the connection and closes it after 1 second of idle time or displays XML Error. Check Sonar log for error messages Check that Sonar ports are open on the firewall(s) Check that the WLAN encryption key has correct definition (or run a Manual test selecting the Eye Ethernet Interface to narrow down the problem). Check that the key is bound to the managed network Check connectivity options and requirements for Eye and Sonar b.
9.4 Eye IP address forgotten 9.4.1 Reset Eye IP configuration From Sapphire release 5.2 onwards, Eye restarts and obtains its IP address from a DHCP server. In earlier Sapphire releases, Eye IP will be reset back to static 192.168.0.1. Indoor Eye 2000 1. 2. 3. 4. Locate Reset button of the Indoor Eye unit. Push and hold the Reset button ~ 30 seconds Eye LED light blinks 5 times Release the Reset button Indoor Eye Eye 2100/500/2200 1. 2. 3. 4. Locate Reset button of the Indoor Eye unit.
9.5 Collecting information for further analysis Sometimes it might be necessary to collect Sapphire log files and Linux system information and send them to 7signal support team. To make this easier, “7carat collect logs” will gather all required information into one file. On the Carat server, as root, issue the command: # 7carat collect logs The command collects Sapphire log files and other information (see chapter 12.4) and stores all data to one file, Sapphire_logs-. tar.gz.
COMMAND-LINE UTILITY FOR EYE 10.1 Overview 7config i s a command line utility for configuring various things on the Eye unit. Commands are divided into command groups so that each group contains one or more commands. A command may also have an argument and a value. Currently supported command groups are the following: ● ● ● ● ● ● ● ● ● ip: IP address management. keys: Key storage management. ap: Access point configuration storage management. conn: Connection management.
Command group specific help can be shown with command: 7config help General help can be shown with command: 7config help 10.2 7config ip command group This command group contains commands for configuring IP configuration of the Eye Ethernet interface. Currently, it is possible to show the current IP configuration, set IP address, network mask and default gateway address (or alternatively, use DHCP configuration) of the management interface.
gateway Set IP address of default gateway (optional) VALUE = Valid IPv4 address or 'remove' to remove configured gateway dhcp Set DHCP on/off VALUE = on|off 'show' command arguments: none 'backup' command arguments: create Create backup from existing IP configuration. restore Restore IP configuration from backup.
Restore IP configuration from a backup: # 7config ip backup restore Show current IP configuration: # 7config ip show 10.3 Keys command group This command group contains command for managing WLAN network keys stored on the Eye unit. Currently, the only supported operation is to destroy all WLAN keys from the Eye. # 7config keys destroy 10.4 AP command group This command group contains commands for managing the Access Point information stored to the Eye unit.
10.5 Conn command group This command group contains commands for managing encryption settings of management traffic between the Eye unit and Carat server, and command for configuring the Carat server connection information (how the Eye can connect to a Carat server). 7config conn [VALUE] 'cert' command arguments: set Set management connection encryption certificate file. VALUE = Certificate file name. File must reside in /nand/etc/certificates directory.
'ssh' command arguments: show Show SSH public key or tunnel configuration. 'show key': Show SSH public RSA key. 'show tunnel': Show tunnel configuration. set tunnel Set SSH tunnel configuration.
::[:organization] remove Remove Carat configuration. 'dns' command arguments: show Show 7signal DNS server information. set Set 7signal DNS server name/address VALUE=DNS name or IP address of 7signal DNS server. remove Remove 7signal DNS configuration. Defaults to 'dns.7signal.com' force Force DNS. Eye will wait until it gets Carat configuration from DNS server.
Configure Eye to connect a Carat server by using DNS redirector service # 7config conn dns set 10.6 Run command group This command group contains commands for managing Eye software run-state. Currently supported operations are to ask current status of the software, to start, stop and restart the software, activate software version, show installed version, uninstall a software version, and to reconfigure Eye unit without restarting it.
remove Uninstall Eye software version. Example: 7config run remove 02.61 Uninstalls SW version 2.61 Examples: Query status of the Eye software: # 7config run status Start the Eye software: # 7config run start Stop the Eye software: # 7config run stop Restart the Eye software: # 7config run restart List installed Eye softwares: # 7config run list 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
Reconfigure the Eye: # 7config run reconfig 10.7 Txp command group This command group contains commands for showing and setting of TX power related parameters. Currently supported operations are showing of TX power settings, setting default TX power, setting gain of an external antenna and setting cable loss of the external antenna. 7config txp [ARG] [VALUE] 'show' command arguments: default Show default TX power. ext Show configured gain of external antenna.
cable VALUE = Gain of external antenna (dBi). Set cable loss of external antenna. VALUE = Cable loss of external antenna cable (dB). Examples: Show all information in TX power configuration: # 7config txp show Show configured cable loss: # 7config txp show cable Set external antenna gain to 10 dBi: # 7config txp set ext 10 10.8 Log command group This command group contains commands for configuring log production of the Eye.
log resides in the folder /nand/ as files named syslog*, in 802.11a/b/g/n in folder /var/log as files named messages, and in 802.11a/b/g/n/ac (Eye 2100/500/2200) in folder /var/log as files named 7signal.log. Reading of the log files is either from the chosen storage directly or with the command logread (Eye 1000/2000 only). By default, only the critical messages are logged. Currently, the supported commands are: ● ● show which shows the current log configuration.
Log levels are cumulative, i.e. the level CRIT logs only critical messages, WARN logs all levels including CRITICAL, ERROR and WARN messages. DEBUG logs all possible messages. Log command group arguments: 'show' Show log configuration. 'set' command arguments: level Set log level. VALUE = CRIT | ERROR | WARN | INFO | DEBUG default Set default log level. This log level will be active when 7signal software starts. VALUE = CRIT | ERROR | WARN | INFO | DEBUG target Set logging target.
Set default log level to ERROR: # 7config log set default ERROR Show default log level: # 7config log show Set logging target to NAND flash: # 7config log set target persistent 11 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
COMMAND-LINE TOOL FOR DATABASE MANAGEMENT 7db command is a tool for the Carat database. It supports limited data retrieval, general management and database backup administrator for both immediate and automatic backups. It is recommended that database backups should be taken regularly.
NOTE: the command is trivial to issue but its consequences are highly resource consuming. Observe awareness when using this command. There are two different logging modes in 7signal Sapphire. This command switches between the modes. There is lots of informative output as this command should not be used carelessly or without proper planning and understanding of the consequences. The command examines the current state of all three different underlying databases.
NOTE: the backup policy should be well-planned. Please see the 7signal Sapphire User Guide for further discussion on backup and the options available. Backup commands: ● show Show automatic backup configuration ● remove Remove automatic backup configuration ● set Configure automatic backup o o daily weekly = Mon, Tue, Wed, etc.
# 7db backup remove Backup offline every Wednesday at 00:30 to /mnt/backups # 7db backup set weekly Wed 00:30 /mnt/backups offline Backup online every day at 03:00 to /mnt/backups # 7db backup set daily 03:00 /mnt/backups online Change backup directory to /mnt/newbackups, do not change time settings # 7db backup set directory /mnt/newbackups Backup every Sunday at 00:30, do not change backup directory # 7db backup set weekly Sun 01:30 Back the system up immediately offline # 7db backup now /mnt/backups
# 7db backup workdir set /opt/largefilesystem Restore a known-to-be-good system state # 7db backup restore 11.3 Show command group Shows the status and configuration of the database Show commands: ● tabstatus Show the status of the tables. o all ● o conf Show configuration of the database. Examples Show status of the tables in the MEAS7 and MGMT7 databases # 7db show tabstatus all Show status of the tables in the SECUR7 database 7signal Solutions Inc.
# 7db show tabstatus secur7 Show status of the CARAT7.ap_ftp_qos_test table in the MEAS7 database # 7db show tabstatus meas7 ap_ftp_qos_test Show configuration of the database # 7db show conf 11.4 Reinit command group Empty the database and resume initial state of the system. # 7db reinit Examples: Re-initialize the MEAS7 and MGMT7 databases # 7db reinit all Re-initialize the MEAS7 database # 7db reinit meas7 7signal Solutions Inc.
Re-initialize CARAT7.ap_ftp_qos_test table in the MEAS7 database # 7db reinit meas7 ap_ftp_qos_test 11.5 Reorg command group Reorganize the database. # 7db reorg Examples: Re-organize the MEAS7 and MGMT7 databases # 7db reorg all Re-organize the MEAS7 database # 7db reorg meas7 Re-organize the MGMT7 database # 7db reorg mgmt7 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
12 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
COMMAND-LINE TOOL FOR CARAT SERVER 7carat command is a tool for Carat server management.
Show the license information # 7carat license Install new carat license # 7carat license set 12.2 Integritycheck command group Verify the database integrity. Examples: Execute the integritycheck # 7carat integritycheck IMPORTANT: Sapphire Carat must not be running when issuing this command! 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
12.3 Ip command group If the IP address of the Linux host is changed, the changed IP address needs to be configured to the Carat server as well. Examples: IP address of the Linux server is changed to 192.168.10.10. Configure new address to Carat server. # 7carat ip set 192.168.10.10 # 7carat restart 12.4 Collect command group Collect information about Sapphire installation and status of the Linux host for analysis.
● ● DB2 o Log files o DB2 diagnostics log o DB2 instance log file Linux host o CPU information o Kernel log o Memory information o System log files o List of running processes o Linux distribution information o Top memory consumers o System information (uname) o vmstat output The information is collected to a file named Sapphire_logs-.tar.gz. 12.5 Memoryconf command group The Carat installer sets appropriate size for the Carat server Java heap memory automatically.
13 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
UPDATING ENCRYPTION CERTIFICATES Sometimes it is necessary to update encryption certificates used throughout the Sapphire solution. Certificates can be updated from the certificate package file in Linux, a separate truststore file and truststore password are needed in Windows. Certificate packages can be downloaded from 7signal Share File. It is also possible to install a custom HTTPS certificate for the Analyzer/EyeQ/Configurator.
Extracting 7signal keystore password.............................OK Updating server configuration file...............................OK Updating setup configuration file................................OK 13.2 Updating web app certificates Step 1: Login to Application server host as root user Step 2: Use 7analyzer tool to update certificates # 7analyzer certificate set /path_to_package/mycerts-7signal-all.tar.gz Validating archive file..........................................
13.3 Updating Eye certificates Step 1: Transfer certificate package to Eye /tmp directory by using SCP For example, in Carat server host: # scp /path_to_package/mycerts-7signal-all.tar.gz root@:/tmp Step 2: Login to Eye by using SSH # ssh root@ Step 3: Install certificate from certificate package # 7config conn encryption install /tmp/mycerts-7signal-all.tar.gz 13.
Importing custom certificates require that all certificates must be in PEM format. In order to avoid browser warnings, the whole certificate chain must be included (root certificate and all intermediate certificates). Certificates must be in a right order. The root certificate must be on bottom, and the server certificate on the top. The server certificate private key must be also available in PEM format. Example: There are four certificates: ● AddTrustExternalCARoot.crt: Root certificate ● UserAddTrustCA.
If the certificates are in all_certificates.pem and the private key is in file mykey.pem: # 7analyzer certificate install all_certificates.pem mykey.pem Certificate and private key are in PEM format, ok Removing current TLS certificate.. Creating temporary keystore.. Importing temporary keystore to Analyzer keystore.. Entry for alias tomcat successfully imported. Import command completed: 1 entries successfully imported, 0 entries failed or cancelled Successfully installed a custom TLS certificate.
14 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
DATABASE MAINTENANCE In order to keep the database working optimally, it is suggested that the following database maintenance tasks are scheduled to be done automatically: 1. 2. 3. 4. 5. Online data purges. Data purges prevent database file systems to not get full. Database backups. Recent backups are mandatory in order to recover from fatal file system errors, broken disks, etc. Table / index reorganizations. By doing regular reorganizations the database structure stays in optimal shape.
Alternatively, screen utility can be used. Please wait for one task to complete before starting the next one. 14.1 Online data purge The measurement data collected by 7signal Sapphire can take lots of disk space. Sapphire provides a tool for online removal of old measurement data. Configuring the data purge requires knowledge about DB2 database, so a Database Administrator should always be involved when setting up measurement data purge process.
If the DB2 archival logging is enabled, online data purge can be configured without any further steps. Notice that data purge produces lots of database transactions, and transaction logs will be archived, so a proper backup plan must be in place (backup process deletes old archived transaction logs automatically). Database with circular logging If the DB2 circular logging is enabled (the default), some additional steps are needed.
After changing the database configuration, you must restart the database instance: $ db2stop force $ db2start After changing the configuration parameters, try to re-create the indexes (as described chapter 14.1.1). ● If the indexes are generated successfully, restore the original database configuration parameters and restart the instance. ● If the index creation fails again due to insufficient transaction log space, increase the database configuration parameters and try to recreate the indexes.
NOTE: If the database partition does not have much free disk space, it is suggested that current index set is dropped before the new ones are created. Issue the command: $ /opt/7signal/dbms/v/ db2/drop_meas_indexes.sh Update the index set by issuing the command: $ /opt/7signal/dbms/scripts/update_meas7_indexes.sh Step 4: Rebind purge stored procedure $ db2 "CALL SYSPROC.REBIND_ROUTINE_PACKAGE ('P','CARAT7','','PRUNE_DATA','')" 14.1.
# su – db7sign Step 3: Execute initial data purge Usually, users want to keep certain amount of historical data in the database. When configuring the data removal first time, there can be more data in the database than desired amount of days. The first Check the options: $ /opt/7signal/dbms/scripts/7PurgeTool.sh -h Usage: 7PurgeTool.sh OPTIONS OPTIONS -d Number of days of data left to the database.
$ /opt/7signal/dbms/scripts/7PurgeTool.sh –c –d 90 –w 0 -w 0 means that the utility does not wait before it proceeds to delete the next day. The utility starts to delete data one day at once: Database Connection Information Database server SQL authorization ID Local database alias = DB2/LINUXX8664 10.5.
Parameter Value : 00000 Parameter Name : P_ERROR_MSG Parameter Value : Parameter Name : P_START_TIME Parameter Value : 2017-12-19-13.28.41.665326 Parameter Name : P_END_TIME Parameter Value : 2017-12-19-13.29.04.810131 Return Status = 0 Purge executed successfully. Waiting 0 seconds ...
Parameter Name : P_START_TIME Parameter Value : 2017-12-19-13.29.04.880104 Depending on how many days it needs to delete, the execution can take from few hours to few days. Step 4: Configure daily purge Once the initial purge is complete, a daily purge can be configured as a cron task. As db7sign user: $ crontab –e Add a line for a scheduled purge. In an example below, purge is executed daily at 3am 0 3 * * 0 2>&1 /opt/7signal/dbms/scripts/7PurgeTool.sh -d 90 >> /var/log/purge.
The 7Reorg.sh tool, located in directory /opt/7signal/dbms/scripts, checks if tables or indexes need a reorganization, and executes the online reorganization if necessary. Depending on DB2 license, the tool can either reorganize tables and indexes, or indexes only: ● ● DB2 Express-C (default license): Reorganizes indexes only. The tool outputs a warning if it detects a table that would need reorganization. Offline reorganization is needed for the tables. DB2 Express/Workgroup etc.
Local database alias = MEAS7 WARNING: CARAT7.SCAN_RADIO needs OFFLINE REORG WARNING: CARAT7.SPECTRUM_PARAM needs OFFLINE REORG WARNING: CARAT7.SPECTRUM_RESULT needs OFFLINE REORG WARNING: CARAT7.SPECTRUM_RESULT_5GHZ needs OFFLINE REORG Checking index CARAT7.GTS1_X1_AIR_UTILIZATION_TEST Reorganizing all indexes of table AIR_UTILIZATION_TEST DB20000I The REORG command completed successfully. Checking index CARAT7.GTS1_X2_AIR_UTILIZATION_TEST Checking index CARAT7.
Database server SQL authorization ID Local database alias = DB2/LINUXX8664 10.5.5 = DB7SIGN = MEAS7 Reorganizing table CARAT7.SPECTRUM_RESULT_5GHZ DB20000I The REORG command completed successfully. DB21024I This command is asynchronous and may not be effective immediately. Reorg done. Reorganizing all indexes of table CARAT7.SPECTRUM_RESULT_5GHZ DB20000I The REORG command completed successfully. Checking index CARAT7.
7Reorg.sh output may indicate that reorganizing some of the tables offline would be beneficial. For example: “WARNING: CARAT7.SCAN_RADIO needs OFFLINE REORG” In order to execute offline reorganization of tables: Step 1: Stop Carat and Application servers # 7carat stop # 7analyzer stop Step 2: Switch to “db7sign” user Step 3: Connect to measurement database $ db2 connect to meas7 Step 4: Execute reorganization command for each table that required offline reorganization $ db2 reorg table CARAT7.
Notice: Offline reorganization of a table can take several hours. However, table level reorganizations are not needed very often. 14.2.3Scheduling reorganizations Reorganizations should be done regularly. Probably the easiest way to schedule reorganizations is to use cron. Important: Use crontab of “db7sign” user. Example reorganizations schedule Use “crontab -e” to edit the crontab of the “db7sign”user. # Reorganization every Sunday at 3 am. Redirect output to /var/log/reorg.
14.3 Database backups Database backup utility 7BUtool.sh can be found in directory // scripts. The utility can be used to take offline, online and incremental online delta backups. Online backups are possible only if archival logging has been enabled on DB2. The utility is also able to transfer backup images to a remote storage server. Multiple backup directories can be provided. By using multiple backup directories backup process is faster, due to DB2 I/O parallelism.
● ● ● If DB2 archival logging (which enables online backups) is in use, archived transaction log files can take lots of disk space. When taking a backup, archived log files will be included in the backup images, and they can be deleted afterwards. 7BUtool.sh deletes the old archived log file automatically, but by default it keeps log files of last 7 days. You can control how many days will be kept by using -l option of the 7BUtool.sh utility.
-i -f -t -k -l Do an online incremental delta backup. Email sender address. The email address that will appear in "From:" field of email notifications. Email recipient address. The email address to which the email notification will be sent. Keep delta backups for number of days. Keep archived transaction logs for number of days. Arguments: Backup directories on this server where DB2 will put the backup images.
● ● ● ● ● ● ● -s : Name of this server. The name of the directory to which the backup images will be will be copied on a remote storage server. -o: Do a full online backup. By default, a full offline backup will be created. NOTE: Archival logging is required for online backups. -i: Do an incremental online delta backup. NOTE: Archival logging is required for online backups. -f : Sender email address in email notifications send by the utility.
14.3.3Examples Offline backups Local full offline backup Step 1: Switch to root user (or use sudo) Step 2: Execute the backup command Full offline backup by using two backup directories, backup images are not transferred to a remote storage server: # /opt/7signal/dbms/scripts/7BUtool.sh -s my-carat-server -f my-carat-server@example.com -t admin@example.
Full offline backup by using two backup directories, backup images are transferred to a remote storage server: # /opt/7signal/dbms/scripts/7BUtool.sh -s my-carat-server -f my-carat-server@example.com -t admin@example.com -b remote-backup.example.com -u backup -d /home/backup/my-carat-server /home/db7sign/dir1 /home/db7sign/dir2 The backup images will be copied to directory /home/backup/my-carat-server/my-carat-server-offline/ on the remote storage server remote-backup.example.com.
Full online backup, backup images are transferred to a remote server Step 1: Switch to “db7sign” user Step 2: Execute the backup command Full online backup by using two backup directories, backup images are transferred to a remote storage server, keep 2 days of archived transaction logs locally: $ /opt/7signal/dbms/scripts/7BUtool.sh -o -l 2 -s my-carat-server -f my-carat-server@example.com -t admin@example.com -b remote-backup.example.
$ /opt/7signal/dbms/scripts/7BUtool.sh -i -k 5 -s my-carat-server -f my-carat-server@example.com -t admin@example.
Probably the easiest way to schedule backups is to use cron. For online backups, use crontab of “db7sign” user. For offline backups, use crontab of the root user. Example backup schedule Use “crontab -e” to edit the crontab of the “db7sign”user. # Full online backup every Sunday at 3 am 0 3 * * 0 /opt/7signal/dbms/scripts/7BUtool.sh -o -s my-carat-server -f my-carat-server@example.com -t admin@example.com -b remote-backup.example.
The command syntax is the following: Usage: cleanupOldBackups.sh Where: OFFLINE ONLINE ONLINEINCDELTA ● ● ● ● - Number of offline backups left to the backup directory - Number of online backups left to the backup directory - Number of online incremental delta backups left to the backup directory is the same directory which is provided to 7BUtool.sh with -d option.
14.4 Collecting statistics Collecting statistics (“RUNSTATS”) about the data in regular basis is important in order to keep database query optimizer up to date, and it makes possible for the optimizer to always select the best access path for the data. The 7Runstats.sh tool, located in directory /opt/7signal/dbms/scripts, collects statistics on all measurement data tables. 14.4.1Executing statistics collection Step 1: Switch to “db7sign” user Step 2: Execute the utility.
Local database alias = MEAS7 Doing RUNSTATS for carat7.AIR_UTILIZATION_CODECS DB20000I The RUNSTATS command completed successfully. Doing RUNSTATS for carat7.AIR_UTILIZATION_TEST DB20000I The RUNSTATS command completed successfully. Doing RUNSTATS for carat7.AP_ACCESS_TEST … End time: Wed Aug 22 12:30:11 EEST 2018 14.4.2Scheduling statistics collection Statistics collection should be done regularly. Probably the easiest way to schedule reorganizations is to use cron.
14.5 Watching DB and log filesystem usage db2_watchdog.sh script, found in directory /opt/7signal/dbms/scripts can be used to monitor DB and archive log filesystem disk usage. If the disk usage exceeds configured usage percentage, the script will shut down the Sapphire applications and DB2, preventing possible database corruption caused by a full filesystem. db2_watchdog.sh must be run as root user. The utility has the following options: # /opt/7signal/dbms/scripts/db2_watchdog.
14.5.
14.5.2Scheduling DB2 watchdog db2_watchdog.sh should be run at least once in 10 minutes. Probably the easiest way to schedule checks is to use cron. Important: Use crontab of “root” user. Example schedule Use “crontab -e” to edit the crontab of the “root” user. Add line */10 * * * * /opt/7signal/dbms/scripts/db2_watchdog -t -d /opt/7signal/database -p /DB-archive/logs -s /DB-archive/logs -l /var/log 14.
# Incremental delta backups from Monday to Saturday 0 3 * * 1-6 /opt/7signal/dbms/scripts/7BUtool.sh -s my-carat -f my-carat@example.com -t reports@example.com -i /backups >> /var/log/backup.log 2>&1 # Data purge every day at 12:30 am 30 0 * * * /opt/7signal/dbms/scripts/7PurgeTool.sh 2>&1 >> /var/log/purge.log # Statistics collection every Saturday at 10 am 0 10 * * 1 /opt/7signal/dbms/scripts/7Runstats.sh 2>&1 >> /var/log/runstats.
LOGICAL CONNECTIONS Sapphire elements and their logical connections are in the picture below: • • • • • Eye – a WLAN probe with both WLAN interface (WLAN client and analysis functions) and Ethernet interface (management functions). Sonar – Server software emulating various business services for testing purposes. Deployment method is two-fold as follows: 7signal Solution: the application is running in hosts chosen by the customer. 7signal Site Miner: a dedicated mini-laptop is running the application.
Eye – Sonar connection Con n ID Description Data content Listening port(s) Remarks 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
1 Test management and typical test connection Test control message and pseudo-data TCP/80 Traffic is properly encapsulated HTTP. Uses Eye WLAN interface. Configurable during Sonar deployment 2 3 MOS test, uplink direction MOS test, downlink direction MOS test specific data MOS test specific data udp/50000 – 50019 Configurable during Sonar installer udp/9999 Configurable during Eye deployment Optional. Uses Eye WLAN interface. The number of port varies between 0 and 20.
understanding of the network between the endpoints and the ability to affect all the network elements necessary. To test and use the wireless connection the following variables must be known: ● ESSID – test parameter to connect to a particular wireless network. ● WLAN encryption Network keys – pre-shared keys, certificates or similar - are stored in Eye file system by Carat application.
Carat server connects to Eyes (”Enterprise setup”). Conn ID 1 Description Data content Eye server TLS encrypted binary protocol for management and testing. Listening port(s) TCP/7799 Remarks Uses Eye Ethernet interface. Configurable in Eye deployment In this case the Eye acts as a server and Carat software is a client. 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
Carat – Eye connection Eyes connect to Carat server (”Cloud setup”). Conn ID 1 Description Data content Carat server TLS encrypted binary protocol for management and testing. Listening port(s) TCP/7799 TCP/7800 Remarks Uses Carat Ethernet interface. Configurable in Carat deployment In this case the Carat acts as a server and Eyes are clients. 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
Internal connections in Carat server Note: as the following connections occur inside one host machine only, this part may be skipped regarding the firewall settings and other networking. 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
Con n ID 1 Description Data content RMI service. RMI service protocol Listening port(s) TCP/1099 Remarks Discovery service for conn #2. Typically not changed. 2 3 4 web-apps connecting as a client to a Carat server. IBM DB2 database service for web apps. IBM DB2 database service for Carat. RMI calls TCP/47777 JDBC traffic. Configurable during Application server deployment TCP/7722 JDBC traffic. Configurable during DBMS deployment TCP/7722 7signal Solutions Inc.
Configurable during DBMS deployment Analyzer is a web-application that visualizes the measurements and it has a dual-role in the sense of connectivity: Analyzer acts as a client to both the Carat server and DB2 and as a server to the browser clients. Currently, Carat, Analyzer and IBM DB2 applications are inseparable as they run in the same host in all supported setups. 7signal installers contain the installation medium for DB2 and the setup of DB2 is automated by 7signal DBMS installer.
Analyzer – Internet browser connection Con n ID 1 Description Data content Standard HTTP connection. Standard HTTP traffic for creating a HTTPS connection. Listening port(s) TCP/80 Remarks Redirects to HTTPS port of Application server. 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
2 Standard HTTPS connection for measurement requests and responses. Secure HTTP. Report and chart requests and responses. Configurable during Analyzer deployment. TCP/443 Business connection for Application server. Configurable during Application server deployment. Appendix B. 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
BANDWIDTH REQUIREMENTS NOTE: the volume estimates are estimates and vary based on the configuration. 14.6.1 Eye – Sonar From To Medium Eye Sonar WLAN Sonar Eye WLAN Traffic motivator Automated test engine and interactive testing by users. Volume estimate Low, each request is a few hundred bytes. Responses to client. Typically pseudo-data that varies based on the test parameters. Eye acts as one WLAN end-user would do, one operation per minute.
For example, the TCP download test transfers by default 2 megabytes of data that does not take long. The amount of data is exceptionally high for data transfer in a logistics environment but on the other hand in office environment transfer of this size is relatively low. The test parameter should be adjusted, either to simulate typical transfer or to save the bandwidth while keeping the transfer size high enough to give measurements out of the network. 14.6.
In data communications sense the traffic for single Eye is minimal. 14.6.3 Analyzer server – Analyzer client (browser) From To Medium Analyze r host Clients in WWW Ethernet, general networking Traffic motivator User actions Volume estimate Volatile. Like one HTTP client. Major factor User activity. Per any request the amount of requested KPIs is the driving factor. There is no continuous machine-to-machine interaction, all activities are initiated by the user.
APPENDIX C. 7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA, 216-777-2900, info@7signal.com, www.7signal.
OFFLINE DATA PURGE The utility used for offline data removal is “purge_old_data.sh” and it can be found on the Carat server in directory “/opt/7signal/dbms”. The suggested data purge method is online data purge, which is described in the chapter 14.1.
Usage: purge_old_data.sh Options: -w Use work directory -m Number of months left to DB (default 6) -s Number of months spectrum data left to DB (default 2) -r Number of months scan radio data left to DB (default 3) Step 5: Execute data removal tool: For example, if data older than one year should be removed from the measurement DB. Spectrum and Scan Radio data older than three months will be removed: # ./purge_old_data.
