SDDM Admin Guide

From FireScope Documentation Site
Jump to: navigation, search

The Administration Guide provides valuable information on tasks performed by your Administrator.

System Requirements

The following outlines the minimum requirements required for implementation of FireScope SDDM. 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 Device System Requirements

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 SDDM cloud.

  • 8 vCPUs
  • 12 GB of RAM
  • 100GB for Primary Disk

Note: The storage requirement for the Edge device is large, to ensure sufficient storage space for caching in case of loss of connectivity with the FireScope SDDM cloud. The number of Configuration Items it collects from frequency of polling, and scope of data collection methodologies impact its performance.

Additional Components Required for an On-Premises Implementation

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 SDDM using the Software-as-a-Service(SaaS) model, the following components will not be required.

Elastic Web Component (EWC)

Of the three cloud components of FireScope SDDM, 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:* 4 vCPUs

  • 4 GB of RAM
  • 40GB for Primary Disk

Elastic Application Component (EAC)

The EAC is responsible for receiving data from the Edge device(s) an normalizing the data. Therefore, CPU becomes a critical requirement for this component.* 6 vCPUs

  • 12 GB of RAM
  • 60GB for Primary Disk

Elastic Storage Component (ESC)

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.* 4 vCPU

  • 24 GB of RAM
  • 60GB for Primary Disk
  • 500GB for Secondary Disk

Note: For each ESC, provision a secondary VMDK with minimum storage of 500 GB.

Port Communication Requirements

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 SDDM and each Edge device.

Internal

The following table specifies the internal ports you must keep open for the listed servers.

Servers Open Ports
Elastic Storage Component(ESC) <----------> Elastic Web Component (EWC) 22, 27020, 30000, 40000
Elastic Web Component (EWC) <–-------> Elastic Application Component( EAC) 22, 25, 80, 443, 8080http: 28050, 28051 https: 28060, 28061
Elastic Application Component( EAC)<–-------> Elastic Web Component (EWC) 15672
Elastic Application Component( EAC)<----------> Elastic Storage Component(ESC) 22. 30000, 40000
Edge <----------> Elastic Application Component( EAC) http: 18050, 18051 https: 18060, 18061

External

The following table specifies the external ports you must keep open for the listed servers.

Servers Open Ports
Elastic Web Component (EWC) 80, 443
EMI 8004
Edge <----------> Elastic Application Component( EAC) http: 18050, 18051 https: 18060, 18061
All Servers ←-------→ stratisupdate.firescope.com 80, 443
Web Services 38050, 38051, 38060, 38061
Edge ----> RabbitMQ 5672
sFlow Collector ------> Edge 6343(UDP)
NetFlow Collector ----> Edge 2100 (UDP)

Note:* If you want to use 38060 for SSL you need to disable peer authentication.

  • Edge to RabbitMQ---The edge has to reach web2 via ssl port 5671 or non ssl port 5672.
  • The address each Edge should use to reach the RabbitMQ is to be filled out in the Global Network Traffic Settings form on the Edge Devices page inside your account.Enter the address in Application Messaging IP/DNS field.

Link=

Web Browser Requirements

FireScope SDDM supports the following Web browsers:

Internet Explorer 8 and aboveNote: Compatibility mode not supported. HTML5 is not natively supported in versions older than 9.
FireFox 6 and above
Safari 3.2 and above
Chrome 6.0 and above

Additionally, the following requirements apply to all browsers:# JavaScript is enabled

  1. Minimum resolution: 1024 x 768

On-Premise Implementations Minimum Requirements

If you are opting for a private instance of FireScope SDDM, there are additional requirements needed for the FireScope SDDM Cloud itself. All of the previous minimum requirements are still required.

Ensure that you meet the following environment requirements to deploy FireScope SDDM successfully.


ESX Servers 3 (5 preferred)
Minimum Instances 3 x EWC2 x EAC2 x ESC1 x Edge Device
VM Environment VMware vSphere 4+ESX servers with proper configuration(Key settings are correct Time Source and Hostname)Standard VMware images, with VMDK support
Supported Storage FC SAN (preferred)Fast iSCSIDirect Attached SAS*NAS is not supported.
Network Fast Ethernet, fully switchedDistributed vSwitches for ESX

All primary Firescope SDDM components (EWC, EAC, and ESC) communicate over TCP/IP Protocol within the Firescope SDDM Cloud Environment. Each layer must have the appropriate access to the other layers in order for the application to perform optimally. As the Firescope SDDM Cloud Environment is typically housed in the same location, no special firewall rules or protocols should be required.

Pre-Deployment

The following items must be addressed before FireScope DDM can be initialized.# NTP must be configured in the Firescope Console of each VM. Record the IP address or DNS name for an authoritative NTP time source here: _______________

  1. The following VMware OVAs from Firescope are delivered prior to onsite visit:
    1. SAPP
    2. SEDGE
    3. SMONGO
    4. SWEB
  2. Access to vCenter with correct permissions to deploy, edit, and start/stop VMs.
  3. Access to the OVAs location (e.g., shared drive, datastore).
  4. IPs pre-allocated for each VM.
    1. Complete the DDM Core Setup Table.
  5. Access to a primary and secondary DNS server with the ability to do forward and reverse DNS lookup of IP addresses.
  6. DNS A records and reverse lookup entries for all Stratis servers.
  7. Load balancer configuration pre-allocated and configured.
    1. See the Load Balancer Configuration Example.
  8. Pre-allocated storage space for each Mongo database.
    1. Separate VMDK in the datastore (minimum size recommendation 200GB)
    2. Network Attached Storage
  9. Firescope will assist with this.
    1. Other
  10. Firescope will assist with this.


Firewall settings. For more information, see the Deployment Guide.

SDDM Core Setup Table


Hostname Function IP Datastore Name ESX Host Target (Initial) vCPU Memory
sapp1 App Server 1.1.1.1
sapp2 App Server 2.2.2.2
smongo1 Mongo Server 3.3.3.3
smongo2 Mongo Server 4.4.4.4
smongo3 Mongo Server 5.5.5.5
smongo4 Mongo Server 6.6.6.6
sweb1 UI Server 7.7.7.7
sweb2 UI Server 8.8.8.8
sweb3 UI Server 9.9.9.9
sedge1 Edge Server 10.10.10.10

Load Balancer Configuration Example

You may use load balancers for the EXC and EAC VMs. The following table is a load balancer configuration example.

DNS Name Purpose IP Ports Health Check Load Balance Metric Pool Members
uibalance FireScope UI 11.11.11.11 ALL /blank.php (80) Fewest Connections sweb1, sweb2, sweb3
appbalance FireScope App 12.12.12.12 ALL  :18050/edge_services/attribute_results Fewest Connections sapp1, sapp2

Note: Load Balancer Health Check URLs

http://<app-server-ip>:28050/ui_services/cihttp://<app-server-ip>:18050/edge_services/attribute_resultshttp://<app-server-ip>:38050/web_services/cihttp://<app-server-ip>/ui_services/cihttp://<app-server-ip>:18050/edge_services/attribute_resultshttp://<app-server-ip>:38050/web_services/ci

Deployment Guide - On-Premises

For a successful deployment of FireScope DDM on-premises, we recommend the following:# Install the Elastic Web Component (EWC), Elastic Application Component (EAC), and Elastic Storage Component (ESC) components in the same location.

  1. If you choose to set the static IP for a server (instead of using a dynamic IP),
    • Provide the IP details
    • Allow the scripts to run
    • Wait until you are returned to the main console screen before proceeding
  1. When you set the date and time for your server, sync the server with a network time protocol (NTP) server.
  2. When you complete the final step in an AMI Configuration Wizard, do not close the AMI before it automatically directs you to the associated server's AMI.
  3. During the Edge device setup, select HTTP as the communication protocol. If you select HTTPS you will reduce your bandwidth capabilities between the Edge device and the other servers.
  4. Start the servers in the following order:
    • MongoDB servers
    • Application server
    • UI servers 1 and 2
    • UI server 3
    • Get IP address

Upgrading

When upgrading your FireScope DDM environment, complete each one in the following order one VM at a time:# All MongoDB VMs.

  1. All Application VMs.
  2. All UI VMs.
  3. All Edge Devices.

MongoDB Servers

Follow these steps for the two MongoDB VM servers:# Start the two MongoDB servers.

  1. Access each server's console and either:
    1. Find the dynamic IP, or
    2. Set the static IP
  2. Note both servers' IP addresses for future reference.

For more information, see the MongoDB online documentation.

Application Server

Follow these steps to get the IP address for the application server:# Access the server's console and either find the dynamic IP or set the static IP.

  1. Note the IP address for future reference.

UI Servers 1 and 2

Follow these steps for two of the three UI VM servers:# Start two of the UI servers.

  1. Access each server's console and either:
    1. Find dynamic IP, or
    2. Set the satatic IP
  2. Note both servers' IP addresses for future reference.

UI Servers 3

After you start the first two UI VM servers, you will start the third UI VM server and configure it to function as the main UI server. To start and configure the third UI VM server, follow these steps.

Get the IP Address

To get the IP address for the third UI server, follow these steps:# Access the server's console and either find the dynamic IP or set the static IP.

  1. Note the IP address.

[1]

Edge Device

The Edge device resides at each business location, performs Discovery and data collection, and pushes the resulting data up to the central FireScope DDM Cloud. All Edge device configuration is performed through the central FireScope DDM interface, enabling new business locations to be easily integrated into Dashboards by starting up a new Edge device and pushing down configuration. Edge Devices can be physical or virtual appliances, depending on the size of the environment they reside in and volume of data collected.

Communication with the central cloud can be over standard HTTP or HTTPS, is configurable per Edge device, and leverages message queuing to ensure accurate delivery of data. Additionally, if an Edge device loses connectivity to its cloud, data will be locally cached until connectivity is restored, at which time a secondary history queue is used to push cached Attribute data without disrupting real-time data.

600px

Deploy Edge Device(s)

NOTE: You should have downloaded your OVA with your welcome e-mail if you haven't please go download and come back here.

Once the file is downloaded successfully, connect to ESX Server via vSphere client or vSphere webclient

Image2.png Image3.png

Click on Deploy OVF Template and Deploy OVF Template wizard and follow along

Click on Browse and select the SEDGE.ova that was downloaded and click Next

Specify a Name of the VM (as per your company standards) and click Next

Select DataStore and click Next

Select Thin provision and click Next

Check the box Power on Deployment and Click Finish

After successful deployment, node will start. Once the node is started, follow steps below in your VM Console for Network and hostname assignments.


Enter 1 for Configure Network Settings

Image4.png

  • Select No

Image5.png

  • Enter the Hostname. Give the edge a hostname

Image6.png

  • Enter IP Address. Provide an open non-provisioned IP

Image7.png

  • Enter a Subnet Mask

Image8.png

  • Enter Gateway

Image9.png

  • Enter PRIMARY DNS Server

Image10.png

  • Enter SECONDARY DNS Server

Image11.png

  • Enter NTP Server. Provide either an internet or local NTP server.

Image12.png

Note: Once you enter all above details, SEDGE Node will be installing required modules / updates and Creates Database and tables etc.

Create Edge - CMI Account

Create Edge Device # Log into CMI Account

  1. Click on Administration > Device Management > Edge Device, Manage Edge devices page will be displayed.

5277.CMI Edge Page 1.png-957x477.png

  1. Click on the Create button. Create Edge Device form will be displayed.    

CMI Edge Form.png-707x671.png

  1. Complete the form.
  1. Click on the Save button.                                                                                                                 
  1. Click on Download Key button
  2. Select Save file option.

  Note: Registration key is necessary for Edge Registration

Create Edge - Non CMI Account

SAAS customers do not have access to the CMI Account, so to create an Edge device the user has to log in with Account Admin User Access level.

To create an Edge device# Log in to FireScope SDDM with Firescope or Account Administration privileges. Click on Configuration > Edge Device, Manage Edge devices page will be displayed.

Edge Device.png-803x133.png To create a new Edge Device click on the Create button or to set the network traffic collection rules for all edge devices click on Global Network Traffic Settings (upper right hand corner) button.

Create New Edge Device

Create Edge Device form will be displayed.

Create Edge DDM.png-801x556.png

Select the Edge Device Status from the drop down list. Edge Device. If you select Disable, the Edge Device will stop collecting data. In Edge Device Details section, enter Enter a name that will describe the Edge Device, for e.g name based on location or department. Enter description regarding the Edge Device like location, department or purpose. TimeZone - You can click on the Change button to select a different Country and its Timezone from the drop down list.

7450.NonCMI Edge TimeZone.png-405x248.png

  1. Proxy: Click on the Check box Use Proxy if you want to use a proxy for this Edge device. Proxy section will be expanded with the connection information fields.

7713.NonCMI Edge Proxy Section.png-320x240.png

Method: Chose a Method from the drop down list.

  • Enter Username and Password
  • Enter Host and Port of the Proxy.

Select the Application Server Connection Settings from the drop down list. Network Traffic Collector - Set the rules for network traffic collection in this section.

3884.Network Traffic Collector.png-488x251.png

Collect Traffic: Select Enabled or Disabled from the drop down list. Select Options:

  • Collect NetFlow:  NetFlow is a network protocol developed by Cisco for collecting IP traffic information and monitoring network traffic. By analyzing flow data, a picture of network traffic flow and volume can be built. Supported versions: V1/V5/V7/V8/V9/V10.
  • Collect SFlow:  sFlow is a general purpose network traffic measurement system technology. sFlow is designed to be embedded in any network device and to provide continuous statistics on any protocol (L2, L3, L4, and up to L7), so that all traffic throughout a network can be accurately characterized and monitored. Supported version: V2/V4/V5.
  • Promiscuous Mode: In a network, promiscuous mode allows a network device to intercept and read each network packet that arrives in its entirety. This mode of operation is sometimes given to a network snoop server that captures and saves all packets for analysis (for example, for monitoring network usage).
  • Promiscuous Mode Network Interface: Specify network interface for capturing promiscuous network traffic.

Lowercase, alphanumeric characters only. Leave blank to default to OS selected network interface.

Enter the IP Exclusion List which is a comma-separated list of IPs to be excluded. The list you enter, uses normal IP range syntax, so it can include hostnames, CIDR netblocks, octet ranges, etc.

Port Exclusion List: Enter a comma-separated list of ports you want to exclude. The list can be individual ports (8024,8025) or a range of port (8024-8034).

IP Inclusion List: Enter a comma-separated list of IPs to be the ONLY ones included in network traffic data collection. The list you pass in uses normal IP range syntax, so it can include hostnames, CIDR netblocks, octet ranges, etc.

Port Inclusion List: Enter a comma-separated list of ports to be the ONLY ones included in network traffic data collection. The list can be individualports (8024,8025) or a range of port (8024-8034).

Click on the Save button. The Edge Device page will be displayed.


Edge Page 1.png-801x191.png

Click on the Download Key button. Option to Save or Open the Edge device key is displayed. Select the Save option. Note: This registration key will be used for [2]

Register Edge

Open your browser and type http://<ip or dns of your newly deployed Edge Device>:8004. Login page will be displayed.

Pastedimage1472835239176v1.png-320x240.png

Enter Username and Password. Click on Login. FireScope DDM EMI menu page will be displayed.

Pastedimage1472835239177v2.png-320x240.png


Click on Administration > Edge Registration. Edge Registration Key page will be displayed.


Pastedimage1472835239177v3.png-320x240.png

Drag & Drop EDGE Registration Key or Browse and upload Key. Note: Follow below link to obtain EDGE Registration KeyFor CMI

Click on the Validate Registration Key. Validation page will be displayed.


Pastedimage1472835239177v4.png-591x205.png


Click on Submit the Registration Key. Edge Registration Complete page will be displayed.


Pastedimage1472835239178v5.png-693x313.png

Click on Edge Registration Complete. Refresh the Manage Edge Device page in CMI account. You will see the registered Edge Device IP address.

Edge Device Manage.png-765x139.png

Edge Assignment Rules - Non CMI Account_DDM

Here you can schedule Data Analysis, assign discovered CIs to Edge Devices based upon IP ranges and if there are CIs which do not match the IP filters and ranges you can assign them to a default Edge device.


Note: Saving the Edge assignment Rules page will restart the job.


To accomplish the above,

Log in to FireScope DDM with Firescope or Account Administration privileges.


Click on Configuration > Edge Assignment Rules, Edge Assignment Rules page will be displayed


0447.Edge Assignment Rule.png-806x574.png


Status: You can enable or disable the Edge assignment Rule by selecting Active or Disable from the drop down list.


Dependency Analysis Schedule:  Select the interval of frequency from the drop down list. to determine often you want the job to run.


Last Check: Displays the date and time the job starts processing


Finished: Displays the date and time the job was completed .


Results: This displays the status (success/fail) and number of Service Groups processed


Edge Device Assignments for Network Traffic: Network Traffic which is selected by Business Service Rules will be assigned to the selected Edge Devices based on matching IP ranges. You can also select the default Edge Device assignment for all other CIs not matching the specified IP ranges.

Click on Add Rule button to add IP addresses or IP range. IP Range section will be displayed

7776.ED Assignment For Network Traffic.png-520x119.png


IP range: Enter Network IP address(s) you want to assign to a particular Edge Device. You can enter a single IP, multiple IP's or a Range of addresses.


Examples:Multiple IP's:192.168.0.1,192.168.0.2,192.168.0.3

IP Ranges:192.168.0.1-254 (means 192.168.0.1 to 192.168.0.254)192.168.0-14.1-254 (means 192.168.0.1 to 192.168.14.254)192.0-1.1-4.1-254 (means 192.0.1.1 to 192.1.4.254)191-192.0-1.1-.1-254 (means 191.0.1.1 to 192.1.4.254)Also supports CIDR notation (192.168.0.0/24) See http://www.subnet-calculator.com/cidr.php

Edge Device: Select an Edge Device from the drop down list, to which the network traffic will be assigned to. Note: You can add multiple rules by clicking on the Add Rule button or remove a rule by clicking on the Remove button.

Select an Edge device from the drop down list  to which all the other CIs that do not match the IP filter and ranges will be assigned to.

Cloud Migration: Risk Analysis Thresholds: Here you can enter the score that will determine the color which is related to the risk level of the service group. This makes it easy to analyze the risk of each Service group at a glance. The color is based on minimum score threshold entered. For e.g if you enter 45 Medium risk then all the Service Groups with a score of 45 and above will display a yellow color on the risk card, and if you enter 85 as Low risk then 85 and above will display a green color. So the score from 1 to 45 will be medium risk, 45 to 85 will be low risk and 85 to 100 will be no risk.Note: Enter numbers from 1 - 99 in Low risk and Medium risk boxes. High Risk and No Risk(Max Score) score are hard coded.

2313.Color Indicator.png-481x257.png

Click on the Save button.

To see the results of the Cloud Migration: Risk Analysis Thresholds settings click on My Services > Cloud Migration > Risk Analysis. In the example below you can see that * 0 to 34 is Red

  • 35 is yellow
  • 36 to 100 is Green

2477.Cloud Migration Risk Analysis.png-804x284.png

Agent

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.
  1. 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

Agent Installation

From time to time, FireScope will release new agents to be used with your DDM deployment.  If you do not see the agent for your operating system listed on in your Agent Management page, either create a help desk ticket or contact support@firescope.com.  FireScope officially supports agents on manufacturer supported versions of most enterprise level operating systems patched to the currently supported service pack/patch level.

Ports 8042 and 8043 are utilized by the Agent and Edge device for communication. Also port 8044 is used by the Agent Manager. Make sure that any local port filtering does not block traffic on these ports.* Agent listens on port 8042 for messages from the Edge device.

  • Edge device listens on port 8043 for messages from the Agent.
  • Agent Manager listens on port 8044 for messages from the Edge device.

Pastedimage1489416071143v1.png-695x178.png


Notes: * To install any agent, you need root-level access to the system you will install on.

  • For all Unix systems except Redhat 5 use the Dynamic Installer.
    • What is a Dynamic Installer and why is it used? With Dynamic Installer the agent binary is dynamically linked. Since the dependent libraries are not bundled inside the agent binary, Agent uses the libraries from the operating system. This is because REdhat 6 and above were not compatible with how this Operating System wanted to be.
  • For all other Unix platforms including RedHat 5, use the Static Installer.
    • What is a Static Installer and why is it used?
      With Static Installer the agent binary is statically linked. The dependent libraries are bundled(linked/packaged) inside the agent binary itself.

  The latest installation packages for Agents are available below.

 

OS Package Link
Linux Static Installer Download
  Dynamic Installer Download
Windows Installer for 64bit Download
  Installer for 32bit Download
Solaris Installer for Sparc Download
  Installer for x86 Download
HP UX Installer Download
AIX Installer Download

Platform-Specific Agent Installation Guides

FireScope Agent for Unix(Linux, AIX, Solaris)FireScope Agent for Windows

System Resources:

Depending on the load on an agent; the system resources used by an agent varies.* On a typical Windows as well as Unix system, the agent uses under 10MB and the agent manager uses about 1MB of memory.

  • The local storage used by the agent is shown as below:

2642.Screenshot 1.png-568x436.png

Screenshot 2.png-454x190.png-577x242.png

Unix(Linux, AIX, Solaris)

Selecting the Installer

All Linux and UNIX platforms must use the Dynamic Agent Installers except for RedHat-5 (32/64bit) and below which will use the Static Agent Installers.

Instructions to Install

By default, the Linux and Unix Agents will be installed under /opt/firescope.

sh FireScopeAgent_Installer_Solaris-4.0.57_42376.sh -A <firescope-edge-device-ip>

If you want to install the Agent in a different directory add -b option, followed by the directory you want it to be install in. For Example:

sh FireScopeAgent_Installer_Solaris-4.0.57_42376.sh -A <firescope-edge-device-ip> -b /export/home/fsbuild/instalationstuff/

The installation shell script can be modified to suit your OS needs.

For the purposes of this document, you can replace opt with the target directory of your choice. However, everything under the firescope/ directory must remain as documented.

To install the Agent:# Extract the tar file. e.g. tar xvf FireScopeAgent_DynamicInstaller_Linux-4.0.61_42952.tar

  1. Invoke the installation script.Example:e.g. sh FireScopeAgent_DynamicInstaller_Linux-4.0.61_42952.sh -A <firescope-edge-device-ip>This will place the Agent and all necessary files in /opt/firescope and place the appropriate init scripts where necessary. The installation will also create the firescop user account. Once the installation has completed, you can tail the log file (tail -f /opt/firescope/agent/log/firescope_agentd.log) to verify that it's running.
  2. After the agent is installed, it takes a few minutes for the Stratis to start the collection of data.

Starting and Stopping the services

Use the following commands as needed:

  • Linux
    • service firescope_agent_managerd start or service firescope_agent_managerd stopThis will automatically start/stop the firescope_agentd service as well. If there is a need to start/stop the firescope_agentd service separately, use following commands.service firescope_agentd startservice firescope_agentd stop
  • Solaris
    • svcadm enable firescope_agent_managerd or svcadm disable firescope_agent_managerdThis will automatically start the firescope_agentd service as well. If there is a need to start/stop the firescope_agentd service separately, use following commands.svcadm enable firescope_agentdsvcadm disable firescope_agentd
  • AIX
    • /etc/init.d/firescope_agent_managerd start or /etc/init.d/firescope_agent_managerd stopThis will automatically start the firescope_agentd service as well. If there is a need to start/stop the firescope_agentd service separately, use following commands.
    • /etc/init.d/firescope_agentd start
    • /etc/init.d/firescope_agentd stop

Uninstalling the FireScope Agent

  • To uninstall the FireScope Agent, use following script.sh /opt/firescope/FireScope_Agent_Uninstall.shThis will shut down all FireScope processes, remove the associated files, and delete the firescop account.

FireScope Agent Important Files

Configuration file/opt/firescope/agent/conf/firescope_agentd_posix.xml

Log file/opt/firescope/agent/logs/firescope_agentd.log

PID file/opt/firescope/agent/logs/firescope_agentd.pid

Store and forward cache directory/opt/firescope/agent/cache

Windows

The following information provides instructions for installing the FireScope SSDDM Agent on any 32- or 64-bit version of Windows 2000 Server or Windows 2003 Server.

 Desktop operating systems are not supported.

Notes:* Ports 8042 and 8043 are utilized by the FireScope Agent and Server for communication. Make sure that any local port filtering does not block traffic on ports 8042 and 8043 to ensure maximum effectiveness from your FireScope SSDDM solution.

  • To install any agent, you need administrative access to the system you will install on.


To install the Agent for Windows:# Follow the instructions for Installing an Agent for Firescope SDDM.

  1. Double-click the FireScope Agent for Windows executable.
  2. Click Next. The FireScope End User License Agreement (EULA) is displayed. Read the EULA carefully.
  3. Click I Agree to continue the installation.
  4. Accept the default selection to install the FireScope Agent component.
  5. Click Next.
  6. Enter the name of the FireScope server that will manage this server. You can enter the IP address or the Fully Qualified Domain Name (FQDN). The Hostname should contain the host name of this server and does not need the FQDN.
  7. Click Enable Remote Commands if you want to allow FireScope to perform automated tasks on this server (e.g., restart services on failure or execute scripts based on specific events that you specify within FireScope).
  8. Click Next.
  9. Select the destination folder where you want to install the FireScope Agent.The default destination folder is C:\Program Files\FireScope Agent.
  10. Click Next. The FireScope Windows Agent creates a service called FireScope Agent, which automatically starts after installation and on system boot, using Local System for login credentials. You can modify these settings in the Services administrative tool.
  11. Click Close.
  12. Add this host on the FireScope SDDM appliance you specified during this installation.

Silent Installation

In 2008 r2, DEP and UAC are major limiting factors, so run a cmd window as administrator, then use the following command:* Least required for install:msiexec /i FireScope_Agent_Windows_Server-xxbit_x.x.x.xx-xxxx.msi /qn SERVER=xxx.xxx.xxx.xxx
Note: SERVER is the actual IP address of the Edge device

Property Description Value
SERVER FireScope Appliance  
LISTENIP Agent Listen IP  
CINAME Configuration Item Name  
JAVAHOME Path to Java.exe  
PORT FireScope Agent Port 8042
SPORT Agent Server Port 8043
MPORT Agent Manager Port 8044
RMTCMD Remote Commands TRUE
REALTIME Store and Forward TRUE
STORETIME Cached Time 300
STORECOUNT Cached Count 100
JPORT JMX Port 8046
ENABLEJMX JMXDelegate TRUE
WPORT WMI Port 8047
ENABLEWMI WMIDelegate TRUE

Silent Uninstall

In 2008 r2, DEP and UAC are major limiting factors, so run a cmd window as administrator, then use the following command:* Least required for uninstall:msiexec /x FireScope_Agent_Windows_Server-xxbit_x.x.x.xx-xxxx.msi /qn

For more information on msiexec, refer to this link

https://technet.microsoft.com/en-us/library/bb490936.aspx

Agent Configuration

Note: To Configure any agent, you need root-level access to the system you will be performing the installation on.# Log in to FireScope DDM as a FireScope Administrator.

  1. Click Administration > Utilities > Agent Management. The Agent Management page will be displayed.

4061.Image 1.png-802x420.png

  1. In the Agent IP / DNS column, click the Agent you want to configure. There is a pause while FireScope DDM establishes a remote connection to the Agent and the Agent Attributes are updated. A summary of the Agent's configuration will be displayed on the Agent Management window.

1780.Image2.png-766x480.png

Configuring or Updating Multiple Agents

To simplify configuration of multiple Agents, or to ensure that multiple Agents have a consistent configuration, FireScope DDM includes a bulk editor for agents.

To configure multiple agents:# On the Agents Management page, check the box next to each Agent you want to configure.

  1. Click Edit properties for selected button. There is a pause while FireScope DDM establishes a remote connection to the Agent and the Agent Attributes are updated. Note: The Agents Management page is divided vertically and displays the properties for the selected Agents.
  2. Use the Properties to save section to specify a global value to apply to all selected Agents.
  3. The Agents to update side displays the current configuration for each selected Agent, displayed three at a time with paging controls at the top.Note: You can update the Agents individually in this section.

1588.Iamge3.png-806x1517.png-597x1123.png

  1. Perform one or more of the following tasks:
    • To edit a property for one Agent, in the Agents to update section, edit the appropriate field in the column for that Agent.
    • To remove a property from all Agents, in the Save column, clear the box next to the property you want to remove.
    • To add a custom property to all Agents, click Add custom property (at the bottom).
    • To edit a property for all Agents, in the Properties to save section, edit the appropriate field in the Value column.
  2. In Change Properties Reason, type the explanation for your changes.
  3. Click on the Save Properties button. The configuration updates are pushed to all of the selected Agents.

Agent Upgrade

To update an Agent with the latest upgrade:# Download latest upgrade file by clicking on the appropriate Download Link from the table 

Latest Upgrade File below.

  1. After you download the file you have to upload the Agent file into CMI account. This will make the file available to Accounts in Firescope Stratis for upgrade.
    To upload an Agent upgrade file for Firescope DDM Account:
    1. Log in to FireScope CMI account.
    2. Click on Administration > Device Management > Agent Upgrades. The Agent Upgrades page will be displayed.

Pastedimage1490298430346v1.png-692x253.png

    1. Click on the Upload button( upper right corner). The Agent Upgrade page will be displayed.

Pastedimage1490298460905v2.png-729x201.png

    1. Click on Browse in Upload an Agent Upgrade file.
    2. Select the upgrade file you want to upload.
    3. Click on the Save button.
    4. Log out of CMI account.

To Upload Agent Upgrate# Log in to the desired FireScope DDM Account with Administration privileges.

  1. Click Administration > Utilities > Agent Upgrades. The Agent Upgrades page will be displayed.

Upgrade Page.png-767x178.png

  1. Click on the Manage Agents on Edge Devices button(Upper right hand corner). Upload Agent Upgrade page will be displayed.

Upload Agent Upgrade.png-760x444.png

  1. Select the Edge Device from the drop down list.
  2. Select Agent files from the Available list, click on Add button. File is added to the Active list box.
  3. Click on the Save button.

To update an Agent for a single CI/server or multiple CIs/servers:

  1. Click Administration > Utilities > Agent Management. The Agents Administration page will be displayed.  

File:Agent Management Page.png-792x292

  1. In the Remote Agents section in Agent IP / DNS column, click on the check box next to the Agent you want to update. For multiple updates select as many Agent as you want to upgrade.
  2. Under Available Versions select the version from the drop down list.
  3. Click on the Deploy updates for selected button, Deploy Schedule page is displayed.    

Deploy Schedule Page.png-790x289.png

  1. Under Deploy section, complete the following fields
    1. Deploy Reason: Briefly explain the reason for the update.
    2. Schedule Deployment: Select to deploy now or choose a future date/time.
  2. Click Deploy update.
  3. The ACTIVE JOB QUEUE section on the Agents Management page shows the status of any pending updates.

Deploy Schedule.png-762x100.png

Latest Upgrade File

OS Package Version Link
Linux (RedHat_and_CentOS_64) Static Upgrade 4.0.51_41539 Download
Linux (RedHat_and_CentOS_32) Static Upgrade 4.0.51_41539 Download
Linux (SUSE_64) Static Upgrade 4.0.51_41539 Download
Linux (SUSE_32) Static Upgrade 4.0.51_41539 Download
Linux (RedHat_and_CentOS_64) Dynamic Upgrade 4.0.51_41539 Download
Linux (RedHat_and_CentOS_32) Dynamic Upgrade 4.0.51_41539 Download
Linux (SUSE_64) Dynamic Upgrade 4.0.51_41539 Download
Linux (SUSE_32) Dynamic Upgrade 4.0.51_41539 Download
Windows 64 Upgrade 4.0.49_41179 Download
Windows 32 Upgrade 4.0.49_41179 Download
AIX Upgrade 4.0.50_41188 Download
Solaris 10 Sparc Upgrade 4.0.40_39977 Download
Solaris 9 Sparc Upgrade 4.0.40_39977 Download

Agent Management

The Agent Management page centralizes updates and configuration of data collection in FireScope Agents, which simplifies the management of large deployments. From this page, you can:

  • Configure one or more Agents at once
  • Update one or more Agents immediately or at a future day/time

See [3] for a list of supported Agents.

To access the Agent Management page:# Log in to Firescope SDDM as Administrator.

  1. Click Administration > Utilities > Agent Management. The Agent Management page will be displayed.   

Pastedimage1487888328776v1.png-750x315.png

Section Descriptions

The default Agent Management page is divided into three sections that provide an overview of the current status of active Agents.

Section Description
Active Job Queue Pending actions to be performed on Agents or Agent Groups.
Remote Agents Agents that are currently capable of remote administration.
Legacy Agents Agents that are communicating but not a revision capable of remote administration from the FireScope Stratis DDM platform.

Additional options that are available via the drop-down in the top right corner are:


Option Description
Overview Default view of the Agent Management page, see the previous section descriptions.
Job Queue Displays pending jobs and job that completed in the last twenty-four hours for Agents or Agent Groups.
Agents Displays only the remote Agents and legacy Agents.
Agent Groups Allows creating Agent Groups to facilitate Agent management functions.

Create Agent Group

You can organize Agents logically into groups to simplify management. These groups can be used to ensure a consistent configuration and versions across Agents. A common example is to create a group for each platform, such as all Windows Agents.

  1. Log in to FireScope SDDM with Administration privileges.
  2. Click Administration > Utilities > Agent Management. The Agent Management page will be displayed.

Image 0.png-919x412.png

  1. Select Agent Groups from the drop-down in the top right corner. The Agent Management page displays existing Agent Groups.

Agent Group.png-924x205.png

  1. Click Create Agent Group. The Agent Management page displays Agent Group fields.

Agent Grou Create.png-928x429.png

  1. Complete the form.
  2. Click on the Save button.

Agent Resource Usage

On one of the Windows systems following resource usage was noticed:

CPU Usage

File:2474.agent cpu.jpg-806x225.png

Memory Usage

File:8168.agent memory.jpg-802x238.png

Network Usage

File:0247.agent network.jpg-805x181.png