Overview
OneIQ Pulse for Datacenter supports the collection of configuration and performance data from Azure Local clusters, nodes, and virtual machines. This article explains how to deploy OneIQ Pulse to connect with an Azure Local platform.
Prerequisites
Outbound Internet connectivity on port 443 (SSL) to OneIQ
A read-only user for Azure Stack.
OneIQ Pulse server - Windows Server 2016 or later with the following specifications.
Cluster Virtual IP and Management IPs of all Azure Stack HCI cluster nodes should be accessible through WinRM.
Machines | Without Network Flows | With Network Flows |
Up to 5,000 | 2 vCPUs, 4 GB memory | 4 vCPUs, 8 GB memory |
5,000–10,000 | 4 vCPUs, 8 GB memory | 8 vCPUs, 16 GB memory |
NB: For environments larger than 10,000 machines, contact our team.
Discover Azure Local HCI clusters
Open the OneIQ Pulse console and follow the steps below:
Select the Microsoft Azure Local platform
Copy the connection key to the clipboard or save it. Then select Download OneIQ Pulse for Datacenter to download the OneIQ Pulse executable.
Once you’ve downloaded the OneIQ Pulse for Datacenter binary to a Windows Server in your environment, run the executable.
Paste the Connection key into OneIQ Pulse during setup.
In the Select Discovery Target step, choose Microsoft Azure.
Enter the following information for the Azure Stack HCI cluster:
Cluster FQDN or Cluster Virtual IP as Hostname or IP address
Username and Password
Click Create to initiate Azure Stack HCI cluster discovery.
Upon successful discovery, a new Azure Stack HCI tile will appear in the Dashboard with the following information:
Hostname or IP address
Username
Status
What's next?
Use OneIQ Pulse to discover other supported datacenter platforms and collect network flows to identify network dependencies.
Cloud-native platforms inside the datacenter can be connected using the following OneIQ Pulse connectors: