Product Blog

6 Posts authored by: serena Employee

The SolarWinds® product management team is happy to announce the general availability of all 14 products on Orion Platform 2019.4. Every product has new features available in this release. Download now through your Customer Portal and solarwinds.com. By downloading the unified SolarWinds Orion installer from any one of those download sources, you'll be able to install or upgrade your entire Orion environment in a single, streamlined, upgrade session.


 

What's New for Orion Platform 2019.4

 

Updates to the Orion® Platform will provide you with:

  • Deployment flexibility - SolarWinds and Microsoft have partnered to enable the Orion Platform and its modules, including Database Performance Analyzer (DPA), to be deployed from the Azure Marketplace, simplifying and accelerating the process to deploy the platform into an Azure subscription.
  • Support for Azure SQL Database Managed Instance - Deploy the Orion Platform database with support for the latest version of Azure SQL Database.
  • Leverage your Azure subscription to:
    • Host the Orion server
    • Host the Orion database using Azure SQL Database
    • Host the Orion database using Azure SQL Database Managed Instance.
    • Host the Orion database as an Azure VM
  • Orion Maps enhancements - A redesigned Entity Library for quickly identifying what you need, enhancements for bulk administration, the ability to add custom images, and enabling topology relationships to be manually defined without ever leaving the editor.
  • Integration with SolarWinds Service Desk - Improve time-to-resolution via integration with the SolarWinds ITSM solution, enabling service desk tickets to be automatically created from Orion Alerts.
  • Web performance improvements across several Orion Platform modules, including Network Performance Monitor (NPM), NetFlow Traffic Analyzer (NTA), and Network Configuration Manager (NCM).
  • Standardized release numbering for easier compatibility comparison. All products in this release will be versioned 2019.4.

 

What's New for Systems Management Products

 

This release of the systems portfolio expands our capability to monitor additional devices, many of which have been top asks from our customer base. Upgrade to enjoy enhanced Microsoft Active Directory monitoring through domain trust support, simplified REST API monitoring, Hardware Health visibility for Nutanix clusters, support for Dell EMC Data Domain devices, and much more.

 

What's New for Network Management Products

 

This release of the network portfolio adds Device View, Real-Time Charts, Meraki flow support, visibility for Palo Alto policies, Cisco Unified Call Manager support, and more. We've also done a great deal of work to improve overall webpage performance and produce a better user experience.

 

What's Next

 

The SolarWinds product team is constantly looking ahead to build world class monitoring solutions to solve your monitoring woes. Watch and subscribe to What We Are Working On to get an updated view on what's next for the Orion Platform and its modules. Let us know how we're doing and what we can be delivering to keep you ahead of the curve.

serena

Revisiting AppStack™

Posted by serena Employee Aug 23, 2019

After a long tenure working on the Orion® Platform, I’ve recently shifted my responsibilities to fully focus on Server & Application Monitor (SAM). Features designed on the platform and in SAM have eye-opening similarities due to deep integration between SAM, Virtualization Manager (VMAN), Web Performance Monitor (WPM), and other heavy hitters in our systems portfolio. The same tenets of componentization and shareability demanded by the Orion Platform exist in AppStack the way they do for PerfStack or the newest generation of Orion maps.

 

In honor of this revelation and how far our integration story has come since the first introduction of AppStack in 2014, I’d like to revisit this milestone feature and show those new to the SolarWinds systems portfolio the power of what we provide. For those who enjoy nostalgia, revisit the first AppStack post here https://thwack.solarwinds.com/community/solarwinds-community/product-blog/blog/2014/11/03/appstack. Personally, I was taken aback by the amount of change that’s occurred in the UI itself.

 

Welcome to 2014, amirite? (I stole this screenshot from Jeremy's original 2014 post.)

Fast forward to 2019, the look and feel is quite different. Navigate to AppStack through the menu bar, or enjoy the contextual AppStack widget on the details page for an entity.

For those who land on the full AppStack view today, you'll notice we have new entities appearing in the stack with the inclusion of container monitoring.

When we as Product Managers introduce the capability to monitor new entities such as containers, we must first ask if it deserves a place in the AppStack. For containers, this is certainly true, due to their ephemeral nature and clear distinction as a generic entity type. The same can be said for the improvements to Cisco UCS monitoring, where SAM added chassis, blade, and rack server statistics into the AppStack view. However, in the case of VMware vSAN entities, you'll notice their inclusion into AppStack in a subtle approach aligned with customer expectations for hyperconverged infrastructure.

 

In 2019.2 versions of the platform and later, the spotlight workflow is still an effective tool to quickly analyze where the problem might lie along your infrastructure stack.

The subtle difference lies in the changes to node status in the Orion Platform 2019.2 release. With simplified status calculations, and clear contributors detailed in the popovers, it's easier than ever to navigate to where you need to drill in for detailed troubleshooting. 

With additional changes from VMAN 8.4 to add virtual entities as status contributors and the ability to control the status contributors via the Node status contributors page, the AppStack solution becomes even more powerful. Through continued improvement and integration throughout the Orion Platform and the system portfolio, AppStack in 2019 has aged well and can help you navigate the intricacies and quirks of your environment.

Supplementing AppStack capabilities, through the addition of new Orion Maps and PerfStack, you now have a full toolset available to visualize your environment, narrow down the problem, and then troubleshoot the problem in-depth in real time.

 

Now that we've walked through how AppStack has grown over the years, I'd love to hear from you, both new and familiar to AppStack. What was your introduction to AppStack? Was it back in 2014 or the newer versions available today? What would you like to see improved in the future and what would you like to see preserved to keep the heart of AppStack beating strong for the next generation of Systems Management product releases? Put your feature request into Server & Application Monitor Feature Requests  for tracking and community input.

Virtualization Manager (VMAN) 8.4 is now available and can be downloaded from your customer portal. In recent releases, we brought you VMware vSAN monitoring, container support, and better centralized upgrades to your deployment overall.

 

 

VMware Event Monitoring, Correlation, and Alerting

 

As a virtualization admin, it's a primary concern to track the many changes that occur in dynamic and often automated virtualization environments. While many virtualization vendors tout that the simplicity of their solution alleviates the need for admins to worry, I err on the side of caution. With VMware event monitoring, you now have real-time access to alert and correlate VMware's alarms, health checks, events, and tasks to issues in your environment. Ephemeral events such as vMotions are now easily tracked, and if you also have Log Analyzer, you can tag them for future cataloging.

Looking at my VMware Events summary, there are quite a few warning and critical events in the last hour. Filtering down to the warning events to do deeper inspection, I can see four of them are warning me of a failed migration for virtual machine DENCLIENTAFF01v

Clicking on one of these events allows me to drill in to get more context. Clearly, I need to look at the configuration of my vMotion interface.

Clicking "Analyze Logs" allows me to have better filtering and is also where I would configure processing rules to start configuring real-time alerting on these VMware events. Yes, event collection is real-time, and as a result, your alerts configured on these events are also triggered in real-time. If you want to be alerted to host connection changes, or when vMotions are triggered when they aren't supposed to be, you now can be alerted immediately.

 

For those of you who have Log Analyzer, you have even more troubleshooting tools that play very nicely with this VMAN feature. Are you looking to visually see occurrences of this event over time? Easy. Click "Analyze Logs" to navigate to the Log Viewer. Your Log Viewer will differ in that you'll have a visual graph to see how many times this event has occurred over the specified time period. In the example below, I increased the time to two hours, and searched for "vMotion." In addition, I've used the tagging feature to tag all events like this with a "vMotion" tag.

So how do I correlate this to problems? By using PerfStack dashboard.

After troubleshooting your issues, simply save the PerfStack project and put that project on your NOC view for future visibility.

 

Deeper Dives and Other Features

 

For a more in depth look at the VMware events feature check out these documents. Let me know if you have use cases that require real time alerting, monitoring and reporting so we can consider putting them in as OOTB content.

 

For those of you who are curious what we have for those users who do not need VMware event visibility check out these documents for more details:

 

Next on the VMAN Roadmap

 

Don't see what you're looking for here? Check out the WHAT WE'RE WORKING ON FOR VIRTUALIZATION MANAGER (UPDATED NOVEMBER, 2019)  post for what our dedicated team of virtualization nerds and code jockeys are already looking at. If you don't see everything you've been wishing for there, add it to the Virtualization Manager Feature Requests

 

This version of VMAN is compatible with the legacy VMAN 8.1 appliance; however, all the newly available features are only on VMAN on the Orion Platform. If you're using the appliance on your production VMAN installation, I recommend that you consider retiring the appliance at your earliest convenience to reap all the benefits of the new features we are developing for VMAN on Orion. If you cannot retire the appliance for any reason, I'm very interested in your feedback and reasons, and would love to see them listed out in the comments below.

Helpful Links

Network Performance Monitor (NPM) 12.4 and the Orion Platform 2018.4 are now generally available in your customer portal. For those of you subscribing to the updates in What We're Working on for NPM (Updated June 1st, 2018)  you may have noticed a line item called "Centralized Upgrades." This update will give you the first chance to experience Centralized Upgrades on your environment.

 

Great news this upgrade is going to be easier than ever!

 

 

Planning for Your Upgrade to 2018.4

 

Read the release notes and minimum system requirements prior to installation as you may be required to migrate to new server or database infrastructure. For quick reference, I have provided a consolidated list of release notes below.

Note: Customers running Windows Server 2012, 2012 R2, and SQL 2012 will be unable to upgrade to these latest releases prior to migrating to a newer Windows operating system or SQL database version. Check for the recommended Microsoft upgrade path through the upgrade center.

 

See more information about why these infrastructures are deprecated here: Preparing Your Upgrade to Orion Platform 2018.4 and Beyond - Deprecation & Other Important Items

 

SolarWinds strongly recommends that you update to Windows Server 2016 or higher and SQL Server 2016 or higher at your earliest convenience. 

 

 

 

 

 

Refresh your upgrade knowledge with the following upgrade planning references.

 

 

Always back up your database and if possible take a snapshot of your Orion environment.

 

 

Start Your Upgrade on the Main Polling Engine

 

Download any one of the latest release installers to your main polling engine.

 

For the screenshots that follow I'm upgrading my Orion deployment with the following setup:

  • Main Polling Engine is installed with Virtualization Manager (VMAN) 8.3 and will be upgraded to VMAN 8.3.1
    • Utilizes a SQL 2016 database
  • Three scalability engines
    • One Free Additional Polling Engine for VMAN on Windows 2012
    • One Free Additional Polling Engine for VMAN on Windows 2016
    • One HA Backup on Windows 2016

 

My first screen confirms my upgrade path to go from 8.3 to 8.3.1.

  • If I'm out of maintenance for a specific product, I would see indicators here first on the screen. Being out of active maintenance will prevent you from upgrading this installation to the latest, so please pay attention to the messaging here.
  • The SolarWinds installer will upgrade all of the products on this server to the versions of product that are compatible with this version of the Orion Platform for optimal stability. This may mean that you'll be upgrading more than just one product.
  • When in doubt, feel free to run the installer to see the upgrade path provided, so you can plan for your downtime. Cancelling out at the pre-flight check stage will give you all the information needed to plan ahead, without surprises and without changes to your environment.  This information can also be used for your change request before scheduling downtime for your organization.

The second step will run pre-flight checks to see if anything would prevent my upgrade from being successful on the main polling engine.

  • In case there are no blocking, warning, or informational pre-flight checks, we will proceed straight to the next step, accepting the EULA.
    • My main polling engine server and DB meet all infrastructure system requirements for the 2018.4 Orion Platform, so I am not shown any blocking pre-flight checks at this stage.
  • Pre-flight checks can block you from moving forward with your installation
    • You  may need to confirm whether you meet new infrastructure requirements (e.g. NTA 4.2.3 -> 4.4 upgrade) to proceed. Blockers will prevent you from successfully installing or upgrading, so the installer will not allow you to proceed until those issues have been resolved.
    • Warning pre-flight checks give you important information that could affect the functionality of your install after upgrade but will not prevent you from successfully installing or upgrading.
    • Informational pre-flight checks give you helpful troubleshooting information for "what if" scenarios, in case we don't have enough information to determine whether this would be an active issue for your installation.

 

The online installer will start to download all installers needed from the internet

  • SolarWinds recommends that you use the online installer because it will be able to auto-update and download exactly what's needed for the installation. Not only is it more efficient, but it will save you from downloading unnecessary or outdated bits.

 

This screen gives you an overview of next steps. The Configuration wizard will launch next, to allow you to configure database settings and website settings.

In this release, all scalability engines, including Additional Polling Engines, Additional Websites and HA Backup Servers, can be upgraded in parallel manually, using the scalability engine installer. Manual upgrades are still supported, but if you have scalability engines, please try our centralized upgrade workflow to save you time.

 

Follow the configuration wizard steps to completion. If you only have a main polling engine to upgrade, your installation is now complete. Log in to your SolarWinds deployment and enjoy the new features that have been built with care for your use cases.

 

Centralized Upgrades of the Scalability Engines

For those customers who have chosen to scale out their environment using scalability engines, such as Additional Polling Engines, HA Backup Servers or Additional Websites this is the section for you.

 

If you kept the "Launch Orion Web Console" checkbox checked in the final step of the Configuration Wizard, the launched web browser session will navigate you directly to the Updates Available page, where you can continue with the Centralized Upgrade workflow. If you want to open a new web browser session on a different system, you can quickly navigate to where you want to go by following these steps.

 

Launch the web browser and log in.

Navigate to 'My Orion Deployment' from the Settings drop-down.

 

Click to the UPDATES AVAILABLE tab. If this tab is not showing, that means there are no updates available for you to deploy.

Click Start, to begin the process of connecting to your scalability engines.

My environment is not experiencing any issues connecting to my scalability engines.

Bookmark this page Connection problems during an Orion Deployment upgrade - SolarWinds Worldwide, LLC. Help and Support  for future guidance on common "gotcha" scenarios, and how to handle them.

After the contact with scalability engines has been established, pre-flight checks will be run against all scalability engines

Looking at my pre-flight checks you can see that one server PRODMGMT-49 has a blocker that would prevent upgrades from occurring, mainly that it does not meet infrastructure requirements for this version of the Orion Platform.

However, my "Start Upgrade" is enabled. This is because if at least one scalability engine is eligible for upgrade, we will allow you to proceed. Only when none of the scalability engines are eligible will this button be disabled. Pay attention to servers that have blocking pre-flight checks, as you will have to manually upgrade them or move items being monitored via this scalability engine to one that is upgraded.

 

Clicking "Start Upgrade" begins the centralized upgrade process, first by downloading all the necessary bits to all the scalability engines in parallel. Notice how my scalability engine that was on incompatible 2012 infrastructure is not being upgraded.

Grab a coffee as the rest of your installation and configuration happens silently on each of the servers being centrally upgraded.

Oh no, an error occurred. What can you do at this point?

  • Click Retry download after troubleshooting (e.g. did the scalability engine lose connectivity to the main polling engine?)
  • RDP directly into the server using the convenient RDP link that is provided

 

Common scenarios to investigate:

  • Is this scalability engine set up inconsistently from the other servers? For instance, you may have Engineer's Toolset on the Web installed on this server and not on the others.
  • Do some of the installed products have dependencies on .NET 3.5? Engineer's Toolset on the Web has a dependency on .NET 3.5 to be able to upgrade. Ensure that if you have enabled .NET 3.5 and try again.
  • Check the Customer Success Center for more scenarios to help while troubleshooting.

 

In my case, I clicked Retry and was able to get past the issue.

My upgrade is complete! Congratulations on an upgrade well done.

Click Finish to complete your Centralized Upgrade session.

 

Gotchas - What to do with Unreachable Servers

If your server isn't being blocked because of incompatible infrastructure, you have an opportunity to manually upgrade that server in parallel while the rest of your environment is being centrally upgraded.

 

In the installation example captured below, if I were to run the installer on the Additional Website that is currently being upgraded by Centralized Upgrades, I would be blocked from running the installer on that server. However for the listed unreachable Additional Website, I can run that upgrade manually with no problem in parallel.

If you're blocked from proceeding on a manual upgrade, you would see the following. Only until you have finished the Centralized Upgrade process will you be allowed to proceed with a manual upgrade that is blocked in this fashion. For these scenarios, simply navigate to My Orion Deployment and exit out of the deployment wizard flow to cancel the centralized upgrade session.

 

Manual Upgrades

Manual upgrades of your deployment are still supported. If you have only one scalability engine, Centralized Upgrades may not be the fastest way to upgrade. However, if you have more, it is. This upgrade is still beneficial for those considering using manual upgrades for their deployment, and the reason is the installation and configuration wizard process can now be run in parallel. Existing customers have always known that there were some scenarios where you could run the configuration wizard in parallel across servers (e.g. same server type) and some that you could not. It took time and training to understand what scenarios those were. In this release, that limitation is lifted, and all server types can be configured in parallel.

 

There are times where you may need to consider falling back to manual upgrades in combination with your Centralized Upgrade. As an example, take this installation: two have completed, one has the configuration wizard in process.

If the download, installation, or configuration is taking a long time for one of your scalability engines, and you need to see more information that is only available in the client, you may consider canceling out of the Centralized Upgrade session to resume the rest of your upgrade manually. The servers that have been upgraded thus far will remain in a good spot, so you can cancel out with confidence. Proceed with this option carefully, as you will want to ensure that you have upgraded everything by the end of your scheduled downtime.

Check the My Orion Deployment page to ensure that all the servers in your Orion deployment are upgraded.

 

Support

We have all been there, despite all the best intentions and all the preparation in the world, something went wrong. No worries! File a support ticket Submit a Ticket | SolarWinds Customer Portal  and start gathering diagnostics via our new web based and centralized diagnostics.

 

Click to the Diagnostics tab

Select all the servers in your deployment,

and click "Collect Diagnostics."

Sit back and relax as your diagnostics are centrally gathered in preparation for your support call.

 

Customer Experience

 

Early adopters and those who have participated in our release candidates have already begun to enjoy the benefits of centralized upgrades. Check out our THWACK forums for testimonials from customers just like you as they experience the new and improved "Easy Button" upgrade experience. Here's a link to one from one of our very own THWACK MVPs  The "Easy Button" has arrived with the December 2018 install of NAM (and other Solarwinds modules) If you'd like to share your upgrades with me, I'm very interested, and we'd love to see screenshots and your feedback on this new way to upgrade your SolarWinds deployment.

 

More centralized upgrade success - Success with Centralized Upgrades

 

Starting with NPM 12.2, SolarWinds has embarked on a journey to transform your Orion deployment experience with fast and frequent releases of key deployment components. The first step was revamping the legacy installer to the new and improved SolarWinds Orion installer. The installer was able to deploy new or upgrade an entire main poller in one seamless session. The second iteration of the installer released the capability to do the same for your scalability engines. In this release NTA has been updated to utilize a MSSQL database, allowing us to happily say that the SolarWinds Orion installer is truly an All-in-One installer solution for your Orion deployment. For NPM 12.3, we have made tremendous scalability improvements that allow you to utilize even more scalability engines. As a result, your Orion deployment upgrades gain in complexity, so the installer team is providing additional updates to how you can stage your environment for minimal upgrade time.

 

Normal Upgrade Process

 

Using the All-in-One SolarWinds Orion installer, your upgrade process will look like the following.

 

Step one:

 

Review all system requirements, back up your database and if possible snapshot the Orion deployment. This will be especially important in this release, as the NTA Flow Storage database requirements have changed. Note: Flow Storage database refers to the database instance that stores NTA collected flow data. In previous versions this was utilizing a Fastbit database, but in this release has been updated to use MSSQL with a minimum version of 2016. An Orion database is the primary database that stores all polled data from NPM and other Orion products.

 

Step two:

 

Download the NPM 12.3 installer, selecting either the online or the offline variant according to your system requirements. Note: the SolarWinds Orion installer is

 

Step three:

 

Run the installer on your main poller and upgrade it to completion. If you have any other Orion product modules installed, the installer will upgrade this instance to the latest versions of those modules at the same time to maintain compatibility with the new Orion Platform 2018.2. If there are new database instances to be configured, that will be handled during the Configuration Wizard stage of the main poller upgrade. This release of the installer has a new type of preflight check that requires confirmation from you before proceeding. In the example below, is one for the NTA upgrade. Click for details to see the confirmation dialog and select yes or no.

 

Configuration Wizard step for NTA:

 

Step four:

 

If you don’t have any scalability engines, e.g Additional Polling Engines, Additional Websites or HA Backups you’re ready to explore all of the new features available in this version!

 

Scalability Engines

 

For those environments utilizing scalability engines or for those who are looking to try them out, this section will guide you through the process of deployment. Even if you have not utilized scalability engines previously, trying them out to test the scale improvements is incredibly easy. Like every SolarWinds Orion product, they are available for an unlimited 30-day free evaluation.

 

Deploying a fresh scalability engine is handled with the same installer that you downloaded for the main poller.

 

1. Copy the installer to your intended server and Click to “Run as Administrator”

 

Note: If you downloaded the offline installer, which is about 2 GB, the download process to your server can take some time and does not currently stage the scalability engine for faster upgrade. In the future, this is something we’d like to improve but is not an available feature for this release.  if you’d like to shorten the initial download of installer file to server, you can always use the online installer to set up your scalability engine. This installer file is about 40 MB so the download of installer file time to the server is much shorter. This will still meet offline requirements because when selecting the “Add a Scalability Engine” option, it will choose to download from the main poller to maintain version compatibility and does not require internet access. As always, the 40 MB scalability engines installer is also available for download from the All Settings -> Polling Engines page.

 

2. Select the “Add a Scalability Engine” option.

 

first screen of installer

 

3. Similar to the main poller upgrade process, at this point system checks that are specific to scalability engines will be run.

 

Note: Anything tagged as a blocker may need confirmation or action from you before proceeding.  If this is the case, address those issues and run the installer again. Things that are tagged as a warning or informational message are simply for your awareness and will not prevent your installation from proceeding.

 

4. Select the type of scalability engine that you are looking to deploy, and then complete the steps in the wizard to finish your installation per your normal process.

 

 

Upgrading a scalability engine, is also handled through the same installer. However, this is where you have an opportunity to utilize our staging feature.

Note: If you were to proceed with your normal practice of putting the scalability engines installer on each server you need to upgrade, and then manually upgrading, that process will work perfectly well with no changes. Please read through the “Staging Your Environment for your Scalability Engines Upgrade” section below to see the alternative workflow that allows you to stage your environment.

 

Staging Your Environment for Your Scalability Engines Upgrade

 

For customers with more than a handful of scalability engines or with some distributed over WAN links, we noticed that they were occasionally experiencing extremely high download times from their main poller to their scalability engines. In addition, there was no centralized area where one could see the upgraded state of the scalability engines. Navigate to "All Settings", and click "High Availability Deployment Summary" and you will see the foundational pieces for an Orion deployment view.

 

The Servers tab contains the original High Availability Deployment Summary content, and is where you can continue to set up additional HA pools and HA environment.

 

Check out the new Deployment Health tab! You may not have heard of our Active Diagnostics tool, but it comes prepackaged with every install of the Orion Platform with test suites designed to test for our most common support issues. We've brought that in depth knowledge to your web console in the new Deployment Health view. With nightly run tests across your Orion Deployment, every time you come to this page you will see if there are any issues that could be a factor in the performance of Orion or your upgrades.

 

You are able to refresh a check if you're working on an issue and wish to see an updated test result. If there are tests that you don't want to address, silence them to hide the results from the web console. Click on the caret to the right and you'll be able to see more details and a link to a KB article that will give you remediation advice.

 

On the Updates tab is where you will be able to stage your scalability engines.

 

The first page of the wizard will let you know if there are updates that are available to be installed on your scalability engines. At this point you've upgraded your main poller, so there are definitely updates available!  Click "Start" to get started!

 

The second page is where we are testing the connection to each of the scalability engines. If we are able to determine the status of these engines, we'll give you the green light to proceed to the next step. Common issues that could prevent this from being successful could be that the SolarWinds Administration Service has not been updated to the correct version or is not up and running at this point. Click "Start Preflight Checks" to proceed.

 

Similar to the Deployment Health tab, these are running preflight checks across your Orion Deployment. You'll be able to see all of the same preflight checks that were available through the installer client, except centralized to one view. If there are blockers present on this screen, you can still proceed in this flow if at least one scalability engine is ready to go, but please note down those scalability engines with blockers. You will need to address those blockers before an upgrade can occur on those servers. Click "Start download" to start the staging process.

 

 

 

At this point, we are starting the download process of every msi needed to upgrade your scalability engines. In this example, I'm only staging one scalability engine, but if you  have multiple, you can see the benefits in time savings right away! All of the downloads will be triggered in parallel.

Sit back and relax as we stage your environment for you. You can even open up RDP sessions to those servers with one click from this page.

 

When everything has finished downloading, we will let you know which servers are ready to install. Click on the "RDP' icon to open your RDP session to the server.

 

On your desktop, you should see the SolarWinds scalability engines installer waiting for you to click on and finish the upgrade.

 

Visually you will run through the same steps that you normally would in clicking through the installer wizard. However, when you actually get to the installation part, you'll notice that there is no download appears in the progress bar. Finish your upgrade and move on to the next!

 

I hope you enjoy this update to how you can upgrade your Orion Deployment. I'm always looking for feedback on how we make this as streamlined as possible for you.

Starting with VMAN 8.0, and continuing with 8.1  we've streamlined how you deploy and use VMAN.  Virtualization Manager 8.2 , the latest edition of these efforts, is now available on your Customer Portal.

 

One of the biggest pain points that surfaced over the last 2 releases was that the process for adding virtualization nodes to be monitored was not intuitive. This is solved with a new simplified workflow!

 

Whether choosing to add a Node or setting up a Discovery job, we've updated those entry points to direct you to the new, separate workflow.

 

Add a Node - Select VMware vCenter or Hyper-V devices
Network Discovery - Add VMware vCenter or Hyper-V devices
All Settings -  Add VMware vCenter or Hyper-V devices

 

Once you click on any of those entry points you'll be able to get started monitoring your environment with a few simple clicks.

 

Add a Virtual Object for Monitoring
See the thresholds that apply to your virtualization manager entities
Click Finish and you're successfully on your way to monitoring your virtualization environment

 

If you identified any thresholds that you'd like to tweak, simply navigate to All Settings -> Virtualization Settings to update your thresholds. Within a few clicks, you're ready to take advantage of capacity planning, recommendations and much more!

 

Get Started with Documentation

VMAN 8.2 Release Notes

VMAN 8.2 Getting Started Guide

VMAN 8.2 Administrator Guide

VMAN 8.2 Deployment Sizing Guide

Filter Blog

By date: By tag:

SolarWinds uses cookies on its websites to make your online experience easier and better. By using our website, you consent to our use of cookies. For more information on cookies, see our cookie policy.