The following outlines the minimum requirements required for implementation of FireScope. Please note that FireScope only supports environments whose dependencies are within the current support by the original equipment manufacturer. For example, FireScope virtual machines will not be supported on VMware versions that have reached the end of general support by VMware.
Edge devices can be physical or virtual appliances. They are deployed on-premise to perform discovery of IT assets, data collection and accurately forwarding all of this data to the FireScope cloud.
In addition to the overall environment requirements, ensure that you meet the requirements for each individual component. Requirements for each component—EWC, EAC, ESC are outlined in the following sections. Please note that if you are implementing FireScope using the Software-as-a-Service(SaaS) model, the following components will not be required.
Of the three cloud components of FireScope , the EWC has the lowest requirements as this component is dedicated to delivering the FireScope user experience and nothing else. Because of this role, the primary consideration in sizing is the number of concurrent users. Factors such as the size of the environment and activity will not significantly impact the EWC. As a result, in many environments, only a few EWC instances may be required.
Each UI server needs:
The EAC is responsible for receiving data from the Edge device(s), normalizing the data, and analyzing status of Event Definitions, Aggregate Event Definitions, and Policies. Therefore, CPU becomes a critical requirement for this component.
Storage and memory are key for the ESC, as this is where all Attribute data is stored and queried. As much of the data set as possible is stored in memory for best query performance, therefore the amount of memory provided for this type of instance has implications on performance of the entire solution. Data retention settings are also key considerations for this instance type.
Note: For each ESC, provision a secondary VMDK with minimum storage of 500 GB. Also, anti affinity rules must be in place to ensure no 2 ESC nodes are ever on the same host or datastore.
All communication between the Edge device and the FireScope cloud is initiated by the Edge device for security purposes. The following ports will need to be open for successful communication between FireScope and each Edge device.
The following table specifies the internal ports you must keep open for the listed servers.
The following table specifies the external ports you must keep open for the listed servers.
FireScope supports the following Web browsers:
Additionally, the following requirements apply to all browsers:
If you are opting for a private instance of FireScope , there are additional requirements needed for the FireScope Cloud itself. All of the previous minimum requirements are still required.
Ensure that you meet the following environment requirements to deploy FireScope successfully.