Manage a cloud instance or VM as an Orion Platform node
This Orion Platform topic applies only to the following products:
ACM — IPAM — NAM — SAM — VMAN
You can configure a cloud instance/VM as a managed node in the Orion Web Console to leverage the full capabilities of the Orion Platform, including the ability to:
- Use SolarWinds SAM to:
- Monitor the performance, capacity, and health of Linux and Windows apps across data centers, remote offices, and the cloud.
- Poll specific OS metrics beyond the basic metrics gathered by cloud service APIs, including instance/VM memory and other metrics retrieved by SAM application monitors.
- Track cloud instances/VMs that do not support agentless monitoring.
- Monitor multi-vendor applications, servers, databases, and storage.
- Develop and deploy custom script monitors for PowerShell, Nagios, Linux/Unix, and Windows.
- Leverage SAM application monitors and templates to poll for app health and performance metrics to pinpoint the root cause of application issues.
- Track dependencies and troubleshoot issues via interactive visual mapping in AppStack.
- Use SolarWinds Virtualization Manager (VMAN) to:
- Fix vSphere and Hyper-V issues in minutes through performance recommendations and monitoring.
- Assign Custom Properties to nodes.
- Reduce downtime with proactive alerts and recommendations.
- Save time by fixing issues faster with active performance alerts.
Reclaim an average of 23% of virtual resources using VM sprawl recommendations.
VMAN recommendations that trigger actions in virtual environments such as vCenter do not impact cloud instances/VMs.
Use SolarWinds SAM and VMAN together to:
Before configuring a cloud instance/VM as a managed node, note these details:
- Before performing maintenance on a managed cloud instance/VM, use the Unmanage/Manage toggle to release the license and halt polling. See Perform actions against cloud instances/VMs
- If you halt polling for a managed node, the cloud service API stops polling for metrics but continues to monitor the node for status.
- Depending on how Azure subscriptions are configured, deploying an Orion agent on an Azure VM may require different Azure credentials. See Configure a VM for use as a managed node in the Orion Platform and consult your subscription administrator, as necessary.
- Managing a cloud instance/VM as a node consumes VMAN sockets and SAM licenses.
Configure a cloud instance/VM as a managed node
To manage a cloud instance/VM in the Orion Web Console:
Deploy an Orion agent to an instance/VM. See Deploy Windows agents in the cloud.
Click My Dashboards > Cloud.
On the Cloud Summary page, click the instance/VM in the Cloud Instances Status Summary list to display its Details page.
On the Details page, click Manage Instance/VM As Node.
When the Manage As Node dialog box appears, select an IP address.
Click Yes, Manage This Node.
Follow the instructions provided in the Add Node wizard.
Note these details about wizard options:
For Polling Method, select a method that supports cloud instances/VMs — Agent, WMI, or SNMP.
If you select External Node or Status Only (ICMP), the instance/VM is not related to the node and cloud metrics do not appear on the Node Details page.
- The Orion Platform can use these methods to poll a cloud instance/VM managed as a node:
- An Orion agent with or without a VPN. See Deploying an Orion agent.
- WMI with a VPN connected to an AWS Virtual Private Cloud (VPC) or Azure Virtual Network (VN).
- SNMP with a VPN connected to an AWS VPC or Azure VN.
Before nodes can connect to cloud instances/VMs, the Orion Platform must poll for IP and MAC addresses, which can take 10 to 15 minutes. After data is retrieved, polling starts and node metrics appear in the Orion Web Console.
There are many ways organizations can set up and use Azure. Depending on how Azure subscriptions are configured for your organization, you may need to change VM settings in Azure before configuring a VM as a managed node in the Orion Platform. Consult your subscription administrator, as necessary.
- Log into the Azure Portal.
- Navigate to the VM.
- In the VM's Network Interface security rules, open ports required to monitor the VM with an Orion agent.
- Click Virtual network/subnet.
- On the Resource Group Details page, open network interface details for the Connected device.
- Click Network security group.
- Edit Inbound and Outbound security rules.
- Allow communication using ports required by Orion Agent.
- Verify that the VM has a static public IP address.
- Navigate to the VM Overview page.
- Click Public IP Address.
- Make sure a static IP address is selected.
- Configure the firewall on the VM.
- Use a Remote Desktop Protocol (RDP) to log into the Azure VM.
- Open a port for the Orion agent. See Agent Requirements.
Use PowerShell to disable the firewall the Set-NetFirewallProfile cmdlet.
PS C:\>Set-NetFirewallProfile -Profile Domain,Public,Private -Enabled False
- Press Enter.