RIAT Probe v8.4 Deployment Guide - 20150608
RIAT Probe v8.4 Deployment Guide - 20150608
RIAT Probe v8.4 Deployment Guide - 20150608
RIAT version
: 8.4
Document updated : 08-Jun-2015
Table of Contents
Introduction............................................................................................................................................ 5
1.1
1.1.1
RIAT Probe............................................................................................................................. 5
1.1.2
1.2
Prerequisites........................................................................................................................................... 7
3.1.1
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.5
3.2.6
3.2.7
3.2.8
3.2.9
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
3.3.6
3.3.7
3.3.8
3.3.9
3.3.10
3.3.11
3.3.12
3.3.13
3.3.14
3.3.15
3.3.16
3.3.17
3.3.18
3.3.19
3.3.20
3.4
4
4.2
Pre-requisites .............................................................................................................................. 42
4.3
4.4
4.5
4.6
5.1
5.1.1
5.1.2
5.2
5.2.1
5.2.2
5.3
5.4
5.5
5.6
5.7
5.8
Adding Command Device in VMware Player (Only for USP V storage system) .......................... 58
5.9
5.10
5.11
5.11.1
Adding VMAX probe for already added EMC Unisphere for VMAX.................................... 62
5.11.2
5.12
5.13
5.14
1 Introduction
RIAT is a Virtual Infrastructure Optimization (VIO) solution. It provides an assessment to
measure, analyze, report, and solve optimization issues in data centers that have virtual
infrastructures, storage systems, physical/virtual hosts running the Linux, Unix, and Windows
operating systems, as well as network devices (switches). As virtual environments and the data
associated with them continue to grow, this assessment allows organizations to understand
what configuration changes are needed to enable the environment to run efficiently.
NOTE: From now onwards, MARS Windows Probe software is referred as Windows Probe in the
document.
The performance metrics include CPU utilization, swap rates, memory usage, response times,
kernel and device read/write latency, packets received/transmitted/dropped, IOPS, throughput,
storage capacity and utilization, read/write ratio, vMotion activity, KB /IO, etc.
RIAT Probe collects the performance data on a periodic, granular basis. This allows RIAT Server
to analyze the data received over a period and identify trends, bottlenecks, etc. The data can be
collected as frequently as 1 minute (even more frequently in some cases).
The configuration metrics include the storage vendor, model, type and method of
connectivity, availability method, number of CPUs, storage capacity, etc.
2 Prerequisites
RIAT Probe has the following prerequisites:
vCPUs: 4
Storage devices
o
SVP: By connecting to VSP/HUS VM, USP V, and VSP G1000 storage systems
separately.
SMI-S: Other storage systems, such as Hitachi, EMC, etc. that comply with
the open Storage Management Initiative Specification (SMI-S) standard
Fusion IO: Collects data from machine where Fusion IO storage SSD are
attached.
VMware
XenServer
Database:
o
RIAT Probes for Storage devices, Virtual infrastructure, Network switches and NetFlow/sFlow
enabled network devices, Database, and Data centers with physical/virtual hosts running the
Linux and Unix OS are bundled as a virtual appliance called RIAT Probe Appliance that can
itself run as a virtual machine in a virtual environment.
RIAT Probes for data centers with Windows OS in Physical/Virtual/Hyper-V environment is
deployed differently. Refer to Windows Probe for Windows and Hyper-V machines section.
Inventory location: RIAT Probe will be added under the selected inventory in the
vSphere application.
6. Click Next. In the Host/Cluster section, select the appropriate cluster from the list of available
clusters inside the inventory.
7. Click Next. The system displays the list of resource pools that are available in the cluster. You
can deploy RIAT Probe in the resource pool or in the cluster.
8. Click Next. Select the datastore for RIAT Probe. The system will save all the reports and log data
in the selected datastore.
9. Click Next and define the required disk format:
Thick Provision Lazy Zeroed: Space required for the virtual disk is allocated at
creation time. Each disk block is zeroed out only after it is first accessed by the VM.
Thick Provision Eager Zeroed: Space required for the virtual disk is allocated at
creation time. Each disk block is zeroed out immediately after disk creation.
Thin Provision: The system initially allocates 2.8 GB and it keeps allocating more
space until 104 GB.
10. Click Next. The options you selected are displayed. Verify the details.
11. Select the Power on after deloyment check box.
12. Click Finish to complete the deployment.
13. Proceed to the Configuring RIAT Probe Appliance section.
You can also assign the static IP address to RIAT Probe. For more information, see Assigning a
static IP address to RIAT Probe.
Note: Only one user can be created for a RIAT Probe appliance.
2. Click Submit to create the login account.
11
SVP
HDvM
AMS
HNAS
UCP
SMI-S
Eternus
NetApp
IBM XIV
VMAX
Hitachi Replication
Fusion IO
VMware
XenServer
Network
xFlow
SQLServer
SAP HANA
Linux
Unix
For collecting data from Windows and Hyper-V targets, see Windows Probe for Windows and
Hyper-V machines.
12
RAIDCOM: RAIDCOM is used to collect the configuration and performance data. Hitachi
provides the RAIDCOM in a CD named "Hitachi HUS VM/VSP/USP
RIAT Probe Deployment Guide
Export Tool: Export tool is used to collect the performance data. For each storage system,
Hitachi provides the Export Tool in a CD named <Storage System Name>Document and
Programs DVD<Microcode Version> under path Tools_Pack/ExportTool/UNIX/export.tar or
under path Tools_Pack/ExportTool/HP-UX/export.tar.
Microcode Version in the CD name should be similar with Microcode Version of target
storage system. To find the target storage systems microcode version, see Identifying
Microcode Version.
Performance monitoring has to be enabled on target Control Units (CU) to collect
performance data from LDEV, PG, LU, etc. To enable CUs, refer the documentation of target
Hitachi storage system.
A user with Read-Only permission must be available on SVP to collect data from storage
system.
Note: Data cannot be collected with the user Maintenance.
Follow the steps to add an SVP Probe.
Note: Follow step A only if you are adding SVP probe for USP V storage system.
A. Adding command device (Only for USP V storage system)
B. Uploading RAIDCOM
C. Adding SVP probe in RIAT Probe appliance
13
1. Using vSphere Client, select the virtual machine on which RIAT probe appliance is deployed and
click Shut down the virtual machine.
2. Click Edit virtual machine settings.
3. On the Virtual Machine properties window, click Add.
4. On the Add Hardware window, click Hard Disk and then click Next.
5. In the Select a Disk section, select the Raw Device Mappings button and then click Next.
14
6. In the Select Target LUN section, select the target LUN of USP V storage system for which
command device should be added and then click Next.
Note: If the target LUN is unavailable for the desired USP V storage system, map the target LUN
to the ESX host on which RIAT Probe appliance is deployed. The mapped LUN has to be enabled
as command device and the following device attributes needs to be configured.
10. Review the summary to ensure that the correct options have been chosen and then click Finish.
11. The system adds a new hard disk.
12. Click OK.
13. Power-on the virtual machine.
14. To ensure that command device is added for the USP V storage system, follow the steps as given
below:
a. Log into RIAT Probe VM through SSH client (like putty) using the below credentials:
NOTE: The 'root' user login is disabled on VMware VCenter VM Console.
Username: root
Password: app.jeos
b. Execute the /usr/local/megha/lib/svp/list_devices command to check if
the command device is present for the desired USP V storage device.
c. You can view the details as displayed in the following screen capture. The command device
(OPEN-V-CM) has been added with storage device (serial number 53086).
15
B. Uploading RAIDCOM
To add SVP probe for the first time, RAIDCOM needs to be uploaded. RAIDCOM is provided in a
CD along with storage systems. On CD, RAIDCOM file is located at Linux/X64/RMHORC.
1. In RIAT Probe appliance, click Manage.
2. On the Manage window, click the Upload RAIDCOM link.
3. On the Upload RAIDCOM window, click Choose File button in the Upload new version field.
Note: Upload the latest version of RAIDCOM available with you.
4. Select the RAIDCOM file (.RMHORC file) and click Submit. Once RAIDCOM is uploaded, it need
not be uploaded again. Later on, it can be upgraded if required.
C. Adding SVP probe in RIAT Probe appliance
1. In RIAT Probe appliance, click Home and then click Add Probe button.
2. On the Add Probe window, select SVP from the Probes list.
3. Provide the following details:
SVP IP address: IP address of the SVP that is used to collect data from storage systems.
4. Click Next.
5. After successful validation, click Next and then click OK.
6. Start the probe on the Status page.
AMS Storage Name: Name of the AMS storage system. The name denotes the storage
system for which this probe will be added. This need not be the same as storage name
defined in your environment.
Note: After you add the probe, it will be identified with this name in RIAT Probe
appliance.
Username and Password: User credential of a user who has read only permissions.
Note: If the user authentication for AMS storage is Off, you need to enter a dummy
Username and Password since these two fields are mandatory for adding AMS probe.
HNAS SMU IP: Enter the IP adderess of the HNAS System Management Unit (SMU).
SMU Username and Password: Enter the user credentials of the SMU.
4. Click Next. The system displays the list of available HNAS Servers.
5. Choose the HNAS server from which you want to collect data.
6. Click Next. The system validates the entered details.
7. Click Next after successful validation.
8. Click Ok and start the probe on the Status page to start collecting data.
Chassis details
Port Number: Port number of SNMP to which UCP probe should listen to. By default,
UCP probe listens on port - 161
Chassis Model: Select the chassis model that you want to monitor. CB500 and CB 2000
chassis models are supported.
SNMP Version: Select one of the SNMP versions. v1 and v2c versions are supported.
URL: URL of the SMI-S Server. Ensure to enter the correct namespace along with the IP
address. Hence, the format of URL will be: http://<IP address of SMIS
Server>/<Namespace>
Note: If HTTPS protocol is used, you need to enter the port 5989 at the end of the IP
address. For example, https://<IP address of SMIS Server>:5989/<Namespace>
The following table describes model names and associated namespaces.
Manufacturer
Model
Namespace/s
EMC
Dell
Compellent
root/PG_Internal
interop
root/cimv2
root
root/compellent
IBM
DS6000/8000, SVC
interop
root/ibm
HP
EVA, 3PAR
root/reflection
Interop
root/eva
root/PG_InterOp
19
Username: Any user which has access to the SMIS-Provider. Read-only privileges are
also sufficient.
Password: app.jeos
b) Install the Performance Monitor Control Command (PMCC) software. For example:
rpm -ivh FJSVstxp-2.1.0-0.i386.rpm
c) Type the following commands to change the owner and group of the /opt/FJSVstxp
folder and its content to megha.
chown -R megha /opt/FJSVstxp
chgrp -R megha /opt/FJSVstxp
d) Type the following commands to change the user and group of the
/var/opt/FJSVstxp folder and its content to megha.
chown -R megha /var/opt/FJSVstxp
chgrp -R megha /var/opt/FJSVstxp
e) If SSH is disabled on the Eternus storage for which you are going to add probe, do the
following:
a. Install the Maintenance and Inquiry Control Command (MICC) software. For
example:
rpm -ivh FJSVstxs-2.5.0-1.i386.rpm
b. Type the following commands to change the owner and group of the
/opt/FJSVstxs folder and its content to megha.
chown -R megha /opt/FJSVstxs
20
Conf User-Id and Password: If SSH is enabled on the Eternus Storage for which you are
going to add probe, you should enter the user credentials for the SSH. If SSH is disabled,
you need to enter the user credentials for MICC utility.
Perf User-Id and Password: User credentials for the PMCC software which is used to
retrieve the Eternus performance data.
SSL must be enabled on the target NetApp storage system. NetApp probe uses Port 443
(Https connection) for connecting to NetApp Storage.
Ensure that you have a user (read-only privileges) available on NetApp storage system with
appropriate role to collect configuration and performance data. RIAT Probe supports 7-
21
mode and C-mode types of NetApp storage system. The procedure of creating user differs
as per the target storage system type.
To create user for 7-mode, see Creating user for NetApp 7-mode and to create user for Cmode, see Creating user for NetApp C-mode.
Username and Password: Enter the username and password that you have created.
After downloading it, you need to keep it in RIAT Probe appliance in /opt directory:
I.
Log into RIAT Probe VM through SSH client (like putty) using the below
credentials:
NOTE: The 'root' user login is disabled on VMware VCenter VM Console.
User: root
Password: app.jeos
Port: 22
II.
III.
Copy the XIV CLI package in /opt directory (package name should be something
like this: xivcli-3.0.1-build3-linux32.tar )
IV.
Extract the package at /opt location using command: tar xvf <package
name>
Storage System IP Address: IP address of the target IBM XIV storage system
Username: Username of the storage system. Ensure that user has minimum read only
permissions to collect configuration and performance data.
3. Click Next. RIAT Probe appliance will validate the entered details.
4. After successfully validating the details, click Next and then click OK.
5. Start the probe on the Status page to start collecting data.
Pre-requisites:
Configuration in Target environment
EMC Unisphere for VMAX: A machine with EMC Unisphere for VMAX (v1.6.2.4 or
above) installed, monitoring target storage systems.
EMC Solutions Enabler Symmetrix CLI: A machine (could be the same as above for EMC
Unisphere for VMAX or different) with EMC Solutions Enabler Symmetrix CLI (v7.6.2.26
or above) installed, monitoring all the target storage systems for which probe needs to
be added.
23
-install -all
RIAT Probe Deployment Guide
Configure environment variable entry in netcnfg file: To collect data from target
storage systems using EMC Solutions Enabler Symmetrix CLI , edit netcnfg file.
1. Log into RIAT Probe VM through SSH client (like putty) using the credentials:
(Username: root Password: app.jeos)
NOTE: The 'root' user login is disabled on VMware VCenter VM Console.
2. Edit netcnfg file: vi /var/symapi/config/netcnfg
3. At the end of the file, add entry as follow:
SYMAPI_SERVER - TCPIP <*IP Address> <*IP Address> <Port> NONSECURE
<*IP Address> = IP address of the machine where EMC Solutions Enabler
Symmetrix CLI is installed.
Default port number: 2707
Example:
SYMAPI_SERVER - TCPIP 172.17.40.19 172.17.40.19 2707 NONSECURE
4. Save the file.
For each VMAX storage a separate probe will be added. If you do not want to add probe for all
the listed storage systems, you can add those later on. To add probe for remaining storage
systems later on, see Managing VMAX probe.
7. Click Finish and then click OK. Proceed to start added probe(s).
24
AMS
HUS
USP VM
USP V
VSP
HUS VM
VSP G1000
UR
No
No
Partial
Partial
Yes
Partial
Yes
TC
No
No
Partial
Partial
Yes
Partial
Yes
SI
Partial
Partial
Partial
Partial
Yes
Partial
Yes
Pre-requisites
RAIDCOM: RAIDCOM is used to collect the configuration and performance data. Hitachi
provides the RAIDCOM in a CD named "Hitachi HUS VM/VSP/USP
V/VM/USP/NSC/9900V/9900 Command Control Interface Software Distribution Library"
under <Storage System Name >/<Microcode Version of target storage system
>/program/RM/LINUX/x64/RMHORC.
To find the target storage systems microcode version, see Identifying Microcode Version.
For older Microcode versions, where 64-bit RMHORC file is not available, such as R500-PP50-09-98_14 and R600-PP-60-08-24, then 32-bit RMHORC file is required. It is located
under: <Storage System Name>/<Microcode Version>/program/RM/LINUX
A user with Read-Only permission must be available on Hitachi Replication to collect data
from storage system.
Follow the steps to add a Hitachi Replication Probe.
Note: Follow step A only if you are adding Hitachi Replication probe for USP V storage
system.
A. Adding command device (Only for USP V storage system)
B. Uploading RAIDCOM
C. Adding Hitachi Replication probe in RIAT Probe appliance
Pre-requisites:
Before you add command device, ensure that target LUN is available for the desired USP V
storage system to the ESX host on which RIAT Probe appliance is deployed. The LUN has to be
enabled as command device and the following device attributes needs to be configured.
1. Using vSphere Client, select the virtual machine on which RIAT probe appliance is deployed and
click Shut down the virtual machine.
2. Click Edit virtual machine settings.
3. On the Virtual Machine properties window, click Add.
4. On the Add Hardware window, click Hard Disk and then click Next.
26
5. In the Select a Disk section, select the Raw Device Mappings button and then click Next.
6. In the Select Target LUN section, select the target LUN of USP V storage system for which
command device should be added and then click Next.
Note: If the target LUN is unavailable for the desired USP V storage system, map the target LUN
to the ESX host on which RIAT Probe appliance is deployed. The mapped LUN has to be enabled
as command device and the following device attributes needs to be configured.
10. Review the summary to ensure that the correct options have been chosen and then click Finish.
27
B. Uploading RAIDCOM
To add HITACHI Replication probe for the first time, RAIDCOM needs to be uploaded. RAIDCOM
is provided in a CD along with storage systems. On CD, RAIDCOM file is located at
Linux/X64/RMHORC.
1. In RIAT Probe appliance, click Manage.
2. On the Manage window, click the Upload RAIDCOM link.
3. On the Upload RAIDCOM window, click Choose File button in the Upload new version field.
Note: Upload the latest version of RAIDCOM available with you.
4. Select the RAIDCOM file (.RMHORC file) and click Submit. Once RAIDCOM is uploaded, it need
not be uploaded again. Later on, it can be upgraded if required.
C. Adding Hitachi Replication probe in RIAT Probe appliance
1. In RIAT Probe appliance, click Home and then click Add Probe button.
2. On the Add Probe window, select Hitachi Replication from the Probes list.
3. Provide the following details:
28
Username and Password: Username and password for RAIDCOM to log into the target
storage
4. Click Next. The system validates the entered details and displays the list of Replication Groups.
5. Select one or more replication groups.
6. Click Next. The system validates the configuration file and Replication Groups. It also calculates
time required to collect one dataset.
7. After successful validation, default probe name and collection interval is displayed. You can
change as required.
8. Click Next.
9. Start the probe on the Status page to start collecting data.
FusionIO Probe Name: Enter any name for Fusion IO probe. It will be used to identify in
RIAT Probe appliance.
Username & Password: Username and password of the hosts that you want to probe.
The name of the hosts will be entered in Hostlists field.
Hostlist: Enter IP address of host where Fusion IO storage SSD is attached. If you are
entering multiple IP addresses, those should be separated by comma and all hosts
should share same username and password.
Username: Any user having access to vCenter. Read-only privileges are also sufficient.
If you want to specify multiple XenServer masters, ensure that these masters are
part of same group. You will need to define that group user name and its password
in Group User Name & Group Password fields.
Group User Name & Password: Login username and password of the XenServer group.
Note: The login credentials of the user with read-only privileges is sufficient to collect
configuration and performance data for the XenServer environment.
More details about the permissions available for the read-only role, refer to:
http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/reference.html#RBAC-roles-def
Connection Protocol: Connection protocol (HTTP or HTTPS) that will be used to collect
data from XenServer hosts.
30
communication in the trusted list and the trusted list has been assigned the default
keystore password.
4. Click Next. The system validates the entered details.
5. Click Next after successful validation.
6. Click Ok and start the probe on the Status page to start collecting data.
3. Enter the network switch details - IP Address, data Collection Interval, and Port using one of the
following methods:
31
By entering IP address of each network switch and data collection interval, as well as
port number for each switch.
By Importing a CSV file in which IP address of network switches, data collection interval,
and port details. You need to create this CSV file manually before importing it, which
RIAT Probe Deployment Guide
contains one or more than one IP addresses. The format of each entry must be: <IP
Address>:<Port>, <data collection interval>
See CSV File Format to understand the CSV file format.
Note: If port and data collection interval are not mentioned, the default values are
considered. Default values are - Port 161, Data Collection Interval 5 Minutes.
4. Click Add/Import CSV based on your requirements. The details of the added devices will be
dislayed in a tabel on same window.
5. Click Next. The Security Settings section appears.
B. Define Security Settings
1. Select IP address of the device for which you want to define the security. After selecting the IP
address, the SNMP Security Version list is displayed. SNMP queries are run to collect
configuration information for each device. For SNMP V1 and V2c, you need to enter only read
community string name for authentication. For SNMP V3, authentication information is
required.
2. Select SNMP Security Version from the list and enter the authentication details as per the
requirements.
If you select v1 or v2c SNMP Security Version, the Read Community String field will be
displayed. See the following table for details.
If you select v3 option, the SNMP Security Level list is displayed where you must select
the security levels. Based on SNMP Security Level, the required authentication must be
provided. See the following table for details.
32
Required Authentication
Read Community String
Username
Security Name
Username
Security Name
Authentication
Authentication Password
Required Authentication
Username
Security Name
Authentication
o MD5
o SHA
Authentication Password
Encryption
o AES
o DES
Encryption Password
3. Click Apply Settings to All Devices if you want to apply authentication settings to all the devices
that are available in the Select IP Address list.
4. Click Save. The authentication details are saved.
5. After you finish defining authentication details for all the required devices, click Next.
The system attempts to connect to devices. If it is successfully connected to devices, the
interface of each device is displayed, else Connection request to this device timed out.
message is displayed. Check if the authentication details of each device are correct.
C. Choose Interfaces
1. Choose the interfaces to enable data collection.
2. Click Next. The selected interfaces are displayed with its speed and counter type (32 bit or 64
bit). 32-bit counter type is by default config to each interface. If the target interface supports 64bit data collection, you can change it to 64-bit counter.
D. Configure probe: Change Interface Speed or Counter Type
33
The speed is by default displayed based on the interface configuration. Change it, if required in
the IfSpeed (Kbps) column.
By default, counter type is 32 bit. If you want to perform 64 bit data collection and the target
interface also supports 64 bit data collection, click the checkbox in the 64 Bit column.
Note: For v1 security level, the checkbox for 64 bit counter selection is disabled.
E. Add Network probe
Click Finish to add the probe. The Status window is displayed.
F. Start Network probe
Start the probe on the Status page to start collecting data.
For NetFlow:
o
Ensure that NetFlow is enabled on network device and network device is configured
to send the flow records to RIAT Probe appliance.
The process of enabling NetFlow and configuring NetFlow network devices to send
the flow records to collector (RIAT Probe) varies on Network device model and
manufacturer. Usually, a network device has many interfaces and NetFlow
functionality is configured for each interface.
The following webpage contains the NetFlow configuration steps for a range of
devices from different device vendors
http://www.plixer.com/Scrutinizer-Netflow-Sflow/configuring-netflow-ipfixsflow.html
34
Ensure that active and inactive timer expiry intervals are set less than or equal to
aggregation interval of xFlow probe:
Before NetFlow flows are exported, they are cached on the network device. As and
when flows expire they are grouped together into "NetFlow Export" datagrams for
export from the NetFlow-enabled device.
There are timers associated with a flow to determine if it is inactive or it is long
lived. These timers are configurable and have certain default values assigned to
them depending on the device. For example, for CISCO devices:
The inactive timer exports a packet with a default setting of 15 seconds of traffic
inactivity and it can be configured to any value between 10 and 600 seconds.
The active timer exports a packet after a default setting of 30 minutes of traffic
activity and it can be configured to any value between 1 and 60 minutes.
RIAT xFlow probe collects these flows and aggregates traffic activity at every
aggregation interval. This aggregation interval can be configured when xFlow probe
is added or edited. Possible values for Aggregation interval are 1, 3, 5, 10 and 15.
Hence, NetFlow flow active and inactive timer expiry intervals should be less than or
equal to xFlow probe aggregation interval.
For sFlow: Ensure that sFlow is enabled on network devices.
The sFlow Toolkit provides an 'sflowenable' shell script that can be used to configure a
device for sFlow exports if the device supports the sFlow version 5 SNMP MIB.
The following web pages collate the sFlow configuration steps for a range of devices from
different device manufacturers:
http://www.inmon.com/products/sFlowTrend/help/html/appendix.switchsflow.html#appendix.switch-sflow.snmp
http://www.plixer.com/Scrutinizer-Netflow-Sflow/configuring-netflow-ipfix-sflow.html
Clocks of RIAT Probe appliance and xFlow exporting device should be in sync. xFlow probe
can accommodate maximum of 5 minutes time difference between the RIAT Probe
appliance and xFlow-exporting device.
Flow type: Type of the flow the network device exports (NetFlow or sFlow)
UDP Port: UDP port on which the probe listens for network flow exports from the network
device. It has to be unique for each xFlow probe.
Aggregation interval (Minutes): Time interval at which the traffic data is aggregated. The
default value is 5 minutes.
35
4. Click Next. The system validates the details and probe waits for about a minute to check if the
device is exporting xFlow datagrams. If the target system exports the datagrams, the Configure
Probe screen is displayed as described in step 6. If the probe does not receive any flow
datagrams from the network device in a minute, system displays the following message:
Unable to receive flow datagrams from the target network device in last one minute. You may
still continue to add this probe if you have correctly configured the target device.
You can do one of the following if the above message is displayed:
a. Check if network device is configured correctly.
b. Click Retry. The probe listens for another one minute on the given UDP port to check if the
device is exporting xFlow datagrams. You can retry this activity for multiple times till the
time probe receives the datagrams. If the probe receives datagrams, the system displays
Configure Probe window.
c. Ignore the message and click Next. The system will allow to add the probe. If network device
is configured correctly, the probe will receive datagrams after some time.
5. Review the device details and then click Finish. The Status window is displayed.
6. On the Status window, start the probe. When the probe starts, the data aggregation time is
always rounded up to the nearest multiple of aggregation interval. For example, if the xFlow
probe is started at 11:34:49, and aggregation interval is 1 minute, then the probe will start
aggregation at 11:35.
Ensure that SQL Server/Windows domain user with minimum View any database, View
any definition, and View server state permissions are available. If you want to create a
new user with these permissions, see Creating User in SQL Server.
36
Server Name: Host name or IP address or Host name\instance name of the SQL Server
Username: Enter username for the Windows or SQL Server authentication. In case of
Windows authentication, domain is supported (DOMIN\username).
Server Name/IP: Enter HANA database server IP address/host name. Hostname should
be a fully qualified domain name (FQDN).
Port Number: Port of the HANA database server. The default port is 30015 for JDBC
connection.
Username and Password: User name and password of the HANA database server.
37
All target machines should have PERL installed with packages - IO::Select, IO::Handle,
File::Path qw(mkpath), Getopt::Std, File::Path, Time::HiRes qw(gettimeofday) and
Getopt::Std.
Directory with same name should be created manually on all target machines to copy all
the data collection scripts.
If you are going to add probe for more than one target machines, a same user
name and password should be available on each target machine.
Probe Name: Probe name should be alpha numeric string with length Min. 4 and Max.
64 characters.
Username: A user on each target Linux machine with read , write and execute
permissions.
Installation Directory: Installation directory where all the data collection scripts will be
copied.
Sample Interval (Seconds): Defines at which interval data samples should be collected
from Linux machines. You can either define sample interval to one second or sixty
seconds.
Transfer Interval (Seconds): Defines at which interval data will be trasferred from Linux
machine to RIAT Probe appliance.
4. Click Next. The Add Host window appears. Enter host names of target Linux machines. Click Add
More button if you want to add some more host names.
5. Click Next. RIAT Probe appliance will validate the entered details. Validation status will be
displayed in the table. If validation of any target machine is failed, you can move ahead to add
probe or you can go back to previous window to correct the host name details.
6. Click Next. The scripts to collect data from target machines will be deployed on each target
machine you have added.
7. Click Next and then click OK.
8. Start the probe on the Status page to start collecting data.
38
AIX
Linux
Solaris
HP-UX
Pre-requisites:
Installation Directory:
o
Target host user should have root privileges or it should be the sudo user. To know
more about sudo users, click Add sudo user.
SELinux must be disabled if user wants to use Enable Public Key option while adding
probe. To disable SELinux, edit /etc/selinux/config file with this configuration:
SELINUX=disabled
Click Download Sample CSV File link to download a sample CSV file.
Create a CSV file to import target hosts using downloaded sample CSV file.
Username and Password: Credentials of the user having root privileges or a sudo
user on target machine.
Installation Directory: Enter the installation directory which you have created on
target machine.
Enable Public Key: Select this checkbox if you want to allow further communication
without using password. With this, probe will continue data collection even if target
machine password is changed in future.
Note: If you want to add more target machines, click Add More button.
4. Click Next. Entered details are validated. After successful validation, click Next.
Note: If you have entered multiple target machines and validation of only few target machines
succeeded, you can still move ahead to add probe or you can go back to previous window to
correct the failed target system details.
5. Click Next. Scripts to collect data will be copied in Installation Directory.
6. Click Next and then click OK.
7. Start the probe on the Status page to start collecting data.
40
Description
41
4.2 Pre-requisites
For Method 1
Targets
SCOM
Pre-requisites
Target Windows machines should be configured in SCOM
For discovering SCOM, user should have Advanced Operator or Administrator
role in SCOM and it should have remote logon permissions to SCOM Server.
Remote registry service must be running on all the machines configured in SCOM.
For importing Cumulus management pack in SCOM (which configures
performance rules), access to SCOM console is required.
42
Targets
SCCM
Pre-requisites
Target Windows machines should be configured in SCCM
Hardware Inventory Client Agent (of SCCM) must be running on target machines.
This agent collects required configuration data and dumps into the SCCM
database.
For discovering SCCM, it is required to connect database, which is configured for
SCCM. The discovery user should be part of db_datareader group in SQL Server.
43
For Method 2:
Targets
SCOM
Pre-requisites
Target Windows machines should be configured in SCOM
For discovering SCOM, user should have Advanced Operator or Administrator
role in SCOM and it should have remote logon permissions to SCOM Server.
Remote registry service must be running on all the machines configured in SCOM.
For importing Cumulus management pack in SCOM (which configures
performance rules), access to SCOM console is required.
WMI
User should be a domain administrator and ensure that the user has permissions
to access ROOT and ROOT/CIMV2 WMI namespaces on each target machine.
Permissions required for these namespaces are: Execute Methods and Remote
Enable
Firewall exceptions must be added for WMI on all the target machines. Add the
exceptions using the following commands:
o
For Method 3
Probe machine and target machines should be part of either Workgroup or Domain.
If the firewall is enabled on target machine, open the ports for WMI and Perfmon to
respond to remote connections. To add WMI and PerfMon firewall exceptions, execute the
following commands on every target system:
o
o
44
For domain computers Discovery user should be either domain administrator or should be
added in local adminitror group on every target machine.
For workgroup computers Following settings are required only in case of Workgroup
computers and if you are not using built-in administrator for connections.
o
Pre-requisites for Windows machine where you will deploy Windows Probe:
o Windows 7
o Windows 8
o Windows Server 2008
o Windows Server 2008 R2
o Windows Server 2012
o Windows Server 2012 R2
RAM: Minimum 8 GB
One Windows Probe can collect data from maximum 100 individual machines. To collect
data from more than 100 Windows machines, you need to deply another Windows probe.
Windows 7
Windows 8
45
46
Method 2:
Data collection
from SCOM and
WMI
1. Select Use SCOM and enter the details mentioned in the previous
row.
2. Select Use WMI and enter the following details:
User Name (Administrator): <Domain Name>\<User>
Password: Password of the entered user
47
For method 3:
Method
Data collection
through WMI
and PerfMon
Discover Hosts: Click this button to discover all hosts present in current domain i.e.
domain of this machine. Out of the listed target machines, you can choose target
machines that should be probed by selecting/clearing checkbox corresponding to the
host.
Add Hosts: Click this button if you want to enter host names manually. A new window
will appear, where you should enter comma-separated list of Windows machines host
names/IP addresses, which will be monitored by this probe. After entering target
machines, save the changes.
6. After you successfully discovered/entered hosts, click the Validate & Save button to establish
connection.
After connecting successfully, the list of the Windows hosts is displayed in the table.
48
Table Details:
Column Name
Description
Host
SCOM Status
SCCM Status
Can Collect?
49
Description
Object
Counter
Rule Exists
Rule Name
Enabled
Frequency in sec
Instances
50
Row in the Green color indicates that the rule for given object and counter is present in
the SCOM Server and no action is required.
RIAT Probe Deployment Guide
Row in the Gray color indicates that the rule is present in the SCOM server for the given
object and counter but it is disabled. You need to enable these rules in SCOM.
Row in the Red color indicates that the performance rule for the given object and
counter is not present in the current SCOM server.
51
5 Advanced Operations
This chapter describes steps that are not common but required only in specific situations.
Password: megha!234
IP address
NetMask
Gateway
Domain Name
Server Name
The system assigns the desired static IP address to RIAT Probe if there are no conflicts.
52
Password: megha!234
The rest of the steps are identical to that of Assigning static IP address to RIAT Probe in
vSphere
53
54
8. Click OK.
55
Port: 22
RIAT Probe Deployment Guide
User: root
Password: app.jeos
To copy the data collected by RIAT Probe to a FTP location do the steps as follow:
1. Log into the RIAT Probe VM through SSH client (like putty) using the below credentials:
NOTE: The 'root' user login is disabled on VMware VCenter VM Console.
Localhost login: root
Password: app.jeos
2. To display the contents of the directory execute ls command.
The Probe data is stored in the directory with a long name. For example - 7fe18389-7a45-4b1e89eb-3b37459c7f27. This name is the unique appliance id assigned to RIAT Probe appliance.
3. Navigate to appliance ID folder.
cd <Appliance ID folder name>
4. Create zip folder:
zip
-r
<ApplianceIDFoldername>.zip *
5. Log into the RIAT Probe appliance using Filezilla (Third party tool) and enter the following
details:
Note: If you do not have Filezilla, download it.
Username: root
Password: app.jeos
Port: 22
6. Copy the zipped folder from RIAT Probe appliance to your local machine.
7. Extract the folder on the local machine and upload this folder on:
Host : datamartftp.hds.com
Username : riatdata
Password : riatdata123
Port : 22
Pre-requisites:
You must have two upgrade files for RIAT Probe, as appropriate. It consists of a .zip file and a
.hash file that has the same filename as the target version number.
For example, if you are upgrading RIAT Probe to a new version RIAT-probe-8.1-12072010 then
you will need the following files:
a. Build file: riat-probe-8.1-12072010.zip
b. Hash file: riat-probe-8.1-12072010.zip.hash
To upgrade RIAT Probe without losing the data, do the following:
1. On RIAT Probe UI, click the Manage link and then select Upgrade Probe.
2. Select Upgrade option.
3. Browse to the Build and Hash file, and then click OK.
4. Restart RIAT Probe.
Verify the new version number at the bottom of the RIAT Probe/Server Login window.
Timezone settings
FTP information
To reconfigure these details, click Reconfigure located at the bottom of the RIAT Probes Home
page and reconfigure the details on Reconfigure Settings window.
Administrator Contact Name and Administrator Contact Email: Name and email address of
the administrator.
Technical Contact Name and Technical Contact Email: Name and email address of the
technical contact.
3. Click Save.
5.8 Adding Command Device in VMware Player (Only for USP V storage
system)
Command device enables SVP probe to collect configuration data from USP V storage system.
58
Pre-requisite:
Ensure that RIAT Probe appliance is powered-off. Ignore this, if it is already powered-off.
1. Select the virtual machine where you have deployed RIAT Probe appliance and then click Edit
virtual machine settings.
2. On the VMware Machine Settings page, select Hardware tab, and click Add.
3. On the Add Hardware Wizard, select Generic SCSI Device, and click Next.
4. Select the appropriate SCSI device, select the checkbox for Connect at power on and click
Finish.
5. Ensure that that command device is added for the USP V storage system:
a. Log into RIAT Probe VM through SSH client (like putty) using the credentials: (Username:
root, Password: app.jeos)
NOTE: The 'root' user login is disabled on VMware VCenter VM Console.
b. Execute the /usr/local/megha/svp/list_devices command to check if the
command device is added for the desired USP V storage device.
c. In the following screen capture, the command device is highlighted:
59
Run the following command for NetApp storage system version 8.0.1:
useradmin role add <Role Name> -a login-http-admin,api-systemget-info,api-license-list-info,api-aggr-list-info,api-volumelist-info,api-nfs-exportfs-list-rules,api-disk-list-info,apiquota-report,api-lun-list-info,api-lun-map-list-info,api-qtreelist,api-perf-object-instance-list-info,api-perf-object-counterlist-info,api-perf-object-get-instances,api-system-getversion,api-snapmirror-get-status,api-useradmin-user-list,apivolume-get-root-name,api-volume-options-list-info,api-useradmingroup-list,api-snapshot-list-info,api-useradmin-role-list,apinet-ifconfig-get,security-api-vfiler
For example:
60
3. Add a group:
useradmin group add <Group Name> -r marsrole
For example:
4. Add a user:
useradmin user add <User Name> -g mars_group
For example:
3. In the Users pane, click Add and enter details in Add User window:
61
Password & Confirm Password: Enter password for above user and confirm it.
Under User login methods section, click Add and do the following:
Click OK.
4. Click Add. The new user will be added. You can use this user to collect configuration and
performance data.
Next: Proced to Add NetApp probe in RIAT Probe Appliance
5.11.1 Adding VMAX probe for already added EMC Unisphere for VMAX
1. Click Home link and then click Add Probe.
62
2. Select VMAX from the Probes list. The VMAX Unisphere Details window appears.
3. Click Add Storage link corresponding to the Unisphere for which you want to add Probe. The
Managed VMAX Storage System window appears.
4. Select the checkbox for which you have not added probe(s):
5. Click Finish and then click OK. Proceed to start added probe(s).
RIAT Probe setup will inform you when invalid values are found and will set it to default five
minutes.
63
1. In the internet browser, type the RIAT Probe URL https://<ip_address>:<Port Number>and click
Enter.
The Login screen appears.
2. Log on to RIAT Probe.
Note: The user name and password is set at the time of deployment.
3.
2. Click Next.
3. In the Spcify Name and Location section, specify name of the virtual machine in Name field and
then click Next.
4. In the Assign Memory section, specify the required memory. Minimum: 4 GB Recommended: 8
GB
Click Next.The Configure Networking section appears.
5. Configure network for the VM and then click Next.
6. In the Connect Virtual Hard Disk section, click Use an existing virtual hard disk button.
7. Browse to the location to select RIAT Probe VHD.
66
8. Click Finish.
9. Right-click VM and start it.
10. Proceed to the Configuring RIAT Probe Appliance section.
4. Click Next. The system skips the EULA section, as it is not applicable to RIAT Probe OVA file and
displays Location section to specify the location of RIAT Probe and home server.
5. In the Loction section, select a pool to deploy RIAT probe appliance from the Import VM(s) to
list. Based on the selection, the Home Server will be selected. A Home Server provides the
resources for RIAT Probe.
6. Click Next. In the Storage section, select the Storage Repositories (SRs) for keeping RIAT Probe.
To keep all the imported disk images for RIAT Probe on the same SR, click Place all
imported virtual disks on this target SR and select a SR from the list.
To keep the disk images for RIAT Probe on different SRs, click Place imported virtual
disks onto specified target SRs. Then, for each virtual disk, select the target SR from the
list in the SR column.
7. Click Next.
In the Networking section, specify the virtual network interface.
8. Click Next. In the Security section, select the Verify Manifest Content check box to specify the
security settings.
67
9. Click Next. The OS Fixup Settings section appears. When RIAT Probe OVA file is built on a
hypervisor other than XenServer, sometimes there could be compatibility issues when trying to
deploy it on XenCenter.
By selecting the Use Operating System Fixup check box, XenCenter ensures a basic level of
interoperability for RIAT Probe OVA file that is being imported.
10. Click Next.
In the Transfer VM Settings section, the network settings for RIAT Probe can be configured.
To configure the network settings (IP address, subnet mask, and gateway) for RIAT
Probe, do one of the following:
o
To configure networking settings manually, click the Use these network settings
button and enter the IP address, subnet mask and gateway.
VMware Player on Linux machine RIAT Probe VMware Configuration (VMX) file.
VMware Player on Windows machine RIAT Probe Open Virtual Appliance (OVA) file.
The deployment process is similar for both RIAT Probe appliance file formats.
1. Open the VMware Player application.
2. From the File menu, select Open a Virtual Machine. The Open Virtual Machine window appears.
3. Navigate to RIAT Probe VMX/OVA file, select it and then click Open.
4. On Import Virtual Machine window, click Import.
5. Click Play Virtual Machine to start RIAT Probe.
6. Proceed to the Configuring RIAT Probe Appliance section.
69