Skip navigation

The VMAN 7.0 RC 2 install bits can now be downloaded from your Customer Portal.  Please note that the Release Candidates are fully tested and supported releases and are suitable to be run in production. 7.0 RC2 can be run as an upgrade from 7.0 RC1, as well as from the 6.3 installs. If you have problems with the RC, you can file a ticket with Support just as you would for any other Generally Available (GA) version.  To familiarize yourself with new features in 7.0 you can use Welcome to the Virtualization Manager 7.0 Beta 1 as a reference.

 

VMAN RC2 Button.png

 

The VMAN team is excited about this release and can't wait to receive your feedback in the Virtualization Manager Release Candidate forum. Make sure to review all documentation prior to the upgrade which can be found on the VMAN 7.0 Support page.

 

 

New features and improvements

Read this section for descriptions of the new features and improvements VMAN and VIM offer in this release.

 

Recommendations

When VMAN identifies a way to optimize VM resources for active and potential issues, it makes a recommendation for one click optimization. Recommendations display in the Orion Web Console with a description for optimizing your network, and provides a series of steps you can apply immediately with a button click or schedule at a later time.

  • Balance the virtual environment for optimal performance. You can spread load over hosts, which optimizes the performance for all virtual machines.
  • Optimize capacity. Virtualization Manager predicts when you will run out of resources on virtualization entities, so you can plan in advance when you have to assign new resources.
  • Predict possible future performance and capacity issues based on past trends.

 

Web-based License Manager

Easily add, activate, and manage Orion product licenses through the web-based License Manager. Accessing the License Manager on your main polling engine, you can monitor and update full product and evaluation licenses for your main poller, additional pollers, additional web servers, stackable pollers, and high availability pools all through one page. The License Manager also provides automatic online and offline modes for managing licenses. Add and manage evaluations with ease, including HA.

text-document.png Read more about these changes.

 

Other improvements

Various performance improvements and security fixes

How to upgrade

Use the following resources for planning and upgrading:

Fixed issues

Virtualization Manager 7.0 and VIM 7.0 fix the following issues.

 

CASE NUMBER

DESCRIPTION

1037297

NPM not showing CUP and Memory usage for some ESXi servers

1013905

Asset tree is not loading properly

999345

List of Virtual Machines on a host not displaying the OS version for Windows 10

953038

657558

Collector Data Processor keeps crashing

951495

VCenter data is inaccurate

951394

Additional Orion Web Server VM reports do not run

908177

VM to node mapping is not using MAC if integration is enabled

916806

sinpsyesx004.intlsos.com not returning any data - duplicated datastores causing data processing to fail

898072

VCenter status unknown on the Orion Web Console

890835

IVIM schema error on APE SWIS log

885008

Polling Engine Details page shows absolute value of jobs count instead of percent

825684

Issues with vShield Manager and VMs that are natted

820300

Orion Web Server does not display

997655

Unable to start collection jobs

989236

CPU overallocation

1001589

VMAN on-demand report displaying incorrect or old data

966359

Integration issue with Datastore and VMAN

975063

VIM appliance not passing data to the Orion server

978665

SSH Server CBC Mode Ciphers enabled

978638

Vcenter status unable to poll

967710

Invalid depletion data shown on Datastore dashboard for VMAN

968708

Vcenter data not being displayed in the Orion Web Console

945034

SSL certificate changes back to default after upgrade

941086

False alerts regarding VM reboots

934585

VMAN application unable to load because postgres service will not start

918211

VMAN crashes when a secondary collector is used

920658

Host rebooting during configuration collection

913169

Blue screen on host when running the configuration wizard, when collection has started

910234

No data displayed in the "cluster.cpuMHzPeak.day" column

896552

Trend widget does not populate when "multi-trend" mode is enabled

893378

VMAN stops working after upgrade to vSphere 6.0

891270

Query does not return the correct number of VMs when searching past 9 days

884311

Intermittent collection

873270

Mast applicance shows ActiveMQ transport "Usage Manager Memory Limit is full errors"

856868

Fatal error occurred during collection

853303

VMAN stopped polling and displaying data

422089

Virtual Machine not appearing in VMAN list

 

 

Download VMAN from the Release Candidate section of your Customer Portal.

 

VMAN RC2 Button.png

We have reached the Release Candidate (RC) status for Web Help Desk (WHD) 12.5. RC1 is the last step before general availability and is a chance for existing customers to get the newest functionality before it is available to everyone else.

 

 

Web Help Desk 12.5 includes the following enhancements:

  • Dashboard interface – New and improved dashboard user interface and functionality

WHD_125_Dashboard.jpg

 

 

  • Technician interface - Manage ticket approvals from the technician interface (Thank you to those who elevated this Feature Request on THWACK!)

 

WHD_125_Tech_Approval.jpg

 

 

  • Bulk action capabilities – Use bulk actions to link parent tickets
  • Fixes for customer issues and security vulnerabilities

Other Recent Improvements:

Recently added in Web Help Desk Service Release version 12.4.2 includes functionality that allows multiple FAQs to be added to a request type. For those who helped vote this feature into existence, we thank you. You can also find this feature included in the latest version of this product.

 

WHD_1242_FAQ.png

 

 

Download Web Help Desk 12.5 in the Release Candidate section of your Customer Portal.

RC builds are provided as a special privilege to customers on active maintenance in advance of the formal release. These are used to get customer feedback in production environments, and are fully supported. If you have any questions, I encourage you to engage the Web Help Desk RC forum on THWACK.

Something we hear quite often is "how can I build custom SLA report in Orion". Everybody who is a bit familiar with Orion knows our web-reporting tools which is the right place to start, however sometimes it requires more than a click & point tweak in reporting.

(we've made this article official: SLA Reports )

 

I'll use this SLA request example: WAN SLA availability by time zone & 7x24 in order to demonstrate one of the ways how to get there.

 

What you'd need to accomplish this?

  1. NPM (or any other SolarWinds product)
  2. Orion SDK - Orion SDK Information
  3. At least one hour data history for the devices which should appear in your SLA report. In my case, Nodes and business hours.
  4. 30 minutes of your time

 

What will be the result:

Our goal is to create daily custom SLA report for Node availability (in %) which shows the device availability only for our business hours - in our case 7AM - 6PM

The result may look like this:

Node             SLA Availability          SLA Hours         

New York      92.33                         7am-6pm   

 

Let's get started:

First problem we need to solve is how to "tell" system what are our report business hours. This seems to be a best fit for Orion custom properties. Let's create two custom properties: 1) time_from 2)time_to and assign the values to all nodes.

 

Go "All Settings" -> "Manage Custom Properties" -> "Add Custom Property" -> Select Nodes and click "next" -> specify property name "time_from" and apply on "reports" -> Select all nodes to assign a property.

 

Now we need to assign the start rush our time in a bulk operation to all nodes. Select "view/edit values" and set "7" to the field:

 

 

Ok, now go and repeat all steps above for "time_to" and value "18" (6PM).

 

Ready? Good. We have data ready and now it's time to data-mining. For that purpose we're going to use SolarWidns proprietary business logic and data layer represented by SolarWinds Information Service - SWIS. Which has simimar syntax to SQL but gives you much more power to get properties via "." operator (no need to know entire database table structures). In order to tune the final query we will use SWQL Studio tool which is part of SDK you already installed into ProgramFolder (x86)\Orion SDK\

 

Run the studio and enter the FDQN name of your Orion server (or IP Address), Administrator credentials and from drop-down select "Orion (v3)" which defines version 3 of SWIS.

If the connect is successful you'll see the SWIS database structure on the left hand side:

And again, this is not equal to your SQL server structure, this is the database structure Orion primarily use for viewing data and it's strongly recommended to use over direct SQL access because it provides data consistency, performance optimization and it will guarantee your reports to be working even if database structure is changed during product updates.

 

Prepare the SWQL query

Not the fun begins and we need to define SWQL query for our data set.

 

Here is the one I use to get the data for my SLA report:

 

select n.Caption, sub_query.sla_day, sub_query.sla_availability, n.CustomProperties.time_from, n.CustomProperties.time_to FROM

(

   SELECT avg(Availability) as sla_availability, datetrunc('day',datetime) as sla_day, r.NodeID

   FROM Orion.ResponseTime r

   where hour(datetime) >= r.Node.customproperties.time_from and hour(datetime)<= r.Node.customproperties.time_to

    group by datetrunc('day',datetime), r.NodeID

) as sub_query

 

inner join Orion.Nodes n ON n.NodeID=sub_query.NodeID

 

For those who are bit familiar with any SQL type of language it should look familiar. Here is what I've done

 

First I need to compute average data from Orion.ResponseTime table and I need to apply rush hour limitation defined by custom properties from above. This represents inner query. "Datetrunc" function is able to take a day, hour or month from entire date. I need a day so I can guarantee avaliability for each node is computed for only a given day and then for rush hours time interval. It's easy compare condition.

 

Second I need to return the results of average node availability for time-segment and apply a table formatting so I will see "Node Caption", day/date, availability and time_from and time_to defining SLA business rush hours.

 

And the result?

Great, so we can tune our query and add/remove columns or apply additional sorting.

 

Publish and view in Orion reporting.

Time to take our work and make it available for all Orion users. To do so, go to Orion web console -> reports -> manger reports -> create new report. And we will create new CustomTable based report.

Follow the steps below to accomplish your task where we enter our SWQL query, select the columns for report and apply sorting by date:

 

1)

2)

3)

4)

5)

6)

7)

8) voila - here comes the final report

 

We're done. Till now our new report "Node SLA report - business hours" will be available in the list of reports in Orion and you can also schedule the report on daily/weekly basis as you need.

Please be aware our maintenance rolls-off the finest detailed data each month (30 days) and if you run the report after that period you won't be able to see full granular details beyond 30 days time border.

 

I hope you find this useful and it inspires you to experiment more with SWQL and SWQL studio in order to build the reports you're looking for. SWQL studio will also help you to browse our data structures so you can learn by walking and master your custom report skills in Orion.

Filter Blog

By date: By tag: