1 2 3 4 Previous Next

Product Blog

49 Posts authored by: cvachovecj

We have reached the Release Candidate (RC) status for Network Configuration Manager 7.3. RC 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.

 

Here is the content of this RC version:

  • NCM and NPM databases become merged
    Streamlined node management: Using a single database enables NCM to manage its nodes, adding and removing them, on the Orion Platform HOME page.
    Optimized reading and writing: Merging the NCM into the Orion Platform database, and using a single database schema, facilitates the NCM software’s use of SQL statements to efficiently manage the insertion, retrieval, and modification of data.
    Account limitations applied to jobs: Using a single database enables NCM to apply Orion Platform account limitations in creating and managing jobs.
    Subviews: Using a single database schema allows NCM to efficiently support subviews.
  • Enhanced Configuration Management
    This version introduces a much more flexible user interface for doing your configuration management work.
  • Enhanced EOL/EOS data and data management.
    NCM offers additional EOL/EOS inofrmation and higher granularity for tracking the reliability of the data.
  • Enhanced Web Console
    • Admins can clear all transfers for all users from the Transfer Status resource.
    • Jobs Summary sorts by any column in the table.
    • Users can preview the list of nodes assigned to a job when the criterion is "Dynamic".
    • NCM uses SWISv3 to manage the web console’s database transactions.


More details and screenshots can be found in Beta2 for Network Configuration Manager v7.3 is Available!

 

RC builds are made available to existing customers prior to 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 leverage the NCM RC forum.


You will find the latest version on your customer portal in the Release Candidate section.

We are pleased to announce the general availability of Kiwi CatTools v3.10.

 

This version includes the following enhancements:

  • Variations added to the following device types: Cisco Router.General, Cisco.Switch.IOS.
  • Variations added to the following device types: Dell.Switch.CLI, HP.Switch.2500, and Enterasys.SecureStack.
  • Monthly Scheduling options on Activites.
  • Support for Cisco Small Business devices.
  • Support for HP Devices 12000, 12500, and 3500.
  • New option to ignore a block of text from comparison during Device Running Config activity.
  • Support for Windows Server 2012 R2
  • Newest SolarWinds licensing framework adopted

 

Kiwi CatTools v3.10 is available for download in your customer portal for those customers under current Kiwi CatTools maintenance.

 

You can view the full set of release notes, including problems fixed here.

 

Enjoy Kiwi CatTools 3.10!

Regular expressions are used in many places in the Network Configuration Manager (NCM). Because of technical and historical reasons, NCM uses a few different flavors of regular expressions for different functionality. In this post, I would like to explain the differences and provide references to more detailed documentation.

 

What Are Regular Expressions

Informally, a regular expression is a search pattern (sequence of characters) used mainly for string pattern matching and string finding. The term originated in formal language theory where regular expressions are exactly defined and related to other concepts of the same power (regular languages, finite automata, etc.). Although the current tools still use the term 'regular expression' (regex), it would be more precise to call them something like 'search patterns'; the expressive power of the search engine is, in fact, often much higher than that of the original regular expressions. (Many modern tools support patterns that are even more powerful than context-free languages.).

 

Regular Expressions for Comparison Criteria

When you compare two config files for changes, you may want to ignore some of them. (Examples: certificates, last modification time.) Defining comparison criteria enables you to filter out of comparison results lines that you do not need NCM to evaluate; this saves both processing time and, more importantly, makes the review of compared files easier.

 

Comparison-Criteria.PNG

 

The regular expressions you create and enable in the settings (Settings -> NCM Settings -> Comparison Criteria) are used throughout NCM — for example, in performing scheduled jobs — wherever the software needs to compare config files as part of its work. A few criteria that are often used come with NCM out of the box; you can also define your own. The lines you typically want to ignore are often informational comments like when was the configuration changed last.

 

NCM uses the well-known diff tool (from the GNU Diffutils package) for config file comparisons. As you can find in Diffutils documentation, diff uses grep-style regular expressions; then it's not difficult to learn from GNU grep manual that the default regex flavour for grep are basic regular expressions (BRE). Please note that the diff program works line by line -- you cannot define a regex that would match multiple lines.

 

Let's review some implications of BRE being the regex kind used in NCM comparison criteria.

  • Meta-characters ‘?’, ‘+’, ‘{’, ‘|’, ‘(’, and ‘)’ lose their special meaning; you must use the backslashed versions ‘\?’, ‘\+’, ‘\{’, ‘\|’, ‘\(’, and ‘\)’. In other words, you will use backslashes to give certain characters special meaning, while many other regex implementations use backslashes to take the special meaning away.
  • You have to use '%%' in the pattern when you want to match '%'.

 

More details on BRE syntax can be found e.g. on this page.

 

Device Templates

The parameter RegEx may be added to certain commands to recognize the string that is received when the command is complete. For example, if the command is complete when the device responds with System Characteristic, then you must add the following attribute to the command: RegEx="System Characteristic".

 

Another example: If you login on a device and must switch user context to execute a command, resulting in a different command prompt, use the following example to guide you when switching context and recognizing the new command prompt:

<Command Name=”Reset” Value=”appropriateSwitchContextCommands” RegEx=”newPrompt”/>

(You should also specify that the template logic should run in CLI mode: <Command Name=”MenuBased” Value=”false”/>)

 

NCM uses the Microsoft VBScript Regular Expression 5.5 engine to parse the value of the RegEx parameter. This engine implements Perl-style regular expressions with some limitations that you will probably never notice. Please see the details on this page.

 

Using Regular Expressions for Compliance Checks

Policy reports help ensure device configurations conform to both internal business practices and federal regulations, such as Sarbanes-Oxley Act (SOX), Health Insurance Portability and Accountability (HIPAA), and Computer Inventory of Survey Plans (CISP). Policy reports scan configuration files and report any discovered rule violations. For example, a rule requires configurations not to include the read-only community string public. You can run a report on your configuration files, and then display any configurations that violate the rule.

 

If you want to search the device config for a text block, or by a regular expression, you should use the Advanced Config Search. Compliance checks use the Microsoft .NET Framework regex engine. The syntax is described in Appendix B of the NCM Administrator Guide (http://www.solarwinds.com/documentation/orionNCM/docs/orionNCMAdministratorGuide.pdf) and also in Regular Expression Language - Quick Reference and Using Regular Expressions with .NET - C# and Visual Basic.

 

A Basic Example

By Tim Nelson.

When you create an advanced rule with multiple patterns, it simply takes the true/false of the patterns and then performs an AND operator on them to see if any are violated based on the overall criteria, not the individual rule criteria. Second, you can use parentheses to make rules inclusive of each other. This is needed when you want conditional statements with dependencies. Think of it as a creative way around if-then statements. So to explain this in better detail let’s cover what will and will not match in a policy.

 

If you create an advanced rule and you want to do a conditional based on bandwidth, you can say the following (keep in mind you should test ALL rules with the single regex you want to match before creating a complex multi-line rule, or use a regex tester):

 

       Must contain “string”: bandwidth 1536

and    Must not contain “regex”: class ipp1[^\r\n]

or     Must not containt “string”: bandwidth 1536

 

In order for this to actually work the top two rules must be contained within parentheses to make them inclusive of each other, i.e. one requires the other. What we are actually doing with the middle pattern is matching anything BUT “class ipp1\r” or “class ipp1\n” which is why we used, Must not contain. Lastly, all of this is wrapped within a container of “Must not contain” for rule violation, this is what actually decides if the rule is violated or not.

 

Policy-Create-Rule.PNG

 

What you will notice when this violates is that the “bandwidth 1536” is matched within the config, because you put “must contain” and it matched, NCM will add a plus sign where ever there is a pattern match. You must keep this in mind as you write rules, as without being the creator of the rule, this can become difficult to parse through.

 

NCM will show the first line on a multi-line match as the violation, so for end-user readability we can create rules that identify the exact line in error and therefore have more granular reporting. You should keep in mind that if your standards change in your network environment, you will have to be able to update these rules. So it is best to fully document your logic for every advanced rule you create.

We have completed another bulk of the development effort and are now focused on testing the latest release of Network Configuration Manager (NCM); We have Beta2 for NCM v7.3 available. This is your chance to install the latest version and provide feedback on the new features and fixes. Providing feedback during the beta is the best way to ensure that your feedback will be incorporated in to the release. To participate, simply fill out this survey and you will be sent the download links for the Beta. Remember, Betas cannot be installed in production and you cannot upgrade the Beta to any other future versions.

 

The following enhancement have been added to NCM so far:

  • NCM and NPM databases merged
    • Optimized DB schema
    • Account limitations are applied to NCM jobs.
    • Core node management page is used to add/remove devices from NCM.
    • In the discovery wizard, users can choose whether to import newly discovered nodes into NCM.
    • Node Sync is gone!
    • Subviews are fully supported.
  • A completely new version of the Configuration Management page
  • EoL/EoS info on (NCM) node details page
  • Admins can now clear all transfers for all users from the Transfer Status page in the Web UI.
  • Limit policy reports for individual accounts
  • Jobs Summary table can be sorted according to any column.
  • NCM supports SWISv3 now.

 

Volunteers Wanted!

Before I describe all the great new improvements in details, I would like to ask you to help us with the database migration tuning. We would like to test the database merge procedure and collect statistics from as many real environments as possible. We can offer the following:

  • Detailed instructions on the procedure (Database Migration Assistance).
  • Assistance from NCM engineering team.
  • Extra portion of thwack points (on top of the usual amount + badge for Beta testers).
  • Good feeling that you helped improve the product .

 

Benefits of the Merged Databases

The merge of NCM and NPM databases enable NCM users to take advantage of certain features of the Orion Platform (Core) that were not possible to use before.

 

Improved Node Management

As there is no concept of "NCM Node" anymore, "Licensed by NCM" has become just a flag for Orion nodes. What does it mean? You can manage all NCM properties using the Core none management infrastructure:

 

Node-Management.png

 

Node-Properties.png

 

Improved Node Details

The merged DB made it possible to use sub-views -- you can easily review NCM node details next to information from other Orion modules.

 

Node-Details.png

 

New Configuration Management UI

This is a great improvement in usability of the NCM Web UI in this release. Unlike the old UI, the new one is much more node-centric to make the workflows much smoother: First you select the devices and then perform an action. The new UI enables you to accomplish a chain of tasks efficiently as you can work with the same set of nodes repeatedly.

  • You can group your devices by up to three parameters.
  • The node selection is persistant; even if you switch to another group of nodes or another page, your selection is preserved.

 

New-Config-UI.PNG

The engineering effort on Kiwi CatTools v3.10 Release Candidate has been completed. RC 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.

You will find the latest version on your customer portal in the Release Candidate section.

 

Here is the content of this RC version:

  • Support for scheduling activities on a monthly basis
  • Support Cisco® Small Business devices
  • Improved support for HP® switches
  • Enhanced possibilities for ignoring text in device configuration
  • Newest version of SolarWinds® licensing framework adopted
  • Fixed problem with Connect Via feature when both target and media devices use variations
  • Various updates of device templates
  • Bug fixes

 

RC builds are made available to existing customers prior to the formal release. These are used to get customer feedback in production environments and are fully supported.

We have completed another bulk of the development effort and are now focused on testing the latest release of Network Configuration Manager (NCM); We have Beta2 for NCM v7.3 available. This is your chance to install the latest version and provide feedback on the new features and fixes. Providing feedback during the beta is the best way to ensure that your feedback will be incorporated in to the release. To participate, simply fill out this survey and you will be sent the download links for the Beta. Remember, Betas cannot be installed in production and you cannot upgrade the Beta to any other future versions.

 

The following enhancement have been added to NCM so far:

  • NCM and NPM databases merged
    • Optimized DB schema
    • Account limitations are applied to NCM jobs.
    • Core node management page is used to add/remove devices from NCM.
    • In the discovery wizard, users can choose whether to import newly discovered nodes into NCM.
    • Node Sync is gone!
    • Subviews are fully supported.
  • A completely new version of the Configuration Management page
  • EoL/EoS info on (NCM) node details page
  • Admins can now clear all transfers for all users from the Transfer Status page in the Web UI.
  • Limit policy reports for individual accounts
  • Jobs Summary table can be sorted according to any column.
  • NCM supports SWISv3 now.

 

Benefits of the Merged Databases

The merge of NCM and NPM databases enable NCM users to take advantage of certain features of the Orion Platform (Core) that were not possible to use before.

 

Improved Node Management

As there is no concept of "NCM Node" anymore, "Licensed by NCM" has become just a flag for Orion nodes. What does it mean? You can manage all NCM properties using the Core none management infrastructure:

 

Node-Management.png

 

Node-Properties.png

 

Improved Node Details

The merged DB made it possible to use sub-views -- you can easily review NCM node details next to information from other Orion modules.

 

Node-Details.png

 

New Configuration Management UI

This is a great improvement in usability of the NCM Web UI in this release. Unlike the old UI, the new one is much more node-centric to make the workflows much smoother: First you select the devices and then perform an action. The new UI enables you to accomplish a chain of tasks efficiently as you can work with the same set of nodes repeatedly.

  • You can group your devices by up to three parameters.
  • The node selection is persistant; even if you switch to another group of nodes or another page, your selection is preserved.

 

New-Config-UI.PNG

We have completed the bulk of the development effort and are now focused on testing the latest release of Kiwi CatTools. CatTools v3.10 has reached Beta status. This is your chance to install the latest version and provide feedback on the new features and fixes. Providing feedback during the beta is the best way to ensure that your feedback will be incorporated in to the release. To participate, simply fill out this survey and you will be sent the download links for the Beta. Remember, Betas cannot be installed in production and you cannot upgrade the Beta to any other future versions.

 

The following enhancement have been added to CatTools so far:

  • Support for scheduling activities on a monthly basis
  • Support Cisco® Small Business devices
  • Improved support for HP® switches
  • Enhanced possibilities for ignoring text in device configuration
  • Newest version of SolarWinds® licensing framework adopted
  • Fixed problem with Connect Via feature when both target and media devices use variations
  • Various updates of device templates
  • Bug fixes

To receive updates on the Kiwi Syslog roadmap, JOIN thwack and BOOKMARK this page.


LAST UPDATED March 2015

 

We are just coming off the latest Service Release of Kiwi Syslog in which we added support for Windows 2012 R2 and the development team is already hard at work on the next version and I am pretty excited about some of the things we have coming.  Below is a highlight of some of these items in the pipeline.

  • IPv6 Support
    • The ability to receive not only IPv4 messages, but also IPv6 as well.
  • Enhanced SNMP Support
    • SNMPv3 Support
      • We already support the ability to both receive and send SNMPv2 traps, this will also add SNMPv3 support as well
    • Allowing trap "varbind" elements in output
      • Originally suggested by our own head geek adatole when he was a customer, this is native supporting of the parsing of incoming trap data into "varbind" elements so that these varbinds can be used in output options (send syslog, email, log to file, etc
    • Enhanced SNMP Trap Forwarding
      • Similar to how we do with Syslog today, allowing you to retain the actual IP and trap message data from the Kiwi server
  • Enhanced Email Reports
    • Better reporting around system and message receiving statistics
  • Enhanced Web Console User Access
    • Removing the existing hard limitation of only 5 users accounts in the web console

 

Disclaimer: Comments given in this forum should not be interpreted as a commitment that SolarWinds will deliver any specific feature in any particular time frame. All discussions of future plans or product roadmaps are based on the product teams intentions, but those plans can change at any time.

To receive updates on the Kiwi CatTools roadmap, JOIN thwack and BOOKMARK this page.

 

The Kiwi team is currently focused on new feature work for Syslog currently and once completed will work on the next release of Cattools.  Any serious bugs or other issues, we will release updates as required.

 

Disclaimer:  Comments given in this forum should not be interpreted as a commitment that SolarWinds will deliver any specific feature in any particular time frame. All discussions of future plans or product roadmaps are based on the product teams intentions, but those plans can change at any time.

To receive updates on the UDT roadmap, JOIN thwack and BOOKMARK this page.

 

After the release of UDT 3.0 and 3.0.1, we have been working on some fixes and also planning the content of the next release. During this time, we would like to give you the possibility to vote on the ideas we are exploring:

 

 

Disclaimer: Comments given in this forum should not be interpreted as a commitment that SolarWinds will deliver any specific feature in any particular time frame. All discussions of future plans or product roadmaps are based on the product teams intentions, but those plans can change at any time.

To receive updates on the NCM roadmap, JOIN thwack and BOOKMARK this page.

 

After the release of NCM v7.2, we have been working on the next release. Here is our "hot list" of things we are currently working on. Your comments, feedback and specially participation in Beta releases are more than welcomed.

  • Merge NCM and NPM databases
    • Optimize the DB schema.

    • Account limitations must be applied to NCM jobs.

    • Use Core node management page to add/remove devices from NCM.

    • In the discovery wizard, allow users to choose whether to import newly discovered nodes into NCM.

    • The database connection settings will be the same for NCM and Core/NPM (e.g. password etc.).

  • Improve th EoL/EoS feature:
    • Improve matching reliability for EoL/EoS.
    • Include more information in EoL/EoS data. (Candidates: End of Software Maintenance, Replacement Part Number)
  • Create a new version of the configuration management page.
  • Move config snippets from Win32 to the Web UI.
  • Enhance the flexibility of the device templates so that more devices can be supported by NCM.
  • Move to SWISv3.
  • Support for Windows Server 2012 R2.
  • Various small fixes and enhancements including but not limited to:
    • Retrieve OS version from IBM BNT switches.

 

Disclaimer: Comments given in this forum should not be interpreted as a commitment that SolarWinds will deliver any specific feature in any particular time frame. All discussions of future plans or product roadmaps are based on the product teams intentions, but those plans can change at any time.

We are pleased to announce the general availability of Kiwi Syslog v9.4.

 

This version includes the following enhancements:

  • New UltiDev Web Server implementation.
  • Active Directory authentication for web access.
  • Support for SSL (https) support for Web Access
  • Alerting for Message Queue Monitor based on defined thresholds.

 

Kiwi Syslog v9.4 is available for download in your customer portal for those customers under current Kiwi Syslog maintenance.

 

You can view the full set of release notes, including problems fixed here.

 

Enjoy Kiwi Syslog 9.4!

cvachovecj

UDT Whitelisting FAQ

Posted by cvachovecj Aug 30, 2013

Now with version 3.0 of SolarWinds User Device Tracker (UDT) you can define a set of rules to determine if a network device belongs on your white list. If so, the device appears in UDT resources list as a safe device. Devices connected to your network that are not on the white list will appear in the Rogue Devices resource list and an alert will be automatically generated for each of them. You can also define a set of rules that determine if a network device should be ignored by UDT. If so, UDT discards all related data. This is handy for HSRP and VRRP MAC addresses.

 

Although the purpose of whitelisting seems crystal clear at first, you quickly realize that its possibilities extend far beyond 'a list of devices'. This is certainly a big feature, so let’s talk about some of the common questions you may have when getting familiar with this new functionality.

 

What is the Default Setting?

By default we whitelist everything. Therefore, when you install / upgrade to UDT 3.0.x, the white list contains three rules: Any hostname, Any IP address, and Any MAC address. These rules mark any connected endpoint as safe, thus preventing your new UDT 3 system from being flooded by rogue device alerts. When you want to actually use the white list, you have to disable some of the rules first.

 

Whitelist-Include.PNG

 

Another part of this feature, that comes pre-configured with the installation, is the list of ignored MAC addresses. It includes both HSRP and VRRP ranges.

 

Whitelist-Ignore.PNG

 

When is an Endpoint 'Safe'?

An endpoint is considered safe (i.e. not marked as rogue) when its hostname, IP address, and MAC address are all on the white list. In other words, if e.g. the MAC address in on the white list but the hostname not, an alert will be generated.

 

I Only Want to White List MAC Addresses

If you don't care about hostnames and IP addresses, simply leave the default rules 'Any hostname' and 'Any IP address' active and disable/delete the 'Any MAC address' rule. Then create your own rules for MAC address.

 

Can I Create a Black List?

No. The current logic considers rogue every endpoint not on the white list. If you are interested in the other approach (everything is safe and only listed devices are rogue), please vote here: http://thwack.solarwinds.com/ideas/1367.

 

I Would Like UDT to Automatically Shut Down the Port Where a Rogue Endpoint is Connected

This is currently a feature request: http://thwack.solarwinds.com/ideas/2328.

It can be achieved via Orion SDK/API plus advanced alert manager, but this approach is not officially supported as functionality like this would have to be used with extra care -- for example, you probably don't want to shut down a trunk port.

 

How Do I Specify White List Items? How Do I List the Safe Devices?

On the 'Included' tab click on 'Add new':

 

UDT-WhiteList-Summary-Add-Item.png

 

and then you have several options:

 

Individual Entries

You can add individual MAC addresses, IP addresses, or hostnames:

 

UDT-WhiteList-Add-Individual.png

 

For one rule you can only add one type (e.g. MAC addresses).

 

IP Address and MAC Address Range

UDT-WhiteList-Add-IP-Range.png        UDT-WhiteList-Add-MAC-Range.png

 

Subnet

UDT-WhiteList-Add-Subnet.png

 

Custom Entries

The last option gives you very high flexibility. You can enter IP addresses, MAC addresses, or hostnames. Again, only one type per rule.

 

UDT-WhiteList-Add-Custom.png

 

How Do I Import My List of Safe Devices?

If you have e.g. a list of MAC addresses that represent safe devices on your network and want to add them to the white list. How do you do it?

  • If there is a pattern in the list, you can use the MAC Range or Custom entry with wildcards.
  • If there is no pattern, then it's probably best to format the list as a plain text file and copy-paste the content to the Custom entry field.

 

This blog post will be updated regularly based on the question we receive. If you have a question that is not answered here, please let us know.

You can find the installation packages in your customer portal.


This service release delivers the following fixes:

  • Fixed multiple SSID issues.
  • Fixed an issue where user information was not being displayed.
  • Fixed issues with database maintenance not completing.
  • Fixed issue where "All Network Connections" resource would not load until clicking the refresh icon.
  • Fixed issue where Wireless resources popup shows invalid data.
  • Fixed issue with false MAC address alerts.
  • Fixed issue with alerts not triggering for new MAC addresses after upgrading UDT.
  • Fixed SSID association issue with Cisco wireless devices.


More details can be found here.

Now that we have released Network Configuration Manager v7.2 (NCM), it is a good time to take a look at one of its most awaited features: End-of-Life / End-of-Support (EoL/EoS) information management. The purpose of this post is to set expectations on what this feature is/isn't and to provide a few tips for using it in the most efficient way.

 

As I outlined in my previous posts on this topic,

you may try to solve the EoL/EoS problem in different ways ranging from a do-it-yourself, spreadsheet-based approach (cheapest but most difficult) to an automated third-party service (fastest but most expensive and may require access to vendor-specific service APIs like e.g. Cisco CDS opened only to Cisco partners).

 

This new NCM feature, which we have just delivered, enables you to manage the EoL/EoS dates in a much more convenient way than a spreadsheet, because it is connected with other information about the devices that NCM stores.

 

How is This Feature Going to Help?

  • We provide suggestions for Cisco and Juniper devices out of the box. (For other vendors, you can enter your own information.)
  • You do not have to track the end-of-life information in a spreadsheet.
  • You can group, sort, and filter your devices according to node details and custom properties.
  • Once end-of-life data is entered, you can generate a highly customized report. (See the second blog post.)

 

What is the EoL/EoS Feature NOT?

  • A fully automated solution that will report all the end-of-life information automatically.
  • A complete multi-vendor database of different devices and extension cards. Today, this NCM feature handles devices only; not cards and modules, yet.

 

Typical Workflow

  1. Notice the "End of Support" view under the Configs tab. (Note that this feature is only available in the Web console and not in the Win32 client.)
  2. Select the devices you want to define end-of-life information for.
    You can do it in many different ways using e.g. the Group By drop-down box on the left side and/or filtering on column values in the main group. Most probably you will want to define the same EoL/EoS information for a group of devices of the same properties -- e.g. machine type, firmware version etc. You can see the applied filter(s) in the top left corner.

    NCM EOL Summary Page
  3. Select the resulting devices and click on "Assign Dates".

    NCM EOL Summary Assign Dates
  4. Inspect the suggestions and either
    • select one of the suggested pieces of EoL information,
      (We provide external links to vendor pages that help you choose the correct item. You can also enter a comment that will be displayed in the resulting report.)

      NCM EOL Assign Page
    • or, if our database does not provide any suggestions, enter your own data.
      (In addition to the dates and comments, it is advisable to insert link to the source of the information.)

      NCM EOL Summary Assign Page Custom Dates
  5. Click on "Assign".
  6. If interested, create a report. You can filter the columns as you need and also export the result as spreadsheet.

    NCM EOL Report

Vendor Information

If our database does not provide suggestions to choose from, you can look up the end-of-life information yourself. An alternative to search engines are vendor pages. Here are a few of them:

 

We would also like to encourage you to post your EoL/EoS data item on thwack here: http://thwack.solarwinds.com/thread/58861.

Ideally in the following format:

Device Type, System description, end-of-sale date, end-of-support date, Vendor EOL statement URL

 

NCM 7.2 is now available for all customers on active maintenance in the customer portal.  Please check out EoL/EoS and let us know what you think.

 

As a bonus, you can watch this video about EoL/EoS:

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.