Comments
-
so it is essentially a problem with the SNMP instead of the IPmonitor, correct?
-
Someone created the same question before but the resolution was to create an alert based on Endpoint count and then use Whitelisting. thwack.solarwinds.com/.../udt---multiple-mac-per-port
-
same with sum_giais. You can try to click on reset to default.
-
Ok. It seems what you are looking at is SNMP neighbor vs. SNMP neighbor. That is actually not listed on the IP Address conflict scenario. My take here is that the IPs are getting conflicts but since you are only getting it from one source which is SNMP neighbor, it is not being detected. You might want to send this over to…
-
that means the polling is not being able to catch the MAC address change. When the polling happens, the arp table should catch both of them having the same IP. What happens when you actually check the IP Address Details? It is only listing one MAC? did you check the MAC address History of the said IP? Is it showing both…
-
On what you are describing, the ARP table simply switches MAC address and does not really show both value at the same time, is that correct?
-
By default, UDT supports Kerberos authentication scheme only. Authentication Operating System Event Code Kerberos Windows 2003 672 and 673 NTLM Windows 2003 680 Kerberos Windows 2008 and later 4768 and 4769 NTLM Windows 2008 4776 I don't think it logs the log off.…
-
Follow planglois. also, if it is erroring out on the configuration wizard, check the logs. * Check your logs. c:\ProgramData\SolarWinds\Logs\ Orion\ConfigurationWizard.log Try attaching it on this thread.
-
Kindly check Rocco's post. However, you have a version from way back. NPM 11.5 is 2014 or 2015. I'm pretty sure you can't simply upgrade it to the newest versions. This would require skill.
-
Is the time on your browser the same time on the device?
-
Good Question. However, you need to understand that the Modern dashboards was initially designed for a quick look of information. If you would need to have some sort of a drill down and in depth look, you will be better off with the Summary Page.
-
Most probably they would be checking the SWIS logs and check the NULL value on the DB.
-
If it's working from the Server itself, that means you are having issues communicating from the the remote system. You might want to review the link above.
-
You might also want to check the link below for that error. support.solarwinds.com/.../Invalid-input-detected-at-marker
-
Most probably, you will have to enable session trace and then replicate the job post processing issue and check the Session trace logs. support.solarwinds.com/.../Generate-session-trace-logs
-
thwack.solarwinds.com/.../solarwinds-information-service---enable-for-external-api-access
-
KMSigma just replied to your query, but I don't think you need to create SWQL/SQL query for this. It seems you can simply do a straight up web report for this. Something like the one below. thwack.solarwinds.com/.../interface-count-on-each-node
-
Tell them it is a core bug. JIRA Case: CORE-15843 Then refer them to this thwack link. Even though it is outside the Normal support as it is Orion SDK/API, they should have basic knowledge on what are the known bug within the product. thwack.solarwinds.com/.../swis-swql-studio-api---windows-group-authentication-issue
-
careerkarma.com/.../
-
I'm thinking perfstack but those processes are not yet included. thwack.solarwinds.com/.../perfstack-2-0---real-time-polling
-
You might want to create a feature request.
-
looks like it should be filed as a feature request
-
Endpoints are group with IP, DNS and MAC. If you only created a whitelist for DNS, but the endpoint is detected on the MAC address level, it will still be rogue device. The most basic information that UDT gathers is the MAC address, it would be best to create whitelist using the MAC addresses.
-
You can group the UDT endpoints with IP Address, MAC and DNS. The Device Tracker Summary looks at all three, together with the User, node and Port. As for the Inventory Pages, it groups it between Device Endpoints and Users. It does not include Node and Port.
-
documentation.solarwinds.com/.../ipam-ip-address-conflicts.htm
-
support.solarwinds.com/.../Importing-an-IPAM-spreadsheet-getting-COMMAND-FAILED-An-item-with-the-same-key-has-already-been-added
-
Based on the screenshot, the IP Address you imported are orphaned IPs. It does not know where to put the said IP Addresses.
-
what you are doing make sense as I encounter the same with other tools for Solarwinds(namely the addip tool for IPAM). They always ask to use the Native Orion Accounts instead of windows account. However, for that error, that is as clear as it gets, you need to input the correct username and password. Try to follow…
-
if the error is a straight up unknown password, then it is what it is, You can follow superfly's suggestion. If there's a legit error, it would be great if you can share it.
-
Do you get any error messages?