SNMP
After reviewing telemetry data and conducting interviews with customers to determine use of this capability, this target was deemed appropriate to deprecate. If you replaced this technology with something that is currently not supported, submit an idea at the Cloud Management and AIOps Idea Portal. The last Turbonomic version that will contain this target is 8.15.0.
Turbonomic will discover application and operating system resources using SNMP (Simple Network Management Protocol) on Linux hosts within the specified scope of your environment.
Prerequisites
Underlying VM host targets added to Turbonomic (for discovery)
-
SNMP service enabled/configured on target VMs to allow access to the OIDs required. The credentials used must allow access to the following OIDs:
1.3.6.1.2.1.1.1 - sysDescr
1.3.6.1.2.1.25.4.2.1.2 - hrSWRunName
1.3.6.1.2.1.25.5.1.1 - hrSWRunPerfEntry
1.3.6.1.2.1.25.3.3.1.2 - hrProcessorLoad
1.3.6.1.4.1.2021.4.5 - memTotalReal
1.3.6.1.4.1.2021.4.6 - memAvailReal
1.3.6.1.4.1.2021.4.11 - memTotalFree
1.3.6.1.4.1.2021.4.14 - memBuffer
1.3.6.1.4.1.2021.4.15 - memCached
For environments that include SNMP targets, Turbonomic can discover incorrect memory values for Linux systems. This can occur for the systems that use the net-snmp package, version 5.7.2-43.el7. You should use versions less than 5.7.2-43.el7, or greater than or equal to 5.7.2-47.el7.
https://technet.microsoft.com/en-us/library/dn798297%28v=ws.11%29.aspx
For VMware hosts, you must install VMware Tools on the target VMs.
Adding SNMP targets
-
Click Settings > Target Configuration.
-
Click New Target > Guest OS Processes.
-
Select SNMP.
-
Configure the following settings:
-
Target Name
Specify a name that uniquely identifies this connection.
This name is for display purposes only and does not need to match any name in SNMP.
-
Scope
Specify the scope Turbonomic uses for application discovery.
Turbonomic searches for SNMP applications on the Virtual Machines found within the set scope. This scope can be set to the entire environment, single or multiple clusters, or particular Virtual Machines.
Note:A single scope (target) must not contain more than 500 Virtual Machines. Turbonomic recommends utilization of multiple SNMP targets for environments exceeding this limit.
-
Community
Specify the SNMP v2c community string Turbonomic uses to connect to the SNMP agent on the VM.
-
Port number
Specify the port number Turbonomic uses to connect to the SNMP agent on the VM.
-
Full Validation
If you select this option, Turbonomic requires all database servers hosted on the VMs in the selected scope to be a valid target. If Turbonomic is unable to authenticate a database server in the scope, the target does not validate and data is not collected.
-
Enable SNMPv3
If you select this option, Turbonomic uses SNMPv3 to connect to the virtual machines in the selected scope.
-
SNMPv3 Username/SecurityName
Specify the username/SecurityName that Turbonomic uses to connect to the Virtual Machines hosting the application.
-
SNMPv3 Enable Privacy
If you select this option, Turbonomic encrypts using the privacy password to keep the connection private.
-
SNMPv3 Authentication Password
Specify the Authentication Password Turbonomic uses to connect to the virtual machines in the selected scope. This allows requests to be authenticated, confirming the sender's identity.
-
SNMPv3 Privacy Password
Specify the Privacy Password Turbonomic uses to connect to the Virtual Machines in the selected scope. For requests to be encrypted, the SNMP manager and the SNMP agent must share knowledge of the privacy password associated with the username.
-
SHA-1 For Authentication
If you select this option, Turbonomic uses SHA-1 Authentication to connect to the virtual machines in the selected scope. When unchecked, Turbonomic uses MD5
-
AES For Privacy
If you select this option, Turbonomic uses AES 128 to connect to the virtual machines in the selected scope; otherwise, Turbonomic uses DES.
Note:Turbonomic does not support AES 192 or 256 for SNMP targets.
-
Enabling guest load metrics
For environments that use WMI or SNMP probes, you must configure the Turbonomic installation to enable guest load metrics. Without this configuration, the WMI and SNMP probes will not display discovered guest load data.
To enable guest load metrics, you must edit the CR file and restart the platform:
Open the cr.yaml file for editing.
/opt/turbonomic/kubernetes/operator/deploy/crds/charts_v1alpha1_xl_cr.yaml
Enable guest metrics in the
properties
section of the file:properties: repository: showGuestLoad: true
Save your changes to the file.
Apply your changes.
Run the command:
kubectl apply -f /opt/turbonomic/kubernetes/operator/deploy/crds/charts_v1alpha1_xl_cr.yaml
To restart the component, delete the repository pod.
Run the command (where {POD_ID} is the ID that is appended to the pod in the
get pods
listing):kubectl delete pod -n turbonomic repository-{POD_ID}
Monitored resources
Turbonomic monitors the following resources:
-
WMI/SNMP Application
-
Virtual CPU (vCPU)
Virtual CPU is the measurement of CPU that is in use.
-
Virtual memory (vMem)
Virtual memory (vMem) is the measurement of memory that is in use.
-
-
Virtual Machine
-
Virtual CPU (vCPU)
Virtual CPU is the measurement of CPU that is in use.
-
Virtual memory (vMem)
Virtual memory (vMem) is the measurement of memory that is in use.
-
Virtual storage
Virtual ssorage is the measurement of virtual storage capacity that is in use.
-
Storage access (IOPS)
Storage access, also known as IOPS, is the per-second measurement of read and write access operations on a storage entity.
-
Latency
Latency is the measurement of storage latency.
-
Actions
The specific actions that Turbonomic recommends can differ, depending on the processes that Turbonomic discovers.
For other application components, Turbonomic can recommend actions based on the resources it can discover for the application. For example, Node.js® applications report CPU usage, so Turbonomic can generate vCPU resize actions and display them in the user interface.
Turbonomic supports the following actions:
-
Virtual Machine
-
Provision additional resources (VMem, VCPU)
-
Move Virtual Machine
-
Move Virtual Machine Storage
-
Reconfigure Storage
-
Reconfigure Virtual Machine
-
Suspend VM
-
Provision VM
-
Without separate targets to discover Guest OS Processes or Application Servers, Turbonomic does not generate actions on applications. Instead, it generates resize actions on the host VMs. For on-prem environments, if host utilization is high enough on the host running the application VM, Turbonomic can also recommend provisioning a new host.