When designing an Avalanche infrastructure the question always arises on how many Mobile Devices servers to install and what logic should be applied to determine the number and location of the Device servers. This is specially true if either a new Avalanche environment is being installed or an upgrade is performed in the form of a side by side migration. Side by side migration is where the previous installation of Avalanche is not upgraded but a new Avalanche 6.1 infrastructure is installed along side the existing installation and the devices are migrated from the old infrastructure to the new infrastructure. How the devices can be migrated between environments can form part of another article.
There are two models possible:
1. Centralised model and
2. Distributed model
Lets look at both these models in bit more detail and the scenarios where these can be typically implemented.
Centralised model - All of the Avalanche services are installed on a single computer. This type of configuration is typically used for smaller implementations of under 5000 devices connecting to the Device server. A good example of this is a lab environment or development environment. If there are no specific business requirements or bandwidth considerations this model can also be used. Two configurations are possible with the centralised model depending on whether smart (Android/iOS) devices are present in the environment.
i) Enterprise Server with Mobile Device Server and Smart Device Server - used for implementations of under 1500 devices.
ii) Enterprise Server with Mobile Device Server - used where there are no smart devices to be managed, and the number of AIDC devices are under 5000.
Distributed Model - In a distributed model the Device servers are installed on different servers. Depending on the server specs (CPU,RAM and Disk Space) the maximum number of devices that can connect to a device server is 10000.
There are several requirements which can dictate the number and placement of Device servers apart from the number of devices connecting to the Device server. Lets look at some possible scenarios.
i) Bandwidth requirements - for low bandwidth sites it is advantageous to have a Device server on site rather then in a central data centre. That way the devices connect to local server to download packages.
ii) Business Requirements - If a business has several business sections it may make sense to install a Device server for each business. The devices for each business connect to their respective Device server.
iii) Device Types - If several different types of devices are present in the environment it may make sense to split device servers per model. Example - a device server for printer and a device server for scanners.
iv) Geo location - One other option is to create a Mobile Device Server in each state of the country.
Note - there can be multiple device servers but only one smart device server.
There are two models possible:
1. Centralised model and
2. Distributed model
Lets look at both these models in bit more detail and the scenarios where these can be typically implemented.
Centralised model - All of the Avalanche services are installed on a single computer. This type of configuration is typically used for smaller implementations of under 5000 devices connecting to the Device server. A good example of this is a lab environment or development environment. If there are no specific business requirements or bandwidth considerations this model can also be used. Two configurations are possible with the centralised model depending on whether smart (Android/iOS) devices are present in the environment.
i) Enterprise Server with Mobile Device Server and Smart Device Server - used for implementations of under 1500 devices.
ii) Enterprise Server with Mobile Device Server - used where there are no smart devices to be managed, and the number of AIDC devices are under 5000.
Distributed Model - In a distributed model the Device servers are installed on different servers. Depending on the server specs (CPU,RAM and Disk Space) the maximum number of devices that can connect to a device server is 10000.
There are several requirements which can dictate the number and placement of Device servers apart from the number of devices connecting to the Device server. Lets look at some possible scenarios.
i) Bandwidth requirements - for low bandwidth sites it is advantageous to have a Device server on site rather then in a central data centre. That way the devices connect to local server to download packages.
ii) Business Requirements - If a business has several business sections it may make sense to install a Device server for each business. The devices for each business connect to their respective Device server.
iii) Device Types - If several different types of devices are present in the environment it may make sense to split device servers per model. Example - a device server for printer and a device server for scanners.
iv) Geo location - One other option is to create a Mobile Device Server in each state of the country.
Note - there can be multiple device servers but only one smart device server.
No comments:
Post a Comment