cobrien1

The release notes bundled into the RC download unfortunately only point to the release notes on our website, which do not include 11.5.3 yet since it is not yet available to all customers. Here's the notes though: SolarWinds NPM 11.5.3 includes the following fixes: IssueCase NumberInterfaces: If database maintenance starts…

I'd also suggest looking at the interface in NPM and confirming NPM has correctly discovered the interface bandwidth is 1000mbps.

In addition to what has already been stated, more specifics can be found in the Netpath Requirements -> Probe Computer section on page 188 of the NPM Admin Guide: https://support.solarwinds.com/@api/deki/files/10232/NPM_Administrator_Guide.pdf/..

Thanks for the feedback, Ken. I will certainly take your points as they stand, as a plea for a higher ratio of improving on old content vs creating new. Meanwhile, I can shed some light on our thinking in this area and how things may not always be what they seem. It really comes down to two things. First, new and shiny…

Do you have your ticket number for this? I'd like to look into it as well.

If you're seeing your router as the source, it sounds like you're exporting flow traffic post-NAT, for example on the outside interface of a border router rather than the inside interface. If you export from both interfaces, you can inspect the inside interface's flow to see pre-NAT packet data which will give you the…

I left this thread alone for a few days since you were specifically requesting the assistance of the community. Regardless of who is at fault, it is SolarWinds responsibility to help you monitor your gear. Our latest beta has made some improvements to hardware health monitoring specifically so that you can work out…

Added to featured content. Quick survey to make the ASA feature better!

I thought that thin APs going down could only be determined by polling the controller and noticing that the APs are no longer mentioned. Are the thin APs showing as "down" or "unknown"?

I haven't seen that before. lanli.fsm​, have you?

What type of devices are these?

I’m not sure. We’re you on an eval license prior to upgrade. This looks fairly urgent so I’d suggest calling in to us so we can troubleshoot: SolarWinds Contact Us

Got it. Thanks!

NTA's beta is also out!: NTA 4.5 Beta 1 Available

Thanks for all of the responses so far. This has been extremely helpful for the team.

Thanks so much for all the uploads so far. The Dev team is devouring them. So far it appears we have not received any uploads for a Nexus running multiple VDCs. If you have one, we'd love the upload. If you already uploaded a device that has multiple VDCs, please let me know and we will dig deeper as to why we're not…

Thanks for the emailed screenshots so far. Today is the last day for submission. Please submit any screenshots you intend to for your thwack points!

Also, I'm curious what you use RFID tracking for? Trying to understand what you accomplish with it in your specific environment. Have you thought about using active RFIDs?

We don't presently provide an interface specific to RFID tracking. If the device exposes the information via UNDP you may be able to get the data you want in Orion, but you could not, currently, show in on a map or anything of that nature.

We have fixed a couple of memory leaks since 12.0. The best bet is to install the latest Service Release and Hot Fixes. If the issue continues, it's time to open a Support case and we'll dig in with you.

Is Orion seeing all of the clients attached to the APs in the Network -> Wireless section? I'm not aware of a well known issue that causes this problem, so it may be best to open a support ticket and dig in. I'd be happy to track the case if you can shoot me the number.

This fix has been incorporated into NPM 12.4.

${CurrentValue} and ${Status} can be used. What others would you like to use, and how do you envision using them?

I'd like to look into this some more from our side. Could you PM me your case # or SWID? I can't seem to find your case.

The traditional reply is to find the SysOID and add it here: Tell us your "Unknown" devices! The future is coming soon though! NPMv12 beta has the capability to setup your own polling of node details such as Vendor. If you're interested, you can check it out here: NPM 12.0 Beta1 Now Available

L2 connections are discovered physical connections. L3 connections are logical connections and they may or may not, in some cases, duplicate physical connections. Very similar to how you would have an L2 and L3 map, but if you laid them on top of each other there would be duplicate lines.

Have any of you guys opened tickets on these issues and come to a conclusion? I'd be very interested to hear where these went.

Hi Alex, NPM does indeed use CDP as well as MAC address tables, ARP tables, and a bunch of other stuff to discover and calculate topology. The following things help make it more accurate: * Add all of the involved network devices to NPM. * Make sure topology polling is enabled on each node (list resources tells you). *…

What status did NPM show the interface in when it "did not recover"? That's the key to figuring out why there wasn't an alert. There is a never ending list of metrics and indicators of unhealthy you could look for in infrastructure. At some point it makes sense to test the transit traffic and use that as your catch all for…

After investigating some SNMP Walks, we've found out that this Motorolla controller behaves quite differently from most other wireless controllers. It keeps track of the APs and associated wireless information differently. As a result, it's much more difficult to support. We'd still like to support these devices, but given…