68 DSView 3 Software Installer/User Guide
• Converting a hub server to a spoke server by registering it as a spoke to another DSView 3
software hub server. The DSView 3 software system data on the hub server being converted
will be lost and the converted hub server will replicate the data of the new specified hub server.
You may also change the properties of a spoke server or remove spoke servers from your system.
To display a list of spoke servers:
NOTE: The Spoke Servers window is only available on the hub server.
1. Click the System tab.
2. Click DSView Server in the top navigation bar. The side navigation bar will include the name
of the server to which you are logged in.
3. Click Properties in the side navigation bar, and then click Spoke Servers. The Spoke Servers
window will open.
You may change the fields that display by using the Customize link. See Using the Customize
link in windows on page 26.
Each spoke server in the list includes status.
To add a spoke server:
1. Install the DSView 3 software on the computer that will be used as a spoke server. See
Installing the DSView 3 Software on page 10.
2. Configure the computer as a spoke server. See Configuring the DSView 3 Software on page13.
Table 5.2: DSView 3 Software Spoke Server Status
Status Cause
Responding Normal operation. The hub and spoke servers are communicating with each other
using HTTPS.
Not responding The hub and spoke servers cannot communicate with each other using HTTPS. This
typically indicates a network communication error. Ensure that network connectivity is
occurring between the two servers.
Hub/Spoke Versions
Not Compatible The versions of DSView 3 software on the hub and spoke servers are not compatible.
Certificates Do Not
Match
Certificates on the hub server and spoke servers do not match. See Managing hub and
spoke server certificates on page 60 for information about updating the server
certificates so that they will match.
Invalid Server or
Versions Not
Compatible
A server responded, but it is not compatible with the DSView 3 software. This typically
occurs when communication is attempted with a server that does not contain the
software, or if either server contains an older version of the software. Ensure that both
servers are running the same DSView 3 software version.