Agent Installation and Configuration
Overview
FireScope DDM includes optional Agents that can be installed on most commonly deployed server platforms. These Agents enable to better access to OS-specific performance metrics and log files. FireScope officially supports Agents on manufacturer supported versions of enterprise level operating systems patched to the currently supported service pack/patch level. If an Operating System is unsupported by our C++ Agent, then our Java based Flex Agent could be used for compatibility.
Agent Operation
At the time of installation, the installer creates the necessary user, group and other folders needed for the Agent to run. The Agent comprises of two processes:
- firescope_agentd - The firescope_agentd listens on the configured port which is usually 8042. The firescope_agentd has following functions,
- It periodically(every 30 seconds) sends the agent_info to Edge device. Agent info is an xml content as shown below.
<?xml version="1.0" encoding="UTF-8"?>
<agent_info>
<ip>10.0.23.221</ip>
<port>8042</port>
<mgmt_port>8044</mgmt_port>
<os>windows</os>
<arch>64</arch>
<version>4.0.49</version>
<build>41179</build>
<ping_period>30000</ping_period>
<last_upgrade_time />
<last_upgrade_status />
</agent_info
- When the Discovery job is run by Stratis, the Edge device requests the agent_capabilities from the Agent. Agent capabilities is an xml content that includes the details about storage, cpus, interfaces, and system.
<?xml version="1.0" encoding="UTF-8"?>
<discovery>
<hosts>
<host address="constant">
<capabilities>
<cpus>
<cpu>
<name>Cpu 1</name>
<description>0</description>
<index>0</index>
<load-oid>cpu_utilization(0)</load-oid>
</cpu>
<cpu>
<name>Cpu 2</name>
<description>1</description>
<index>1</index>
<load-oid>cpu_utilization(1)</load-oid>
</cpu>
<cpu>
<name>Cpu 3</name>
<description>2</description>
<index>2</index>
<load-oid>cpu_utilization(2)</load-oid>
</cpu>
<cpu>
<name>Cpu 4</name>
<description>3</description>
<index>3</index>
<load-oid>cpu_utilization(3)</load-oid>
</cpu>
</cpus>
<interfaces>
<interface>
<name>Local Area Connection</name>
<description>Local Area Connection</description>
<admin-status>UP</admin-status>
<operational-status>UP</operational-status>
<interface-type>ethernet-csmacd</interface-type>
<inbound-errors-oid>network_interface_incoming(Local Area Connection,errors)</inbound-errors-oid>
<outbound-errors-oid>network_interface_outgoing(Local Area Connection,errors)</outbound-errors-oid>
<inbound-traffic-oid>network_interface_incoming(Local Area Connection,bytes)</inbound-traffic-oid>
<outbound-traffic-oid>network_interface_outgoing(Local Area Connection,bytes)</outbound-traffic-oid>
<admin-status-oid />
<operational-status-oid />
</interface>
<interface>
<name>Loopback Pseudo-Interface 1</name>
<description>Loopback Pseudo-Interface 1</description>
<admin-status>UP</admin-status>
<operational-status>UP</operational-status>
<interface-type>softwareLoopback</interface-type>
<inbound-errors-oid>network_interface_incoming(Loopback Pseudo-Interface 1,errors)</inbound-errors-oid>
<outbound-errors-oid>network_interface_outgoing(Loopback Pseudo-Interface 1,errors)</outbound-errors-oid>
<inbound-traffic-oid>network_interface_incoming(Loopback Pseudo-Interface 1,bytes)</inbound-traffic-oid>
<outbound-traffic-oid>network_interface_outgoing(Loopback Pseudo-Interface 1,bytes)</outbound-traffic-oid>
<admin-status-oid />
<operational-status-oid />
</interface>
</interfaces>
<memories>
<memory>
<name>Memory 1</name>
<description>Memory 1</description>
<storage-type>RAM</storage-type>
<total-space-oid>memory_size(total)</total-space-oid>
<free-space-oid>memory_size(free)</free-space-oid>
</memory>
</memories>
<storages>
<storage>
<name>C:\</name>
<description>C:\</description>
<mount>C:\</mount>
<storage-type>FIXED_DISK</storage-type>
<total-space-oid>filesystem_size(C:\,total)</total-space-oid>
<used-space-oid>filesystem_size(C:\,used)</used-space-oid>
<pused-space-oid>filesystem_size(C:\,pused)</pused-space-oid>
</storage>
<storage>
<name>E:</name>
<description>\vboxsrv\SpinningDrive</description>
<mount>E:</mount>
<storage-type>NETWORK_DISK</storage-type>
<total-space-oid>filesystem_size(\vboxsrv\SpinningDrive,total)</total-space-oid>
<used-space-oid>filesystem_size(\vboxsrv\SpinningDrive,used)</used-space-oid>
<pused-space-oid>filesystem_size(\vboxsrv\SpinningDrive,pused)</pused-space-oid>
</storage>
<storage>
<name>Z:</name>
<description>\fsfile\storage</description>
<mount>Z:</mount>
<storage-type>NETWORK_DISK</storage-type>
<total-space-oid>filesystem_size(\fsfile\storage,total)</total-space-oid>
<used-space-oid>filesystem_size(\fsfile\storage,used)</used-space-oid>
<pused-space-oid>filesystem_size(\fsfile\storage,pused)</pused-space-oid>
</storage>
</storages>
<system-description>
<description>Windows 8 (x64 version)</description>
<up-time>1074</up-time>
<contact />
<name>Bryancan-PC</name>
<location />
<organization />
<description-oid>host_information</description-oid>
<up-time-oid>host_uptime</up-time-oid>
<contact-oid />
<name-oid>host_name</name-oid>
<location-oid />
</system-description>
</capabilities>
</host>
</hosts>
</discovery>
- When the Edge device sends a query to collect the value of an attribute, the Agent processes the request and sends the response back to the Edge device.
2. firescope_agent_managerd - The firescope_agent_managerd listens on the configured port which is usually 8044. The firescope_agent_managerd has three main roles.
- Ensure that the firescope_agentd process is always running. If it is not running then the firescope_agent_managerd attempts to start it every 30 seconds.
- Update the Agent when a new update becomes available.
- Change the Agent configuration properties.
Supported Operating Systems
| Operating System | Versions |
| Microsoft Windows | Windows 2003 Server and above, 32- and 64-bit |
| Red Hat Enterprise Linux | 4 and above, 32- and 64-bit |
| SUSE Linux Enterprise | 10 and above, 32- and 64-bit |
| Solaris | 9 and 10, Sparc and x86 |
| AIX | All versions officially supported by IBM |