Hi Team,
I'm currently creating a custom report of all my virtual machines in hyper-v, however I can't find a way to add its host server name to the report for example:
SERVER1 192.168.0.1 Windows Server 2012 Hosted By: HyperV-Server1
As for now I was able to retrieve all my virtual machines in one report but I'm unable to get its host server name
Your suggestions will be highly appreciated,
Best regards,
we are using veeam to backup and replicate our virtual servers is there any way to monitor the veeam jobs to get alerts if they complete/fail?
I call myself searching for the answer and i have not found any.
Co-Stop (%CSTP) is the percentage of time that a SMP virtual machine was ready to run, but incurred delay due to co-vCPU scheduling contention. To remedy Co-Stop on a VM, decrease the number of vCPUs on that VM. If there are multiple VMs with high %CSTP on a host, it is likely a sign of CPU contention and resource starvation due too many vSMP VMs on that host. Migrate some of those VMs off to other hosts to re-balance the load in the cluster and also, decrease the number of vCPUs allocated to those VMs to see if the %CSTP goes to zero.
| VM CPU Co-stop (%CSTP) Alert in Virtualization Manager | VM CPU Co-Stop Alert Viewer in Virtualization Manager |
|---|---|
|  |
Either SolarWInds completely overlooked this when changing how Virtualization Objects are added to Orion, or I am completely missing the setting to do this for us.
Previously you could just run a one hop Network Discovery with the vCenter server as the only IP address. You just had to put in valid VMware credentials and Everything would get brought in as Orion nodes and with the VMAN appliance integrated it would automatically marry the data up. You could even put in WMI and SNMP credentials on the appropriate pages of the Discovery wizard and it would even scan and bring in all of the VM's as well. It worked great for bulk adding all of our ESX hosts and VM's into Orion in one big swoop.
Now however, the page in the Discovery wizard where you used to put in the VMware credentials has been replaced by the "Add VMWare VCenter or Hyper-V Devices" button. Clicking this button exits you from the Discovery Settings wizard and takes you to the new Add Virtualization Objects page. I thought to myself, "OK, cool, so we just add the vCenter server and it will now automatically add the ESX Hosts in for us. I hope it also adds in the VM's like the old Discovery Wizard does too, but as long as it at least gets the Hosts I'll be happy.". I figured surely they wouldn't overlook that, right?
Well, they did... Adding the vCenter server this way only brings the vCenter server in as an Orion node. The ESX hosts are only brought into Orion as "Orion VMAN" nodes. This means the hosts are not pinged by Orion every 2 minutes, they are not polled for additional metrics like CPU, SNMP, HARDWARE HEATLH, or any of the other data that Orion gathers. It also means you can't assign custom property values to them or anything. This is a HUGE miss by SolarWinds. We have nearly 300 ESX hosts between our two vCenters. Clicking on each one individually and choosing "Manage This Node" is just not feasible.
The only other thing I can think to do would be to do a SWQL\SQL query to get a list of all the ESX Host IP's from the VIM.Hosts table, then run a "Ping Only" discovery against that list of IP's. It should marry them up once brought in (I hope). This is a pain though and is a big step backwards compared to how it used to work.
Luckily I had two Discovery Profiles saved that are setup the way I described above. Running them worked just like it used to and brought in all the VMware Hosts and VM's as both Orion and Orion VMAN nodes. But what if these profiles ever get deleted? What if we get a new vCenter server that I need to Discover?
Please SolarWinds, tell me you have a function built somewhere that replaces the features I listed above? We are a large environment, so when you remove functionality that allowed us to bulk manage things in Orion that really hampers us and makes our job harder. What is SolarWinds vision for Orion VMAN with regards to monitoring hosts? Do you intend for your users to just have to click on each host individually to manage them as Orion Nodes? Do you intend for us to only manage them as VMAN Nodes and thus no longer get hardware health or other important data that is collected by Orion core? I just don't understand how such a major thing was overlooked? I scoured the admin guides and documentation last night and could not find a single word about adding hosts in (other than adding standalone esx hosts). Our use case is not unique by any stretch of the imagination, so how are other users handling this? I really don't get it at all. It is baffling to me how this oversight exists... Or, like I said, maybe I'm just missing something. I sincerely hope that is the case.
ESX datastore queue depth
Virtualization engineers are curious lot, especially now that we've given them access to the pre-production VMAN environment. With all of the stats out there, of course they would find the *one* stat that I couldn't find in the tool.
Is the ESX datastore queue depth (current queue depth) captured and reported? I'm not looking for configured max queue length though it would be really cool to be able to compare the max queue length and current queue length.
Anyone?
Trying to find one, anyone aware of such a beast?
Thanks
Hi Team,
I'm currently creating a custom report of all my virtual machines in hyper-v, however I can't find a way to add its host server name to the report for example:
SERVER1 192.168.0.1 Windows Server 2012 Hosted By: HyperV-Server1
As for now I was able to retrieve all my virtual machines in one report but I'm unable to get its host server name
Your suggestions will be highly appreciated,
Best regards,
CPU Ready (%RDY) is the percentage of time that a VM is ready to execute but has not been schedule for CPU time because it's waiting for a CPU to become available. This most often comes up when CPUs are oversubscribed. For example, a system has 16 physical CPUs but the sum of the number of vCPUs across all the VMs on that system is much greater than 16.
The general rule of thumb for a VM with 8 or less vCPUs is for %RDY to be between 8-10 ; otherwise, CPU contention is a factor. Next, since it's the summation of the all the vCPUs on that VM so %RDY may be higher with 32, 64, or 128 vCPUs. So a %RDY of 20 may be acceptable in those cases.
To remediate, make sure your VMs are right sized and that your host or cluster is not highly over-committed. Also, load balance your VMs across your hosts and clusters.
We're currently running VMAN 6.1.1 and we've integrated our instance with our NPM instance. Ta-da -- magic datastore data appears for hosts and VMs and -- oh, wait a minute? Why doesn't that host have storage related data? We have 8 or 9 vCenters that we poll data from via VMAN and all are managed in NPM. As a data geek I have a health distrust of data collected until I can be sure that it is reliably collected and reported -- and even then I want to be able to prove that point at any given time.
I have two challenges -- one is VMware hosts that are not managed nodes in NPM and two, and perhaps the more challenging, is VMware hosts that are not reporting storage metrics. I'll share my query for the first one if someone would be so kind as to help with the query for the latter.
Hosts That Are Not Managed in NPM
SELECT [HostID]
,[NodeID]
,VIM_DataCenters.Name AS DataCenter
,VIM_Clusters.Name AS Cluster
,[HostName]
,[PollingSource]
,[BootTime]
FROM [SolarWindsOrion].[dbo].[VIM_Hosts] WITH (NOLOCK)
RIGHT JOIN VIM_DataCenters WITH (NOLOCK) ON VIM_DataCenters.DataCenterID = VIM_Hosts.DataCenterID
RIGHT JOIN VIM_Clusters WITH (NOLOCK) ON VIM_CLusters.ClusterID = VIM_Hosts.ClusterID
WHERE NodeID IS NULL
Run this query and then take the resulting hostIDs and plug them into this URL - [Your_Orion_ServerName]/Orion/VIM/HostDetails.aspx?NetObject=VH:[HostID] This will take you to the Host page and you should see something like the capture below. Click on Manage This Node and follow the prompts.
NOTE: If the node is already managed in NPM you will get a warning that looks like the warning below. If the node can be polled via SNMP simply click cancel and then click next again from Add Node page again. Follow the prompts and you will find that the custom properties are already populated as per the node in NPM. Finish the process and the HostID will disappear from the query above.
If the host is ICMP only you will have to either convert it to an SNMP node in NPM or delete the node in NPM and add it via the process above. I'm not sure why the same process doesn't work for ICMP only nodes but it doesn't.
We have been using the free VM Monitor tool to do quick look at specific ESX servers. However, when we upgraded to VMware 6.7 the toll no longer connects?
Is there a setting we missed or does it not work with this newer version on VMWare?
Any info or suggestions?
Hi All,
I thougnt I'd post the question here in case anyone can help or has the same query.
The site I am working on is looking at VMAN, NPM and SAM as a base product set. This particular query is around VMware vCenter as well as ESXi polling.
I have added a vCenter Appliance as a monitored Node using Status Only: ICMP and Poll for VMware Providing creds.
When I clicked through the vCenter Node to get to an ESXi host, it was unmanaged to I added this in the same way. The wizard stated that I was polling the ESXi host via the vCenter and that I should use Status Only: ICMP as the polling method.
From what I understand, if I want to view VM interfaces stats (i.e. virtual NICS) using an Agent this does not count against my NPM interface count, which is great.
What I'm unclear about is how I monitor network interfaces on the ESXi hosts themselves. From what I can see, this isn't done via vCenter so I assume I would need to enable SNMP in order to get this information, which goes against the Add Node wizard guidance.
On this point also, if I want the vCenter to be able to send SNMPv3 traps to Orion, presumably I need to add it as an SNMPv3 managed host?
Unless I'm missing something, I can't see how ESXi interface statistics get monitored via any other means than SNMP.
Has anyone got any more info on this that might help?
Many thanks!
M
Is there documentation that more completely details the role, function, and implementation of the VMAN Free Additional Polling Engine (APE)?
(....what aspect of VMAN are they intended to be used for? , which installer would be used to install one?... )
thanks
Environment: vMan Orion 8.1 (no appliance) and Orion 2017.3 with SAM 6.5
Objective: Alert on disk utilization from any VMs managed by vMan. These VMs are only managed by vMan and not managed by SAM thus the VMs are not managed nodes from Orion perspective. In other words, I like to alert when vMan VM Component Volumes object shows in Red:
I don't see any option to specify these objects and triggers when building alerts.
Thanks
j
Since upgrading our environment to ESXi/vCenter 6.5U2 we have been experiencing "VM Disk Latency" according to VMAN. Frequently it will show latency approaching 25 seconds! After hours of trying to find the cause of this latency we are starting to wonder if the data in Orion could be incorrect. We can not find any evidence of latency exceeding 8ms in vCenter nor on the hosts using esxtop.
Where is VMAN pulling the VM Disk stats from and how can I validate that an issue actually exists?
*Note: VMAN 8.2.1 HF1
Hi Guys
i want to work out what each datastore's iops are for the day and over maybe a week or month. Anyone any tips on how to build a query to do this and add the widget to the storage dashboard
excuse my ignorance i'm new to hyper 9/virtualization manager
thanks
p
Our backup solutions uses snapshots in it's backup process, with this happening nightly we have a desire to send out a daily report to see if there are any snapshots that may have been left behind.
The issue has been that the report isn't accurate all the time.
Additionally, i've deleted Snapshots and after hours SolarWinds is still showing them.
I've been trying to research the polling interval for this data but can't seem to find any information that talks about it.
All of our polling seems to be working in VMAN and eventually the Snapshot data catches up (I'm not sure if it's X time later or if it's after the nightly database maintenance)
Hi,
What is the root password for the appliance? I have had a power failure on the machine running the virtual instance of Solarwinds Virtualization Manager, which means i need to run fsck before it can restart.
However, i can't run fsck without the root password.
Thanks in advance!
Hi all-
#1. I am hoping someone can help me resolve this certificate error. when clicking the dashboard tab under virtualization in Orion:
I have installed the cert multiple times, both on my workstation and server and still get this message. After closing the browser and reopening it I have to do the process over again.
#2 Is there a way to pass login from orion to Virtualization Manager so we wont have to log in twice?
Hello,
I am new to Virtualization Manager, and really like it.
Can you please tell me if there is a way to report on the space being consumed by the vmware.log files for each vm on the datastore, and which VM's they are?
Currently we tend to find log files that grow into the gigabyte, and are getting concerned that are datastores will fill up.
Any help would be greatly appreciated.
Thank you.
I'm writing this as a tutorial of my issues with VMAN, specifically the backup process, but also as a point to gather information about how others are handling it.
We installed VMAN in June 2016. Details of the infrastructure are as follows:
VMAN running on ESX 5.5
Collecting data from 8 vCenters, totaling 17,000 VMs, 850 hosts, 2500 datastores, and 150 clusters
We were backing up the appliance using Avamar. Avamar backups the VM by taking a snapshot, backing up the data, removing the snapshot, and running the disk consolidation job.
The process was running fine for a while until the database got to over 1TB in size. After that we started having issues with the appliance to where it would suddenly crash. When it crashed, it was unrecoverable by a simple reboot as it would not accept any commands including to power off or vmotion. The process of recovery involved moving all of the remaining VMs from the host and rebooting the host. When the host reboots, the appliance would migrate to another host and allow it to power back on.
Solarwinds support was unable to find an answer to the problem as the VM was down. VMware was unable to fine a solution as there were no error logs or indication of what was occurring. Solarwinds was saying it was a VMware problem since the VM was down and not functioning and VMware was saying it was a Solarwinds problem since we had no other problems in our environment.
The VM crashed beyond repair in early November, and we had no good backup. The VM was rebuilt and seemed to be working fine until mid January when the problem resurfaced.
After extensive research on my part, the root cause was determined to be because the disk consolidation job was not completing. There was a change in ESX 5.5 where the disk consolidation process was designed to be less intrusive, preventing the VM from going into a stunned state. As a result, the disk consolidation job cannot keep up with the amount of IO from the data collections. The disk consolidation job times out, causing backend disk problems.
VMware recommended removing the timeout condition. This worked with the VM completely powered off, but the job took about 2.5 days to complete. It however, later caused additional problems as the VM crashed during a consolation job and we could not power it back on until the job finished.
We recently quit using Avamar to back up the data and went to TSM. The downside of TSM is that it does not have a postgresql agent, so we have to back up the data to a flat file and then have TSM back up the flat file.
The script is referenced at Perform backups in the Virtualization Manager - SolarWinds Worldwide, LLC. Help and Support. The database is currently about 1.7TB. I chose the custom backup option and it takes about 20 hours to complete, resulting in a 100GB file. During the backup job, the application goes in and out of a usable state, so we have numerous missing data points, sometimes lasting multiple hours. After the backup completed, the application returned to a usable state. As a result of this, we cannot back up the database more than once a week.
Next steps are to come up with a way to do incremental backups. If anyone is already conducting a weekly backup with a nightly incremental, I would be curious to hear how you have it configured.
