Server Hardware.book

Transcription

RETAILNEXT USER MANUAL
VERSION 5.X
SERVER HARDWARE
MINIMUM HARDWARE REQUIREMENTS
SYSTEM DEPLOYMENT OVERVIEW
CHANNEL & STORAGE RECOMMENDATIONS
STAGING THE RETAILNEXT SERVER
Published May 2015
LEGAL NOTICE
No part of this publication or any derivatives of this publication may be reproduced or used in any form without the express consent of RetailNext. The material in this manual as well as the Software or any other RetailNext product is subject to change without notice.
The software is provided strictly on an “as is” basis. All Software, including any Firmware, furnished to the user is on a licensed basis per the terms and conditions of the applicable license agreement. Customer may possess only such number of copies of the Software as has been expressly authorized. Customer will not (and will not allow any third party to) (i) otherwise use, copy, distribute, sub‐license, transfer, provide, lease, lend, or disclose the Software; and (ii) modify, reverse engineer (except to the extent applicable law prohibits reverse engineering restrictions), incorporate or use in any other works, or create derivatives of any portion of such Software. RetailNext retains all rights and ownership and Customer will maintain the copyright notice and any other notices that appear on the product or documentation. CUSTOMER ACKNOWLEDGES THAT THE SOFTWARE MAY INCLUDE FEATURES TO PREVENT USE AFTER THE APPLICABLE LICENSE PERIOD AND/OR ANY USE INCONSISTENT PER THE TERMS AND CONDITIONS OF THE LICENSE AGREEMENT. Customer acknowledges that Software may contain or be distributed with third party software (“Third Party Software”). All use of Third Party Software shall be governed by the respective licenses for such Third. Prior to disposing of any media or apparatus containing any part of the Software, Customer shall completely destroy any Software contained therein. From time to time upon request, RetailNext may audit all applicable systems and records to ensure compliance with the foregoing. Any audit showing noncompliance will be at Customer's expense and RetailNext may revoke the applicable license. Rev. 5.X
Contents
1. Software Installation Options & Minimum Hardware
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
RetailNext Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Deploying on a RetailNext Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Deploying on Different Hardware that Meets RetailNext Specs . . . . . . . . . . . . . . . . 4
Deploying on a Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. System Deployment Overview . . . . . . . . . . . . . . . . . . . . . . . 6
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Solution Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Corporate (HQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Store Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Scenario 1: Standard Cameras . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Scenario 2: Cameras with Built‐in Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Scenario 3: Hybrid Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Network Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Internet Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Client PC (Web Interface) Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Mobile Application Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Bandwidth Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Video Stream Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Store Server Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Open (Inbound) Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Outbound Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
RetailNext Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Appliance Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Appliance Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Other Solution Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Cameras . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
RETAILNEXT™ SERVER HARDWARE: TABLE OF CONTENTS
i
Point of Sale (POS) Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Staffing Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Legacy DVRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Network Video Recorders (NVRs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Legacy Traffic‐counting Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Store Connectivity Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Scenario 1: Over a Secure Intranet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Scenario 2: Over the Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Support and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3. Channel & Storage Recommendations . . . . . . . . . . . . . . 18
Confirming the Channel Capacity for RetailNext Servers . . . . . . . . . . . . . . . . . . . . . . . . 19
Testing Scenarios on non‐RetailNext Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4. Staging the RetailNext Server . . . . . . . . . . . . . . . . . . . . . . . 22
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Obtaining a RetailNext License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Configuring the System BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Installing the RetailNext Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Accessing the RetailNext Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Stand‐alone With No Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Network‐based Using a Laptop With DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Network‐based Using a Laptop without DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Configuring the RetailNext Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Uploading a License Via the RetailNext System Console . . . . . . . . . . . . . . . . . . . . . . . . 36
Accessing the RetailNext Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
RETAILNEXT™ SERVER HARDWARE: TABLE OF CONTENTS
ii
System Overview
1.
Software Installation Options &
Minimum Hardware Requirements
This guide describes the options for installing the RetailNext software, the minimum hardware requirements, and the best practices for optimal performance.
The RetailNext solution enables retailers and manufacturers to use video, transaction data, and other data sources to address some of their highest priority objectives: optimizing store operations, gaining valuable sales and marketing data, and improving in‐store security. System Overview
RetailNext is a client‐server system with a web‐based user interface and a Linux back‐end software. RetailNext can integrate with a wide variety of IP and analog cameras, video encoders, point‐of‐sale systems, and third party DVRs. It can also integrate with external video analytics.
RetailNext Installation Options
There are three deployment options available for installing the RetailNext application:
•
RetailNext Appliance. This is the most common deployment option. RetailNext sources an HP appliance on which our image has been already loaded. In some deployment cases, sourcing a RetailNext appliance is not possible, not practical, or simply not preferred. For example, an IT department may have a conflicting policy on direct hardware sourcing or a different sourcing option may be more practical for an international deployment.
•
Different Hardware, Same Specifications. The RetailNext application is installed on a different appliance (for example, a Dell) that meets the same hardware specifications as the RetailNext appliance. •
Virtual Machine, Same Specifications. The RetailNext application is installed on top of a software virtual machine. Note: The RetailNext application is CPU‐intensive and has specific memory and storage requirements, so if Option 2 or 3 is selected, it’s imperative that the RetailNext hardware specifications be met in order for the application to work correctly.
RETAILNEXT™ SERVER HARDWARE
1
Deploying on a RetailNext Appliance
The RetailNext application is most often deployed through our RetailNext appliance. The RetailNext appliance provides the RetailNext application out of the box. There are several appliance models available, depending on the number of channels required for the installation and on the installation preference: desktop or rack‐mounted. RetailNext appliances are available in US‐based deployments. For international deployments, sales representatives will let you know if a RetailNext appliance can be sourced or if you must consider a different option.
When you use a RetailNext appliance, RetailNext supports the full software stack through one of our available Support Engagement models. For more information about Support Engagement models, contact your sales representative.
See Channel & Storage Recommendations for information about channel calculation.
Table 1 shows the specs and the capacity for each of the available appliances.
Table 1: Available Appliances
MODEL
RN‐STORE‐500‐DT
(Desktop version)
SPECS
• Processor: Intel Pentium G2020, 2.9 GHz, •
•
•
•
(Desktop version)
•
•
6 channels
2 cores
Memory: 4 GB
Storage: 500 GB (2 x 500 GB, RAID 1)
Dimensions (WxDxH): 13.3 x 15 x 3.95 in (33.8 x 38.1 x 10 cm)
Weight: 16.5 lb (7.5 kg)
• Processor: Intel Xeon E3‐1225v2, 3.2 •
•
•
CAPACITY (See Note)
16 channels
GHz, 4 cores
Memory: 8 GB
Storage: 2 TB (2 x 2 TB, RAID 1)
Dimensions (WxDxH): 3.95 x 15 x 13.3 in (10 x 38.1 x 33.8 cm)
Power supply: 240‐Watt 90% efficient 2
Table 1: Available Appliances
MODEL
(Desktop version)
SPECS
• Processor: Intel Xeon E5‐1650, 3.2 GHz, 6 •
•
•
•
•
• Processor: Intel Pentium G850, 2.90 GHz, RN‐STORE‐1000‐RM
(Rack‐mount version)
• Processor: Intel Xeon E3‐1220v3, 3.1 •
•
•
•
16 channels
GHz, 4 cores
Memory: 8 GB
Dimensions: 1U half‐depth rackmount, 1.7"H x 17.11"W x 15.07"D (4.32 x 43.46 x 38.30cm)
Power supply: 300W
• Processor: 2 x Intel Xeon E5‐2620, 2.0 •
•
•
6 channels
2 cores
• Memory: 4 GB
• Storage: 500 GB (2 x 500GB, RAID 1)
• Dimensions: 1U half‐depth rackmount
•
•
•
Corporate Server SM/MED/LG
32 channels
cores
Memory: 16 GB
Dimensions (WxDxH): 7 x 17.5 x 17.63 in (17.78 x 44.52 x 44.76 cm)
Power supply: 600‐Watt 90% efficient power supply
RN‐STORE‐500‐RM
RN‐STORE‐2000‐RM
CAPACITY (See Note)
32 channels
GHz, 12 cores total
Memory: 16 GB
Storage: 4 TB (4 x 2TB, RAID 10)
Dimensions: 1U, 1.7"H x 17.1"W x 29.5"D (4.3 x 43.5 x 75 cm)
Power supply: 500W
General product specs
• Same as RN‐STORE‐2000‐DT or RN‐
STORE‐2000‐RM
3
You can review the general product specs and data sheets for the appliances listed in Table 1 at https://bvinetworks.jira.com/wiki/display/PM/RN+Appliance+Hardware+Specs
Deploying on Different Hardware that Meets RetailNext Specs
You can install the RetailNext application on any hardware certified to run 64‐bit RHEL 6.x. The CPU, memory, and storage specifications of the chosen appliance must match those of the equivalent RetailNext appliance as shown in Table 1. See https://hardware.redhat.com/ for details.
When you use hardware other than a RetailNext‐provided appliance, RetailNext supports only the RetailNext application software through one of our Support Engagement models. End‐users are responsible for the installation and support of the hardware.
Deploying on a Virtual Machine
You can use a virtual machine (VM) to install the RetailNext application on different hardware than a RetailNext‐provided appliance.
The CPU, memory, and storage specifications for the resources allocated to the VM running the RetailNext application must match those of the equivalent RetailNext appliance. However, overhead caused by running through virtualization reduces the number of channels supported for each server. Unless the VM resource allocation complies with the minimum requirements described in Table 2 and is not oversubscribed, RetailNext cannot ensure the correct functioning of the RetailNext application.
Table 2: Equivalent Resources for Virtual Machines
Server Type
VM Specifications
STORE ‐ 6 Channels
Equivalent to RN‐500‐STORE
• CPU: equivalent to Intel Pentium G2020, 2.9 GHz, 2 cores • Memory: 4GB
• Disk: 500 GB
• CPU: equivalent to Intel Xeon E3‐1225v2, 3.2 GHz, 4 cores *
• Memory: 8GB
• Disk: 2 TB
• CPU: equivalent to Intel Xeon E5‐1650, 3.2 GHz, 6 cores *
• Memory: 16GB
• Disk: 4 TB
4
Table 2: Equivalent Resources for Virtual Machines
Server Type
VM Specifications
CORPORATE SM/MED/LG
Equivalent to RN‐STORE‐2000‐DT
• CPU: equivalent to Intel Xeon E5‐1650, 3.2 GHz, 6 cores *
• Memory: 16GB
• Disk: 4 TB
* Exact resource mapping is rarely accurate when you work with VMs since resource mapping depends on the specific hardware and the specific configuration for that particular machine. We recommend adding an extra 15% to 20% in CPU performance for all configurations.
You can use any VM provider, but we recommend VMWare ESXi 5.x. Related resources can be found at the following links:
•
•
https://my.vmware.com/web/vmware/info/slug/datacenter_cloud_infrastructure/
vmware_vsphere_hypervisor_esxi/5_1
http://h18004.www1.hp.com/products/servers/software/vmware/esxi‐image.html
When you run the RetailNext application on a VM, RetailNext supports only the RetailNext application software through one of our Support Engagement models. End users are responsible for the installation and for hardware and VM support.
You can go to the PassMark Software CPU Benchmark website to compare the capabilities of a variety of CPUs at http://www.cpubenchmark.net/cpu_list.php
5
Introduction
2.
System Deployment Overview
Introduction
This chapter provides a top‐level description of the components required to successfully deploy a RetailNext system in a store. It covers these areas:
•
System components
•
Store scenarios (the component options available within the retail environment)
•
Network connectivity options
•
Bandwidth requirements
•
Store server details (security features, inbound ports, and outbound connections)
•
RetailNext appliance information and specifications
System Components
Solution Architecture
The RetailNext solution architecture consists of these components:
Figure 1: RetailNext Solution Architecture
6
Store Scenarios
Corporate (HQ)
Your store network requires only a single RetailNext Corporate server. You can host the server in your data center or with RetailNext in our secure cloud:
Figure 2: RetailNext Corporate Server
Store Scenarios
You can deploy the RetailNext system using standard IP or analog cameras, cameras with built‐in analytics, or a combination of the two.
Scenario 1: Standard Cameras
If you use standard IP or analog cameras at each store,
•
The Store server records and analyzes video. RETAILNEXT™ SERVER HARDWARE
7
Store Scenarios
•
The Corporate server retrieves analytic data hourly from the Store server (video is not retrieved): Figure 3: Store with Standard Cameras
Scenario 2: Cameras with Built‐in Analytics
If you use dedicated traffic counting cameras at each store,
•
No in‐store appliance is required.
•
Traffic data are sent directly from the cameras to the Corporate server: Figure 4: Store with Cameras with Built‐in Analytics
8
Network Connectivity
Scenario 3: Hybrid Setup
If you use a combination of standard and analytics‐capable cameras,
•
The Store server records and analyzes video from the standard cameras.
•
The Store server stores traffic data from the cameras with built‐in analytics. •
The Corporate server retrieves data regularly from the store server: Figure 5: Store with a Mix of Standard Cameras and Cameras with Built‐in Analytics
Internet Connectivity
For the most part, neither Corporate servers nor Store servers require Internet connectivity, and absolutely no information is sent out of a customer's private intranet.
Internet connectivity is required only in the following cases:
•
When no email (SMTP) server is available in the customer's intranet
•
When no time (NTP) server is available in the customer's intranet
•
When no web proxy server is available in the customer's intranet (web proxy is required for RetailNext to securely retrieve daily weather data)
•
For Mobile Device Detection in order to obtain an opt‐out list (HTTP)
9
Remote Access Management with iLO or iDRAC There are two NICs on the rear of all rack‐mounted RetailNext servers:
•
Main NIC: Provides direct access to the network.
•
iLO/iDRAC NIC: Provides remote access to the network.
–
iLO: Hewlett‐Packard ‘s Integrated Lights‐Out (iLO) provides out‐of‐band management facilities and makes it possible to perform activities on a server remotely.
–
iDRAC: Dell’s integrated Dell Remote Access Controller (iDRAC) allows you to remotely manage servers with or without a systems management software agent. When direct access to the Corporate network is not possible through the Main NIC, the iLO/
iDRAC NIC provides you with remote access.
iLO/iDRAC Requirements
•
Software configured by the RetailNext staging team
•
Cable hookup completed by the RetailNext installation team:
Figure 6: NIC Cable Hookup
•
Separate IP address
•
Available physical port on the switch
•
These open ports your firewall:
–
–
–
–
Remote Console Port: 17990
Webserver SSL Port: 443
IPMI over LAN Port: 623
AMT Port: 16992 (only if the DT is deployed)
10
Bandwidth Requirements
Client PC (Web Interface) Connectivity
User PCs require access to the following two ports on the RetailNext Corporate server:
•
TCP port 80 (HTTP) for data
•
TCP port 9800 for video
User PCs do not require access to the Store servers.
Mobile Application Connectivity
The mobile application needs access to the following two ports on the RetailNext Corporate server:
•
TCP port 443 (HTTPS) for data
•
TCP port 80 (HTTP) for video
External access to the two ports is required for the app to work when a user is outside the office (and hence is not connected to the internal Wi‐Fi).
This can be accomplished securely in several ways; for example:
•
Configure VPN on the mobile device.
•
Configure the firewall to allow limited external access.
Bandwidth Requirements
Low bandwidth links are generally sufficient.
•
The RetailNext web client is low bandwidth.
•
Data sync between a Corporate server and Store servers is low bandwidth since no video is sent out of the store.
High bandwidth links are required to view video remotely.
•
Live or recorded video is retrieved from the store only when a user requests it from the web interface or mobile application.
Video Stream Bandwidth Bandwidths are per channel of H.264 video at 10 frames per second. Numbers are approximate and assume a moderate amount of activity in the camera view.
To calculate the total bandwidth required for the store, multiply the per‐channel bandwidth by the number of cameras you want to view simultaneously in the store.
11
Store Server Details
Table 3: Video Stream Bandwidth
Security Features
The Store server provides these security features:
•
Customized, secure Linux OS
•
Removal of all unnecessary services
•
Only the minimal number of ports open on the server •
Only two login accounts: –
1 privileged (root)
–
1 non‐privileged (bvi)
•
Logging of all user activity
•
A user‐friendly, web‐based system console for easy system administration
12
Open (Inbound) Ports
The Store server has these open‐port requirements:
Table 4: Open (Inbound) Port Requirements
1
You can use the system console to configure the system firewall and block optional ports.
2Either an HTTP or an HTTPS port must be open.
3Not optional if UPS is being used in a clustered store server configuration.
Outbound Connections
The Store server has these outbound‐connection requirements:
Table 5: Outbound Connection Requirements
Note: An outbound connection can be made via web proxy to avoid direct Internet access.
13
RetailNext Appliance
RetailNext Appliance Appliance Information
The RetailNext solution is shipped as an appliance for both stability and ease of installation.
•
The hardware has undergone long‐term stability testing and been certified.
•
The software is shipped pre‐installed and ready to run.
•
If a hardware appliance is not desired, RetailNext can be installed on a VM.
•
Only VMWare ESXi 5.0 and above is supported.
•
The VM specifications must be equivalent to the corresponding RetailNext appliance specifications.
Appliance Specifications
These are the RetailNext appliance specifications:
Table 6: RetailNext Appliance Specifications
1
The Channel limit is calculated with H.264, VGA/D1/4CIF resolution, 10 fps video streams. The limit varies if
a different codec, resolution, or fps is used.
2Clustering of store servers is supported for processing more than 32 video streams in a single store.
14
Other Solution Components
Cameras
RetailNext supports these types of cameras:
•
Most popular IP camera models
•
All analog cameras (via a supported video encoder)
•
MJPEG, MxPEG, MPEG‐4, and H.264 codecs
•
HTTP and RTSP protocols
•
All frame rates and resolutions
The ideal stream for analytics is 640x480 (VGA) resolution at 8 frames/second.
•
A higher resolution and/or frame rate impacts server performance without providing any significant increase in accuracy.
See Appendix A: Supported Devices for a list of all devices supported by the RetialNext system.
Point of Sale (POS) Systems
RetailNext interacts with POS systems in these ways:
•
The RetailNext server integrates with most systems using the comma‐separated value (CSV) format. •
The POS server transfers data from the POS server to the RetailNext server in CSV format; RetailNext does not touch the POS server.
•
Data transfers can occur as frequently as every few minutes but must be performed at least once at the end of each day.
•
No PCI data (for example, customer IDs and credit/debit card numbers) are transferred or stored.
15
Staffing Systems
RetailNext interacts with staffing systems in these ways:
•
The RetailNext server integrates with staffing systems in the CSV format (similar to POS system integration).
•
Data transfer must occur once at the end of each day.
Legacy DVRs
RetailNext can retrieve both live and recorded video from some legacy digital video recorders (DVRs). DVR video is available via the RetailNext web interface and the mobile client.
This capability allows you to
•
Seamlessly add new IP cameras to the store while preserving your investment in analog cameras and DVRs.
•
Replace DVRs with video encoders and switch recording to RetailNext at any time: Figure 7: Legacy DVR Video Retrieval
Network Video Recorders (NVRs)
RetailNext can work side‐by‐side with NVRs; you simply add the desired IP cameras to the RetailNext system.
Existing NVRs will not be impacted since IP cameras can serve video over the network simultaneously to multiple clients.
16
Store Connectivity Scenarios
Legacy Traffic‐counting Systems
RetailNext can mimic traffic data from several legacy traffic vendors. This capability allows you to gradually swap out older traffic‐counting systems with RetailNext without impacting internal systems that depend on the traffic feed.
Store Connectivity Scenarios
Store servers can connect to a Corporate server over a secure intranet or via the Internet.
Scenario 1: Over a Secure Intranet
When there is an existing corporate intranet linking stores to HQ, use routers with secure VPN technology (such as IPSec): Figure 8: Connecting via Secure Intranet
17
Support and Maintenance
Scenario 2: Over the Internet
When there is no corporate intranet linking stores to HQ, use standard DSL, ISDN, cable, modems, etc.: Figure 9: Connecting via the Internet
Support and Maintenance
Email Support at [email protected] or contact your integrator.
Note: Remote connectivity to each device is required for support.
Your system integrator or RetailNext Support can handle system maintenance and the following types of issues:
•
Operating system and application software upgrades
•
Appliance hardware issues (if the appliance has been provided by the integrator or RetailNext)
•
Database, analytics, video recording, and other module issues
•
Issues with other hardware such as cameras and encoders (if provided by integrator or RetailNext)
18
3.
Channel & Storage
Recommendations
The RetailNext Channel and Storage Recommendation Calculator is an Excel tool used to estimate Store server requirements. A channel consists of a camera plus an analyzer. This tool is for internal use only and can be downloaded from the Wiki; search for “Channel and Storage Recommendation”:
Figure 9: Channel and Storage Recommendation Calculator RETAILNEXT™ SERVER HARDWARE
18
Confirming the Channel Capacity for RetailNext Servers
Confirming the Channel Capacity for RetailNext Servers
If you’re using RetailNext hardware, follow these steps to confirm the channel capacity determined by the Channel and Storage Recommendation calculator:
1. Configure cameras and analyzers:
•
•
•
•
•
•
1 analyzer per camera
Frame rate: 10 fps
Encoder: h.264
Camera resolution: 640x480
Analyzer type: tracking (people count)
Activity level: – Low: 0 or 1 person in the scene
–
Medium: 1 ‐ 2 people in the scene
–
High: 3 ‐ 4 people in the scene
–
Very high: 5 or more people in the scene
Record on Motion: enabled 2. Add cameras and analyzers to the server, let the server run for at least 24 hours, then check the system as described on this page. Find the maximum number of cameras and analyzers that can be added without violating these requirements. These are the targets for each appliance:
• RN‐500‐DT/RM: 6 channels
•
Testing Scenarios on non‐RetailNext Hardware
If you’re not using RetailNext hardware, follow these steps to test the channel and storage recommendations for your server.
The RN Channel and Storage Recommendation Calculator estimate is influenced by various factors such as the number of cameras, types of analyzers, level of activity, and video resolution. The following scenarios should be tested to determine the best values with which to populate a Store server’s Channel Calculator.
1. Test without Record on Motion (RoM): Repeat the test above but disable Record on Motion for each of the cameras. RoM is more CPU‐intensive than recording always, but fewer frames are recorded, thereby reducing disk I/O.
19
2. Test with a lower resolution: In some situations, it may be appropriate to reduce the camera resolution to increase the number of cameras and analyzers. • Repeat Steps 1 and 2 above under “Confirming the Channel Capacity” with Camera resolution set to 320x240 instead of 640x480. 3. Test demographics: Demographics analyzers consume more CPU than Tracking analyzers. a. Add two Tracking analyzers to the server and check the CPU utilization. b. Replace those cameras with face‐view cameras configured for Demographics analytics. From the results, you can determine the relative performance impact of Tracking analyzers vs Demographics.
4. Test analytics with higher levels of activity: Analyzers consume more CPU when there are higher levels of activity in the scene. a. Add two Tracking analyzers to the server for cameras with a low level of activity (0 or 1 person in the scene) and check the CPU utilization. b. Replace those with cameras (or clips via the Wowza server) with a medium level of activity (1 ‐ 2 people) and check CPU utilization. c. Repeat for high (3 ‐ 4 people) and very high (5 or more people) activity. From the results, you can determine the relative performance impact of various activity levels.
5. Test higher resolution: RoM consumes more CPU when processing higher resolution streams. a. Add two cameras at 640x480 and check the CPU utilization and disk I/O. b. Increase the resolution to 1024x768 (or similar). c. Repeat with RoM disabled. From the results, you can determine the relative performance impact of 1024x768 vs 640x480.
20
Here’s an example of a populated Excel Channel & Storage Recommendations worksheet:
Figure 10: Channel and Storage Recommendation Calculator (Populated)
21
Overview
4.
Staging the RetailNext Server
Overview This chapter is intended to help stagers install and configure the RetailNext Operating System and Application on a RetailNext server or compatible virtual machine. It includes instructions for preparing a RetailNext server for UI and analytics configuration.
Staging Outcome:
RetailNext server configured with the RetailNext Operating System and Application 5.0.1
Staging Process:
1. Install the RetailNext software on a compatible server or virtual machine.
2. Configure the software.
Prerequisites
Equipment
•
RetailNext Installation DVD or ISO Image file
•
RetailNext server or compatible virtual machine
•
RetailNext server MAC address
•
VGA‐ & DVI‐compatible monitor
•
USB keyboard and mouse
•
PC or Mac laptop (optional)
Information
•
Basic configuration information for the RetailNext server
Obtaining a RetailNext License
You are not required to upload a RetailNext license in order to complete the installation of a server. You can always go back and upload a license via the System console after the installation is complete. However, until a valid license has been uploaded to the server, you can access only the System console, not the RetailNext application.
If you do want to upload a license while you’re installing the server, the easiest way is to obtain a RetailNext license and download it to your laptop before you begin the server installation.
22
Configuring the System BIOS
To obtain a license,
1. Obtain the server MAC address.
2. Email [email protected] and provide the MAC address with a request for a license.
3. When you receive the license, download it to your computer.
Now the license can be accessed when you reach the Enable License step in the server configuration process.
Configuring the System BIOS
1. Bring up the system BIOS and verify that the date and time are correct: Figure 11: Set Date and Time
2. Navigate to Advanced > Power‐on Options and select Power On for After Power Loss: Figure 12: Power‐on Options
23
Installing the RetailNext Software
3. Navigate to Advanced > Device Options and enable S5 Wake on LAN: Figure 13: Power‐on Options
4. Navigate to Storage Options and enable RAID+AHCI Mode for SATA Emulation: Figure 14: Storage Options
1. Insert the RetailNext Installation DVD into the server.
2. Restart the server.
24
3. Select Install RetailNext: Figure 15: Start Installation
The installation process automatically detects and formats the hard disks, sets up RAID, and installs the OS and RetailNext application software. This process can take up to 20 minutes. Figure 16: Installing the Application
25
Accessing the RetailNext Server
When the installation has completed, press Enter to reboot the server: Figure 17: System Reboot
4. Immediately remove the RetailNext Installation DVD to prevent the server from booting from the DVD. Once the RetailNext server has rebooted, it’s ready for basic configuration. • If the RetailNext server is attached to a network providing DHCP, on reboot the server requests an address and uses it on its Ethernet interface. • If the server is not connected to a network or is connected to a network that does not have the DHCP service available, it auto‐configures its Ethernet interface to 192.168.0.200. You can change this in the next step of the configuration.
There are three ways to access a RetailNext server for basic server configuration:
•
•
•
Stand‐alone with No Network: Access the RetailNext server directly by plugging in a monitor, USB keyboard, and USB mouse.
Network‐based with a Laptop using DHCP: If the RetailNext server is connected to the network with DHCP, use a laptop or PC to discover and access the server via a web browser.
Network‐based with a Laptop without DHCP: If the RetailNext server is connected to the network but DHCP is not available, use a laptop or PC to access the server via a web browser using the default server IP address 192.168.0.200.
26
Stand‐alone With No Network
1. Connect a standard VGA monitor, USB keyboard, and USB mouse to the server. All connections are located on the back of the server. 2. Turn on the server.
The server starts loading RetailNext.
3. Make sure the server is loading properly: Figure 18: System Reboot
When the server has loaded the RetailNext application, the login screen opens. RETAILNEXT™ SERVER HARDWARE
27
4. Log in using login information obtained from RetailNext Support: Figure 19: RetailNext Login Screen
5. On your desktop, double‐click the RetailNext icon to launch RetailNext and connect to the server: Figure 20: RetailNext Desktop Icon
28
Network‐based Using a Laptop With DHCP
1. Make sure the UPnP service on a PC or the Bonjour service on a Mac is running on your laptop to auto‐discover the RetailNext Server.
• On a PC, open the Control Panel, go to Administrative Tools > Services, scroll down to UPnP, and make sure it's running. • On a Mac, Bonjour service is on by default.
2. To access the server, open the Computer window and click on Network: Figure 21: PC Computer Window
29
Configuring the RetailNext Server
When the Network window opens, the RetailNext server is listed under Other Devices: Figure 22: PC Network window with RetailNext App Logo
3. Double‐click the RetailNext icon to open a browser and connect to the server.
Network‐based Using a Laptop without DHCP
When DHCP is not available on the network, the RetailNext server uses the default IP address 192.168.0.200. You use this address to access the server in order to complete the basic configuration.
1. Connect your laptop to the same physical network as the RetailNext server.
2. Change the IP address of your network card, for example to 192.168.0.100.
3. Open a web browser and connect to the RetailNext console at http://192.168.0.200/
console.
4. Log in using login information obtained from RetailNext Support to connect to the server.
Once you’ve accessed the RetailNext server, the License Agreement window opens.
30
1. Click Next to accept the license agreement: Figure 23: License Agreement
2. Specify how you want to configure the system and click Next: Figure 24: System Configuration Preference
3. Specify the system type and click Next
•
Store: The system will be installed in a store and will collect data from cameras installed in the store.
31
•
Corporate: The system will be installed in a datacenter and will aggregate data from multiple stores. Figure 25: System Type
4. Enter a system name and click Next: Figure 26: System Name
When the server boots up on the network for the first time, it requests an IP address via DHCP, then populates the Network Settings screen with the values it receives from DHCP.
32
5. To keep these values, remove this IP from your DHCP scope. We recommend that you change to a dedicated IP address. 6. To change the values, enter the desired network settings for IP Address, Subnet mask, Default gateway, Hostname, and DNS servers and click Next. Note: If you need a second DNS server, click the plus sign (+) to open a field for a second DNS server IP. Figure 27: Network Settings
7. Select the NTP setting for the system and click Next: Figure 28: NTP Setting
33
8. Specify the system time zone and click Next: Figure 29: System Time Zone
9. If you have downloaded a RetailNext license to your computer, click Upload license, navigate to the license on your computer, and click OK: System
MAC
address
Figure 30: Upload License
If you have not yet obtained a license, note the system MAC address, click Next to skip the license upload, and complete the installation. RETAILNEXT™ SERVER HARDWARE
34
Note: You will be able to upload a license file later via the System console.
If you’ve uploaded a license to the server, a message confirms that it has been successfully installed: Figure 31: License Installed Successfully
This completes the basic installation of the RetailNext server: Figure 32: Installation Complete
10. Click Finish.
The server applies your settings, closes the browser window, and reboots. RETAILNEXT™ SERVER HARDWARE
35
Uploading a License Via the RetailNext System Console
You can access the RetailNext application only after a valid license has been uploaded to the server. If a valid license has not been added, you can access only the System console. To upload a license via the RetailNext System console,
1. If you haven’t already done so, email [email protected], provide your RetailNext server MAC address, and request a license.
2. When you receive the license, download it to your computer.
3. Open a web browser and go to http://<Server IP Address>/console. 4. On the System Console login screen, log in using login information obtained from RetailNext Support: Figure 33: RetailNext System Console Login Window
36
5. On the System Console Overview screen, click License: Figure 34: RetailNext System Console Overview Screen
6. On the License screen, click Upload license: Figure 35: RetailNext System Console License Screen
37
7. Browse to the location on your computer at which you downloaded the license file emailed to you by RetailNext Support and click OK: Figure 36: Select License File
A License Activation window informs you of the progress of the license activation: Figure 37: License Activation Window‐Activation in Progress
38
Accessing the RetailNext Application
When the license has been successfully activated, the License Activation window offers the options of opening the RetailNext application or closing the License Activation window and remaining in the System Console: Figure 38: License Activation Progress Window‐Activation Successful
To access the RetailNext application, 1. Open a web browser and go to http://<Server IP Address>. RETAILNEXT™ SERVER HARDWARE
39
2. Log in using login information obtained from RetailNext Support: Figure 39: RetailNext Administration Login Window
40
Index
upload a license via the system console 36
system deployment overview 6
bandwidth requirements 10
C
video stream bandwidth 10
channel & storage recommendations 18
RetailNext Channel and Storage Recommendation calculator 18
M
network connectivity 9
client PC (web interface) connectivity 9
Internet connectivity 9
mobile application connectivity 10
minimum hardware requirements 1
deploying on a RetailNext appliance 2
deploying on a virtual machine 4
deploying on different hardware that meets Retail‐
Next specs 4
RetailNext installation options 1
system overview 1
N
network connectivity 9
R
RetailNext Channel and Storage Recommendation cal‐
culator 18
other solution components 14
cameras 14
legacy DVRs 15
legacy traffic‐counting systems 16
network video recorders (NVRs) 15
Point of Sale (POS) systems 14
staffing systems 15
RetailNext appliance 13
appliance information 13
appliance specifications 13
store connectivity scenarios 16
over a secure Intranet 16
S
software installation options 1
stage the RetailNext server 22
access the RetailNext application 39
access the RetailNext server 26
network‐based using a laptop With DHCP 29
network‐based using a laptop without DHCP
30
stand‐alone With no network 27
configure the RetailNext server 30
over the Internet 17
store scenarios 7
cameras with built‐in analytics 8
hybrid setup 9
standard cameras 7
store server details 11
open (inbound) ports 12
outbound connections 12
security features 11
configure the system BIOS 23
support and maintenance 17
install the RetailNext software 24
system components 6
obtain a RetailNext license 22
corporate (HQ) 7
overview 22
solution architecture 6
prerequisites 22
41

Server Hardware.book

Transcription

Similar documents

Giuliana Rancic - Stephanie Stephens

coRcIAL. BaNks

Installing ANSYS 15 Mount the iso files using Virtual Clone

Lightning Fast Search Solutions for the Enterprise

FREE PLUS - BrandSource Digital

OPERATING INSTRUCTIONS MODEL: XXLS

Sears Commercial Discount Program

Bronica SQ-B Brochure

REUSABLE GEL HEAT PACK

WELCOME TO CAESARS PALACE