User guide

55
CHAPTER
3
DSView Server
About the DSView Server
The DSView Server contains the DSView software that enables DSView users to securely access,
manage, monitor and control remote target devices through DSR switches and CPS serial over IP
appliances. The DSView Server provides a centralized database repository for storing
configuration, DSView user, unit and system information and also provides services for
authentication, access control, auditing, monitoring and license management.
A Hub DSView Server is responsible for maintaining the master copy of the database in a DSView
system. Only one DSView Server in a DSView system may be configured as the Hub DSView
Server. The Hub DSView Server is assigned to your DSView system during system configuration.
Spoke DSView Servers perform database replication with the Hub DSView Server. The Hub
DSView Server acts as the traffic cop for database replication between itself and all of the other
Spoke DSView Servers in a DSView system. A Hub DSView Server and Spoke DSView Server
both offer the same DSView software functionality to a DSView user. The distinction of "Hub" or
"Spoke"only has to do with the database replication role that the server plays and not with the
functionality that the server offers to the DSView user. Adding one or more Spoke DSView Servers
to a DSView system provides redundancy and the ability to distribute DSView functionality across
multiple sites.
Once the Hub DSView Server and optional Spoke DSView Server(s) are configured, you may
create and configure the type of access levels you wish to provide for DSView users within your
network environment. Access levels may be assigned to DSView users when they are created, or at
a later time by click on a DSView user’s name. See Adding DSView Users on page 229 for
information on creating DSView users and Viewing the Access Rights of DSView Users on
page 237 for information on modifying DSView user access levels.
You may also set up audit logs to record full details of user access and individual KVM switching
activity. See Working with Audit Logs on page 401 for more information.