|
|
|
|
Prior to your install, you should ensure that you have complete information about your IT environment where Traverse is being installed.
Note: You can specify a port number other than (the default) 80 when installing Traverse. Remember to include this port number in the Traverse URL.
Traverse Installation Checklist
Question |
Relevance |
Number of geographical locations with significant concentration of devices? |
Instead of geographical locations, you can use the network topology instead. Install a DGE at each location that has a large concentration of devices. Use a single centralized DGE for small remote locations. |
Number of devices to be monitored in each location? |
This is for sizing the DGE at each location. Each DGE can typically handle 500-1500 devices. |
Are there any large switches, routers, or servers at each location? |
A large switch with 500 ports can have close to 3000 tests (6 tests for every port). This is the same as the number of tests on 100 devices. |
Number of departments accessing the system? |
You need to determine the permissions for each department (Read-Only or Read/Write). Also, you need to determine whether departments manage their own devices in Traverse, or whether another centralized department manages these devices. |
Are there any existing custom monitors that require migration to Traverse? |
Use the various APIs to interface any custom monitoring scripts to Traverse. See the Traverse Developer Guide & API Reference. |
Do you need to interface with any existing provisioning system? |
You can add the existing inventory system you use manage devices on the network directly into Traverse. |
Are there any other web servers or instances of MySQL operating on the Traverse Server? |
Traverse includes its own web server, and you must disable IIS or any other web server operating on the server. Alternatively, configure Traverse to operate on an alternate port. See Web Server TCP/IP Port for more information. Make sure that you disable any firewalls operating on the Traverse server. See Problem: Cannot access Web Application for more information. |
Large Environments
For large environments that have at least 30000 to 50000 tests, for 1000 or more devices, Kaseya recommends that you add an additional DGE for monioring for every 800-1200 devices, approximately one DGE for every 20000 tests.
The actual monitoring capacity depends on the number of tests on each device. A server might only have four or five tests, but a large switch with 500 ports can have as many as 5000 tests. If a DGE can no longer manage tests due to high volume, the internal queues begin backing up and a message is automatically sent to the error log.
However, avoid deploying too many DGEs, because it increases administrative overhead and the probability of failures.
An example hardware configuration for a DGE-only server in a large environment is as follows:
Static IP Addresses
Because Traverse components (on different servers) communicate with each other over TCP/IP protocols, you must configure the servers on which you are installing Traverse with static IP address. During the installation process, you are prompted for the IP address of the host w/BVE ObjectStore. When configuring new DGEs in the Traverse Web Application or BVE API server, you must specify the corresponding IP addresses.
Using a static IP address ensures proper operation of the communication subsystem service and prevents issues from occurring in BVE/DGE communications.