cvachovecj

Hi, the feaure request has been tracked here: . Regards, Jiri

Hi, There's feature request for AD authentication. You can vote here: http://thwack.solarwinds.com/ideas/1029 Regards, Jiri

Yes, it's a major feature request. We know that very well, but it's really big, so it's not easy to put it into a release. Regards, Jiri

Hi, You are correct. UDT is currently not able to poll information from Cisco ASA. These device don't expose the required information via SNMP. The only possibiliy is to establish a terminal session, issue needed command and parse the output. This is a feature request: http://thwack.solarwinds.com/ideas/2688 Regards, Jiri

Now this thread will help.

Answered here: . Jiri

Hi, No, KSS only supports IPv4. The feature request for IPv6 can be found here: http://thwack.solarwinds.com/ideas/1258 Regards, Jiri

Or upgrade to a newer version of NCM and get the config archaive maintenance job by default: I don't remember in wich version exactly we added this job, but I think it would be 7.2. Please also note that NCM 7.0.2 and older is not going to be supported anymore from September 2015. See Currently Supported Software Versions.…

I agree with mkomeara. NCM gives you a lot of possibilities what to do with the configs -- I suggest exploring the scripting functionality. Regards, Jiri

Two independent answers and we seem to agree. That's good :-). J.

Have you updated the inventory?

Correct. However, you might be interested in Nutanix is Now Validated for SolarWinds . Jiri

John, What you could do is upload the template to content exchange (if not already there) and attach description of the problem with root vs. regular user. I don't want to take the credit here. Regards, Jiri

Just don't forget to disable the session tracing once you collect it. It affects performance and consumes disk space. Regards, Jiri

Let's ask peter.ksenzsigh‌, the current PM for UDT.

Hi Ellen, You need to run switchport when configuring certain interface/port. You can find more details here: http://knowledgebase.solarwinds.com/kb/questions/3245/Cisco+Nexus+Switch+NX-OS+%28Network+Operating+System%29+Support As I replied below, we have now a support case for Nexus that will hopefully result in us better…

Hi, I appreciate your offer very much. Just before I finished writing email to you to discuss the details, a new support case had arrived. The customer has many different Nexus'es, some of them work, some not. The team must now concentrate on helping this customer and then we can compare what we find with you. Could you…

Thanks a lot. Email sent. Jiri

Thanks.

Hi, We can't confirm any timeframes but as you can see, there are many different extensions possible -- not all can be implemented soon. You can also vote here: http://thwack.solarwinds.com/ideas/1080 Regards, Jiri

Wow, that's impressive! We are always looking for developers, don't you want to join SWI? Jiri

Hi, What you need to do is install NCM 7.2.2 on the NPM server and point it to your existing 7.1.1 DB. Then upgrade to 7.3. Regards, Jiri

More inspiration can be found in this thread.

ttl, Our dev team know about this issue -- req. #13018 -- and it's under investigation. Regards, Jiri

If the device doesn't work with NCM out of the box, I would look for a device template in Network Configuration Manager. (You can import the template directly from NCM 7.4 UI.) Jiri

Correct -- IPAM can inly poll information from the main poller. Jiri

Hi, The new IP Address Tracker really is free. You have the option to upgrade to the full paid IPAM, but if you don't, the tool never expires. Jiri

Hi, Just to make sure -- have you created custom config types for all the contexts? Jiri

Hi Wayne Barry, Your hypotheses are mostly correct. Let me add some details. NCM handles the storage of downloaded configs automatically. You don't have to worry about that. Create a new config type, download the config and you'll see the exact structure yourself. You should look at the device template not as a script but…

You have to use the command for switching the context for your particular device. If the device command (like for ASA) is changeto context mycontext1 then the Reset command should read <Command Name="RESET" Value="terminal width 0${CRLF}changeto context ${ConfigType}"/> and you have to create new config type "mycontext1".…