Please bring me the following in IPAM v1.1
PS - If any of Santa's elves can answer to these points now, thanks for that
The scanning interval GUI is horrendus. Get rid of the touchy slider and let us just type in the times we want to scan. Also, give some flexibility. Maybe I dont want my scopes scanned on Thursdays. Who knows. But the slider should go.
Why, everytime I make any change to an IP, after the change loads, I am directed back to page one of my range? This is frustrating. After I endit an IP on page 5 of my range, I would like to stay on page 5. Not go back to 1.
IP Range -
Adding an IP range works perfect. Deleting an IP range is torture. Unless I am missing something, to delete an IP range, you have to manually select the IPs in the range. Why cant the delete work jsut as the add works. Just type in my starting and ending IPs, and choose whether to delete or add.
PLease fix the multiselect option. Right now, I have to click in the ROW, hold down shift, then click in another ROW to select all rows in between. What are the checkboxes for? The multiselect does not work when using the checkboxes. weird.
Thats all I can think of off the top of my head.
I have a pretty simple request (I think).
I prefer to use the subnet address for the Display Name of the subnet, so that I can quickly scan all the subnets in the left pane and find the one I am looking for.
The problem is that IPAM does not list the IP subnets in the correct order in the left-pane. For example, a /24 subnetted into /29's should look like this:
IPAM lists it like this:
As you can see, the subnets get jumbled up.
Also, by default, the right-pane orders the subnets in the same way. However, you can click on the Address column and it will re-order the subnets correctly. It would be nice to have a way to define the default ordering method/column for both the right and left-pane.
Just getting started, will be back with more!
I said I'd be back, but didnt think this quickly:
When adding a new subnet, by default, IPAM marks the First address and last address as Subnet Address and Broadcast Address respectively (as it should). However, only the Broadcast Address is marked as "Reserved". The Subnet Address should be "Reserved" as well.
IP type from dynamic to static user managed
Terrific feedback and for sure noted.
I can say # 8 is high on my hit list for the next release and other items listed above we already had on the list. I would like try pry into a couple of these items further.
Traps - what are you thinking here, just filtered intergration with the Orion Trap view?
Reporting on contrainer groups - I assume you mean categories? Do you have something specific in mind you would like to report on?
Keep the feedback coming!!
Traps is the wrong word,
I'd like the ability to generate a filterable event within Solarwinds Alert Manager. When a scope reaches a certain threshold, a scripted event of some sort would then take place. That would lend itself well to work flows as an admin receives an email regarding DHCP scope and modifies excluded/reserved IP's based on usage to relieve the pressure.
Reporting on container groups - group being the key word. So my IP "tree" has the master high level group, with child groups for each region of the world, DMZ's, CIDR's, Public IP, Management networks, wireless networks, available networks, transport networks, and loopbacks within it.
Having the ability to pick a group from my tree and generate a report on it (any available report) would be swell.
And yes, for what SWis asking for this product, you can bet I'll be keeping the feedback coming.
Again, the ability to subnet a given network and have it remain in it's parent group without having to create individual networks separately would be really handy. You could add a tag under status for those IP's lost to subnetting when the parent IP is carved up.
I'd like to add that the user integration should allow specific users to be assigned to specific groups and that they can assign IP addresses in those groups but not be able to edit outside of those groups.
Hi Brandon and others,
Am running the IPX-version of IPAM, and have some questions / wishes / comments as well. My list is absolutely not complete, but here are my current entries:
I would like to see an option to turn off color coding of a subnet's status on a subnet-by-subnet basis. In the current release, if you have a small subnet used for a WAN link which only has 4 addresses, it is marked in red as dangerously full. Since there is no need for any other devices to be added, having it be red just makes it difficult to see the real problems--especially if you have many of these subnets.
Maybe a check box to turn off the color coding for that subnet and allow the color to be white or pale gray?
I agree, or add a value field that doesn't count against availability metrics.
I have many 30 transport networks scattered across my network.
Peter Cooper (of SW) was kind enough to walk me through the custom field entry from the subnet property page.
We created a field called "Purpose" (which I then populated), and applied a filter to the top XX report that excluded any subnet with pupose field applied.
It has removed the 30 bit networks from my top XX reports.
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.