I understand the concept of "Reserved" in IPAM, but I would also like to be able to designate certain IP ranges for certain intended uses.
For example, if I add a subnet without adding the IP addresses at the same time, I can then add ranges of addresses under that subnet. I would like to be able designate a range for a certain use, e.g. for routers or switches or printers. Se what I mean?
In other words, how can I designate certain IP ranges as set aside for defined uses without designating them as Reserved in the IPAM sense of the word?
Solved! Go to Solution.
I believe what you ultimately are looking for is a subnet template which would allow you to set a standard subnet definition when you add a new subnet, correct? You cannot do this in IPAM today, however, what you can do as an alternative is you can define and set custom fields at the IP level and then set that custom field to be the intended use or target, for example printers or server etc.
Template, yes! This proposed solution is rather inelegant (or even unworkable) for a number of reasons. Including the challenge in making multiple changes ... export/bulk import is a work-around to mass changes but we really need the ability to select groups of devices and be able to mult-edit shared/common fields, such as a custom field.
But the custom field also cannot be set for IPs that are "Available" so this doesn't really work as a mechanism to define a "name range" or template within a subnet/vlan. These IPs could be marked as "Reserved" but that isn't really a clear indication either, because what we really mean here is more like "Available but Restricted".
So, please consider this a feature request, the ability to define a subnet "template" or otherwise identify named usage of ranges within a subnet. Using the "IP Range" function for example would be nice if it included the option to "name" the range and subsequently group the IPs within the range visually.
Understood that is was not ideal, was just trying to be creative with existing functionality you have today in the product. The template or policy is already an idea/enhancement I have in the system, I will append ya'll to this request.
Another idea just thinking more is since you can duplicate a subnet within the system and can choose which IP's show up within a subnet defintion, you could use the folders/category as your "template" and have a folder for printers and one for servers etc. and under each category have a subnet defined with just those IP's which belong to that template. Hope that makes sense.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.