donrobert5 · Implementation Engineer · ✭✭✭✭✭

Check if any of the OIDs are present via SNMPwalk. https://support.solarwinds.com/SuccessCenter/s/article/Hardware-health-OIDS?language=en_US support.solarwinds.com/.../Run-SolarWinds-SNMPWALK

Submit a feature request and post it here so that other people can vote and it will be noticed by the PMs. support.solarwinds.com/.../Submit-a-feature-request

Try going to SA license manager page. On the right side, you'll see products.

Try going to SA license manager page. On the right side, you'll see products

Exactly

Based on the error, it seems you have created a view limitation either on your account or on the view itself that restricts you from viewing the wireless heatmap. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-configuring-view-limitations-sw791.htm…

navigate to Settings > All Settings > UDT Settings >> Manage Ports. From there you would see all nodes that are added in UDT/Enabled Layer 2 and layer 3 Polling for UDT.

Settings >> All settings >> UDT settings >> Monitored Port Types

It's on the edit node page. https://support.solarwinds.com/SuccessCenter/s/article/Verify-Layer-3-polling-in-UDT?language=en_US Try going to manage nodes, click checkboxes for multiple nodes and then click on edit property. Then enable/disable the UDT Layer 3 Polling.

I do not have a solarwinds environment as of the moment, but can you try this one? thwack.solarwinds.com/.../2150

I don't know how to use it either, but you can check the videos below. https://www.youtube.com/watch?v=wBEuc0k6xns www.youtube.com/watch

Do you mean you don't intend to add the AP as a node? Because that is the norm. You really do not have to add the AP as a node unless you want to add it as a node via ICMP. You monitor APs by monitoring the WLC. If it's Meraki, check the link below. documentation.solarwinds.com/.../npm-monitor-meraki-devices.htm

as mentioned, I currently do not have a solarwinds Environment. It seems to me that Orion.UDT.Custom.UnunsedPorts cannot be found. Since the post have been posted 7 years ago, it might no longer exists on the current iteration.

Is this still about installation or a completely different issue? I haven't encounter this error before. As much as I would like to help you, I no longer have a Solarwinds environment.

This has been a known issue for over a year ago. This started with the supply chain attack where SW ask to take the servers offline and use offline installer. This was the result. Pretty much the article resolves that.

https://support.solarwinds.com/SuccessCenter/s/article/Thin-Access-Point-Alert?language=en_US https://support.solarwinds.com/SuccessCenter/s/article/Thin-AP-down-Alert?language=en_US https://support.solarwinds.com/SuccessCenter/s/article/Thin-Access-points-status?language=en_US…

UDT does not really care about the IP status of a device. You can use IPAM and then utilize Neighbor Scanning or Integrate your DHCP server into IPAM so it would scan the leases as well. Have you considered using Netpath instead? It's not really monitoring UP or down, but at least you can check if you are reaching the…

That would depend as I'm not really sure what you choose to put in on the report resources. Try searching on the report UpTime or availability. I'm pretty sure there is an out of the box report. It would be better to find that and then duplicate and edit and start from there.

I hope so. But I think they will have you upgrade to the latest version. documentation.solarwinds.com/.../solarwinds_platform_2022-2_release_notes.htm

That's all I got. Good job in finding that article, If I was on your position, I would document everything and submit this to support. It's most likely an issue within the environment as it is only happening to one server. As Bshopp suggest, creating a ticket would be the best route as of this time.

This one would work, but be mindful that Hostname is one of the default information that IPAM gathers and every time you run the subnet scan(or enabled the auto scan), it will just put in the result of the scan. If it is not resolving to any, it would be back to NULL.…

did you find the scan job progress page?

support.solarwinds.com/.../How-hostname-resolution-works-in-IPAM

Remove the old DHCP server from IPAM and re add the new ones. Just make sure you don't delete the scopes when the warning pops out. I get that they no longer exists, but just to save you of any trouble that it might cause.

https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-creating-new-accounts-sw1310.htm#Creating

there are multiple ways to do this. The one I tried and tested is the one below. https://support.solarwinds.com/SuccessCenter/s/article/MAC-address-does-not-show-the-icon-or-vendor?language=en_US You can also try the two articles below.…

re install the service again by running it via Command prompt admin.

UDT_Endpoint and UDT_EndpointIP.

thwack.solarwinds.com/.../feature-request---mute-alerts-shedule-daily-weekly-monthly-at-specific-time

This are mostly gathered via SNMP so if you changed it somehow, it will just be polled the next polling cycle. https://support.solarwinds.com/SuccessCenter/s/article/List-of-NPM-NTA-VNQM-MIBs-and-OIDs-used-for-Polling?language=en_US Most probably, there would be a Macro that can show you those information and put it on the…