Can someone explain the difference between Virtualization Manager and IVIM? What do I get from Virtualization Manager that I don't get from IVIM? Does it require a separate machine and cannot be installed on the same machine as NPM and all the other modules?
↧
Virtualization Manager Versus IVIM
↧
Cannot clear Datastore Excessive VM log files alert
One of my datastores has thrown the alert about excessive vm log files. I've gone through and pulled all log files then purged essentially all but the base vmware.log file. My report shows these files as gone, but Solarwinds is still triggering this alert. In addition if I query the VIM_DiskFile table, it still contains all the log files that I deleted. I assume this is why the alert is still triggering.
It has been some 5 hours since I've done this but it hasn't cleared yet. I cannot see anywhere to force a poll on the datastore to refresh the VIM_DiskFile table. I am likely just overlooking it as a Solarwinds newbie. Can anyone point me where I need to go?
↧
↧
alert for VMOTION
how to trigger an alert for VMOTION please? Thank you.
↧
VMAN, ESXi, vCenter
There don't seem to be videos on adding ESXi hosts to Solarwinds for monitoring. Also are there any recommendations as to what to monitor for ESXi 6.5? Any KB articles on grouping ESXi hosts and creating alerts?
↧
Monitoring RAID Status for ESXi Servers
Hi!
Is VMan capable of monitoring the RAID Array status of ESXi servers? I specifically mean the direct-attached disks that are RAID-configured on a VMWare server.
Can't find anything in the VMan guide. Hope somebody can help.
Thanks in advance,
Paulo
↧
↧
VMware Polling / SNMPv3
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
↧
VMan / Orion report for CPU Ready [%]
Hi all,
Trying to get a report via the Orion portal for CPU ready.
I know it's avail in VMan, but in Orion the value comes up with {0:0.00} ms.
Anyone familiar with this and can confirm it's actually displaying CPU Ready % and just needs the Custom Format changed?
I'd prefer it in Orion obviously, but if VMan Reporting is the only solution, then I need to narrow the calculations down to business hours M-F, 6am - 9pm.
In my below examples, I attempted to set the clustername seperated by OR statements before the AND, however it did not appear to work.
Is it possible to optimise the queries for the the VMs in the various clusters, or is it correct how I have done it.
VM - CPU Utilisation
vm.powerstate:poweredOn AND cluster.name:"METRO-PROD" OR
vm.powerstate:poweredOn AND cluster.name:"DC-PROD" OR
vm.powerstate:poweredOn AND cluster.name:"OL-PROD" OR
vm.powerstate:poweredOn AND cluster.name:"DC-DEV" OR
vm.powerstate:poweredOn AND cluster.name:"OL-DEV" OR
vm.powerstate:poweredOn AND cluster.name:"DC-OPS"
Thanks
↧
"vmStatsProvider" causing Solarwinds to give false "down" alerts?
Hi Everyone,
Does anyone have experience Solarwinds giving false "down" alerts on with virtual servers?
It happened on a server yesterday morning, twice. We received alerts from Solarwinds that a particular server was down around 7:00 and 8:00 AM.
In looking at the application logs for that time on the server I spied numerous line items:
| Information | 10/9/2014 7:08 | vmStatsProvider | 256 | General | The "vmStatsProvider" is successfully initialized for this Virtual Machine. WMI namespace: "root\cimv2". | |||||||||
| Information | 10/9/2014 7:08 | vmStatsProvider | 258 | Guest Library API | The "vmGuestLibrary" is successfully initialized for this Virtual Machine. | |||||||||
| Information | 10/9/2014 7:06 | vmStatsProvider | 256 | General | The "vmStatsProvider" is successfully initialized for this Virtual Machine. WMI namespace: "root\cimv2". | |||||||||
| Information | 10/9/2014 7:06 | vmStatsProvider | 258 | Guest Library API | The "vmGuestLibrary" is successfully initialized for this Virtual Machine. | |||||||||
| Information | 10/9/2014 6:57 | vmStatsProvider | 256 | General | The "vmStatsProvider" is successfully initialized for this Virtual Machine. WMI namespace: "root\cimv2". | |||||||||
| Information | 10/9/2014 6:57 | vmStatsProvider | 258 | Guest Library API | The "vmGuestLibrary" is successfully initialized for this Virtual Machine. | |||||||||
| Information | 10/9/2014 6:55 | vmStatsProvider | 256 | General | The "vmStatsProvider" is successfully initialized for this Virtual Machine. WMI namespace: "root\cimv2". | |||||||||
| Information | 10/9/2014 6:55 | vmStatsProvider | 258 | Guest Library API | The "vmGuestLibrary" is successfully initialized for this Virtual Machine. | |||||||||
| Information | 10/9/2014 6:46 | vmStatsProvider | 256 | General | The "vmStatsProvider" is successfully initialized for this Virtual Machine. WMI namespace: "root\cimv2". | |||||||||
| Information | 10/9/2014 6:46 | vmStatsProvider | 258 | Guest Library API | The "vmGuestLibrary" is successfully initialized for this Virtual Machine. | |||||||||
If I understand this correctly these are coming from the VMWare tools that is installed on the virtual instance?
Can this be causing Solarwinds to see the server being down?
Thanks everyone,
Cheryl
↧
Option to Monitor Datastores grey'd Out in NPM
Hello Community peeps!
I am trying to setup monitoring of VMware datastores in Solar Winds Orion NPM but its grey'd out. Where in the console can I enable this?
↧
↧
How to Bulk Add ESX Hosts as Orion Nodes in new Orion VMAN 8.2?
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.
↧
ESXi Support
Environment:
Orion Platform 2017.3.3 SP3
Cloud Monitoring 1.1.0
IPAM 4.6.0
SAM 6.5.0
DPAIM 11.1.0
VMAN 8.1
QoE 2.4
NetPath 1.1.2
NPM 12.2
Problem Description:
When adding a node, I am unable to successfully "Test" the credentials within the VMware Polling Settings. After attempting to validate the credentials it finally gives up with the error message "Test Failed. Cannot login with selected vCenter or ESX credential." Without question, the credentials are correct. I have no issue with our ESXi 6.0 hosts and their vCenter, but cannot get it working for ESXi 6.7. Is our version of the software not compatible with 6.7? If not, does anyone know if it's compatible with ESXi 6.5?
↧
VM Disk Latency Alerts
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
↧
High Percent Co-Stop (%CSTP)
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 |
|---|---|
|  |
↧
↧
Datastore low free space alert
Will VMAN trigger a datastore low free space alert if the VMs attached to the datastore are allocated over 90% of datastore capacity using thick disk or is the alert triggered when actual stored data (OS, apps, files, etc) reach over 90%
↧
How to Create an alert when there are two or more snapshots for the same VM ?
How to Create an alert when there are two or more snapshots for the same VM?
I have a requirement where we need to trigger alert if there are more than 2 snapshots created of the same VM. Any input will be appreciated.
↧
IPAM Integration with VMware
Hi,
If you deploy virtual machines frequently, what is the desired workflow for assigning IP addresses?
We are looking at enhancing IPAM API (a.k.a. SWIS or Orion SDK) as described here: Add SWIS features to IPAM. The ultimate goal is using this API to integrate with VMware vCenter Orchestrator in order to improve/automate VM deployment by assigning IP addresses via IPAM.
I would like to discuss details of the workflow in detail -- if you are interested in such discussion, please reply to this post, or send me a direct message.
Thanks,
Jiri
↧
Custom Report
I want to create a report showing the analysis that how many VMs are created in each month ? and which VMs are they ? since beginning.
↧
↧
VMware Polling / SNMPv3
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
↧
Solarwinds Recommendations Report
Good morning,
I am new to Solarwinds reporting and thwack community. I am looking for some assistance on a report I need to create for work. I was wondering if anyone has created a report based on the Virtualization/recommendations Top 10 dashboard widgets. The report my management team would like to see is a complete list of our virtualization environment with the Solarwinds recommendations for memory, CPU and disk by virtual machine based on the Solarwinds data collected for a period of time. Any assistance to point me in the right direction would be greatly appreciated.
Thanks,
↧
ESXi Host does not appear in Virtualization Summary
I have added my vCenter server and 'supposedly' all of my VMware/ESXi hosts into inventory using Network Sonar Discovery. Everything was found perfectly, and when browsing Settings > Node & Group Management > Manage Nodes.. *sort by Vendor* > VMware.. I am able to see all of my ESXi hosts as well as vCenter.
Then when looking at the Virtualization Summary page, I am only able to see 2 of the 3 ESXi hosts.
I have removed everything and added it all back, starting with vCenter. I've stopped and restarted polling on the host that is being excluded. And I have refreshed every possible process/thing I could find... I am at a loss.
Has anyone else experienced this & if so what did you to to fix it? Also, the host being left out is in the same cluster as the hosts appearing in the Virtualization Summary page. There is no difference between any of my hosts or how they are managed by vCenter.
↧