I am considering this to be the "Selecting Appliance Type document".
I am considering this to be the "Selecting Appliance Type document".
I am considering this to be the "Selecting Appliance Type document".
Virsae Associates, business partners and customers need some sort of guidance when it comes to choosing the most suitable appliance to deploy for a given environment.
This choice comes down to a blend of the ITIL features selected, and the scale of the deployment.
Features
The software, hardware, and Raspberry Pi Collectors support all ITIL features.
The difference that each Collector type provides comes from the scale of operation that they support.
Scale
Raspberry Pi
For a Raspberry Pi Collector they typical demography of a customer should be:
- Less than 200 BHCC; and
- Less than 1,000 IP station users; and
- Five, or fewer, call server platforms; and
- Less than 20 servers or generic devices.
Typical deployment is for SMB.
Examples include Avaya IP Office, Nortel CS1K, Mitel, Linux Servers, Generic Devices.
Software and Hardware Collectors
For these Collector types, the typical demography of a customer would be close to this:
- Less than 30,000 BHCC; and
- Less than 30,000 IP station users; and
- Less than 10,000 contact centre users; and
- Five, or fewer, call server platforms; and
- Less than 100 servers or generic devices.
This is AND, not OR. The greatest influence runs from 1 through 5. For example, it is possible to have more than five call servers,
provided the total BHCC remains less than 30,000.
Typical deployment is enterprise. Examples include Skype for Business, Avaya Communication Manager and Adjuncts, Cisco Call Manager,
Nortel CS1K, Mitel, Windows and Linux Servers, generic devices.
Machine Proxy Agent (MPA)
The MPA should be installed on all Windows servers under management.
The MPA monitors Windows resources, collects events and monitors the state of services.
The MPA is only compatible with Hardware or Software Collector installations.
Collector Hardware
Software Collector
The Software Collector requires a dedicated machine or virtual machine to run and must meet the minimum specifications listed in the section below.
There are two software packages to be installed, which combined, comprise the Software Collector. These two packages are the Machine Proxy and the Client Gateway, these packages are available from Virsae.
Proxy servers are not currently supported in the Software Collector.
Resource Requirements
Resource requirements for the host machine are listed below:
| Item | Specification |
|---|---|
CPU | Min 2 @ 1.2GHZ, Recommended 4 @ 1.2GHZ |
RAM | Min 2 GB, Preferred 3 GB |
DISK | Min 128 GB |
OS | 64Bit Windows 10 or Windows Server 2012 or later |
Feature | .Net 4.6 |
Legacy Hardware Collector (Removing???????)
The VSM Hardware appliance ships as a 1U 19” rack mount form factor server with rack mounting brackets.
The VSM Hardware appliance needs to be placed in a safe location requiring only power and LAN connection. The LAN connection needs to be configured with either fixed IP addressing or DHCP.
The VSM Hardware appliance runs virtualised services within the same hardware configuration. An initial setup for configuration is required to set the network details of the host machine.
This configuration is performed by directly connecting the appliance maintenance port to the engineer’s computer at the time of installation. All other settings are passed from the Virsae cloud computing service to the appliance.
There are two IP addresses required for the appliance:
- The IP address of the VSM Appliance Host
- The IP address of the VSM Machine Proxy (Probe service)
These are different IP addresses on the same LAN connection.
Where data needs to be directed to the probe server from various devices, such as SNMP traps and syslog data, this requires a defined static IP address. As such a static IP address or DHCP Reservation is preferred.