IPAM 4.6 Release Notes
Release date: December 4, 2017
These release notes describe the new features, improvements, and fixed issues in IP Address Manager 4.6. They also provide information about upgrades and describe workarounds for known issues.
IPAM 4.6 is an Orion Platform product and consumes Orion Platform 2017.3.
New features and improvements in IPAM
IPAM integration with VMware vRealize Orchestrator
IP Address Manager now integrates with VMware vRealize Orchestrator. Orchestrator is a workflow tool that automates tasks in a VMware vSphere infrastructure. You can run or script over a dozen different IPAM actions, such as: Add or remove a DNS "A" records for an IP address, Create or remove an IP address reservation on a DHCP server, Change IP node status, and so on.
IP Address Manager 4.6 is compatible with the following VMware products:
- vCenter Server 6.5
- vRealize Orchestrator 7.2
- vRealize Automation 7.2
Windows Server DHCP failover support
This version of IP Address Manager fully supports the DHCP failover feature set implemented in Windows Server 2012 R2 and Windows Server 2016. With IPAM you can configure failover across multiple scopes using a single screen, whereas in Windows Server you can only configure failover one scope at a time. Similarly, when viewing failover details for systems that were previously configured, IPAM consolidates cluster details into a single pop-up.
For details about DHCP failover options in Windows Server 2012 and later, see the Microsoft TechNet article entitled Understand and Deploy DHCP Failover at https://technet.microsoft.com/en-us/library/dn338978.aspx. (© 2017 Microsoft. Available at https://technet.microsoft.com. Obtained on October 10, 2017.)
Additional Polling Engine (APE) support
You can now install Additional Polling Engines to IPAM. If you have a large number of subnets, adding polling engines can reduce the time it takes to scan your network. Use the Orion Web Console to assign a polling engine to scan individual subnets. The DHCP server properties dialog now shows the name of the polling engine assigned to that server, and a status indicator shows if the polling engine is online and available.
Support for ISC DHCP 4.3 on RHEL 7.x
IP Address Manager now supports ISC DHCP version 4.3 on Red Hat Enterprise Linux (RHEL) version 7.x.
New API methods
See the IPAM 4.6 API documentation page on GitHub for additional documentation.
The following methods are new in the IPAM 4.6 API:
Creates a new IPv6 subnet. The subnet will be placed under the root folder in the IPAM group tree.
|AddDnsAaaaRecord||Adds a AAAA DNS record for the specified IPv6 address.|
Updates a AAAA DNS record for the specified IPv6 address.
|RemoveDnsAaaaRecord||Removes a AAAA DNS record for the specified IPv6 address.|
Changes the DisableAutoScanning flag for a specific Group Node.
New customer installation
For information about installing IPAM, see the IPAM Installation Guide. After installing, see the IPAM Getting Started Guide.
How to upgrade
If upgrading from a previous version, use the following resources to plan and implement your upgrade:
- Use the Product Upgrade Advisor to determine your upgrade path. Based on your current environment and versions, the Product Upgrade Advisor provides an ordered list of how to proceed with the upgrade.
- If you are upgrading:
- When you are ready, download the upgrade package from the SolarWinds Customer Portal.
IPAM 4.6 fixes the following issues.
|n/a||You can use the Create operation for IPAM.IPNode in the IPAM 4.6 API. Previously, the IPAM 4.5 API had a bug that made the Create operation for IPAM.IPNode unusable.|
Issue: Main Functionality of IPAM is broken in Japanese local under IE11
Work-around: No current work-around.
Issue: Duplicated records in SWQL query from IPAM.Subnet entity
Work-around: Change the query from SELECT to SELECT DISTINCT. For the failed queries, try adding "ORDER BY 1" to the end of the query.
© 2017 SolarWinds Worldwide, LLC. All rights reserved.
This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software and documentation are and shall remain the exclusive property of SolarWinds and its respective licensors.
SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
The SolarWinds and other SolarWinds marks, identified on the SolarWinds website, as updated from SolarWinds from time to time and incorporated herein, are registered with the U.S. Patent and Trademark Office and may be registered or pending registration in other countries. All other SolarWinds trademarks may be common law marks or registered or pending registration in the United States or in other countries. All other trademarks or registered trademarks contained and/or mentioned herein are used for identification purposes only and may be trademarks or registered trademarks of their respective companies.