TP-Link 13dBi PharosControl V1 UserGuide - Page 4
Quick Start Guide, 1.1 Introduction, 1.2 Installation
View all TP-Link 13dBi manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 4 highlights
Chapter 1 Quick Start Guide Pharos Control User Guide 1.1 Introduction Pharos Control is a client-server based network management system application that allows for the centralized management and maintenance over the entire network formed by TP-LINK Pharos devices. It provides the following main features: Discover Pharos devices in the same subnet with the server. Connect devices and monitor their status: The Pharos Control server will monitor the status updates of those devices under management. Firmware upgrade: Devices under management can be upgraded from the Pharos Control. Multiple devices can be upgraded synchronously as a batch. Task Schedule: Automatically execute device discovery, reboot and firmware update tasks. These tasks can be performed once or periodically. Device configuration backup and restore: Backup or restore multiple device configurations remotely. Device statistics/graphs: Display the attributes of the device in the device details list and the graph view. Attributes in the graph can be customized and plotted for a period of time. Device grouping: Provide a device tree for navigation and device selection. The built-in auto grouping is categorized as managed and unmanaged. Users can also customize device groups in the manual grouping branch. Log, error and debug history: Record the system's working, error and debugging history. C/S architecture: Allow multiple users to access one single server. Users can be assigned different access levels (administrator, manager and guest). 1.2 Installation Pharos Control server is an application typically hosted on a machine within the private network, together with the managed devices. Users can login the server through the Pharos Control client from anywhere on the network or over the Internet. The server is meant to run continuously, to monitor and collect statistics about the managed devices. It is possible to run the server and client on the same machine, and launch the server on-demand, but this is not recommended. System requirements for the server primarily depend on the number of the managed devices and the frequency of statistic updates from those devices. A single core machine with 512M dedicated 1