bshopp

Yes, this is something we are looking at for a future release of the product.

So two options #1 with 10.0 we have scheduled discovery, so as long as we were scanning that subnet, we would have picked up a new IP being used and you could investigate it and determine it was rogue #2 - Both Cisco and Aruba controllers have rogue detection, here is a doc from Cisco on this here. On the online demo here,…

Correct it does limit to 4GB, but to allow you to eval. you could use Express

OK well let me know if you hear any more info

Apologies, I will review and catch up on some posts, but if you have a specific item or question please let me know.

So, when looking at the Advanced Alerts in the web interface with NPM 10.1 - the parts that are listed as read-only would require access to the server? Yes this is correct Is there or will there be a way to limit the type of items that a user would be able to create/edit alerts upon? Not currently, right now it is all or…

If you edit the following file with these values, the product update notification should use the proxy settings. C:\Program Files (x86)\SolarWinds\Orion\SolarWinds.Orion.Core.BusinessLayer.dll.config <add key="proxyAvailable" value="false" /> <add key="userName" value="" /> <add key="password" value="" /> <add…

Can you both tell me what versions and SP you are currently on?

So we made some performance improvements for maps and network atlas in 10.0, are you interested in installing the 10.0 RC? If yes, send me a private message with your SWID

This can be due to multiple reasons, please open a support ticket

This should work without needing to reinstall, check the following: 1) That you have a “Log to Web Access” action (and it’s enabled). And, 2) Assuming that you are still in eval mode, I’d suggest stop and restart the Kiwi Syslog Server Service. We have a bug where re-starting the service picks up the changes

This is something we have on our list that we are looking deeper at. However, from a product stand point it is sometimes easier said than done due to legal etc. with using Google API in a commercial product

Thanks for the info, I will check into this with Support and the team here. As I mentioned I had not heard of similar experiences from other customers, so hopefully this is more of just an anomaly than a trend, but I will keep an eye on this thread to see if other users post and report similar issues.

Are you interface indexes re-indexing a lot? This could potentially cause this issue. For some Cisco devices you can lock this - http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080134eec.shtml

9.5.1 the maps are stored on the file system. You should be able to copy that folder/directory and that is your backup. In newer versions the maps are in the database, starting with 10.0 I believe.

Another idea is to unmanage the applicable nodes/interfaces

On the nodes that show as up and green, are you getting stats like CPU and Memory? Are you sure SNMP is not being blocked since these are new sites?

If it's grayed out, you will have to do it from the web

Nothing I can give you a firm commitment to at this time. We are keeping an eye on this for sure

Makes sense, we have that already on our list as a work item for a future release

Check out this blog post on this topic here

Customer portal is here. Once you login with your SWID you would see the link on the left.

So not today, but this is something we have on the list for the future of IPAM. Have you looked at our LANsurveyor product? With that product it has a port mapping report which should do what you want.

Are you showing all hidden files and folders? If you search for it can you find that file?

What version of toolset are you running?

This should still work, I just tested against a 9.1 SP4 install with toolset 10 install on my laptop. Where are you looking for the file? On my laptop it is located at C:\Program Files\SolarWinds\Common

Right now the workaround to edit all those IP's is to export the subnet, edit all the IP's you want to edit it and then re-import

#2 - ah perfect, got it, internally we have been calling that indirect discovery #4 - so if we could pull DHCP directly from Cisco devices, then NCM would not need to be apart of the equation then. I am looking into getting you more data on 1 and 3

Open a ticket and submit the diagnostics so we can take a look at the logs and see what is going on

You can take the default report, say last 30 days, edit it to say last 90 or 180 days and save it as a new report. Then your manager has access to the same report for last 30, 90 and 180 days without the need of intervention by you